The Pre-Launch Check: Desktop, Mobile, Flows

Open the priority pages on desktop and check the basic website experience before judging quality.

Confirm layout, navigation, page hierarchy, spacing, media, links, calls to action, forms, footer, hover states, and the main conversion path.

Look for broken layout, repeated content, missing sections, dead links, weak trust signals, or copy that no longer matches the offer.

Mobile needs its own pass because many launch issues only appear on small screens.

Check the menu, text wrapping, tap targets, sticky elements, forms, media crop, button visibility, section order, and whether key content appears before weaker supporting content.

The goal is not to make mobile identical to desktop. The goal is to confirm that the mobile visitor can understand the offer, move through the page, and take action without friction.

After layout checks, follow the actual journeys a visitor might take.

Check whether a first-time visitor can understand the offer, move from the homepage to a priority page, use the navigation, complete a form, reach a confirmation state, and recover if something does not work.

Flow issues are launch risks because they block action. Treat broken forms, unclear next steps, confusing menus, mismatched calls to action, and dead-end pages as higher priority than visual preferences.

Keep this pass factual and evidence-based. Do not turn it into a long strategy audit.

For SEO and AEO, check titles, descriptions, headings, internal links, answer-style sections, crawlability, indexation rules, canonical logic, and obvious schema candidates.

For accessibility, check contrast, keyboard access, focus states, alt text, labels, heading order, readable structure, and touch targets. For consent, check analytics events, form tracking, cookie banner behaviour, blocked scripts, cookie categories, and external setup notes.