Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

JavaScript SEO Audit: Check That Google Sees Your Content

Updated · 8 min read

Short answer Open your page source and search it for a sentence from the page. If the text is there, JavaScript isn't hiding it. If not, run Search Console's live test and check the rendered HTML for your text, links, title, canonical and noindex. Most AI crawlers, including ChatGPT's and Claude's, don't run JavaScript, so key content belongs in the HTML.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

Does my website need a JavaScript SEO audit?

Only if your words or links appear after the page loads instead of arriving with it. Find out in two minutes, no tools needed:

  1. Open a service page in Chrome on a computer and press Ctrl+U (Cmd+Option+U on a Mac). That shows the raw HTML your server sends, the first thing a crawler gets.
  2. Press Ctrl+F and search for a sentence from the middle of the page, then for the address of a page your menu links to.
  3. Repeat on your home page and one blog post.
What you findWhat it meansNext step
Your text and links are all in the sourceJavaScript isn't hiding anythingNo JavaScript audit needed; any ranking issue lies elsewhere
Some text is missing (reviews, prices, FAQ, a menu)Those parts are added by scriptsAudit those parts
The source is nearly empty, mostly script tagsThe whole site is built in the browser (a "single-page app")Run the full audit below

Custom sites built in React, Vue or Angular are the usual "nearly empty" case. Template-builder sites can still load parts by script, such as review feeds, booking embeds or menus. Check rather than assume.

How does Google read a JavaScript page?

In three phases: crawl, render, index. Google's JavaScript SEO basics explain that Googlebot first fetches the HTML and collects its links, then queues the page so a headless Chromium browser can run the scripts, and finally indexes what that rendered version shows. Two details matter for an audit:

  • Rendering waits in a queue. Google says a page may wait "a few seconds, but it can take longer than that". A 2024 study by Vercel and MERJ of over 37,000 renders on nextjs.org measured a median wait of 10 seconds and about 18 hours at the 99th percentile. Long waits are rare, but they happen.
  • Only pages with a 200 (success) code are sure to be queued. Google sends every 200 page to rendering, but on an error page such as a 404, "rendering might be skipped".

Google also never clicks or scrolls. Its lazy-loading guide says "Google Search does not interact with your page." Anything that appears only after a click is invisible to it.

The audit: seven checks on your top pages

