How to Review AI-Generated HTML Before You Publish
Check structure, claims, accessibility, responsiveness, safety, and metadata with a repeatable human review pass.
The short version
Treat AI-generated HTML as a capable first draft that still needs product judgment.
Review the content before the code
Confirm that the page answers the intended question, uses the right audience language, and does not invent evidence. Verify names, dates, links, numbers, and customer claims against their sources.
Read only the heading outline, then only the calls to action. Those two passes quickly reveal whether the page has a coherent argument and a clear next step.
Inspect the rendered behavior
- Navigate the whole page with a keyboard.
- Resize from a narrow phone to a wide desktop.
- Submit forms with valid and invalid values.
- Open links and verify destinations.
- Disable CSS and confirm the reading order still works.
- Check motion with reduced-motion preferences.
Review the source as a system
Look for duplicated ids, generic divs where native controls belong, inaccessible labels, oversized assets, hidden content, unsafe inline scripts, and metadata copied from another page.
Publish the draft to a reviewable link, anchor comments to the exact sections that need work, and ask the agent to revise the same artifact. That preserves context better than sending screenshots and scattered chat messages.