Fetched content page has no non-empty H1
ShipReady found no non-empty H1 in a fetched content page with at least 200 characters of visible body text.
Why it matters
This is a static markup signal that helps review how the page is presented.
How ShipReady detects it
What it inspects
ShipReady extracts H1 text and visible body text from eligible fetched HTML.
What triggers a finding
No H1 contains text and visible body text is at least 200 characters.
What the evidence shows
The inspected static page met the text threshold and had no non-empty H1.
Limits of this check
ShipReady does not assess heading quality, complete accessibility, rendered JavaScript content, or every route. Short shell pages are deliberately skipped.
How to fix it
Add a page-specific H1
Add one non-empty H1 in the server-returned content that identifies the page’s main topic. Keep it distinct from the HTML title; ShipReady does not choose the wording for you.
How to verify the change
Inspect the returned H1
Fetch the affected page and confirm its returned HTML contains the intended non-empty H1 and still meets the page’s content requirements.
Expected: The returned HTML contains a non-empty H1 for the affected content page.