← Sitewalk: SEO Audit & CrawlerCONTENT HISTORY
WHAT CHANGED
Update to Sitewalk: SEO Audit & Crawler
Snapshot Nov 16, 2026 · 18:13 UTC · version 1.5.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Sitewalk: SEO Audit & Crawler and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the user wants a finished Sitewalk audit turned into tasks for a developer, a client's developer or an agency team, such as a ticket list, a to-do list or a brief.",
"included_files": [],
"name": "developer-handoff",
"skill_md_contents": "---\nname: developer-handoff\ndescription: Use when the user wants a finished Sitewalk audit turned into tasks for a developer, a client's developer or an agency team, such as a ticket list, a to-do list or a brief.\n---\n\nTurn a finished audit into a task list. Do not start a new audit for this.\n\n1. Use the `audit_id` of the audit already discussed in this chat. If there is none, ask which site, then run the audit as usual first.\n2. Call `get_audit_report` with `top_n` set to 25.\n3. Write one task per issue, in the report's order. Each task has: a short title, why it matters in one line, the number of pages affected, two or three example URLs, the fix as the report states it, and how to check it is done.\n4. Group the tasks under \"Fix first\", \"Next\" and \"Later\", following the report's ranking.\n5. End with the full report link and the CSV and PDF links from the report, so the developer has every affected URL.\n\nUse only the issues, counts and URLs the report returns. Do not invent effort estimates or deadlines.\n"
}SHA-256 of public snapshot: d4b7952c475460a0bcc0bd118ba0bbfb432cd2e9a285228df9e2a128168e7434