You need Search Console access (or Google's free Rich Results Test, which needs none) and 30 minutes. Do your five most important pages first: home, top services, contact.

#CheckHowPass
1Rendered textSearch Console, URL Inspection, Test live URL, View tested page, HTML tabEvery heading and paragraph you care about is in it
2ScreenshotSame panel, Screenshot tabThe page looks complete, not blank or half-built
3ErrorsSame panel, More info: page resources and JavaScript console messagesNo blocked scripts, no errors on files that build content
4LinksSearch the rendered HTML for your menu linksEach is a standard link tag with an href (address), not a button
5TagsCompare title, meta description, canonical, robots tags and structured data in source vs renderedThey match, and no noindex on a page you want found
6Error pagesOpen a made-up address, like yoursite.com/zzz-testA "not found" page that returns code 404, or carries noindex
7Hidden contentLook for tabs, "load more" buttons and endless scrollThe content is in the rendered HTML without a click

Google's troubleshooting guide names these same tools: the URL Inspection tool or the Rich Results Test show "loaded resources, JavaScript console output and exceptions, rendered DOM". Search Console Help adds that the screenshot exists only in a live test, and that the default inspection view shows the last indexed version, "not the live version on the web".

For check 6, ask your developer or use a free "HTTP status checker" site. A missing page that returns 200 is a "soft 404": Google may index your error page as if it were real content.

What problems does the audit usually find?

ProblemWhat Google saysFix
Menu built from buttons, not linksGoogle can generally crawl only a standard link tag with an href addressReal links; scripts can still handle the click
Page addresses with `#/` (like site.com/#/services)Googlebot "can't reliably resolve" them; use the History API insteadGive each page its own address
noindex in the HTML, removed later by scriptRendering may be skipped, so removal "may not work as expected"Leave noindex out of the HTML on pages you want found
Canonical changed by scriptDon't change it to a different URL from the one in the HTMLSet it once, in the HTML
Content loads on scroll or clickLoad content when it is visible in the viewport; give each chunk of endless scroll its own URL, like ?page=2Ask your developer to follow Google's lazy-loading guide
robots.txt blocks script filesGoogle "won't render JavaScript from blocked files"Allow your JavaScript and CSS folders
Old scripts after an updateGooglebot caches aggressively and may use outdated filesFingerprinted filenames, like main.2bb85551.js

The noindex row causes the most damage, and Google's wording is exact:

"When Google encounters the noindex tag, it may skip rendering and JavaScript execution, which means using JavaScript to change or remove the robots meta tag from noindex may not work as expected." (Google Search Central: Understand the JavaScript SEO basics)

Tabs and accordions are fine when their text is already in the rendered HTML, just folded away. Text fetched only on a click is the problem.

Do ChatGPT and other AI crawlers see JavaScript content?

Mostly no. Vercel and MERJ's December 2024 study of AI crawler traffic found that none of the major AI crawlers render JavaScript, naming OpenAI's GPTBot, OAI-SearchBot and ChatGPT-User, Anthropic's ClaudeBot, Meta's crawler and PerplexityBot. They fetch script files but don't run them. Gemini uses Googlebot's infrastructure, and Applebot renders pages like a browser. The study dates from late 2024 and crawlers change, but don't count on them running your scripts.

So a page that passes Google's live test can still look empty to an AI assistant. If you want to be recommended in AI answers, your services, areas and prices belong in the HTML itself. Where those assistants get local business facts is covered in where ChatGPT finds local businesses.

How do I fix JavaScript SEO problems?

Have the server send the finished HTML. Google's advice:

"Keep in mind that server-side or pre-rendering is still a great idea because it makes your website faster for users and crawlers, and not all bots can run JavaScript." (Google Search Central: Understand the JavaScript SEO basics)
ApproachWhat it isGoogle's view
Server-side renderingThe server builds each page's HTML on requestRecommended
Static rendering (pre-rendering)Pages are built into HTML files ahead of timeRecommended
HydrationHTML first, then scripts add interactivityRecommended
Dynamic renderingBots get one HTML version, people get the script versionA retired workaround
"Dynamic rendering was a workaround and not a long-term solution for problems with JavaScript-generated content in search engines." (Google Search Central: Dynamic rendering as a workaround)

Ask your developer which of these your framework supports; it may be a setting rather than a rebuild. After the fix, run the live test again on the same pages.

Which tools do I need?

ToolCostWhat it doesLimit
View source (Ctrl+U)FreeShows the HTML before scriptsNot what Google renders
Inspect (right-click, Inspect)FreeShows the page after scripts run in your browserYour browser, not Googlebot
Search Console URL InspectionFreeGoogle's own render, screenshot and errorsOne URL at a time; needs site access
Rich Results TestFreeGoogle's render for any public URLOne URL at a time
Screaming Frog SEO Spider£199 a year for JavaScript renderingRenders every page and comparesThe free version doesn't include JavaScript rendering

Screaming Frog's user guide lists JavaScript rendering among the features a licence unlocks. A 10-page site doesn't need it.

Example

Illustrative cases with invented numbers.

A law firm's 12-page site on a template builder

The owner finds every paragraph in the page source, but the Google reviews widget isn't there. The audit stops: nothing important depends on scripts. The reviews still show on the Business Profile.

A remodeler's custom React site

The source is nearly empty. The live test shows full text, but the menu items are buttons, and only 4 of 30 pages are indexed. The developer swaps the buttons for real links and turns on static rendering. A month later the Page indexing report shows 28 indexed.

FAQ

Can Google index JavaScript content?

Yes. Google renders pages in an up-to-date Chromium, but after a queue, without clicking, and maybe not at all on noindex or error pages.

Is JavaScript bad for SEO?

No. Scripts that add features to a page with real HTML cause no harm. The risk is content or links that exist only after scripts run.

Is "view page source" the same as what Google sees?

No. Source shows the HTML before scripts; Google indexes the rendered version. Compare both, and use URL Inspection for Google's own render.

How often should I run a JavaScript SEO audit?

After any redesign, platform move or framework upgrade, and whenever indexed pages fall in Search Console. Otherwise, live-test your top pages quarterly.

Different for you?

Keep learning

NextSPA SEO: how to get a single-page app indexed by GoogleWhy React, Vue and Angular sites go missing from search, how to test what Google sees, and the fixes: server rendering, real URLs and per-page meta tags.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Understand the JavaScript SEO basics
  2. Google Search Central: Fix Search-related JavaScript problems
  3. Google Search Central: Dynamic rendering as a workaround
  4. Google Search Central: Fix lazy-loaded content
  5. Google Search Central: Link best practices for Google
  6. Search Console Help: URL Inspection tool
  7. Vercel and MERJ: How Google handles JavaScript throughout the indexing process (July 2024)
  8. Vercel and MERJ: The rise of the AI crawler (December 2024)
  9. Screaming Frog: SEO Spider user guide, General