Skip to content
Standout

guide

The pre-launch checklist for a vibe-coded website

8 min read · updated November 17, 2026

Most launch checklists get run on the home page, in a desktop browser, by the person who built it. The faults that lose a client are somewhere else: on an inner page, at phone width, in grey text nobody measured. This is the checklist for the whole site, in the order to run it.

The home page is the best page on your site

During a build the home page gets all the attention, so it ends up the most polished page you have. The inner pages are generated later and faster, with less review. A checklist run on the home page tells you the home page is fine, and nothing else.

We learned this on our own site. When we ran a whole-site audit on standoutmcp.io, the home page scored 97 out of 100. One inner page scored 86, with eight findings that no audit of the home page could have shown us.

There is a second reason these faults survive. The agent that built the page reads code, and the faults a visitor meets first only exist on the rendered page: a contrast ratio, a button that overflows at 360px, a link that is too small to tap. So the checklist below is written to be run on the rendered site, one page at a time, starting on a phone.

On a phone, at three widths

Render each page at 360px, 390px and 768px wide. A page that holds at 390 can still break at 360.

  • 01

    Sideways scroll

    One element wider than the screen makes the whole page slide sideways. It is usually a table, a long unbroken word, a code block or an image with a fixed width.

    fix Find the element that is wider than the viewport and let it wrap, shrink, or scroll inside its own box.

  • 02

    Buttons and links too small to tap

    Navigation and footer links are the usual offenders. They look fine with a mouse and get mis-tapped with a thumb.

    fix Give every tap target at least 44px of height with padding. Do not fix it by making the text bigger.

  • 03

    Text touching the edge of the screen

    Copy that runs to the bezel reads as unfinished straight away.

    fix A gutter of at least 20px on both sides, on every section.

  • 04

    A hero that hides its own button

    A hero set to the full height of the screen pushes the call to action under the phone's toolbar.

    fix Use min-height: 100dvh or less, and confirm the main action is visible without scrolling.

  • 05

    One page without the viewport tag

    That page renders as a shrunken desktop page on a phone, while every other page looks right.

    fix Put the viewport meta tag in the shared layout, then confirm it is in the HTML of every page.

Text a visitor can actually read

  • 01

    Grey text below 4.5 to 1

    Light grey on white looks refined on a large monitor and disappears on a phone outdoors.

    fix Work out the contrast ratio from the real rendered colours. Body and label text needs 4.5 to 1. Large headings need 3 to 1.

  • 02

    The same grey on a tinted section

    A colour that passes on white can fail on the pale band further down the page.

    fix Measure each piece of text against the background it actually sits on, not against the page colour.

  • 03

    Body text under 16px on a phone

    Small body copy is tiring to read and reads as a template default.

    fix 16px or more for body text. Keep the small sizes for labels.

  • 04

    Lines that run the full width on desktop

    A paragraph 140 characters wide is hard to follow from one line to the next.

    fix Cap the measure at about 45 to 75 characters per line.

  • 05

    Text over a photo or a gradient

    No formula can score it, because the background changes under every letter.

    fix Look at it on the phone render. If any word is hard to read, add a solid or darkened panel behind the text.

What is true

A build agent fills gaps with plausible content. Before launch, every claim on the site needs an owner.

  • 01

    Numbers, reviews and logos nobody supplied

    An invented testimonial found by one real customer costs more trust than the whole site earned.

    fix If you cannot say where a claim came from, take it out. A plain true line beats an impressive false one.

  • 02

    Placeholder copy and sample names

    Filler text and sample people survive on inner pages long after the home page is clean.

    fix Search the whole project for placeholder text, not just the page you are looking at.

  • 03

    Links and buttons that go nowhere

    A button that does nothing is the fastest way to look unfinished.

    fix Search the source for href="#" and empty links. Every one either gets a real destination or is removed.

What only a whole-site check can show

These faults are invisible when you check one page at a time.

  • 01

    The same title on several pages

    Generated pages inherit the layout's title, so search results show one line repeated for every page.

    fix A title and a description written for each page.

  • 02

    A page that lost the navigation

    A page built outside the shared layout leaves the visitor with no way back.

    fix Open every page and confirm the header and footer are there and match.

  • 03

    Broken internal links

    Routes get renamed during a build and the old links stay behind.

    fix Request every internal link on every page and confirm none returns a 404.

  • 04

    The same fault on every page

    A fault in the shared layout shows up as six separate problems.

    fix Fix it once in the layout, then check all the pages again.

Run it in this order

The order matters. It keeps you from fixing the same thing six times, and from calling something fixed that you never checked again.

  1. 1

    List the pages

    Every page a visitor can reach from the navigation and the footer, plus anything the home page links to. Write the list down. It is the scope of the check.

  2. 2

    Render each page on a phone first

    360px, 390px and 768px. Use real device emulation or a rendered audit. Dragging a desktop window narrower misses the viewport tag and touch behaviour.

  3. 3

    Measure, do not eyeball

    Contrast is a number. Tap targets are a number. Overflow is a yes or a no. Record what you measured for each page.

  4. 4

    Fix what is shared before what is local

    Anything that appears on two or more pages lives in a shared layout, component or stylesheet. One change there clears all of them.

  5. 5

    Check again after every fix

    A fix counts when the same check is run again and passes. A new fault that appears straight after a fix was usually caused by that fix.

  6. 6

    Write down what you could not check

    A page behind a login, a form you could not submit, a site whose bot protection blocked the render. Those are unknowns. Hand them over as unknowns, not as passes.

Frequently asked

How many pages should I check before launch?
Every page a visitor can reach from the navigation and the footer. Checking only the home page checks the page that was always going to be fine. On our own site the home page scored 97 and an inner page scored 86.
Is a Lighthouse score enough?
It is a good check and worth running. It runs one page at a time, so it does not look for faults across pages, such as a title repeated on five pages or a page that lost the navigation. It also has no opinion on an invented testimonial.
Why check at 360px when most phones are wider?
Because a layout that holds at 360px holds at everything above it, and a layout tested only at 390px can still overflow on a narrower phone. Checking the narrow width is the cheap way to be sure.
Can my coding agent run this checklist by itself?
Part of it. An agent can read the code for titles, placeholder text and dead links. It cannot see a contrast ratio or an overflow without a browser or a tool that renders the page for it, which is why those are the faults that reach launch.
What score is good enough to launch?
On the Standout Score, 85 is the client-ready bar. A page above 85 with a blocker, such as a dead link or a failed phone layout, is still blocked. The number is never the whole answer.

more guides