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: Replace each bracketed field with information from your own website. If the assistant can inspect the project directly, give it access to the correct folder or repository as well.
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.
Review this newly published website for post-launch SEO problems. The live domain is [https://www.example.com]. Do not change anything yet.
1. List every important public URL and confirm it uses the live domain.
2. Check HTTP to HTTPS and www/non-www behaviour. Flag redirect chains or conflicting versions.
3. For every important page report its status code, title, meta description, canonical, robots directive and H1.
4. Confirm robots.txt is reachable, does not block important pages and references the correct sitemap.
5. Confirm the XML sitemap is valid, uses the live domain and contains only canonical, indexable URLs returning 200.
6. Identify references to localhost, staging, preview or temporary domains in metadata, canonicals, Open Graph tags, links or structured data.
7. Check that important copy and links appear in the HTML response rather than only after interaction.
8. Test one made-up URL and report whether it returns a genuine 404.
9. Separate findings into Confirmed, Needs a live tool, and Cannot verify here.
Return a prioritised table with evidence. Stop after the report and wait for approval before proposing changes. Do not claim that passing these checks guarantees indexing or rankings.When to use it
- Immediately after connecting the final domain.
- After a redesign, migration or hosting change.
- Whenever a large release changes routes, metadata or deployment settings.
What it checks
- Domain consolidation and redirects
- Per-page metadata and canonicals
- Robots, sitemap and live status codes
- Staging-domain leakage
- Rendered content, internal links and 404 behaviour
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.
- The builder may not be able to request the public site exactly as Google does.
- Search Console indexing data must be checked in Search Console.
- A technically valid page is not automatically useful, competitive or eligible to rank.
Worked example
This is an illustrative scenario rather than a client result.
A five-page site launches on its custom domain. The report finds that canonical tags still use the preview hostname and the sitemap contains an old services URL. Those two changes are approved, republished and checked again before the sitemap is submitted.
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.