On-Page Technical

On-Page
Technical Audit

The technical elements on each page that search engines use to understand content.

Where to find it: Screaming Frog > Page Titles / Meta Descriptions / H1 / Canonical / Hreflang

What It Is

The on-page technical audit examines metadata elements on every page: title tags (length, uniqueness, keyword alignment), meta descriptions (presence, length, differentiation), H1 tags (presence, uniqueness, alignment with title), canonical tags (self-referencing, correct format), hreflang (for international sites), and Open Graph tags. These elements are almost always generated by CMS templates — a single template error propagates across hundreds or thousands of pages simultaneously, making systematic template-level fixes the most efficient remediation approach.

Why It Matters

Title tags are the most direct on-page ranking signal available. A site where every product page uses the same title tag template with no unique keyword targeting is leaving significant ranking opportunity on the table at scale. The on-page technical audit finds these systematic template errors — issues affecting entire page classes that can be resolved with a single template change. A finding of '847 pages with duplicate title tags' is a single fix that improves 847 pages simultaneously.

Common Audit Failure Points

What Goes Wrong

Understanding where audits fail — and why — is the first step to executing them correctly.

CMS Template Patterns Without Differentiation

Title tag templates producing identical or near-identical titles across page types — 'Shop | Brand Name' on every product page rather than unique keyword-targeted titles per product.

Missing Meta Descriptions at Scale

CMS outputting auto-generated excerpt snippets as meta descriptions, or no meta description tag at all — across hundreds of pages simultaneously from a single template setting.

Multiple H1 Tags From Theme Navigation

Website themes injecting H1 tags into site navigation, header logos, or hero sections — resulting in every page having 2–3 H1 tags alongside the intended content H1.

Broken Canonical Tags Using Relative URLs

Canonical tags implemented with relative paths (/page/) instead of absolute URLs (https://domain.com/page/) — breaking canonical resolution and potentially directing Google to incorrect canonical destinations.

Interactive Standard Operating Procedure

The Audit Playbook (Interactive SOP)

Check off each step to track your audit progress live!

Audit Progress: 0% Completed (0/7)

1. Export and Audit All Title Tags

From Screaming Frog, export all title tags. Check for: titles under 30 or over 60 characters, exact duplicate titles across multiple pages, pages with no title tag, and titles using a boilerplate template with no unique keyword targeting. Flag each issue type with a count of affected pages.

2. Export and Audit All Meta Descriptions

Export all meta descriptions. Check for: descriptions under 120 or over 155 characters, exact duplicates, missing descriptions, and auto-generated excerpts being used as descriptions. Note whether missing descriptions are from a CMS template issue (systematic) or individual page oversight (one-off).

3. Export and Audit All H1 Tags

Export all H1 data. Flag pages with: no H1 tag, more than one H1 tag, an H1 that doesn't align with the page's title tag keyword intent, and H1 tags over 70 characters. Sort by frequency — multiple-H1 issues on every page indicate a theme-level problem.

4. Audit Canonical Tag Implementation

Export all canonical tags. Verify: every page has a canonical, all canonicals use absolute URLs with the correct protocol (https://), self-referencing canonicals match the page's actual URL exactly, and no canonicals point to redirect URLs or 404 pages.

5. Audit hreflang for International Sites

For sites serving multiple languages or regions: export all hreflang tags. Verify bidirectional references — every language version must reference every other language version. Check for missing x-default tags and hreflang pointing to non-canonical URLs.

6. Review Open Graph and Social Meta Tags

Check for presence of og:title, og:description, og:image, og:url, and Twitter Card equivalents on all key page types. Flag missing og:image — the most commonly absent tag and the most visible when content is shared on social platforms.

7. Compile All Findings by Template Type and Page Count

Group all on-page technical issues by which CMS template they originate from, with a count of affected pages per issue. Present as 'Product template: 340 pages affected — missing unique title tags.' Template-based framing communicates both scale and fix efficiency to clients.

Tools

Screaming Frog
Paid/Free tier | Comprehensive on-page metadata export — titles, descriptions, H1s, canonicals, hreflang, and Open Graph tags in a single crawl
Sitebulb
Paid | Priority-scored on-page audit with visual recommendations — useful for communicating findings to non-technical clients
Semrush Site Audit
Paid | Cloud-based on-page audit with historical comparison — useful for tracking on-page technical improvements over time across recurring audits

Time Investment

2–3 hours

On-Page Analysis

One template fix = hundreds of pages

Fix Efficiency

Pro Tip

Sort every on-page issue by pages affected — not by severity in isolation.

Missing meta descriptions on 5 pages is a minor one-off fix. Missing meta descriptions on 800 pages is a template error requiring immediate correction that will improve the entire site in one change. Always frame on-page findings in terms of pages affected rather than individual error counts — 'this template error is suppressing 800 pages' creates a completely different urgency than 'there are 800 missing meta descriptions.' Scale communicates impact.

Ep 3: Indexation and Coverage Audit Ep 5: Site Speed and Core Web Vitals Audit

On-PageTechnical Audit