seo 0.13.2 → 0.13.3

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
@@ -13,7 +13,7 @@ keeps your Search Console or analytics data, your reports or a log of your
13
13
  requests. When you first sign up it also notes how you found it: the
14
14
  sign-in path, the agent or app, and the site that sent you there. The only
15
15
  thing kept about your use is an anonymous usage count (the event, report,
16
- agent, version and week). Accounts in the weekly site audit beta also have
16
+ agent, version and week). Accounts with the weekly site audit also have
17
17
  their audited sites' crawl results kept, as described below.
18
18
 
19
19
  The command-line tool runs on your machine. It does not create an SEO
@@ -68,6 +68,12 @@ Cloudflare D1 with only these things:
68
68
  used. A linked machine asks for short-lived Google and Bing tokens and your
69
69
  keys, and makes the Google and Bing requests itself. Nothing it fetches is
70
70
  sent back.
71
+ - **How much metered work the server did for you.** One number a day per
72
+ kind of work: the browser time and pages the weekly audit rendered with
73
+ JavaScript, the Google URL Inspection checks made for you, and how many
74
+ research calls you made with each provider. It holds no URLs, page
75
+ content or research results. It is kept to
76
+ see what the hosted features cost to run.
71
77
  - **Beta features turned on for you.** The name of each beta feature the
72
78
  maintainer turned on for your account, and when. Only the maintainer sets
73
79
  these; most accounts have none.
@@ -96,12 +102,16 @@ it. The token your MCP client keeps carries only your person id.
96
102
 
97
103
  The server keeps nothing else. It does not keep reports, Search Console
98
104
  or Google Analytics rows, lists of your sites, or the pages it checked.
99
- Request logs are turned off. The one exception is the weekly site audit
100
- beta, below, and only for the sites you add to it.
105
+ Request logs are turned off. The one exception is the weekly site audit,
106
+ below, and only for the sites you add to it.
101
107
 
102
- ### Weekly site audit (beta)
108
+ ### Weekly site audit
103
109
 
104
- The maintainer turns this beta on for chosen accounts; no one else has it.
110
+ The weekly site audit is a paid plan, and the maintainer also turns it on
111
+ for some beta accounts. If you pay for it, Stripe takes the payment and
112
+ keeps your card details; the server keeps only your Stripe customer,
113
+ subscription and open checkout ids, the subscription's status and how many sites you pay
114
+ for. Deleting your account cancels the subscription.
105
115
  For each Search Console property you add on the account page, the server
106
116
  crawls the site once a week, up to 5,000 pages, as `SEOSkillBot`, and
107
117
  follows the site's `robots.txt`. It keeps, per site:
@@ -109,7 +119,9 @@ follows the site's `robots.txt`. It keeps, per site:
109
119
  - the property name, when you added it and when the next crawl is due;
110
120
  - the latest crawl and the one before it: each page's URL, status,
111
121
  redirect target, title, description, first heading, canonical, robots
112
- settings, word count and the internal links on it with their link text;
122
+ settings, word count and the internal links on it with their link text,
123
+ and for pages rendered with JavaScript (below) the raw HTML's values where
124
+ rendering changed them;
113
125
  - the findings worked out from them (such as broken links or missing
114
126
  titles), with when each was first seen and resolved; resolved findings
115
127
  are removed after 90 days;
@@ -129,6 +141,15 @@ follows the site's `robots.txt`. It keeps, per site:
129
141
  adding as their own Search Console properties, with which of them you
130
142
  added from the account page.
131
143
 
144
+ Some sites build their titles, canonicals and links with JavaScript. To
145
+ read those, the crawl loads a few pages of each part of the site in
146
+ Cloudflare Browser Run, a browser Cloudflare runs for the server, and if
147
+ JavaScript changes what they show, it loads every HTML page of that part
148
+ there too. It also loads pages whose HTML looks built by JavaScript. The
149
+ server keeps which parts of the site need this for 28 days.
150
+ Browser Run fetches the page from the site as `SEOSkillBot` and returns
151
+ the page after its scripts run. The server asks it not to cache pages.
152
+
132
153
  If you click Create these in Search Console, Google asks you for
133
154
  permission to manage Search Console for that Google account. The server
134
155
  uses that permission once, to add the listed folders as properties and
@@ -166,7 +187,7 @@ Delete everything deletes it for every site.
166
187
  Sign in at [seoskill.dev/account](https://seoskill.dev/account) and choose
167
188
  **Delete everything**. It deletes your person id, linked accounts, keys,
168
189
  Clicky sites, linked machines, beta features, audited sites with their
169
- crawl data and how you signed up,
190
+ crawl data, your plan's Stripe ids (after cancelling it) and how you signed up,
170
191
  and revokes the Google sign-ins. Your agents will ask you to sign in again if
171
192
  you use the hosted server later. You can also revoke SEO Skill in your
172
193
  [Google Account connections](https://myaccount.google.com/connections), which