Fix
Something's broken. Start from what you can see.
Rendering and indexing failures all look alike from the outside — traffic that should exist and doesn't. The diagnosis starts from the one thing you can actually observe: a Search Console status, a symptom in your browser, or your framework's specific failure mode. Pick yours below.
Indexing statuses
Search Console is showing you a status
These four look similar in the Pages report and have completely different causes. Getting the status right is half the diagnosis.
Crawled — currently not indexed
Google fetched the page, saw the content, and declined it. Usually quality or duplication — usually NOT rendering.
Discovered — currently not indexed
Google knows the URL and has never fetched it. A crawl-priority problem: links, budget, server health.
Googlebot can't see my content
The umbrella diagnosis: rendered late, blocked outright, or told to ignore it — three different fixes.
Meta tags not showing in Google
Either your tags never reach the HTML, or they do and Google rewrites them. Opposite fixes.
Visible symptoms
You can see something wrong
Symptoms you can reproduce in your own browser right now — each one narrows the cause differently.
View source is empty
What an empty source does and doesn't mean, the framework shell signatures, and when it's actually fine.
Blank page with JavaScript disabled
What the JS-disabled test really proves — it both over-reports and under-reports, and here's how to read it.
Hydration mismatch
Your server and browser render different pages, and a crawler can capture either. The only problem a green verdict can hide.
Framework-specific
It's your framework
The same indexing failure looks different in each stack — these pages speak your framework's language.
Not sure which symptom is yours?
Run a checkfirst — the verdict narrows it to two or three of these pages immediately. And if the diagnosis is clear but the fix isn't something you want to own, we fix rendering problems for a living.