Does your site use JavaScript (JS)? Many websites do.
If it does, you can use our Site Audit tool to uncover more issues than before.
Google renders your webpages’ unloaded JS to see its full content and to make sure your online visitors can easily access everything too. Now, our Site Audit bots render JavaScript in a similar way to identify any hidden issues on your site.
Here’s how we were able to do that.
What’s New in Site Audit?
We’ve allocated even more resources to crawl and render your site’s JavaScript. Site Audit can now correctly analyze sites largely built on JavaScript, even if they’re client-side rendered.
To show you the difference, let’s look at the two features we’ve recently added:
- JavaScript Rendering
- JavaScript Impact Report
JavaScript Rendering
Site Audit can render JavaScript to crawl more sites fully. Without crawling your site after its JS is fully rendered, you might miss issues that both site bots and searchers will run into.
For instance, here's one audit with JS rendering enabled and another audit (of the same site) with JS disabled.
See the big difference between the number of errors and warnings before and after? With JS enabled, it can properly identify the issues that need to be fixed.
JS Impact Report
Making changes to your code? If it looks good on your end when everything is deployed but your rankings creep down, maybe Googlebot isn’t rendering content as it should.
But if you don’t know which pages are changing, it’ll be hard to figure that out.
The JS Impact report identifies if any of the following elements have changed at the end of a crawl where JS is enabled:
- Titles
- Descriptions
- Links
- Word count
- Canonicals
- Client-side redirects
- Meta robots
- Markup items
There are tons of possibilities for how to use this data. If you notice that some of your important content changes before and after rendering, you should inspect the issue. For example, if rendering JS leads to missing titles or links, it could hurt your SEO.
How you’ll use it to run better audits depends on what you’re trying to do.
How Does JavaScript Impact SEO and Why Does It Matter?
JavaScript rendering is when a site’s JavaScript files are properly executed and displayed to website visitors.
How those files turn from lines of code to an interactive website on your browser can happen in a few ways (like client-side vs. server-side rendering). Each has its pros and cons. However, if you want to audit a site that uses JS and client side rendering, you might run into problems if the crawler can’t render the JS.
Why does that happen? In short, it comes down to resources.
Google has the resources to load both static HTML and injected HTML once a site’s JS is executed. But some site auditing bots don’t have the resources to handle that task (like ours before this update).
Here’s what Airbnb would look like to a bot that can’t render JS.
And here’s what it would look like to a bot that can execute and render JavaScript.
What Happens When Google Renders a Site’s JavaScript?
When Google renders a site’s JavaScript, it first sees if any JS needs to be executed in the first place. If it does, it goes into a queue and then gets executed/rendered to reveal the webpage’s full content. Then, Google indexes it.
Here’s what that looks like according to Google:
In the past, we weren’t able to execute that stage above where a bot processes the JavaScript and renders it. Now our process is similar (minus the indexing).
Why Should You Enable JS Crawling in a Site Audit?
You might not see the full picture of your site’s issues without enabling JS in your next site crawl.
Enabling JS could help you find relevant issues that were potentially missed before.
Especially for sites built on the app shell model (where core components are loaded, but usually not the bulk of a site’s content—think of the earlier Airbnb example).
Some JavaScript sites may use the app shell model where the initial HTML does not contain the actual content and Google needs to execute JavaScript before being able to see the actual page content that JavaScript generates.
How Does Site Audit JavaScript Rendering Work Now?
1. We receive the initial HTML from the web server during crawling
2. We load the JS resources that are linked in this HTML
3. Execute and render JS code
4. Wait 5 seconds
5. Site Audit uses the final HTML for further analysis steps
When you choose to disable JS in Site Audit, we use the original HTML as we did before.
Does Enabling JS Affect My Limits?
No, it will not affect your limits if you choose to enable JS on Site Audit. However, only those with Guru or Business subscriptions can use this feature.
Will It Trigger Trackers, Ads, and Event Handlers?
No, Site Audit will not trigger trackers, ads, and event handlers (i.e. JS triggered by clicking or scrolls). Here’s what we block when our Site Audit bot crawls a site:
- GA4
- GA3
- Yandex Metrica
- Amplitude
- Adobe Analytics
- Google Ads
- OWOX
- SpeedCurve
Does Site Audit Use Chrome for Rendering JS?
Yes, we use the latest Chromium rendering engine. So, we use the same technology as Google does for crawling.
How to Crawl Your Site’s JS with Site Audit
Crawling your site’s JS with Site Audit is simple. First, go to the Site Audit tool and click the ‘create project’ button.
Next, it will prompt you to set up the audit. The only difference is that you’ll choose ‘enabled’ for ‘JS-rendering’ in the crawler settings. You can still leave it disabled if you’d like or change it later.
You can check if your audit is rendering your site’s JS by looking up here in the report:
How to Crawl an Existing Project’s JS with Site Audit
If JS rendering isn’t enabled on a current project, you can change that in the Site Audit settings.
From here, just click the “re-run campaign” button to crawl your site with JS enabled. You can disable JS rendering in the same way if you want to change it back later.
Find All Of Your Site’s Issues with JS Rendering
JavaScript makes sites more interactive, dynamic, and personalized. For example, Netflix uses JS to update the body of a single web document for a speedy, seamless experience.
Similarly, many websites use the app shell model (as well as client-side rendering) to benefit both the user agent and the site owner in their own ways. Your site may use JS to achieve the same results. And if your site does, we can identify what issues Google may run into with Site Audit’s new JS rendering feature.