EP-9 Spec

L8 DOM QA and Render Parity: signals that reach the crawler

Layer 8 of EP-9 ensures the core definition is visible in the HTML a crawler receives, not hidden behind JavaScript or an accordion, with a self-referencing canonical.

DOM QA & Render Parity is layer 8 of the Entity Architecture and Governance Framework (EP-9). It requires the core definition to be visible in the raw HTML DOM, not hidden behind JavaScript or an accordion. It is mandatory quality assurance.

Specification: EP-9 (layer 8 of 9) Source: section 3 of the deposited specification Next: layer 9

What layer 8 covers

Layer 8 covers whether the work of the first seven layers actually reaches a crawler. EP-9 requires the core definition to be visible in the HTML DOM, not hidden behind JavaScript or an accordion, and the entity page to carry a self-referencing canonical tag. A failure here can cancel every layer above it.

A definition that appears only after a script runs, or only after a click, may be present for a visitor and absent for an extractor. The page then looks correct in a browser and still fails.

Testing what the crawler sees

Testing what the crawler sees is done with the URL Inspection tool in Google Search Console. Run a live test and open the tested page to read the rendered HTML Google received. Checkpoint CHK-EP-12 passes when the core answer is present there as text, without any interaction.

Compare that rendered text with the schema description at the same time. It is the fastest way to confirm the parity required by layer 4.

The self-referencing canonical

The self-referencing canonical tells a crawler that the entity page is the preferred URL for its own content. RFC 6596 defines the canonical link relation, and checkpoint CHK-EP-13 requires the entity page to point its canonical at itself, so that signals from duplicates and variants collect on the right URL.

Also confirm that the page is not blocked by robots.txt, marked noindex or hidden by a content-protection setting. Any of these removes the page from consideration, whatever its other layers score.

Does Google render JavaScript?

Google does render JavaScript, in a separate stage after crawling, as its JavaScript SEO documentation describes. EP-9 does not rely on that stage: the definition must already be present before any script runs. Not every crawler runs scripts, so the raw HTML is the one version every reader of the page is sure to receive.

Checkpoints for layer 8

The checkpoints for layer 8 inspect the rendered page for the core answer and the HTML head for a self-referencing canonical tag. They are taken from the 15-point EP-9 technical audit checklist and keep their original identifiers, so an audit report can cite each one directly.

Checkpoints for layer 8, from the 15-point EP-9 audit checklist.
Checklist IDAudit layerMandatory verification requirementTool and method
CHK-EP-12L8 DOM RenderCore answer visible in raw HTML DOM (not hidden under accordion/JS).GSC Live Test
CHK-EP-13L8 CanonicalSelf-referencing canonical tag on Entity Page.HTML Header Test

Run these checks after every template change, not only at launch. A theme or plugin update can move a definition into a script or change a canonical without touching the content.

How to check DOM QA and render parity for EP-9 layer 8

These steps confirm that the core definition and the self-referencing canonical of an entity page actually reach a crawler, so the work of the first seven layers is not lost at render time.

  1. Run a live URL Inspection testOpen the URL Inspection tool in Google Search Console, run a live test on the entity page, and open the tested page to view the rendered HTML Google received.
  2. Find the core answer as textConfirm the core definition is present in the rendered HTML as text, without any click or other interaction, so checkpoint CHK-EP-12 passes.
  3. Compare rendered text with schemaCompare the rendered text with the schema description at the same time to confirm the parity that layer 4 requires.
  4. Repeat checks after template changesRun the checks again after every template change, because a theme or plugin update can move a definition into a script or change a canonical without touching the content.

FAQ about DOM QA & Render Parity

Why does my definition show in a browser but still fail the layer 8 check?

A definition that appears only after a script runs, or only after a click, may be present for a visitor and absent for an extractor. The page looks correct in a browser and still fails. EP-9 requires the core definition to be visible in the HTML DOM before any script runs or any interaction happens.

Which checkpoints from the EP-9 audit checklist belong to layer 8?

Layer 8 uses checkpoints CHK-EP-12 and CHK-EP-13 from the 15-point EP-9 audit checklist. CHK-EP-12, L8 DOM Render, checks that the core answer is visible in the raw HTML DOM with a GSC Live Test. CHK-EP-13, L8 Canonical, checks for a self-referencing canonical tag on the entity page with an HTML Header Test.

What is DOM QA and Render Parity in the EP-9 framework?

DOM QA and Render Parity is layer 8 of the Entity Architecture and Governance Framework (EP-9). DOM QA and Render Parity requires the core definition to be visible in the raw HTML DOM, not hidden behind JavaScript or an accordion, and requires a self-referencing canonical on the entity page. It is mandatory quality assurance.

Does Google render JavaScript, and is that enough for EP-9 layer 8?

Google does render JavaScript, in a separate stage after crawling, but EP-9 layer 8 does not rely on that stage. Under EP-9, the core definition must already be present in the raw HTML before any script runs. Not every crawler runs scripts, so the raw HTML is the one version every reader of the page is sure to receive.

Menu

Add to Home Screen

  1. 1 Tap Share in Safari toolbar
  2. 2 Scroll down, select Add to Home Screen
  3. 3 Tap Add in top right corner

These steps are for Safari on iOS. If viewing inside another app, open in Safari first.