surfup

30 launch checks

Review content, technical foundations, security, accessibility, and analytics before launch.

Use these steps as a working checklist and adapt them to the project’s evidence, scope, and constraints.

Routes and responses

  • Open the home page directly and through an internal link.
  • Open every public route directly.
  • Confirm an unknown route displays a useful 404 page.
  • Check the final HTTP status of each important page.
  • Repeat direct-route checks against the production build.

Page metadata and content

  • Check for a unique title on every indexable page.
  • Check descriptions for clipped or generic template text.
  • Confirm each page has one clear primary heading.
  • Compare canonical with the intended preferred URL.
  • Check that structured data matches visible page content.

Indexing and discovery

  • Confirm robots.txt is reachable and has the intended rules.
  • Confirm the sitemap opens and contains only intended URLs.
  • Compare hreflang sets and x-default across language alternatives.
  • Follow redirect chains and look for loops.
  • Confirm important pages can be reached through ordinary links.

Links, controls, and forms

  • Check internal links for 404 responses and incorrect domains.
  • Use the menu and language switcher with pointer and keyboard.
  • Submit the form with valid and invalid values.
  • Check loading, success, and error states for the form.
  • Confirm consent is required wherever applicable.

Responsive layout and keyboard

  • Review the page at a 320-pixel viewport width.
  • Repeat at a 375-pixel viewport width.
  • Check a tablet viewport and ensure there is no horizontal overflow.
  • Enlarge text and confirm buttons do not overlap.
  • Complete the main flow using only a keyboard.

Accessibility, privacy, and evidence

  • Check field labels and accessible names for buttons.
  • Review text contrast and visible focus styling.
  • Confirm essential content is available without required animation.
  • Ensure secrets and personal data are absent from public assets.
  • Save a record with URL, time, device, expected result, and actual result.

Latest materials

All materials

Practical articles and guides by SurfUp.

Guide · 10 min

“What is…” pages and AI answers: lost clicks or falling demand

A bank’s reference section lost 24% of visits as demand fell 13%. How to tell clicks lost to an AI block from falling demand and how to measure it.

Read
Guide · 8 min

Traffic dropped after a Google update

How to tell whether a traffic drop comes from a Google update, seasonality or a site fault. 2026 update timeline, a six-question check and a plan for the first 14 days.

Read
Guide · 9 min

Demand fell or the site lost: reconciling traffic with Wordstat

Demand for deposits fell 75%, traffic 37%; for cards demand −35%, traffic −63%. How to reconcile traffic with demand and not blame the site for the market.

Read