← Sitewalk: SEO Audit & CrawlerCONTENT HISTORY

Update to Sitewalk: SEO Audit & Crawler

Snapshot Nov 12, 2026 · 06:08 UTC · version 1.2.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for get-started

Full description — Now says: Use when the user asks what Sitewalk checks or how to run a technical SEO audit of a website from a chat.

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Sitewalk: SEO Audit & Crawler and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Oct 24, 2026 · 13:45 UTC

Explains what Sitewalk checks and how to run a technical SEO audit from a chat.

After

Nov 12, 2026 · 06:08 UTC

Use when the user asks what Sitewalk checks or how to run a technical SEO audit of a website from a chat.

Skill instructions

Before

Oct 24, 2026 · 13:45 UTC

Explains what Sitewalk checks and how to run a technical SEO audit from a chat. Audits need a signed-in Sitewalk account: the first call asks the user to connect, which confirms their email. A site the user has not verified gets up to 50...

After

Nov 12, 2026 · 06:08 UTC

Use when the user asks what Sitewalk checks or how to run a technical SEO audit of a website from a chat. The first audit asks the user to connect, which confirms their email with a 6-digit code. Without a confirmed email an audit covers...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,6 +1,6 @@
 ---
 name: get-started
-description: Explains what Sitewalk checks and how to run a technical SEO audit from a chat.
+description: Use when the user asks what Sitewalk checks or how to run a technical SEO audit of a website from a chat.
 ---
 
 Sitewalk crawls a website and ranks the technical SEO problems it finds, each with a plain fix.
@@ -11,6 +11,6 @@
 4. Call `get_audit_report` and present the ranked issues, highest impact first, with pages affected, an example URL and the suggested fix for each.
 5. If the report says the page limit was reached, say so. If the user asks what was covered, use the report's `what_was_checked` and `not_checked` lists.
 
-Audits need a signed-in Sitewalk account: the first call asks the user to connect, which confirms their email. A site the
-user has not verified gets up to 50 pages. Verifying the site on the website unlocks a crawl of up to 500 pages.
+The first audit asks the user to connect, which confirms their email with a 6-digit code. Without a confirmed email an audit
+covers up to 50 pages; with a confirmed email it covers up to 500. No domain verification is needed.
 Report only what the tools return. Do not guess at issues the report does not list.
Full technical diff · 2 changed fields

changed /description

BEFORE
"Explains what Sitewalk checks and how to run a technical SEO audit from a chat."
AFTER
"Use when the user asks what Sitewalk checks or how to run a technical SEO audit of a website from a chat."

changed /skill_md_contents

BEFORE
"---\nname: get-started\ndescription: Explains what Sitewalk checks and how to run a technical SEO audit from a chat.\n---\n\nSitewalk crawls a website and ranks the technical SEO problems it finds, each with a plain fix.\n\n1. Ask for the site address if the user has not given one.\n2. Call `start_site_audit` with the address. Keep the returned `audit_id`.\n3. Call `get_audit_status` every 20 to 30 seconds until the status is completed. A larger audit takes several minutes. Tell the user it is running and how many pages are done.\n4. Call `get_audit_report` and present the ranked issues, highest impact first, with pages affected, an example URL and the suggested fix for each.\n5. If the report says the page limit was reached, say so. If the user asks what was covered, use the report's `what_was_checked` and `not_checked` lists.\n\nAudits need a signed-in Sitewalk account: the first call asks the user to connect, which confirms their email. A site the\nuser has not verified gets up to 50 pages. Verifying the site on the website unlocks a crawl of up to 500 pages.\nReport only what the tools return. Do not guess at issues the report does not list.\n"
AFTER
"---\nname: get-started\ndescription: Use when the user asks what Sitewalk checks or how to run a technical SEO audit of a website from a chat.\n---\n\nSitewalk crawls a website and ranks the technical SEO problems it finds, each with a plain fix.\n\n1. Ask for the site address if the user has not given one.\n2. Call `start_site_audit` with the address. Keep the returned `audit_id`.\n3. Call `get_audit_status` every 20 to 30 seconds until the status is completed. A larger audit takes several minutes. Tell the user it is running and how many pages are done.\n4. Call `get_audit_report` and present the ranked issues, highest impact first, with pages affected, an example URL and the suggested fix for each.\n5. If the report says the page limit was reached, say so. If the user asks what was covered, use the report's `what_was_checked` and `not_checked` lists.\n\nThe first audit asks the user to connect, which confirms their email with a 6-digit code. Without a confirmed email an audit\ncovers up to 50 pages; with a confirmed email it covers up to 500. No domain verification is needed.\nReport only what the tools return. Do not guess at issues the report does not list.\n"
Full snapshot data
{
  "description": "Use when the user asks what Sitewalk checks or how to run a technical SEO audit of a website from a chat.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Use when the user asks what Sitewalk checks or how to run a technical SEO audit of a website from a chat.\n---\n\nSitewalk crawls a website and ranks the technical SEO problems it finds, each with a plain fix.\n\n1. Ask for the site address if the user has not given one.\n2. Call `start_site_audit` with the address. Keep the returned `audit_id`.\n3. Call `get_audit_status` every 20 to 30 seconds until the status is completed. A larger audit takes several minutes. Tell the user it is running and how many pages are done.\n4. Call `get_audit_report` and present the ranked issues, highest impact first, with pages affected, an example URL and the suggested fix for each.\n5. If the report says the page limit was reached, say so. If the user asks what was covered, use the report's `what_was_checked` and `not_checked` lists.\n\nThe first audit asks the user to connect, which confirms their email with a 6-digit code. Without a confirmed email an audit\ncovers up to 50 pages; with a confirmed email it covers up to 500. No domain verification is needed.\nReport only what the tools return. Do not guess at issues the report does not list.\n"
}

SHA-256 of public snapshot: 3a0d6af5327e7d8580af64a23d59c5285a125aaced17ad41c838137876729f38