Resources · 73
JavaScript SEO: check received and rendered content
Compare HTTP responses, rendering and interactions to find information missing during crawling.
· 2 min
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
- 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.
- 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.
- 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.
- 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.
Reusable worksheet
Complete with your authorised observations. These fields are a working template, not observed results.
| Field | Information to record |
|---|---|
| URL | Type, status and capture date |
| Content | Text and links in initial response and rendering |
| Dependencies | Scripts, 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
| Mechanism | Purpose | Check or limitation |
|---|---|---|
| Initial HTML | Content received without script execution | May contain only a shell |
| Rendered DOM | Content after execution | Depends on resources and environment |
Management indicators
| Indicator | What it measures | First action |
|---|---|---|
| Content parity | Essential information present in rendering | Fix omissions and blocked resources |
| State errors | Missing pages or inconsistent directives | Replay 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.
Official references
References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.
Continue exploring
Related analysis
