seo-crawl-audit 0.14.1 → 0.15.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/README.md +6 -0
- package/agent-skill/seo-crawl-audit/SKILL.md +1 -1
- package/bundle/cli.js +51 -48
- package/bundle/comparison-worker.js +19 -19
- package/bundle/mcp.js +11 -9
- package/bundle/server.js +176 -43
- package/bundle/trend-worker.js +6 -0
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -36,6 +36,10 @@ the discovered URL count and requires explicit confirmation above 5,000 URLs.
|
|
|
36
36
|
The overview keeps scan coverage, issue counts, and locally stored trends in
|
|
37
37
|
one place.
|
|
38
38
|
|
|
39
|
+
The local History panel can plot 20, 50, or 100 saved-run observations without
|
|
40
|
+
new page requests. Dashed segments flag changed coverage or policy; a lower
|
|
41
|
+
count alone is not proof of SEO improvement.
|
|
42
|
+
|
|
39
43
|
### Site metrics
|
|
40
44
|
|
|
41
45
|
|
|
@@ -360,6 +364,7 @@ Lists locally saved runs and creates an HTML report with issue trends:
|
|
|
360
364
|
```bash
|
|
361
365
|
seo-audit history https://example.com/
|
|
362
366
|
seo-audit history --history-dir ./audit-history --report history.html
|
|
367
|
+
seo-audit history https://example.com/ --json --trend-limit 50
|
|
363
368
|
```
|
|
364
369
|
|
|
365
370
|
Compare any two saved runs without crawling:
|
|
@@ -399,6 +404,7 @@ seo-audit history \
|
|
|
399
404
|
--preview-headers-env <name>
|
|
400
405
|
Read preview headers from a JSON environment variable
|
|
401
406
|
--history-dir <path> Local snapshot history directory
|
|
407
|
+
--trend-limit <n> Trend range: 20 (default), 50, or 100 saved runs
|
|
402
408
|
--no-history Do not save this scan to local history
|
|
403
409
|
--from <snapshot> Older snapshot for an explicit history comparison
|
|
404
410
|
--to <snapshot> Newer snapshot for an explicit history comparison
|
|
@@ -11,7 +11,7 @@ Use this skill when a user asks to audit a website, check SEO regressions, inspe
|
|
|
11
11
|
|
|
12
12
|
1. Start with `seo_audit_plan` when using MCP. Confirm the URL, sitemap mode, page limit, and robots policy before requesting pages.
|
|
13
13
|
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.
|
|
14
|
-
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.
|
|
14
|
+
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.
|
|
15
15
|
4. Use `seo_audit_report` when a human-readable HTML artifact is needed. Return artifact paths rather than embedding a large report in chat.
|
|
16
16
|
|
|
17
17
|
## Safety and interpretation
|