Website Page QA Checklist: Technical SEO, Links, Headings, and Images

Key points

What to take from this guide

• Start with the final URL and response status before judging page content.
• Check indexing, preview, schema, headings, images, and links as separate passes so one issue does not hide another.
• Use crawler or Search Console data later, but run a single-page QA pass before the page is promoted.

Guide section

The page QA order

A useful page QA pass starts with the URL, then moves outward. First confirm the page resolves cleanly, then check response headers and indexing signals, then review previews and structured data, and only then inspect headings, images, and links.

That order matters because content cleanup can waste time if the page redirects oddly, returns the wrong canonical URL, carries a noindex signal, or cannot be represented clearly in search and social previews.

• URL and redirects: confirm the final page is the one you mean to publish.
• Headers and indexing: check status, cache, content type, X-Robots-Tag, and policy headers.
• Metadata and schema: review canonical, robots, Open Graph, Twitter Card, and JSON-LD.
• Content structure: inspect H1, heading order, image alt text, and link anchor text.

Guide section

Technical checks before content review

Run the redirect checker first. If the URL lands somewhere unexpected, fix that before looking at headings or links. Then use the header checker to confirm the response status, content type, cache behavior, and any indexing or security-relevant headers.

Next, check canonical and robots signals. A page can look perfect in the browser and still tell crawlers to ignore it, consolidate it elsewhere, or expose conflicting metadata.

• Use the final URL from the redirect checker as the input for later checks.
• Check whether a non-HTML response, unexpected redirect, or HTTP error is hiding underneath the visible page.
• Confirm canonical URL, meta robots, googlebot, X-Robots-Tag, and og:url agree with the intended page.
• Use robots and sitemap checks for broad crawlability context, not as proof that the individual page is indexed.

Guide section

Preview and structured data checks

After indexing signals are clear, check how the page describes itself. Social preview fields should support the same promise as the page title, meta description, H1, and visible content.

Structured data should parse cleanly and describe the real page. JSON-LD syntax can pass while the entity choice is still wrong, so treat this as a syntax and inventory check before richer validation.

• Open Graph and Twitter fields should not describe an old page, draft offer, or unrelated image.
• Preview image URLs should be absolute and inspectable.
• JSON-LD blocks should parse cleanly and expose expected @type values.
• Use platform validators for rich-result eligibility after syntax and entity checks pass.

Guide section

Content structure checks

Once the page can be crawled and represented correctly, inspect the visible structure. The H1 should make the page topic obvious, headings should form a readable outline, and image alt text should be intentional.

Then check links and anchor text. This catches empty anchors, repeated destinations, missing noopener on new-tab links, and rel values that matter for sponsored or user-generated outbound links.

• Confirm the page has one clear primary H1 unless the template has a deliberate exception.
• Find skipped heading levels, empty headings, and duplicate heading text before editorial review.
• Review missing alt attributes, empty alt text, decorative images, dimensions, srcset, loading, and decoding hints.
• Check internal/external link mix, anchor text, duplicate hrefs, rel values, and target=_blank safety.

Guide section

Common mistakes

The most common mistake is checking page copy first and technical signals last. If the canonical, robots, redirect, or status is wrong, the page may not be discovered or represented the way the content team expects.

Another mistake is treating one clean checker result as a launch pass. A page can have clean headings and still have broken previews, or clean metadata and still have weak links or missing alt text.

• Using the browser URL instead of the final URL after redirects.
• Ignoring X-Robots-Tag because meta robots looks clean.
• Checking social previews but not JSON-LD, or checking schema but not visible headings.
• Treating empty alt text as always wrong instead of confirming whether the image is decorative.
• Forgetting to rerun the link checker after navigation or CTA changes.

Worked example

One page QA pass

A single launch page can move through the checks without turning into a full site crawl.