GSC Says "Page Indexed Without Content" and Rankings Tank? Google's Official Answer: Stop Blaming JavaScript — Check Your CDN!

Hi everyone, this is Neo.

For anyone running an independent site, the scariest things besides getting banned are probably those red errors in GSC (Google Search Console).

Lately, one error in particular has been giving people heart attacks — “Page Indexed without content”.

What the heck is this? The page looks totally fine, the content is all there — so why does Google say there’s “no content”?

Even scarier: once this error shows up, rankings tend to fall like a roller coaster.

Case in point: a guy on Reddit recently freaked out. His homepage was ranking #1, then suddenly this error appeared and his ranking dropped straight to #15.

He panicked, searched everywhere, and couldn’t find the cause. Finally, Google Search Advocate John Mueller himself stepped in and revealed the truth.

Today, Neo is going to dig into the real cause of this error, and how to save yourself.

01 A Common Misconception: Is JavaScript Rendering to Blame?

When you see “page without content,” what’s your first reaction?

Most people’s instinct is:

  • “Did my JavaScript fail to load?”
  • “Did the page break during rendering and turn into a blank screen?”
  • “Did Google’s crawler get dumber?”

So everyone starts frantically checking front-end code, testing JS rendering, even suspecting their SPA (single-page application) framework.

But in that Reddit case, the guy ran the same tests. He simulated Googlebot fetching with curl, tested with Google’s rich results tool, and even used various third-party SEO tools.

And the result? Everything was normal. Every external tool showed the page content loading perfectly.

Yet GSC stubbornly kept saying: “Page indexed without content.”

02 Google’s Official Reveal: Check Your Server and CDN!

Watching people flail around like headless chickens, John Mueller finally couldn’t take it anymore. He replied directly to that user on Reddit with the authoritative explanation.

Here’s what Mueller said:

“Usually this means your server / CDN is blocking Google from receiving any content. This isn’t related to anything JavaScript.”

Translation: usually your server/CDN is blocking Google from receiving any content. It has nothing to do with JavaScript.

Key takeaway: this is not a front-end rendering problem — this is a block at the server/CDN level!

Mueller went on to explain that this kind of block usually happens at a very low level, often based on Googlebot’s IP address.

That’s why your own tests (from your IP) and third-party tools (from their IPs) all look fine — but Googlebot gets shut out when it tries to visit.

03 Why Does This Happen?

You might ask: “Am I crazy? Why would I block Googlebot?”

Of course, nobody intentionally blocks the goose that lays golden eggs. This is usually collateral damage.

In the Reddit case, the affected site was built with Webflow and used Cloudflare as its CDN.

Mueller pointed out that the culprit is likely certain CDN security settings, such as:

  • WAF (Web Application Firewall) rules: An overly strict firewall can mistake Googlebot for a malicious crawler.
  • Bot Fight Mode: CDNs like Cloudflare all have this feature. If it’s misconfigured, or the CDN provider updates its rules, Googlebot can get caught in the crossfire.
  • IP access controls: Some rules may inadvertently block Google’s crawler IP ranges.

Especially when your rankings suddenly plunge with zero code changes, this kind of “accidental kill” at the infrastructure level is the prime suspect.

Mueller warned: “This means pages on your site are going to start dropping out of the index (soon, or already happening), so you should treat it as an emergency.”

04 One Tactic for a Precise Diagnosis

Since external tools are all unreliable, who can we trust?

John Mueller gave the one authoritative answer: the “URL Inspection Tool” in Google Search Console.

That’s the only tool that truly sees things from Googlebot’s perspective.

Steps:

  1. Open GSC.
  2. Enter the erroring URL in the search box at the top.
  3. Click “Test Live URL”.

If it shows “Something went wrong” or can’t fetch content, while the page loads fine in your browser — congratulations (or condolences) — you’ve indeed run into a server/CDN block.

Don’t blindly trust any third-party SEO tool (Ahrefs, Semrush, Screaming Frog, etc.) on this issue — they can’t simulate the real blocked scenario Googlebot faces.

05 How to Fix It

Once you’ve found the root cause, the fix has direction. If your site is hitting this too, here’s the troubleshooting order Neo recommends:

  1. Check your CDN settings: If you use a CDN like Cloudflare or AWS CloudFront, see whether you’ve enabled any new security modes recently (like Super Bot Fight Mode).
  2. Review firewall logs: Search your server’s or CDN’s WAF logs for records of Googlebot being blocked.
  3. Whitelist Googlebot IPs: Google publishes the IP ranges of its crawlers. You can whitelist those ranges in your firewall or CDN.
  4. Contact your provider: If you use a SaaS site builder (like Shopify or Webflow), reach out to support and ask whether they recently adjusted their security policies.

Neo’s Take

This incident reminds us again that SEO isn’t just about content and backlinks — the stability of your technical infrastructure matters just as much.

A lot of owners and operators only watch keyword rankings while ignoring the underlying server configuration. When you see rankings inexplicably plunge and GSC throws errors you don’t understand, don’t just go hunting through your page code.

Step out of the code and look at the network layer — the truth might be hiding in that silently-working CDN.

Summary of today’s key points:

  1. GSC’s “page indexed without content” error usually means your server/CDN is blocking Googlebot.
  2. Don’t blame JavaScript — this usually isn’t a rendering issue.
  3. Don’t trust external tools, because they don’t use Googlebot’s IP.
  4. The only truth: diagnose with GSC’s “URL Inspection” feature.
  5. Where to look: firewall rules, CDN bot protection modes, IP blacklists.

Hope this article helps anyone pulling their hair out over GSC errors.

I’m Neo — our goal is to make running an independent site simpler. See you next time!

References: