Skip to content
regensbot
DEV-REN-02Must2 of 10 in REN

Have all indexable content in the DOM after load, without clicks, typing or scrolling

Level
Must

Required: the site is not ready to launch without it.

Documentation

Documented

At least one cited Google document states or supports it.

Covered

Automatic

Decided automatically once Regensbot renders your pages.

Why it matters

Googlebot does not click, type or scroll. Content that loads only after a user action is not in the DOM when Google renders the page, so it cannot be indexed, while content that is in the DOM but hidden (tabs, accordions, read-more) can be. Google's slide called content missing from the rendered HTML the most common JavaScript indexing issue.

How to meet it

Ship tab, accordion and read-more content in the initial HTML or DOM and hide it with CSS or the hidden attribute; never fetch it on click. Product specifications, reviews, FAQs and descriptions belong in the page at load. Keep interaction-only loading for content you do not need indexed.

How to test it

In URL Inspection (rendered HTML) or the Rich Results Test, find text from every tab and accordion panel. In the DevTools Network panel, no content request waits for a click.

How Regensbot covers it

AutomaticNeedsRendering in headless Chromium

Decided automatically once Regensbot renders your pages.

Headless Chromium renders the page on an isolated render service, and the raw and the rendered HTML run through the same parsers.

How verdicts workWhat you connect

Sources

Google documents03

  1. 01Fix lazy-loaded contentGoogle Search Central (opens in a new tab)
  2. 02Mobile site and mobile-first indexing best practicesGoogle Search Central (opens in a new tab)
  3. 03Understand the JavaScript SEO basicsGoogle Search Central (opens in a new tab)

Claims in the knowledge base08

  1. D2-C195ConfirmedLightning session D: Rendering and JavaScriptShown on screen
  2. D2-C268ConfirmedWhat is Google friendly JavaScriptSaid on stage
  3. D2-C201ConfirmedLightning session D: Rendering and JavaScriptShown on screen
  4. D2-C196ConsistentLightning session D: Rendering and JavaScriptShown on screen
  5. D2-C202ConsistentLightning session D: Rendering and JavaScriptShown on screen
  6. D2-C262ConfirmedWhat is Google friendly JavaScriptShown on screen
  7. D2-C261UndocumentedWhat is Google friendly JavaScriptShown on screen
  8. D2-C866ConfirmedUnderstanding what's on a pageSaid on stage

Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)

Confirmed
Google's documentation states the same thing.
Consistent
Google's documentation supports it without stating it.
Undocumented
Said or shown at the event, not in the documentation.

Audit

Check it on your site.

One audit checks a URL against all 138 requirements and returns one finding for each, with its source. One URL decides 66; for each of the others, the finding says which source to connect.