seo-crawl-audit 0.14.1 → 0.15.1

package/README.md

@@ -34,7 +34,11 @@ the discovered URL count and requires explicit confirmation above 5,000 URLs.
 ![SEO Crawl Audit summary cards and local scan history](https://raw.githubusercontent.com/MelnixDev/seo-crawl-audit/main/docs/images/report-overview.png)
 
 The overview keeps scan coverage, issue counts, and locally stored trends in
-one place.
+one place. The example screenshot uses synthetic history, not live crawl data.
+
+The local History panel can plot 20, 50, or 100 saved-run observations without
+new page requests. Dashed segments flag changed coverage or policy; a lower
+count alone is not proof of SEO improvement.
 
 ### Site metrics
 
@@ -43,6 +47,14 @@ one place.
 Site metrics separate measured crawl data from external provider values, with
 the source and connection state shown for every indicator.
 
+### Page Explorer
+
+![SEO Crawl Audit Page Explorer with filters and per-page issue counts](https://raw.githubusercontent.com/MelnixDev/seo-crawl-audit/main/docs/images/report-pages.png)
+
+Browse checked URLs, filter by HTTP status or indexability, and open a page for
+its crawl details and current issues. The table does not claim that a page is
+indexed by a search engine.
+
 ### Interactive issue analytics
 
 ![SEO Crawl Audit interactive issue statistics](https://raw.githubusercontent.com/MelnixDev/seo-crawl-audit/main/docs/images/report-analytics.png)
@@ -360,6 +372,7 @@ Lists locally saved runs and creates an HTML report with issue trends:
 ```bash
 seo-audit history https://example.com/
 seo-audit history --history-dir ./audit-history --report history.html
+seo-audit history https://example.com/ --json --trend-limit 50
 ```
 
 Compare any two saved runs without crawling:
@@ -399,6 +412,7 @@ seo-audit history \
 --preview-headers-env <name>
                         Read preview headers from a JSON environment variable
 --history-dir <path>    Local snapshot history directory
+--trend-limit <n>       Trend range: 20 (default), 50, or 100 saved runs
 --no-history            Do not save this scan to local history
 --from <snapshot>       Older snapshot for an explicit history comparison
 --to <snapshot>         Newer snapshot for an explicit history comparison

package/agent-skill/seo-crawl-audit/SKILL.md

@@ -11,7 +11,7 @@ Use this skill when a user asks to audit a website, check SEO regressions, inspe
 
 1. Start with `seo_audit_plan` when using MCP. Confirm the URL, sitemap mode, page limit, and robots policy before requesting pages.
 2. Run `seo_audit_scan` for a baseline, or `seo_audit_check` with a saved baseline for a regression comparison. Keep the default 100-page limit unless the user explicitly asks for more.
-3. Use `seo_audit_compare` for two saved snapshots, or `seo_audit_issues` with filters and pagination to inspect concrete findings. Prioritize errors, then warnings, then informational context.
+3. Use `seo_audit_compare` for two saved snapshots, `seo_audit_history` for a compact read-only trend over saved runs, or `seo_audit_issues` with filters and pagination to inspect concrete findings. Prioritize errors, then warnings, then informational context. Never treat a lower count across an incomplete or policy-changed trend as proven improvement.
 4. Use `seo_audit_report` when a human-readable HTML artifact is needed. Return artifact paths rather than embedding a large report in chat.
 
 ## Safety and interpretation