surfup

Run a technical SEO release smoke test

Catch broken routes, metadata, index controls, and internal links on representative templates.

Use the procedure on a representative sample, keep the evidence, and record the next action.

Verify a release by page type

  • Sample home, category, detail, article, search, and form routes. Include one mobile viewport and one direct URL load per important type.
  • Check status codes, canonical, title, description, H1, robots directives, sitemap presence, and language alternates where relevant.
  • Follow primary user paths: navigation, internal links, form success/error, consent, keyboard operation, and no horizontal overflow.
  • Save URL, device, result, screenshot or response, severity, and owner for every issue; retest fixes before closing the release.

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