Guide

JavaScript SEO: how to check rendered page content

About 3 min read Time to do it: 1-2 hours Updated
Quick answerA page can return HTML successfully while important content or links appear only after JavaScript runs. Compare the initial response with the rendered page before diagnosing indexing or discovery issues.
On this page
  1. When to use this guide
  2. Why this matters for SEO
  3. What can go wrong
  4. Step-by-step
  5. How to confirm it worked
  6. Mistakes to avoid
  7. Tools to use
  8. FAQ
  9. Related guides

Why this matters for SEO

A page can return HTML successfully while important content or links appear only after JavaScript runs. Compare the initial response with the rendered page before diagnosing indexing or discovery issues.

Search visibility depends on several systems agreeing: the page must be reachable, discoverable, technically eligible to be indexed, useful for the query, and supported by a clear internal site structure. Fixing one symptom while another system is blocking the page can produce little or no improvement.

Use this guide as a focused workflow rather than a checklist to complete blindly. Confirm the actual page and response first, make the smallest defensible change, then re-test the same evidence after deployment.

When to use this guide

  • The browser shows content that is missing from the page source.
  • Important links or metadata appear only after scripts execute.

What can go wrong

  • Content depends on client-side API calls that fail or are delayed.
  • The server returns an empty app shell or different metadata from the rendered page.
Diagnosis order

Check access and HTTP status first, then robots and indexability directives, canonicalization, content/template quality, internal links and performance. This order prevents a low-priority content edit from hiding a technical blocker.

Step-by-step

  1. Inspect the initial HTML

    Fetch the URL or view its source. Confirm that the main title, primary content, canonical and important links are present where possible.

  2. Inspect the rendered page

    Use a browser rendering inspection and compare visible content, links and metadata with the initial response.

  3. Check resource access

    Look for blocked scripts, stylesheets, API endpoints, browser errors and failed network requests.

  4. Test important internal links

    Confirm links are real crawlable anchors with meaningful href values, not only click handlers or inaccessible controls.

  5. Prefer resilient rendering

    For critical content, consider server-side rendering, static rendering or progressive enhancement so essential information is available without fragile client execution.

  6. Validate with search tools

    Use URL Inspection in Search Console for the Google-selected rendered view when available; allow time for recrawling.

How to confirm it worked

The initial and rendered versions contain the same essential page purpose, indexable text, canonical signals and crawlable links, with no critical resource failures.

Verification should use the same URL and comparable conditions as the original test. Check the HTTP response, rendered/source markup and the relevant Google Search Console report where applicable. A successful technical change does not guarantee immediate indexing; crawling and indexing can take time and Google may still choose not to index a page it considers redundant or low quality.

Mistakes to avoid

  • Assuming that a browser-visible page is automatically fully understood by every crawler.
  • Blocking JavaScript or CSS without testing the impact.
  • Hiding the only copy of important content behind user interaction.

Tools to use

Canonical URL Checker
HTTP Status Code Checker

FAQ

Does Google render JavaScript?

Google can render many JavaScript pages, but rendering is a separate processing step and can be delayed or affected by resource failures. Build robust pages rather than relying on rendering assumptions.

Check your own site now. The free SeOMeter tools run these checks on your own URLs, no sign-up needed.

Open the SEO tools

Was something unclear or out of date? Tell us and we will improve this guide. SEO checks are diagnostic guidance, not a promise of rankings, traffic or indexing.