Copy-and-paste prompt
This prompt works with any AI assistant that can review your website project or the information you share with it. That includes Claude, ChatGPT, Codex, Cursor and the assistants built into Lovable, Bolt and Replit.
What to give the assistant: Give the assistant access to the website project or the relevant live URLs. Include a previous report when the prompt asks it to compare changes over time.
Ask for the report first. Approve individual changes only after the assistant has shown you where it found each issue and you understand the proposed fix.
Run this week's technical SEO maintenance review. Do not edit files. Compare the current project and live site with the previous approved state if that evidence is available.
Check for:
- new, removed or renamed public routes;
- accidental noindex or crawler blocks;
- sitemap URLs that are missing, redirected, duplicated or non-canonical;
- broken internal links and orphaned important pages;
- duplicate or missing titles, descriptions, canonicals and H1s;
- staging or preview domains introduced by recent changes;
- important copy or links no longer present in the initial HTML;
- new images without useful alt text or with unexpectedly large file sizes;
- missing-page behaviour and server errors.
Report only what changed or needs action. For each finding give evidence, business impact, confidence and the smallest safe fix. Separate code findings from checks requiring Google Search Console or another live tool. Stop and wait for approval.When to use it
- Once a week on an actively changing site.
- After several new pages or releases.
- Before a monthly SEO review so obvious regressions are already documented.
What it checks
- Route and sitemap drift
- Crawler directives
- Metadata duplication
- Broken and orphaned pages
- Rendering, media and error regressions
What it cannot prove
An AI assistant can inspect supplied code and information, but it should not be treated as independent evidence that Google can crawl, index or rank the website.
- It needs a reliable previous state to identify genuine changes.
- It cannot replace Search Console coverage and performance data.
- Running it weekly on an unchanged site may create noise, so the output should focus on differences.
Worked example
This is an illustrative scenario rather than a client result.
A new case-study route was added during the week but was not linked or included in the sitemap. The prompt reports both issues as one related finding instead of recommending a general site rewrite.
Verify the result
After using the prompt, check every approved change on the published website. Save the original report and the final verification so you can see what actually changed.
Book a site review and we will check the live pages for you, or send us a message if you would like to describe the problem first. You can also browse the rest of the resources hub.