What a technical audit is for
Good content can’t rank if search engines can’t reach it, or if they get confused about which page to show. Technical problems also tend to build up without anyone noticing: a page is renamed and the old links now go nowhere, a template change removes a title, a redirect gets added on top of an older redirect. Your site still looks fine from the home page.
A crawler follows the links through your site and checks each page it finds. It’s the quickest way to find this sort of thing, and regular crawls catch new problems soon after they appear.
What it looks for
We report around 40 kinds of problem, and leave out checks that create noise on ordinary websites without helping you. Each is sorted into one of three levels.
- Errors break things for visitors or Google: broken pages, server errors, links to broken pages, missing titles and canonical tags pointing at dead pages.
- Warnings hold back rankings or clicks: duplicate or missing descriptions, duplicate titles, thin content, slow pages, missing H1 headings, redirect chains and broken images or scripts.
- Notices are worth a look but often fine on purpose, such as a thank-you page hidden from Google, or a page buried deep in the site.
Checks on the website as a whole
Some problems belong to the whole site rather than one page, so they’re checked separately: a valid SSL certificate and whether it expires within 30 days, HTTP redirecting to HTTPS, a sitemap, robots.txt, one consistent version of www or non-www, and whether missing pages properly return a 404.
Working through the results
Each issue says why it matters and what to do, then lists exactly which pages are affected. Work from the top: errors first, then warnings. The health score, from 0 to 100, gives you one figure to watch between audits, and the change column shows what’s improved since last time. It’s the crawler’s score rather than Google’s, so use it to track your own progress.
Audit results also feed into your recommendations and the monthly report, so a fix you’ve made shows up as progress you can point to.
What the crawler doesn’t do
The crawler reads the HTML your server sends and doesn’t run JavaScript, so a site that builds its content in the browser can look thinner than it does to a person. Page speed is measured as how long that HTML took to download, so it’s a useful guide to slow pages and not a full browser speed test. On a larger site, pages beyond your plan’s limit aren’t crawled in that audit.
The audit is about how your site is built. To see how it performs in search, pair it with rank tracking.