Broken SSR: when your server sends Google an empty page

In brief

Broken SSR means your server returns near-empty HTML, so Google indexes a page with no content even though the site renders fine in a browser. You need to fix server-side rendering so the content is present in the raw HTML, before any JavaScript runs.

CriticalP1 — Direct ranking

What is it?

The HTML returned by your server is nearly empty, even though the page works in the browser.

Why it hurts SEO and AI

Google indexes the raw HTML first: it sees an empty page until the second rendering pass (24 hours to several weeks later). AI systems (ChatGPT, Perplexity, Claude) execute little or none of your JavaScript: to them, this page is nearly empty. This is the typical SSR failure that goes unnoticed because the site "works" visually.

When it is NOT a problem

  • The page is intentionally client-rendered and not meant to be indexed (app interface, back office).
  • The main content is in the raw HTML and only a secondary part (widget, recommendations) is injected with JavaScript.
  • You are on the very first crawl of a new page: Seogard does not alert until it has a baseline.
Before
<!-- HTML returned by the server -->
<div id="app"></div>
<script src="/app.js"></script>
After
<!-- HTML returned by the server -->
<main>
  <h1>Trail running shoes</h1>
  <p>Our selection of shoes…</p>
</main>

On the left, all content depends on JavaScript. On the right, it is already in the raw HTML that Google and AI systems read first.

How to fix it

  1. Open the page’s real source (right-click → "View page source", not the inspector): the main content should be there.
  2. Find the server-side cause: rendering error, failed hydration, data timeout, or SPA fallback.
  3. Fix server-side rendering so the response HTML contains the content, then redeploy.
  4. Re-crawl the page to confirm the raw HTML is no longer empty.

This scan checks what is missing from the raw HTML but appears in the JavaScript render

Is this issue on your site?

Is your raw HTML empty on some pages? Enter a URL: Seogard compares what your server returns with what the browser renders, and tells you in 30 seconds whether Google sees a blank page. Free, no credit card.

By clicking Scan, I certify that I own this site or have permission to crawl it.

  • No credit card
  • Result in ~30 s

What you get back

Google indexes the real content on the first pass and AI systems can finally read and cite the page.

Seogard catches this regression automatically — through its SSR checker.

Frequently asked questions

How do I know if my SSR is broken?

View the page source (Ctrl+U) without running JavaScript: if the main content is missing, your server is returning an empty page to Google.

Does Google eventually see JavaScript-rendered content?

Yes, on its second rendering wave — often within seconds, but the delay can stretch to days or weeks depending on site size and crawl priority, and the render is never guaranteed. AI answer engines, on the other hand, almost never run it.

Related rules

Page redirectedA page still declared in your sitemap has started redirecting to another URL: the sitemap presents an address that bounces as canonical. Intentional removal — take it out of the sitemap; otherwise, often a broken route. A page that is redirected AND removed from the sitemap is a clean removal: no alert. JavaScript redirectThe page responds 200 but its JavaScript redirects the browser elsewhere. Google only follows it after rendering (delayed, or never if rendering fails) and AI systems read the original HTML, not the destination: machines and humans see two different pages. Broken redirectA cleanly removed page (redirect + removed from the sitemap) now returns a 4xx error: its redirect broke. Link equity from backlinks pointing to the old URL is no longer passed — typically a refactor that deleted the redirect rule or its target.

Updated July 10, 2026