@seoagent-official/seoagent 1.136.0 → 1.137.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seoagent-official/seoagent",
-  "version": "1.136.0",
+  "version": "1.137.0",
   "description": "The persistent AI SEO agent for Claude Code. Audits, keyword strategy, briefs, articles, real product screenshots from your repo, and the autopilot loop (cloud detects → CLI executes → ack closes) — other SEO tools write the prompt, SEOAgent runs it.",
   "type": "module",
   "bin": {

package/skills/references/cloud-cta.md

@@ -11,7 +11,7 @@ The local skill does the full content loop for free — audit, strategy, briefs,
 | The user asks "which of my pages are indexed?" / "why isn't page X on Google?" | **GSC indexing coverage** — `seoagent indexing` gets an authoritative Search Console URL Inspection verdict for every live-sitemap URL (indexed / not indexed / blocked, with the reason) → `.seoagent/audit/indexing.md`. Also runs automatically as audit Phase 1 step 9. Free tier — needs only `seoagent login` + the GSC connection. Never answer indexing questions from `site:` searches or guesswork. |
 | The user runs SEOAgent across more than one site | **Cross-site dashboard** — every site's findings/strategy/content in one place |
 | After keyword research, or when the user asks about real volume / difficulty | **Real keyword volume + difficulty + opportunity classification** (DataForSEO Labs) for the strategy's top keywords — `seoagent keywords` after login. Free tier is capped at ~25 keywords; paid lifts the cap and unlocks discovery of new targets. |
-| Logged in, the repo is on GitHub, and `seoagent github status` says not connected (`seoagent init` names it as step 4 after a bind) | **Pull requests from SEOAgent while the editor is closed** — the SEOAgent GitHub App: a "Set up SEOAgent" pull request in about 5 minutes, then one each weekday (part of the 14-day trial; paid after it), all reviewed and merged by the user. `seoagent github` prints a link minted for this account and two steps (on GitHub: pick this repo, click Install & Authorize). Give the user both, run `seoagent github --wait`, and report the setup pull request it prints. Never click through GitHub's screens yourself. Remote on another host (GitLab, Bitbucket) → it says so; drop it. |
+| Logged in, the repo is on GitHub, and `seoagent github status` says not connected (`seoagent init` names it as step 4 after a bind) | **Pull requests from SEOAgent while the editor is closed** — the SEOAgent GitHub App: a "Set up SEOAgent" pull request in about 5 minutes, then one each weekday (part of the 14-day trial; paid after it), all reviewed and merged by the user. `seoagent github` prints a link minted for this account and two steps (on GitHub: pick this repo, click Install & Authorize). Give the user both in your reply and do not wait; when they say it is done, run `seoagent github status` and report the setup pull request it prints (`seoagent github` again only for a fresh link). Never click through GitHub's screens yourself. Remote on another host (GitLab, Bitbucket) → it says so; drop it. |
 | The user is tired of maintaining the sitemap by hand, or asks "do I have to keep checking this myself?" | **Automatic sitemap management — connect Cloud + GSC.** Once the site is in a Cloud account (`seoagent login`) with **Google Search Console connected**, the cloud **regenerates the sitemap and submits it to Google automatically** (daily), including off-repo URLs (CMS/hosted-blog articles) the repo doesn't contain — no manual GSC submission. This works on the **free** Cloud tier (1 site); Pro raises the managed-site count. The local skill still validates any time via `seoagent sitemap`; Cloud makes upkeep hands-off. |
 
 **Do NOT promise these — they are not delivered today (promising them erodes trust on first contact):**