Inspect the page your visitors actually get
A WordPress content auditor checks the HTML of a rendered page for the structural problems that hurt readers and search engines: heading structure, link issues and image alternative text. Paste the HTML from a rendered page or a content export, and the report counts headings, visible text, images and links, then flags a missing H1, skipped heading levels or empty link labels.
The key word is rendered. What matters is the page as it reaches the browser — including what your theme and plugins add — not what the editor shows while you write. A heading hidden by the theme, or a link label that only makes sense beside its surrounding text, only shows up when you audit the finished page.
How to audit a WordPress page
- Open the published page, view the page source or copy the rendered HTML, and paste it into the tool.
- Press Update result and wait for the report.
- Work through the fix list, starting with a missing H1 and skipped heading levels.
- Review each flagged item on the live page before changing it — a flag is a prompt to look, not a verdict.
Why inspect the rendered page, not just the editor?
The editor shows your content; the rendered page shows your content plus everything the theme, the page builder and the plugins do to it. Auditing the finished page catches problems the editor cannot see:
- A missing H1 — the page has no clear main heading for readers or search engines.
- Skipped heading levels — jumping from an H2 to an H4 breaks the outline assistive technology relies on.
- Empty link labels — a link that says nothing on its own, or an image link with no alt text, leaves screen-reader users guessing.
- Images without useful alternative text — a chart or a photo that carries meaning needs a description.
- Thin or bloated pages — the counts of visible text, images and links show whether the page does what you think it does.
What this audit cannot prove
The tool does not visit your website, check HTTP responses, evaluate CSS contrast or prove accessibility compliance, so a clean report is not a certificate. Empty alt attributes may be correct for decorative images, and the tool cannot judge whether a description is accurate — only whether one exists. It also cannot tell you whether a heading is well written, only whether the structure is sound.
Frequently asked questions
Should I paste editor HTML or rendered page HTML?
Rendered page HTML. The editor shows your content before the theme and plugins reshape it, so problems the theme adds — a missing H1, a duplicated heading, a stripped link label — only appear in the rendered page.
Is one H1 per page a strict rule?
A missing H1 is flagged because a page without a main heading is hard to understand, but the fix is to add a heading that describes the page, not to obsess over counting. Review the flag in context and make the page clearer first.
Why are skipped heading levels flagged?
Headings form an outline that assistive technology uses to navigate. Jumping from an H2 to an H4 leaves a gap, so a listener can miss a section. Keep the levels in order and the page is easier to navigate for everyone.
Does an empty alt attribute always mean a problem?
No. Empty alt attributes may be correct for decorative images, which should stay silent for screen readers. The flag matters for images that carry meaning — a chart, a diagram, an illustrative photo — where a missing description leaves a gap.
Can this WordPress content auditor prove my page is accessible?
No. It checks heading structure, link labels and the presence of alt text, but it does not evaluate colour contrast, keyboard navigation or focus order. Treat it as a structural check, not an accessibility certificate.