Start the separate local audit service, enter a public site URL you have permission to audit, and run a limited crawl. Review scope and failed requests before prioritising findings; save a JSON snapshot for comparison.
Prepare the scope and service
Start npm run dev:audit from the project, or run npm run audit:server alongside Astro. Static hosting alone cannot perform a crawl. Confirm permission, enter a public URL and choose up to 25 same-site pages. Target servers can observe the requests. Login areas and private networks are unsupported.
Read evidence before scores
Check requested pages, robots exclusions, redirects and failed requests first. Missing pages make the audit incomplete. Source HTML may differ from a JavaScript-rendered page. Confirm titles, canonical URLs, HTTP errors and internal links against the intended public site before changing code.
Prioritise repairs
Fix unintended indexing restrictions, broken navigation and incorrect canonicals before polishing descriptions. For AEO, make answers explicit, support factual claims with evidence and clarify who published the content. Lexical answer checks are suggestions, not proof of accuracy or future AI citations.
Compare like with like
Download the JSON snapshot and repeat the audit after repairs with the same origin, page limit and scope. Load both reports in Site Audit Report Comparison. A newly discovered page or failed request can alter counts without a regression. Keep separate evidence for deployed changes and Search Console indexing.
Tools for this workflow
Published by Innovative AI Tools, a project from Innovative AI Solutions. See how your input is handled.