Quick answer
A site built with JavaScript is not at a disadvantage in itself, but if the main content appears only after JavaScript runs, indexing may be delayed or some crawlers may be unable to read the content. Google processes JavaScript web apps in 3 phases, crawling, rendering and indexing, and rendering may be handled later. Crawlers other than Google's (including some AI crawlers) may not execute JavaScript, so it is safer to put important content in the HTML the server sends.
Key takeaways
- Google processes JavaScript in 3 phases: crawling, rendering and indexing
- Rendering may be handled later from a queue
- Some AI crawlers may not execute JavaScript
- It is safer to put important content and links in the HTML the server sends
How does Google process JavaScript sites?
Google processes JavaScript web apps in 3 phases: crawling, rendering and indexing.
With a plain HTML page, the document the crawler downloads already contains the main content, so it can be analyzed right away. By contrast, a page whose content is built only when JavaScript runs in the browser has to go through a rendering phase, in which Google executes the page, before its content can be seen. This rendering goes into a queue and may be handled later.
Google explains that server-rendered pages, where all the content is in the HTML of the HTTP response, are processed well. Google also does not guarantee that it will crawl or index a page, so having one more processing phase means one more point to check.
Do AI crawlers execute JavaScript too?
It varies by crawler, and crawlers other than Google's (including some AI crawlers) may not execute JavaScript.
Each AI service has its own crawlers, such as OAI-SearchBot for ChatGPT search, Claude's Claude-SearchBot and Perplexity's PerplexityBot. Each company's official documentation focuses on the bots' roles and how to control them with robots.txt, so as of writing (2026) the extent of their JavaScript processing is hard to state with certainty and may change.
So from a generative engine optimization (GEO) standpoint, it is safer to use this test: 'Can any crawler that arrives read the key content from the initial HTML response alone?' Google also advises, as a fundamental that applies to AI Overviews and AI Mode, making important content available in text form.
When does JavaScript become a problem?
It can become a problem when key elements such as the main content, links and titles are created only after JavaScript runs.
Google can generally crawl only links that are a tags with an href attribute. Links that work only through click events may look fine to people but can be a dead end for crawlers.
Google also uses mobile-first indexing, so the content of the mobile version as seen by its smartphone crawler is the baseline. Structures where content is left out only on mobile screens should be checked as well.
- The initial HTML response contains only an empty shell and the content is filled in after execution
- Menus and lists navigate only through click events, without an href on an a tag
- Titles, meta descriptions and structured data are inserted only after execution
- Key information sits in areas that load only after pressing a button or scrolling
What should a JavaScript site do about it?
The basic approach is to include key content in the initial HTML response through server-side rendering or prerendering.
Server-side rendering means the server builds and sends finished HTML, and prerendering means sending HTML files built in advance. Both let crawlers read the content without executing JavaScript. If changing the whole site is difficult, one option is to start with the pages where search traffic matters most.
This does not mean you should not use JavaScript. A common setup is to handle screen transitions and interactions with JavaScript while putting the body content, titles and links needed for search engine optimization (SEO) and answer engine optimization (AEO) in the HTML first.
How do you check whether the content is in the HTML?
You can check with your browser's view page source feature and the URL Inspection tool in Search Console.
View page source shows the HTML the server first sent. If you search there for a key sentence from the body and it does not appear, that content is created after JavaScript runs. In the URL Inspection tool in Search Console you can check the HTML Google received and the index status.
Frequently asked questions
Is SEO impossible for a single-page application (SPA)?
No, it is not impossible. Google can render and index JavaScript, and if you also use server-side rendering, other crawlers can read the content too. However, Google does not guarantee indexing, so it is best to confirm the actual result with the URL Inspection tool.
How much does the rendering queue delay indexing?
This article cannot state a fixed time. Google explains that rendering may be handled later from a queue. If your site needs new posts reflected quickly, it is better to put the content in the initial HTML response and not depend on the rendering phase.
Is text inside images read as well?
Google advises providing important content in text form and using high-quality images and videos to complement it. If key information exists only as text inside an image, crawlers may miss it, so it is best to also write the same content as body text.
Key entities in this article
- Search engine optimization (SEO) ( Concept or service )
- The work of helping search engines understand content and helping people find a site through search. Official source: Search engine optimization (SEO)
- Google ( Organization )
- The company behind Google Search, AI Overviews and AI Mode, which publishes official SEO guidance through Search Central. Official source: Google
- ChatGPT ( Concept or service )
- OpenAI's conversational AI service, which includes a search feature that answers with cited web results. Official source: ChatGPT
- Claude ( Concept or service )
- The conversational AI service made by Anthropic. Official source: Claude
- Perplexity ( Organization )
- The company behind an AI search service that shows its sources; it operates PerplexityBot and Perplexity-User. Official source: Perplexity
- robots.txt ( Concept or service )
- The file that tells crawlers which URLs on a site they may access, standardized as RFC 9309. Official source: robots.txt
- Generative engine optimization (GEO) ( Concept or service )
- The work of making content and brands more visible and more often cited in answers that generative AI builds from multiple sources. Official source: Generative engine optimization (GEO)
- AI Overviews ( Concept or service )
- The Google Search feature in which AI summarizes multiple sources and shows them with links. Official source: AI Overviews
- AI Mode ( Concept or service )
- The conversational AI search experience in Google Search for follow-up questions and complex comparisons. Official source: AI Mode
- Structured data ( Concept or service )
- Data that classifies page content in a standard format for search engines, mostly using the schema.org vocabulary. Official source: Structured data
- Answer engine optimization (AEO) ( Concept or service )
- Structuring content and information so search engines and AI can present it as the single answer to a question.
- Google Search Console ( Concept or service )
- Google's free tool for checking clicks, impressions and index status in Google Search. Official source: Google Search Console