Checklist for reviewing an AI-built landing page

By the HTMLAnnotate team14 November 20263 min read

Claude, ChatGPT, v0 and Lovable can turn a prompt into a good-looking landing page in minutes. Good-looking is not the same as ready. These are the mistakes AI-built pages make most often, and a quick way to check for each one before a client or customer sees it.

Why AI pages need their own review

A person writing a landing page leaves gaps where they don't know something. An AI tool fills those gaps with something that sounds right. That is why AI pages look finished sooner, and why the mistakes are harder to spot: they are confident, well formatted and in the right place.

Run through the checks below on every page an AI tool builds, ideally in this order. Facts first, because a wrong claim is the most expensive mistake to ship.

1. Facts, numbers and claims

• Statistics. "Trusted by 10,000 teams" or "cuts review time by 60%". If you can't point to where a number came from, remove it.
• Testimonials and quotes. AI tools often write sample testimonials with realistic names. Replace them with real ones you have permission to use, or delete the section.
• Customer logos. A row of well-known logos implies those companies are customers. Keep only the ones that are.
• Features and prices. Check every feature listed actually exists and every price matches your pricing page.
• Dates, addresses and names. Opening hours, office cities and team names are easy to invent and easy to miss.

2. Links, buttons and forms

• Every button goes somewhere real. AI pages often use "#" or a made-up address as a stand-in. Click each one.
• Forms actually send. A good-looking form with nowhere to send its data loses every lead. Submit a test entry and confirm it arrives.
• No dead links. Run the page through a broken link checker to catch links that return errors.
• Sign-up and checkout flows lead to your real product, not a demo address.

3. The phone layout

Most AI tools design at desktop width first. On a phone, look for headings that wrap badly, text sitting on top of images, buttons too close together to tap, and wide tables or images that make the page scroll sideways.

A responsive checker shows phone, tablet and desktop at once, which is faster than resizing a browser. Then check on a real phone too, because fonts and spacing behave differently there.

4. Accessibility basics

• Image descriptions. Every meaningful image needs alt text that says what it shows. Decorative images should have empty alt text.
• Contrast. Light grey text on white and white text on bright colours are common in AI designs. Body text should be easy to read for everyone.
• Headings in order. One main heading, then sections in a sensible order, so screen readers can follow the page.
• Form labels. Each field needs a visible label, not only hint text inside the box that disappears when you type.
• Keyboard use. Press Tab through the page. You should always see where you are, and every button should work with Enter.

5. The details that make it yours

• Brand name and voice. AI tools drift between names, spellings and tones across sections.
• Sample text. Search the page for leftover filler, stand-in names and sample email addresses.
• Legal pages. Privacy policy, terms and cookie notice linked and correct for your business.
• Contact details. Real email, real address if you list one, working social links.
• Search and sharing. Page title, description and share image set. A link preview checker shows how the link looks when someone shares it.
• Analytics. Tracking installed and firing, so you can tell whether the page works.

Getting the client's review

Once your own checks pass, the client still needs to see it. Screenshots and long emails lose the detail of which section someone means. A review link lets them click the exact headline or button and type a note, on desktop or phone, without an account.

With an AI-built page, the comments can go straight back to the tool that made it. Paste a Copy for AI brief into the chat, or connect an MCP server so the AI reads the comments itself. See letting your AI tool fix client feedback with MCP, or the step-by-step guide to reviewing a page Claude made.

The short version

1. Delete or verify every number, quote and logo.
2. Click every button and submit every form.
3. Check it on a real phone.
4. Fix alt text, contrast, headings and labels.
5. Replace sample text, link legal pages, check the share preview.
6. Send a review link, not screenshots.

For the wider launch, including speed, search and tracking, use our full website launch checklist.

Questions