This information allows you to understand:
- What content has appeared or changed after JS rendering
- If crawlers can index essential content and tags
You’ll be able to identify how many pages change when JS renders and pinpoint where those changes occur.
When to Use This Report
Guide vs. Table View
The Guide view makes it easy to get an overview of the changes we saw after rendering. Scroll down to each section to see where your specific elements changed. For example, if a specific title changes or becomes empty, you’ll see it here.
Switching from the Guide view to the Table view will allow you to filter the whole report and find specific issues.
For example, if you want to dive into just page titles and links that were changed, you can add those filters with the parameters drop down.
Pages Impacted After JS Rendering
At the top of the page, you’ll see the number of pages in the audit where Semrush needed to render the final JS. The more changed pages, the more inspection is required. This number will be dictated by how many pages you’re able to crawl.
If you need to crawl more pages, consider upgrading your plan.
Parameters Changed After Rendering
For example, if your page title is missing before the JS renders, that would mean Google might not see it when it first crawls your page. As a result, the page might not get ranked well in search.
Why is JS Rendering Important?
Running an audit without rendering the JS means you might miss some content on the site. On the other hand, auditing with JS rendering enabled will contain more content and more accurate information to check.
We use a similar technology stack as Googlebot, (Chromium) so the result of crawling will be very close to how Google Bot sees the website.