seo 0.11.0 → 0.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/PRIVACY.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Privacy policy
2
2
 
3
- Last updated: 20 October 2026
3
+ Last updated: 22 October 2026
4
4
 
5
5
  This policy covers the official `seo` command-line tool, library, MCP server,
6
6
  the hosted MCP server at seoskill.dev/mcp with its account page, and the
@@ -55,6 +55,9 @@ Cloudflare D1 with only these things:
55
55
  used. A linked machine asks for short-lived Google and Bing tokens and your
56
56
  keys, and makes the Google and Bing requests itself. Nothing it fetches is
57
57
  sent back.
58
+ - **Beta features turned on for you.** The name of each beta feature the
59
+ maintainer turned on for your account, and when. Only the maintainer sets
60
+ these; most accounts have none.
58
61
  - **How you signed up.** Written once, when your person id is created, and
59
62
  never changed:
60
63
  - the way you signed up: an MCP client, the account page, or `seo login`;
@@ -109,7 +112,7 @@ Request logs are turned off.
109
112
 
110
113
  Sign in at [seoskill.dev/account](https://seoskill.dev/account) and choose
111
114
  **Delete everything**. It deletes your person id, linked accounts, keys,
112
- Clicky sites, linked machines and how you signed up,
115
+ Clicky sites, linked machines, beta features and how you signed up,
113
116
  and revokes the Google sign-ins. Your agents will ask you to sign in again if
114
117
  you use the hosted server later. You can also revoke SEO Skill in your
115
118
  [Google Account connections](https://myaccount.google.com/connections), which
@@ -200,14 +203,17 @@ local token record.
200
203
 
201
204
  Google Analytics and Search Console API responses are cached locally so repeat
202
205
  commands do not make the same request unnecessarily. A cached response is
203
- eligible for reuse for up to 24 hours. Expired cache rows are removed during
206
+ eligible for reuse for up to 24 hours. URL Inspection results (Google's index
207
+ status for each URL, keyed by property and URL) are kept so `seo index` can
208
+ page through or repeat a result without asking Google again; each is reused
209
+ for up to 7 days. Expired cache rows are removed during
204
210
  automatic cache maintenance, which also removes cache rows older than 30 days
205
211
  and enforces local size limits. On a machine where the command is no longer
206
212
  run, expired rows may remain in the local cache file until you delete them.
207
213
 
208
214
  Run `seo cache clear --provider google-analytics` to remove cached Google
209
215
  Analytics responses immediately. Run `seo cache clear --provider gsc` to do
210
- the same for Search Console. Run `seo cache clear --provider clicky` to remove
216
+ the same for Search Console, including saved URL Inspection results. Run `seo cache clear --provider clicky` to remove
211
217
  cached Clicky responses. Settings and saved provider credentials remain until
212
218
  you delete them with the relevant command or run `seo reset --yes`. The reset
213
219
  command removes Google tokens, local configuration, caches, logs, any
@@ -331,9 +337,10 @@ contain the raw error or command arguments. Nothing is sent to GitHub unless
331
337
  you open the link, and you can review the form before submitting it.
332
338
 
333
339
  Aggregate event counts are public at
334
- [seoskill.dev/stats](https://seoskill.dev/stats). Failure counts are not
335
- shown there; the maintainer reads them privately to find and fix bugs,
336
- including a weekly Telegram message with failure totals by version. The
340
+ [seoskill.dev/stats](https://seoskill.dev/stats). Failure counts, setup
341
+ completions and retention are not shown there; the maintainer reads them
342
+ privately to find and fix problems, including a weekly Telegram message with
343
+ failure totals, first audit rates and retention by version. The
337
344
  public counts are described as installs, active machines, and audits, never
338
345
  users. One person can have several installs, and clearing local state creates
339
346
  a new install.
package/README.md CHANGED
@@ -145,7 +145,7 @@ ends with the command to run next, so your agent always knows where to go.
145
145
  | [`seo report`](https://seoskill.dev/docs/report) | Your Search Console overview, then the top rows of each section |
146
146
  | [`seo page`](https://seoskill.dev/docs/page) | One URL: the live page, its Google index status and its queries |
147
147
  | [`seo compare`](https://seoskill.dev/docs/compare) | Before and after a date, with Google updates |
148
- | [`seo index`](https://seoskill.dev/docs/indexing) | Pages that lost their clicks, checked live and with Google |
148
+ | [`seo index`](https://seoskill.dev/docs/indexing) | Google's indexing reasons for known URLs, labelled from live checks, and pages that lost their clicks |
149
149
  | [`seo research`](https://seoskill.dev/docs/research) | Keywords, search results, competitors and backlinks from your own key |
150
150
  | [`seo data`](https://seoskill.dev/docs/data) | Raw Search Console or Bing rows |
151
151
  | [`seo analytics`](https://seoskill.dev/docs/analytics) | Landing pages from Google Analytics or Clicky |