No, JavaScript isn't bad for SEO in itself. Google runs JavaScript with an up-to-date version of Chromium and can index content that JavaScript adds to a page. The risk is in how a site uses it: content that only appears after a click, links Google can't follow, error pages that look like real pages, and crawlers that don't run JavaScript at all. The safest setup is simple to describe: your main content, links, title, canonical and status code should already be in the HTML the server sends.
This guide explains how Google processes JavaScript, the mistakes that cause problems, which rendering approach to choose, and how to check your own site without being a developer.
Can Google read JavaScript websites?
Yes, with an extra step. Google's JavaScript SEO basics guide describes three phases: crawling, rendering and indexing.
- Crawling. Googlebot requests the URL, after first checking robots.txt. If the URL is disallowed, Google doesn't fetch it and won't render it.
- Rendering. Every page that returns a 200 status code goes into a rendering queue, unless a robots meta tag or header says not to index it. Google says a page may wait there for a few seconds, "but it can take longer than that." A headless Chromium browser then loads the page and runs its JavaScript.
- Indexing. Google uses the rendered HTML to index the page and looks through it again for new links to crawl.
So a site that builds its content in the browser can still be indexed. The catch is that everything Google learns about the page now depends on that rendering step working. If the content is already in the first HTML response, Google gets it on the first pass. Our Academy lesson on how search engines work covers crawling and indexing in more depth, and our glossary entry on JavaScript SEO gives the short version.

Why do JavaScript websites still have SEO problems?
Because Google's renderer behaves like a browser that nobody is using. It doesn't click, scroll, accept prompts or remember anything between pages. Most JavaScript SEO problems come from forgetting that. Google's guide to fixing JavaScript problems and its related documentation list the usual culprits:
- Content that waits for a click or scroll. Google says it "does not interact with your page." Tabs, "load more" buttons and lazy-loading that relies on scrolling can hide content. Google's lazy-loading guidance recommends loading content when it's visible in the viewport, and giving infinite-scroll chunks their own URLs.
- Links that aren't real links. Google's link best practices say it can generally only crawl an
<a>element with anhref. Buttons or spans with click handlers may never be followed, which leaves pages undiscovered and weakens internal linking. - Hash URLs for different pages. Addresses like
example.com/#/productsdon't work reliably. Google deprecated the old AJAX crawling scheme in 2015 and recommends the History API instead. - Error pages that return 200. Single-page apps often show a "not found" message while the server says everything is fine. Google calls these soft 404s, and they can end up indexed. The fix is to redirect to a URL that returns a real 404, or add a noindex tag to the error view.
- A noindex tag that JavaScript is meant to remove. When Google sees noindex in the original HTML, it may skip rendering, so script that removes the tag later may never run.
- Canonical tags that change after rendering. Google says JavaScript shouldn't change the canonical tag to a different URL from the one in the original HTML.
- Blocked script files. If robots.txt blocks the JavaScript a page needs, Google can't render it properly.
- Content that depends on stored state or permissions. Google's renderer clears cookies and local storage between page loads and declines permission requests such as camera access.
- Stale files. Googlebot caches aggressively and may ignore caching headers, so Google recommends fingerprinted file names (like
main.2bb85551.js) so updates are picked up.
If pages aren't appearing at all, start with our guide to why a page isn't indexed, since JavaScript is only one possible cause.






