Resources · 73

JavaScript SEO: check received and rendered content

Compare HTTP responses, rendering and interactions to find information missing during crawling.

· 4 min

Empty digital forensics bench with storage devices and precision tools AI-generated editorial illustration

What this guide helps achieve

  • Capture the initial response
  • Compare rendering
  • Review interactions
  • Verify fixes

Quick check

  • Is essential text received or rendered without clicks?
  • Are links crawlable HTML links?
  • Do missing pages have the correct HTTP state?

Step-by-step method

  1. 01

    Capture the initial response

    Record status, title, canonical, robots directives, text and links in received HTML. Choose a detail page, list and missing page. An empty shell returning 200 does not establish delivery of useful content.

    Deliverable: response captures.

  2. 02

    Compare rendering

    Inspect executed content with suitable tools and the rendered view available in Google inspection. Note blocked resources, failed API calls and session dependencies. Google distinguishes crawling, rendering and indexing; other systems have their own capabilities.

    Deliverable: initial/rendered differences.

  3. 03

    Review interactions

    Check that useful links are crawlable HTML links and essential text does not depend on clicks, scrolling or login. Test filters and pagination. JavaScript interfaces still need a coherent URL architecture.

    Deliverable: content and link map.

  4. 04

    Verify fixes

    Replay the same URLs and confirm errors, canonical and text. Do not rely on rendering to remove an initial noindex. Track indexing separately: a technically usable response does not guarantee selection by a search engine.

    Deliverable: before/after evidence and monitoring.

Acceptance case to reproduce

Fictional example: these inputs describe no customer or observed result.

View case inputs
{
    "response_status": 200,
    "html_link": "<span onclick=\"navigate()\">Item</span>",
    "rendered_text": true,
    "script_failure_test": true
}

Expected decision

A clickable span is not an href link. Check discovery and content when scripts fail.

Fictional variations to test

After opening the panel twice, one click triggers two requests.

Check the mount lifecycle and remove old listeners. A dedicated AbortController can group their cleanup; then verify that one gesture produces only one action.

A slow earlier search replaces the result of the latest input.

Associate each response with its request version and ignore outdated responses. Cancelling the previous request can help, but does not replace this version check.

The analytics script fails and blocks navigation.

Isolate optional functions. Test links, content and the essential action when that script cannot load; a measurement error must not block the journey.

Evidence to retain

  • Open, close and reopen sequence, with observed request counts.
  • Request order, version identifiers and response finally displayed.
  • Journey result with the optional script blocked.

Additional reference : WHATWG — DOM, AbortController [EN]

Additional reference : MDN — removeEventListener [EN]

Verification procedure

  1. Capture received HTML, rendered content and href links.
  2. Disable scripts and test essential navigation.
  3. Keep text, links, canonical and robots in both states.

Google Search Central — JavaScript SEO basics

Reusable worksheet

Complete with your authorised observations. These fields are a working template, not observed results.

FieldInformation to record
URLType, status and capture date
ContentText and links in initial response and rendering
DependenciesScripts, APIs, sessions and required interactions

Worked example

Illustrative situation

Fictional example: a product detail shows its description only after clicking a tab.

Decision and expected evidence

The team delivers text in rendered content without mandatory interaction, verifies links and directives and separately monitors indexing.

Distinguish the mechanisms

MechanismPurposeCheck or limitation
Initial HTMLContent received without script executionMay contain only a shell
Rendered DOMContent after executionDepends on resources and environment

Management indicators

IndicatorWhat it measuresFirst action
Content parityEssential information present in renderingFix omissions and blocked resources
State errorsMissing pages or inconsistent directivesReplay normal and missing cases

Common pitfalls

  • Test only an already signed-in developer page
  • Return status 200 for every missing page

Frequently asked questions

Does Google execute JavaScript?

Yes, with limits and a rendering phase. Check observed outcomes on your URLs rather than assuming everything is processed.

Is one architecture mandatory?

No. Choose content delivery compatible with intended readers and systems, then test actual states.

Does successful rendering guarantee indexing?

No. Indexing and selection are separate stages influenced by other signals.

Robots.txt: crawling, indexing and evidence

A directive unseen by the crawler cannot solve indexing

Comparing received HTML, response headers and rendering prevents diagnosis based only on the browser’s displayed DOM.

  • Allow the relevant engine to access a page whose noindex it needs to read.
  • Check directives before and after rendering without relying on JavaScript removal of an initial noindex.
  • Verify useful links and that required rendering resources are not blocked.

Review the twelve robots.txt cases →

References reviewed

Official references

References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.