Technical on-page audit

What it is

An audit turns a pile of crawled pages into a decision. Not "here are 4,000 issues" — that is a report nobody acts on — but "here are the twelve things costing you the most, in order". The auditor is what makes the difference between data and a to-do list.

How it works

Every crawled page is checked against a set of on-page rules. Each finding is weighted by how much it typically matters, then rolled up into a single 0-100 health score for the page and the site.

Weighting is the important part. A missing title tag on your homepage and a missing alt attribute on the tenth image of a blog post are not equal problems, and a tool that presents them as equal is not helping. Findings are also grouped by page template, because the same fault on 400 product pages is one fix, not 400.

• On-page checks — titles, meta descriptions, headings, canonical, hreflang, image alt text, structured data, thin content, keyword cannibalisation.
• Site-level checks — orphan pages, broken internal links, duplicate content, redirect chains, sitemap accuracy.
• Priority — each finding carries an impact estimate so the top of the list is where the money is.

What it does for your site

It replaces "someone should look at the site" with a ranked list and a number that moves. The score gives you a trend: 61 today, 74 next month, and a clear record of what changed. The grouped findings mean an engineer fixes a template once instead of a symptom four hundred times.

Where the results go

Findings are the input to self-healing agents, which turn a finding into a concrete, validated fix. They also drive alerts, so a new critical issue reaches you without anyone logging in to look.