Website review checklist, from 19 fixes an AI reviewer returned

A website review should check, in order, that every planned page and flow exists, that every layout holds at phone, tablet and desktop widths, and that copy and contrast are finished. In 19 fixes an AI reviewer returned on 3 generated sites, 8 were missing pages or flows and 5 were layouts that broke at one width.

Where the fixes come from

OneCraft generates a website in steps, and after a green build a fresh agent reviews the code and the build’s screenshots at 375, 768 and 1280 pixels (390 and 768 for apps, plus Home in dark mode) and returns up to 12 fixes. The code agent applies them and builds again, for at most two rounds.

The fix list is kept in the job record while a run is in progress. Read from OneCraft’s development project on 21 October 2026, only 3 of the 17 completed pipeline runs still held a list: a yoga studio app (6 fixes), a branding agency site with a client portal (7) and a running club site (6). That is 19 fixes, a sample of what the reviewer writes, not every fix it ever returned. The briefs were written by the team, all on one environment, and the pipeline changed during the week. The kinds in the table are a hand grouping of the reviewer’s own problem lines; the area column is the reviewer’s own label.

What the reviewer caught

Missing pages and flows, 8 of 19. The plan for each site lists its pages and the capabilities on each, and the reviewer is given those plans. Most of its code fixes were things the plan promised and the build lacked: an account page where a person edits their profile and sees their invoices, a thank you page that waits for a payment to confirm, a notification bell with an unread count, a separate rules page for a giveaway, a sign in page without the planned forgot password flow, and on the agency site the testimonials, the Organization JSON-LD and a robots.txt.

Layouts that broke at one width, 5. A hero on the app where the Book a class button was clipped at 768 pixels. Bento tiles that left a gap on the right at 1280. A two column tile grid with an empty cell because one class sat alone. A photo strip only about 100 pixels tall at 1280. A sign in gate that floated as a small card in an empty page.

Contrast and dark mode, 2. A footer link in dark grey on navy, nearly invisible, and an icon circle that turned grey in dark mode. WCAG’s contrast minimum asks for 4.5 to 1 for normal text.

Strays, 2. A fifth tab no one planned, with a lowercase title and a generic icon, and a stats row showing the word Freo as if it were a number.

Placeholder copy, 1, and a loading state, 1. Privacy and terms pages still saying the policy was being prepared, and a help page whose tabs showed only ALL over skeleton cards.

Review rounds and failed builds

Across all 17 completed pipeline runs, the job records show 5 with no fix round, 6 with one and 6 with two. Two of the five with none ran out of credits on a test account and stopped at their first green build; the running club’s record shows 6 fixes and a round counter of 0, and does not say whether they were applied. Before any review, the build itself caught faults: 5 of 41 website builds failed, two on the layout check (a page overflowing sideways at 375 or 768) and one on a type error.

The checklist

Use this order on any site, AI written or not.

1. Every planned page exists. Click every link in the menu and footer. Open the account, thank you and error pages directly.
2. Every flow finishes. Sign up, sign in, forgot password, book, pay, cancel. A magic link or Google sign in needs testing on the live address, not only the preview.
3. Every page at three widths. About 375, 768 and 1280 pixels, plus slow resizing between. Watch for clipped buttons, gaps and sideways scroll.
4. Dark mode, if offered. Every icon and border, not just the text.
5. Contrast. Small text against its background, footer links especially.
6. No placeholders. Search for prepared, coming soon, lorem and example. Read the legal pages.
7. Loading, empty and error states. Turn off the network and load a list page; open a list with no rows.
8. Search basics. A title and description per page, canonical and redirects for moved pages, structured data where it fits.

On OneCraft, raise anything left after generation in chat: each change is a commit and a build, and a change whose build fails is rolled back. See editing with AI chat, version history, website accessibility basics and how long AI website generation takes.