{"id":51017,"plugin_id":"plugin_asdk_app_6ac47963cb448191a5b1757e0682bd6a","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:45:13.950Z","digest":"2f87238f9216cdede064a7252277ccdf136318c08e4349125c52fef49272bbec","against":null,"payload":{"description":"Explains what Sitewalk checks and how to run a technical SEO audit from a chat.","included_files":[],"name":"get-started","skill_md_contents":"---\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"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}