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.

Menu

Thêm vào màn hình chính

  1. 1 Bấm nút Chia sẻ ở thanh công cụ Safari
  2. 2 Kéo xuống, chọn Thêm vào MH chính
  3. 3 Bấm Thêm ở góc trên bên phải

Ba bước này là của Safari. Nếu đang xem trong ứng dụng khác thì bấm mở bằng Safari trước đã.