javascript-seo

name	javascript-seo
description	Use when running JS-heavy framework. Google can render JS but limitations apply.

JavaScript SEO

Google renders JS (2-stage indexing). JS-rendered content takes 1-30 days to index vs HTML's hours. Critical content should be in HTML, not JS-only.

Google's two-stage indexing

Stage 1: HTML crawl (immediate) Stage 2: JS render (1-30 days later)

Meaning: content rendered only by JS is indexed slower. Critical content (price, title, key keywords) should be in HTML.

JS-SEO best practices

1. Server-side render (SSR) or pre-render critical content
2. Use Hybrid (SSG + client hydration)
3. Avoid SPA routing for content pages
4. Test with View Source — is content there?
5. Test in Search Console > URL Inspection > 'View tested page'

Anti-patterns

1. SPA where every page has same HTML (URL changes via JS only)
2. Content rendered only after user interaction
3. Lazy loaded content below-fold (LLM and crawl issues)
4. Heavy JS that blocks rendering >3s
5. Cookie wall before content

Where this fits in the X3 empire

JS-SEO considerations for CardPrepAI tools and interactive surfaces.