surfup

JavaScript SEO: when to use SSR or prerendering

A checklist for checking server HTML, rendered content, links, and page metadata.

Search engines may crawl, render, and index JavaScript pages in separate stages. If the initial response is an empty app shell, important text and links depend on later rendering. SSR or static prerendering makes public content available earlier; use it where content is stable or search-critical.

Compare the raw HTTP response with the browser DOM and Google URL Inspection. Check status, title, canonical, main text, links, and hydration errors. Do not serve substantially different pages to crawlers; dynamic rendering adds maintenance and is not the default fix. Google’s JavaScript SEO guide

Steps to follow

  • Fetch the exact URL without running browser JavaScript.
  • Compare initial HTML with the rendered DOM.
  • Check that links use real href values and metadata agrees.
  • Use URL Inspection to verify Google’s rendered 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

Have a task? Write in Telegram — we reply within one working day.

Write in Telegram