SEO site audit: catch technical problems before they cost you traffic

The problem it solves

Technical SEO problems tend to be quiet. A theme update empties your title tags, a category gets deleted and dozens of internal links break, a plugin starts writing the wrong canonical URL. Weeks can pass before anyone notices. One-off audit tools take a snapshot of today but can't tell you what changed since last week.

The second problem is priority. On a site with hundreds of pages, "meta description missing on 43 pages" is not very actionable on its own. Without knowing which pages bring traffic and which haven't had a visitor in years, choosing what to fix first is guesswork.

How it works

Weekly crawl. Once a week SEOLOK crawls your site by opening pages in a real browser, so content rendered with JavaScript is seen too. Each page is checked for:

• Title tag and meta description: missing or problematic
• H1 heading: missing or duplicated
• Canonical tag: missing or pointing somewhere else
• Broken links and redirects
• Click depth: how many steps from the homepage
• Orphan pages: pages no internal link points to
• Thin content: pages with very little text

Core Web Vitals. Page experience metrics come from Chrome UX Report (CrUX) field data, meaning the experience of real Chrome users, and are refreshed daily. These are the numbers your visitors actually get, not a lab simulation.

Signal score and buckets. Crawl results are combined with Search Console and GA4 data when those are connected. Each URL and the site as a whole receive a 0–100 signal score, built from signals such as the CTR gap, engagement rate, content freshness and date consistency, internal link depth and inbound internal links, thin content, title-to-query match, keyword repetition and author or organisation schema. Pages are then sorted into four buckets:

• Push: pages that could deliver more with some support
• Protect: pages that perform well and need careful handling
• Zombie: pages that generate neither traffic nor engagement
• Watch: pages without enough signal yet for a clear decision

The rules are deterministic: the same data always produces the same score, and no AI model decides it. The methodology page explains where these rules draw their inspiration from.

Actions. Each audit ends in concrete suggestions: rewrite the title, refresh the content, add internal links, merge/301, noindex, fix dates, add author schema, disavow candidate, improve Core Web Vitals. You approve or dismiss each.

What the example shows

The list above is a simplified version of the audit screen. Each row describes one finding: what kind of problem it is and how many pages it affects. Findings that can directly hurt visibility, such as broken links or wrong canonicals, are kept apart from minor polish so it is obvious where to begin. Page counts in the example are illustrative.

Use cases

• After a redesign or migration: The first weekly crawl after a new theme or URL structure goes live shows what broke.
• Content clean-up: Review the Zombie bucket and decide whether to merge, refresh or noindex each page.
• Following a speed project: See whether performance work actually reaches real users in CrUX data. For a quick check on a single URL, use the free Core Web Vitals checker.

To push approved title, noindex and redirect changes to a WordPress site in one click, see the WordPress SEO plugin.

Who it's for

• Small teams with limited developer time who want to spot problems early
• Ecommerce sites with hundreds of product and category pages
• Content sites that have accumulated years of articles
• Agencies checking several client sites every week

For a one-off check without an account, try the free SEO site checker.

Limitations

• Weekly cycle: The crawl runs once a week, so an issue introduced between crawls shows up in the next one. Full downtime is a different matter: SEO alerts check availability far more often.
• CrUX eligibility: Sites or pages without enough traffic may have no Core Web Vitals field data.
• The score is a priority, not a prediction: The signal score does not forecast Google rankings; it suggests where to look first.
• Pages behind a login: Areas that require signing in are not open to visitors and are not audited.