Let’s talk
Field notes / practical guide

Audit content missing from initial HTML

An initial-HTML audit checks what the server delivers before browser scripts run. It is one useful diagnostic, separate from a complete indexing assessment.

Compare source and rendered content

Choose a representative service page and inspect the initial response beside the rendered page. Check the main heading, body copy, title, canonical and internal links. Record content that only appears after JavaScript execution.

Put it in context

Search-led content brief

Turn search intent into page structure, evidence requirements and internal links.

DataNotion · AI-generated illustration

Trace the delivery decision

Identify whether the page is intentionally client-rendered or whether a rendering failure removed expected content. Consider pre-rendering stable information. Do not assume the presence of an app shell proves Google cannot ever render the page.

Verify the finished route

Test the response and browser experience after a change. Review relevant Search Console information when available. Keep indexing claims tied to observed evidence, because complete initial HTML alone does not guarantee selection for search results.

Put the guidance to work

Capture your starting point, assign an owner to the next action, and decide what evidence will confirm that it worked.

Discuss this with us
Keep exploring

Your next useful step.