The 20 Checks to Run Before You Put a Claude-Built Site Live
Claude hands you a site that looks finished and ships broken. Here are the 20 things it always skips, and the 5 prompts that close them, in order.
August 14, 2026 · 6 min read
A site built with Claude has one birth defect: it is optimized for what you can see. You look at the homepage, it looks good, you deploy.
Nobody prompts for a 404 page. Nobody prompts for a meta description, alt text on images, or a loading state on a form. So none of it gets built, and your first real visitor finds out for you.
The gap between a demo and a production site comes down to about twenty details, none of them visible from the homepage.This article lists all twenty, then gives you the five prompts that make Claude fix them. Order matters: the first prompt repairs nothing, it just tells you the truth. That is the one that stings.
The Claude AI Lab is my Skool community where I share my Claude systems and the more advanced modules. Access is $67/month.
Join the Lab →The 20 checks, grouped
They are not equal. Some cost you visitors, others just look tidy. Grouping them by family shows you fast where you are most exposed.
Two of these deserve a pause. A form that fails silently is the most expensive bug you can ship: the visitor thinks they signed up, you receive nothing, and nobody will ever tell you. A placeholder contact detail kills credibility in one second, because a contact@example.com in a footer says exactly what it says.
The 5 prompts
The audit
This one repairs nothing. It sets your baseline, and you need it before touching any code.
Here is my site: [paste the repo, the folder, or the live URL]
Audit it against a production launch checklist. Check for: custom 404, CTA
above the fold, unique page titles, meta descriptions, Open Graph image,
favicon set, robots.txt, sitemap.xml, alt text, mobile breakpoints, sticky
mobile CTA, loading states, form error states, thank you page, privacy policy,
terms, cookie banner, analytics, real contact route, image compression.
For each one tell me: present, partial, or missing. Then rank everything
missing by what breaks trust with a first time visitor. Do not fix anything
yet.
The SEO pass
This is the pass with the best return, and the one almost nobody runs, because none of what it produces shows up on the page.
Fix the discoverability layer on this site.
1. Give every page a unique title under 60 characters that says what the page
is for.
2. Give every page a meta description between 120 and 155 characters.
3. Add Open Graph and Twitter Card tags, including an image, so links preview
properly when shared.
4. Generate a full favicon set including the Apple touch icon.
5. Create robots.txt and sitemap.xml covering every public page.
List every file you created or changed, and show me the final head section of
one page so I can check it.
The legal pages
The fastest part to generate and the easiest to get wrong. Claude gives you 80 percent of a draft in a minute. The remaining 20 percent is exactly where the risk lives.
Draft the legal pages for this site.
Context: my site collects [emails / payments / account data / nothing]. It uses
[analytics tool] and [payment processor]. My users are mainly in [country or
region]. I operate as [sole trader / registered company / not registered yet].
Draft: a privacy policy, a terms of service page, and a cookie banner with
accept and reject options.
Then give me a separate list of every clause where you had to guess, and
everything a lawyer in my jurisdiction should review before this goes live.
That second list is the real output of this prompt. It tells you where you are exposed.
The mobile pass
Your site was designed on a laptop and will be seen on a phone. The whole gap sits there.
Go through this site at 390px wide, one page at a time.
Fix: any horizontal scroll, text smaller than 16px, tap targets under 44px,
broken layouts at that width, and navigation that does not work with a thumb.
Then add a sticky bottom CTA on mobile only, linking to the primary action.
Tell me page by page what was broken and what you changed.
The three numbers are not arbitrary: 390px is the logical width of recent iPhones, 44px is Apple's recommended minimum tap target, and a form field under 16px triggers automatic zoom on iOS Safari.
The last look
Everything remaining, in one pass.
Finish the launch pass on this site.
1. Add a custom 404 page that links back to the homepage and the main sections.
2. Add a thank you page after every form submit.
3. Add loading and error states to every form and every async action.
4. Add descriptive alt text to every image.
5. Compress every image over 200kb and convert to a modern format where
supported.
6. Replace every placeholder contact detail with the real one: [your email].
7. Install [analytics tool] and confirm it fires on page view and on form
submit.
When you are done, tell me what you would still fix if this were your own site.
The rerun
After prompt 5, run prompt 1 again on the same site. It is the same audit against the same twenty, and it takes a minute.
Anything still coming back as missing is either a real gap or something Claude said it did and did not. Both are worth knowing before you post the link anywhere.
Want to go further?
In the Lab, I share my prompts, templates and how I chain them to ship real work, not fluff.
A dedicated session or program, tailored to your tools and use cases.
And day-to-day, I post one reel a day on Instagram: @quentin_iamarketing