Here, JavaScript “rendering” means executing JavaScript to generate or update web page content. Browsers display dynamic content to users; search engines also need to crawl URLs, schedule rendering, and then process the content for indexing. So content being visible in a browser does not mean a search engine has indexed it. Google can execute JavaScript, but blocked access, rendering delays, and implementation issues can still affect its ability to retrieve content. You should not assume that all search engines have the same capabilities.
The initial HTML determines whether content must wait for JavaScript
Google’s official documentation distinguishes between two scenarios. On traditional websites or server-rendered pages, the HTML in the HTTP response already contains the content. On some JavaScript websites, the initial HTML contains no actual content, so code must run to make it available.
For example, if a product description is dynamically generated by client-side JavaScript, a search engine that has retrieved only the initial HTML cannot yet see that description; it needs to complete rendering. If the description is already in the HTML returned by the server, the search engine does not need to rely on that code to access the text. The distinction is when important content becomes available, not whether the website uses JavaScript.
Google queues pages for rendering; fetching is not indexing
According to Google’s official explanation, processing has three main stages:
- Crawling: Google first checks whether robots.txt allows access, then retrieves the page and parses its links. Google will not render JavaScript in blocked pages or files.
- Rendering: Unless a robots meta tag or header instructs Google not to index the page, pages with an HTTP 200 status enter the rendering queue. When resources are available, headless Chromium executes the JavaScript. Rendering may be skipped for non-200 pages.
- Indexing: Google uses the rendered HTML to process the content for indexing and adds links found in it to the crawl queue.
The wait in the rendering queue may last a few seconds or longer; this is separate from any limit on JavaScript execution time. As for execution time, in a test by Dave Smart reported by Search Engine Journal in 2026, two API calls could take a combined six to twelve seconds, yet the delayed content still appeared in the rendered DOM. This finding does not support the claim that “anything taking more than five seconds will definitely be missed,” but it also does not guarantee that all delayed content will be processed.
For SEO, check content access first, then performance
Speed is not the only risk: if a search engine cannot retrieve core text correctly, that content may not be indexed. Poor JavaScript implementation can also slow loading. This does not mean that using JavaScript inevitably lowers rankings.
- Make main content available early: Google still recommends server-side rendering or prerendering to help users and crawlers access content faster and to make it available to bots that cannot execute JavaScript.
- Check the version search engines see: Use Search Console’s URL Inspection tool to review the rendered output and check whether it includes important text and links. Do not assume that search engines can access the content simply because the page looks correct in your browser.
JavaScript rendering: perspectives from across the web
Does Google consider dynamic rendering to be cloaking?
Not necessarily. Dynamic rendering can provide a suitable version, such as static HTML, to crawlers that cannot execute the required JavaScript. Google says it generally does not consider this cloaking as long as the content served is similar. However, deliberately serving entirely different content to users and crawlers may be considered cloaking. Any error pages generated are treated as ordinary error pages.
Besides server-side rendering, how can websites accommodate situations where JavaScript cannot run?
Consider progressive enhancement or graceful degradation. These approaches can keep website content usable when JavaScript is disabled or a browser’s implementation is incompatible, and make it accessible to some search engines that cannot execute scripts. They do not guarantee a solution to every crawling issue. Sites that rely on client-side rendering, in particular, should still check for JavaScript errors and content accessibility, and confirm whether their content is fully displayed and indexed.
Can Bing’s JavaScript processing capabilities be assumed to match Google’s?
No. In 2018, Screaming Frog cited confirmation from Bing staff in 2017 that Bing processed JavaScript. However, its observations from a small sample were inconsistent, and the author could not fully confirm whether all the sites tested relied exclusively on client-side rendering. These results reflect only the tests and limitations at that time; they should not be treated as evidence of Bing’s current capabilities or as official rules.
References
- 瞭解 JavaScript 搜尋引擎最佳化 (SEO) 基礎知識 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- 使用動態轉譯功能做為暫時替代方案 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Does Google consider dynamic rendering to be cloaking?
- JavaScript Rendering: What It Is and How to Handle Itwww.semrush.com · 2023-04-03T15:07:00Z — Source used in the article above.
- Is Bing Really Rendering & Indexing JavaScript?www.screamingfrog.co.uk · 2018-06-13T13:08:23+00:00 — Discusses: Can Bing’s JavaScript processing capabilities be assumed to match Google’s?
- Google SEO Test Shows What Happens In 5-Second Rendering Windowwww.searchenginejournal.com · 2026-07-28T09:45:32+00:00 — Source used in the article above.
- JavaScript SEO 是什麼?9 技巧教你優化網頁welly.tw · 2025-01-22T08:30:20.845Z — Source used in the article above.
- Conducting an SEO Content Audit: 6 Things You Might Be Overlookingwww.screamingfrog.co.uk · 2021-11-15T13:37:48+00:00 — Discusses: Besides server-side rendering, how can websites accommodate situations where JavaScript cannot run?
- Does the Google spider render JavaScript?webmasters.stackexchange.com — Discusses: Besides server-side rendering, how can websites accommodate situations where JavaScript cannot run?



