seo 0.2.10 → 0.2.13

package/README.md

@@ -77,7 +77,7 @@ technical report before connecting Google.
 Running `seo help` shows the shape of the tool:
 
 ```txt
-seo v0.2.10
+seo v0.2.13
 
 Run SEO audits, find what needs fixing, and ship the changes with your agent.
 
@@ -181,6 +181,106 @@ seo analytics google properties
 seo analytics google report --property 123456789 --dimensions landingPage --metrics sessions,totalUsers
 ```
 
+Bing Webmaster is optional. Connect it when you want Bing traffic trends,
+crawl changes, and query and page opportunities beside your Google evidence:
+
+```sh
+seo providers bing connect
+seo providers bing report --project example
+```
+
+The guided connection asks for the API key from Bing Webmaster Tools Settings,
+then API Access. It validates the key, lists verified sites, matches one to the
+selected project when the hostname is unambiguous, and stores the key in the
+system keychain with a private local file fallback. Agents and CI can set
+`SEO_BING_API_KEY` and run the report without saving the key.
+
+The report compares recent traffic periods, highlights material crawl changes,
+and returns bounded query and page review lists. Provider responses stay
+uncached and byte limited. Invalid, partial, capped, unavailable, and sampled
+evidence remain distinct. Bing's `inIndex` crawl statistic is provider
+evidence, not URL-level proof that a page is indexed. A query or page missing
+from a weekly top list is unknown, not zero.
+
+Use the same connection to review a bounded set of referring links, or import
+an export from another source:
+
+```sh
+seo links --project example --json
+seo links --file ./links.csv --row-limit 10000 --json
+```
+
+CSV and JSONL imports stream from disk. Regular JSON arrays have a smaller
+file limit to avoid a memory spike. Every result includes the number of rows
+read, rejected, deduplicated, omitted, or stopped by a limit. It is evidence
+from the selected source, not a complete backlink index or an authority score.
+
+## Create an HTML report for a client
+
+The built-in renderer creates a standalone report when you need a predictable
+file without asking an agent to design it:
+
+```sh
+seo report --project example --format html
+seo monthly-report --project example --format html
+seo report-narrative --project example --format html --view analyst
+```
+
+Client view keeps the presentation concise. Analyst view adds evidence coverage
+and unavailable sections. Use `--output ./report.html` to choose the file path.
+The file contains its own CSS, works offline, prints cleanly, and is marked
+`noindex,nofollow`.
+
+An agent can instead design its own report from the structured result:
+
+```sh
+seo report --project example --full --json > seo-report.json
+```
+
+Ask the agent to turn that evidence into one responsive, print-friendly HTML
+file for the intended audience. It can choose the layout and visual style, but
+it must keep provider labels, reporting dates, data status, limitations, and
+verification steps visible. Missing or partial data must not become zero, and
+the presentation must not invent forecasts, causes, scores, or conclusions.
+The installed skill teaches agents this contract automatically.
+
+## Analyze crawler traffic in server logs
+
+Stream a local NGINX or Apache-style combined access log without importing or
+retaining every raw request:
+
+```sh
+seo server-logs analyze --file ./access.log --json
+seo server-logs analyze --file ./access.jsonl --format jsonl --json
+```
+
+The report groups observed search and AI crawler user agents by response class
+and path. Input bytes, rows, line size, unique paths, and returned detail are
+bounded, and any capped or malformed evidence stays visible. User-agent names
+can be spoofed, so the result describes observed request strings rather than
+verified crawler identity.
+
+## Notify IndexNow after a change
+
+Generate a key file in the public asset directory for your site, then deploy
+it before sending notifications:
+
+```sh
+seo indexnow setup --site https://example.com --output ./public
+seo indexnow verify --site https://example.com
+seo indexnow submit --site https://example.com --url https://example.com/changed-page
+```
+
+Use `--dry-run --json` to validate a submission without notifying IndexNow.
+The command accepts one URL, a comma-separated list, or a newline-delimited
+file. A run is limited to 1,000 unique URLs, every URL must use the configured
+host, and the public key file is checked before a live request. The local key
+mapping stays in the system keychain with a private file fallback. Agents and
+CI can set `SEO_INDEXNOW_KEY` for the current process instead.
+
+An accepted IndexNow request confirms receipt only. It does not prove that a
+URL was crawled, indexed, ranked, or shown in search results.
+
 ## Crawl a site
 
 For a large or unfamiliar site, start with the sitemap health pass: