` and a script bundle reference. Content only exists after JS executes in the browser. My App

Bots don't dependably execute your JS. Even when they do, it's delayed and inconsistent. What actually gets indexed is the initial HTML — and whatever text exists at response time. If that HTML has: - <200 characters of visible text - No `

` - No internal links …it is treated as empty. No text, no links, no structure → no indexing. Companion read: [Why Google Can't See Your SPA](https://datajelly.com/blog/why-google-cant-see-your-spa) . ## Step 1: Inspect Raw HTML (Not the Rendered DOM) The most common debugging mistake: opening DevTools and inspecting the Elements panel. That shows the post-JS DOM. Bots don't see that. They see the raw response. Run: curl -A "Googlebot" https://yoursite.com -o page.html wc -c page.html # byte count grep -o '` or paragraphs → failure If you don't see real content in raw HTML, stop. That's the root cause. Everything else is downstream of this. ## Step 2: Measure Content (Real Thresholds) Stop guessing. Use real numbers. These are the production thresholds we apply to every site we audit: | Metric | Healthy | Suspicious | Broken | | --- | --- | --- | --- | | html\_bytes | 20KB+ | 5–15KB | < 5KB | | visible\_text\_length | 1,500+ chars | 200–800 chars | < 200 chars | | word\_count | 300+ | 50–200 | < 50 | | internal\_links | 10+ | 1–5 | 0 | What we see in production: - • <200 chars → indexed as blank - • <1KB HTML → guaranteed no indexing - • 0 internal links → no crawl discovery The [Page Validator](https://datajelly.com/seo-tools/page-validator) applies these exact thresholds for you and flags pages as `blank_page` or `script_shell_only`. ## Step 3: Identify Script Shell Pages Script shells have a clear pattern. If your raw HTML matches this, you have one: HTML size: ~3KB