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 project folder or repository, your intended live domain and any public pages it might not discover from the code.
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 website project for SEO launch readiness. Do not change any files yet. First identify the framework, hosting setup and rendering approach from the project files or information I provide. If you cannot confirm something, say what you need to check instead of guessing.
Live domain or intended domain: [DOMAIN]
Important public pages: [LIST THEM, OR ASK THE ASSISTANT TO FIND THEM]
1. List the public routes and flag account, admin, test or thank-you pages that should not appear in search.
2. For every important page report its title, meta description, canonical URL and H1. Flag missing, duplicated or placeholder values.
3. Explain whether the main copy and links should be present in the initial HTML. Name the file or configuration behind your conclusion.
4. Check robots.txt, the XML sitemap and any noindex rules. Confirm that the sitemap contains only canonical public URLs.
5. Find references to localhost, staging, preview or temporary domains in metadata, links, structured data and sharing tags.
6. Check internal links, image alt text and missing-page behaviour.
7. Separate findings into Confirmed in the project, Needs a live-site check, and Cannot confirm with the access provided.
Return a prioritised table with the finding, where you found it, why it matters and the smallest safe fix. Stop after the report. Wait for my approval before editing anything. Do not promise indexing or rankings.When to use it
- When you built the site with Claude, ChatGPT, Codex or another assistant that does not have a dedicated prompt here.
- When the pages and copy are nearly complete but the site has not launched.
- Before asking an AI assistant to make broad SEO changes.
What it checks
- Framework, hosting and rendering setup
- Public routes and per-page metadata
- Robots, sitemap and index controls
- Temporary-domain references
- Internal links, images 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 assistant needs access to the project or enough pasted information to inspect it properly.
- Hosting redirects and live responses still need checking after publication.
- Passing a technical review does not guarantee that Google will index or rank a page.
Worked example
This is an illustrative scenario rather than a client result.
A founder built a five-page site with Claude Code. The review confirms the routes and titles, but finds that every canonical still points to the preview domain. They approve that one correction, launch the site and then use the post-launch prompt to verify the live response.
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.