Currently Available: Need a skilled Software Developer for your next project?
Categories
SEO, GEO and AEO

Testing If JavaScript Changes Broke Rendering or Indexing

After a JavaScript or framework release, check three things: whether Google can retrieve the page, run its JavaScript and see its important content, and include the intended URL in Search. Rendering means Google runs the page’s JavaScript to produce content and links it can inspect. Indexing means Google considers the page for inclusion in Search.

A page can pass one check and fail another. Google’s URL Inspection tool lets you test the current page as Google sees it, then compare that result with Google’s stored information about the URL. A successful live test shows that the page was accessible and rendered during that test. It does not confirm that Google has indexed the current version.

Test the live page after the release

Start with one important production URL for each changed route or page template. If the release changed how a page loads data from an API, a service that supplies data, include that page too. Record the deployment time so you can compare it with the last crawl shown in Search Console.

In URL Inspection, choose Test live URL. Open View tested page and review the screenshot, rendered page code, loaded resources, and JavaScript console output. Google’s JavaScript troubleshooting guidance recommends examining rendered output and resources when investigating problems.

Check whether the rendered page contains its main text and page-specific content, rather than only an app shell, loading indicator, or error message. Also check that important links, the page title, the robots directive, and the canonical URL are correct. The robots directive gives crawlers instructions about indexing the page. A canonical URL tells Google which URL the page identifies as its preferred version.

If content is missing, compare the rendered output with the resources and console messages. A blocked script, failed API request, or JavaScript exception, an error that interrupts code, can help explain the difference. A console error alone does not prove that it caused an indexing problem. Check whether the missing content depends on a user interaction. Content that appears only after someone clicks or scrolls may not appear in the tested output.

Google processes JavaScript pages through crawling, rendering, and indexing. It fetches a page first, then uses Chromium, a browser that runs without a visible window, to render pages it selects for rendering. Google uses the rendered HTML to understand page content and find links. A successful fetch does not show that rendering succeeded. The documented JavaScript processing steps explain why each stage needs a separate check.

Separate rendering symptoms from indexing outcomes

Use the live test to investigate what Google can access now. Use the indexed view in URL Inspection and the Page indexing report to investigate what Google last processed and whether it included the URL.

What you see What it tells you What to check next
The live test cannot fetch the URL or reports an unexpected response A server, access, or redirect problem may be preventing Google from reaching the page. This alone does not show a JavaScript rendering failure. Review the live-test result and the URL’s response and redirect behavior.
The live screenshot or rendered code lacks the main content The page did not produce the expected output for that test. A rendering or resource problem is plausible. Check loaded resources, console errors, API responses, and whether the content depends on interaction.
The page renders, but the URL is not indexed Rendering succeeded during the test, but that does not settle whether Google will index the URL. Inspect indexing permission, the Google-selected canonical, and the reported indexing reason.
Search Console says “Crawled – currently not indexed” Google crawled the URL but did not index it. That status alone does not show that the release broke rendering. Inspect the rendered page and review the other indexing signals.
Google reports a soft 404 Google may have seen a nearly empty page or an error state, even if the server returned a successful response. Compare the rendered content with the HTTP response and check whether the page clearly communicates its purpose.

A page that returns a successful HTTP status can still show a not-found screen or nearly empty content after JavaScript runs. Google identifies missing resources and error presentations as possible contributors to a soft 404. Check what the rendered page actually says, rather than relying on the status code alone.

For indexing, review Last crawl, Crawl allowed?, Indexing allowed?, Page fetch, and Google-selected canonical in URL Inspection. An unintended noindex directive or canonical URL can explain why a page is absent from Search even when its content renders correctly. The indexed URL details also help distinguish Google’s stored view from the live test.

Interpret differences between the live and indexed views

The live test shows the page as it appeared at test time. The indexed view shows what Google recorded during an earlier crawl. If Google last crawled the page before the deployment, the difference between the two views does not by itself indicate a rendering bug. Check the crawl date, then rerun the live test once the released page is stable.

A “Crawled – currently not indexed” result also does not, by itself, identify a technical defect. Google says this status is common and does not necessarily require action in its Page indexing report guidance. Look for direct evidence of a release-related failure, such as missing main content in the rendered output, before attributing the status to JavaScript.

After you fix a confirmed issue, run the live test again. If the output is correct and a prompt recrawl matters, request indexing. That request asks Google to recrawl the URL; it does not guarantee a specific crawl time or inclusion in Search.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com

Email updates

Usually a new article and a few links I found interesting.

No spam. Unsubscribe with one click.

Leave a Reply

Your email address will not be published. Required fields are marked *