JavaScript frameworks — React, Vue, Angular, Next.js — have become dominant in modern web development. But they create a specific SEO challenge: Google's crawler processes JavaScript differently from HTML, and many JavaScript-rendered pages are either not indexed, indexed with delay, or indexed without all their content.
To understand JavaScript SEO problems, you need to understand Google's two-wave indexing process.
Googlebot initially crawls your page's HTML source. For JavaScript-rendered pages, this HTML often contains little useful content — just the empty framework shell:
<html>
<head><title>My Site</title></head>
<body>
<div id="root"></div>
<script src="/static/js/main.chunk.js"></script>
</body>
</html>
After crawling, Google queues JavaScript-rendered pages for rendering — running the JavaScript, loading content, and capturing the fully rendered HTML in a headless Chrome browser.
The problem: Rendering is resource-intensive and placed in a queue. The delay between crawl and render can be days to weeks for new pages on sites with limited crawl budgets.
| What Google Can Process | What Still Causes Problems |
|---|---|
| Modern JavaScript (ES2020+) | Pages requiring user authentication (Googlebot doesn't log in) |
| React, Vue, Angular, and other major frameworks | Content requiring user interaction to load (infinite scroll below the fold) |
| Content loaded via API calls | Errors in JavaScript that prevent rendering |
| Most dynamically rendered content | Very large JavaScript bundles that time out during rendering |
| — | Content loaded from APIs with CORS restrictions on Googlebot |
How it works: Server sends minimal HTML shell. Browser downloads and executes JavaScript, which fetches data and renders the full page.
SEO problem: Google's first crawl sees the empty HTML shell. Full content only available after two-wave indexing with potential days of delay.
Used by: Standard Create React App, standard Vue CLI apps, Angular apps without server rendering
Recommendation: Avoid for pages that need to rank. If you must use CSR, implement at minimum <meta> tags and structured data in the initial HTML shell.
How it works: Each page request is processed on the server. Server executes JavaScript, fetches data, generates full HTML, and sends complete HTML to the browser.
SEO benefit: Google's crawler receives complete, rendered HTML immediately. No second-wave rendering required. Fast indexing, no rendering delays.
Used by: Next.js (with SSR), Nuxt.js (with SSR), Gatsby (partially), traditional server-rendered apps
Recommendation: Use SSR for all pages that need to rank in search. Next.js is the current gold standard for React SEO.
How it works: Pages are pre-rendered at build time and served as static HTML files.
SEO benefit: Same as SSR — Google gets complete HTML immediately. Additionally, static HTML is served extremely quickly (no server processing), which benefits Core Web Vitals.
Limitation: Not ideal for pages that require real-time data updates. Best for content that changes infrequently.
Used by: Next.js (with SSG), Gatsby, Astro, 11ty
How it works: Pages are statically generated at build time but can be regenerated in the background when content updates, on a configured interval.
SEO benefit: Static-speed delivery with near-real-time content updates. Ideal for frequently updated content (blog posts, product pages).
Used by: Next.js with revalidate parameter
Symptom: Google Search Console shows pages indexed but content missing from cached versions.
Diagnosis: Use URL Inspection in Search Console → "Test Live URL" → View the rendered HTML. Compare to your actual page — missing content identifies the rendering gap.
Fix: Move critical content to server-side rendering. For React: getServerSideProps for dynamic content, getStaticProps for static content.
Symptom: New pages take weeks to index while comparable HTML pages index within days.
Diagnosis: Check Crawl Stats in Search Console. Compare "Crawled pages" vs "Rendering" queue. Large rendering queues indicate Google is deferring your page rendering.
Fix: Implement SSR or SSG to eliminate the rendering requirement. Ensure fast server response (TTFB < 200ms) for SSR pages.
Symptom: URL Inspection shows rendered HTML as minimal or empty despite visible page content.
Diagnosis: Inspect the page in Chrome DevTools Console for JavaScript errors. These errors may not affect user experience (browsers are forgiving) but can prevent Googlebot's rendering.
Fix: Resolve JavaScript console errors. Test with Google's Mobile-Friendly Test and URL Inspection to verify rendering.
Symptom: Pages not being crawled despite existing on the site.
JS generates links like <Link to="/product/123"> (React Router). Googlebot needs to follow standard <a href="..."> tags to discover links. JS-generated navigation that doesn't produce standard anchor tags isn't followed.
Fix: Ensure all navigation links render as proper <a href="/url"> HTML in the server-rendered HTML. React Router, Vue Router, and Next.js Link components all render standard anchor tags correctly — verify yours do too.
Symptom: Google indexes your pages with wrong titles, descriptions, or missing metadata.
Fix: Use server-side metadata rendering:
<Head> component or new metadata exportreact-helmet but accept that there may be delaysvue-metaWordPress doesn't face most JavaScript framework SEO issues by default — WordPress renders PHP server-side and delivers complete HTML. However, JS SEO challenges appear in specific WordPress contexts:
These builders load significant JavaScript that can slow page rendering (INP impact), delay content visibility (LCP impact), and load content conditionally in ways that affect Googlebot.
Fixes:
Headless WordPress delivers content via API to JavaScript frontends. This is the exact JS SEO scenario described in this guide.
Recommendation: Use Next.js with SSG or SSR for the frontend. This gives you WordPress's CMS capabilities with React's flexibility and server-rendered SEO.
Some WordPress plugins and themes load content via AJAX (dynamically after page load). Googlebot may not capture AJAX-loaded content if it doesn't render.
Fix: Verify AJAX-loaded content is captured by URL Inspection in Search Console. If not, implement server-side rendering or pre-population of the critical content.
| Category | Check Items |
|---|---|
| Rendering | Critical content is server-rendered or statically generated · URL Inspection shows correct rendered HTML · No console errors · Navigation links render as standard <a href> tags |
| Meta & Structured Data | Meta titles in initial HTML · Meta descriptions in initial HTML · JSON-LD structured data in initial HTML · Open Graph tags in initial HTML |
| Performance | Core Web Vitals passing (especially INP) · JS bundles split and loaded efficiently · Third-party scripts loaded asynchronously |
| Indexing | XML sitemap includes all important pages · Pages indexed with correct content · No 404 errors from JS-generated navigation |
JavaScript SEO is a technical discipline that's increasingly important as JavaScript frameworks dominate modern web development. The core principle is simple: Google needs to see your content in the initial HTML response. Anything that delays that — client-side rendering, JavaScript errors, render-blocking scripts — hurts your indexing and rankings.
For new projects, choose Next.js or Nuxt.js with SSR/SSG. For existing projects, audit with URL Inspection to identify rendering gaps, then implement fixes in priority order.
Contact us for JS SEO audit and headless WordPress development