Google doesn't index my React or Vite website: technical SEO diagnosis

Published on 2026-11-14 by frfrand

Guide to diagnosing why Google does not index a React/Vite SPA: rendering, HTTP codes, routes, metadata, sitemap, and Search Console.

# Google does not index my React or Vite website: technical SEO diagnosis

When a React/Vite application works in the browser but does not appear on Google, the problem is usually not solved by changing hosting. You need to separate discovery, crawling, rendering, indexing, and ranking. A URL can be indexed and still not receive visits.

1. Confirm the actual status in Search Console

Open URL Inspection with the exact address. Check if it is on Google, which canonical URL was selected, if it could be crawled, and if there are blocks. A live inspection serves to test current accessibility; it does not equal guaranteed indexing. Review Indexing > Pages and avoid interpreting “Discovered, currently not indexed” as an error exclusive to JavaScript.

Check with terminal:

curl -I https://ejemplo.com/servicios
curl -Ls https://ejemplo.com/servicios | head -c 2500
curl -I https://ejemplo.com/robots.txt
curl -I https://ejemplo.com/sitemap.xml
Replace the domain. The initial HTML may be just an empty container: Google can execute JavaScript, but dependency on resources, APIs, or hydration errors adds risks.

2. Check the rendered HTML

In URL Inspection > View tested page review capture and HTML. Verify the H1, descriptive text, links, and products. If the content requires authentication, user events, or requests that Googlebot cannot complete, do not assume it will be indexed. For commercial pages and stable editorial content, consider SSG, prerendering, or SSR. You do not need to migrate all of React: you can prerender only the SEO routes.

3. Metadata, routes and HTTP codes

Each route must have its own title and meta description, a coherent H1, and an absolute canonical link to the preferred URL. A SPA that always returns 200, even for non-existent routes, can generate soft 404s. Configure real 404 responses at the appropriate layer or a compatible rendering strategy. Avoid canonicalizing all cards to the home page. Check that internal links have real href attributes, not just buttons that change state via JavaScript.

4. Sitemap, robots and resources

Publish an XML sitemap with canonical URLs that return 200 and are worth indexing; declare it in robots.txt and submit it to Search Console. A sitemap suggests URLs, it does not guarantee indexing. Do not block scripts or styles necessary for rendering. Verify that there are no inherited noindex tags from staging or unexpected X-Robots-Tag headers.

5. Diagnosis by symptom

| Symptom | Check first | | --- | --- | | URL not discovered | Internal linking and sitemap | | Crawling blocked | robots.txt, firewall, HTTP | | Empty rendering | JS, API, resources, SSR/SSG | | Duplicate, Google chose another canonical | canonical and content | | Crawled, not indexed | Quality, duplication, usefulness | | Indexed, no clicks | Intent, position and snippet |

6. Correction and validation

Choose two representative pages, apply corrections and check HTML, HTTP response, links and Google view. Request reindexing once and monitor for days or weeks without promising dates. Document before and after: valid URLs, coverage, impressions and errors.

To publish a SPA, also consult React + Vite with Nginx and domain and SSR vs SSG. ArduMaker can be part of the deployment; indexability depends on the implementation, not the provider.

Frequently asked questions

Does Google execute JavaScript? Yes, but rendering can introduce delays and failures. Is Vite bad for SEO? No. The problem arises when the main information depends on inaccessible rendering. Is publishing a sitemap enough? No; crawlable, useful and canonical URLs are needed.

Technical source: https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics

  • React
  • Vite
  • indexación
  • SEO técnico
  • Search Console

Keep reading

All articles · VPS plans