Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Audit Guides

Technical SEO Audit Scorecard

A scored technical SEO audit: crawlability, indexation, canonicals, site architecture, structured data, Core Web Vitals, mobile and international setup.
Auditintermediate7 min readUpdated

Scope: what this audit covers and what it does not

The scorecard covers the parts of a site that decide whether search engines can find, render, understand and index its pages: robots rules and sitemaps, status codes and redirects, index directives, canonical signals, duplicate handling, site depth and internal linking, structured data validity, page speed and stability, mobile rendering, and language or regional targeting. It is written for sites of any size, though the crawl efficiency rows matter most on large or frequently changing sites.

It is not the method. How to run the crawl, which reports to open and how to trace a fault to its source are taught in the technical SEO audit tutorial, and the pass-or-fail list for the review is the technical SEO audit checklist. Content quality, search intent and title writing are on-page questions with their own scorecard in the audit library. Backlinks and digital PR are out of scope entirely. Day-to-day handling of individual errors belongs to the Search Console error triage procedure; this audit looks at the pattern those errors form.

Before you score: access and evidence

You need verified access to Search Console for every relevant property, a full crawl of the site with a tool that can render JavaScript, the XML sitemaps, the robots file and, ideally, server logs for a recent period. Ask for a list of the page templates and which sections of the site matter most commercially, because the scorecard weights findings by the importance of the pages they touch.

Pull the page indexing report and note the main reasons pages are excluded. Pull the Core Web Vitals report grouped by template. If the site serves several languages or regions, export the hreflang annotations from the crawl. Record the date of the crawl and keep the same crawler settings for the rescore, otherwise the comparison shows changes in the tool rather than the site. The tutorial on configuring a site crawl chooses those settings from the question the crawl must answer and saves them with the results.

Criteria and scoring

Rate each row missing, partial or solid. Crawlability and indexation rows are gates.

CriterionWhat good looks likeScore guidance
Robots rules (gate)Robots file blocks only what should be blocked; no important section disallowedMissing: key sections blocked / Partial: unclear or over-broad rules / Solid: precise rules
Status codes and redirectsImportant URLs return success; redirects are single hops to final URLsMissing: errors on key pages / Partial: chains or soft errors / Solid: clean responses
Indexation of key pages (gate)Pages that should rank are indexed; excluded pages are excluded on purposeMissing: key templates not indexed / Partial: some unexplained exclusions / Solid: matches intent
Index directivesNoindex used deliberately; no conflicting signals between tags and headersMissing: noindex on key pages / Partial: inconsistent use / Solid: deliberate
XML sitemapsSitemaps list only canonical, indexable URLs and are kept currentMissing: none or broken / Partial: stale or polluted / Solid: clean and current
Canonical signalsEvery page declares a correct canonical; signals agree with links and sitemapsMissing: absent or wrong / Partial: conflicts on some templates / Solid: consistent
Duplicate and parameter handlingFilters, sorting and tracking parameters do not create indexable duplicatesMissing: uncontrolled duplication / Partial: partly contained / Solid: controlled
Crawl efficiencyCrawlers spend time on valuable URLs, not on infinite spaces or old redirectsMissing: large waste visible in logs / Partial: some waste / Solid: focused crawl
Site depth and architectureImportant pages reachable in a few clicks from the home pageMissing: key pages buried or orphaned / Partial: uneven depth / Solid: shallow and logical
Internal linkingDescriptive links point to priority pages; no orphansMissing: orphaned priority pages / Partial: thin linking / Solid: deliberate linking
Structured dataValid markup on relevant templates, matching visible contentMissing: none where useful / Partial: errors or mismatches / Solid: valid and accurate
Speed and Core Web VitalsTemplates meet the good thresholds in field dataMissing: key templates poor / Partial: some need improvement / Solid: good across templates
Mobile renderingContent and links equal on mobile; nothing hidden from the mobile crawlerMissing: content missing on mobile / Partial: usability issues / Solid: parity
JavaScript renderingPrimary content and links present in rendered HTMLMissing: content only after interaction / Partial: delays or gaps / Solid: rendered reliably
International targetingHreflang reciprocal and valid; language versions canonicalise to themselvesMissing: broken or absent where needed / Partial: errors in sets / Solid: valid sets

Score the international row as not applicable for single-language sites and leave it out of the band. For everything else, judge against Google's own documentation, starting from the SEO Starter Guide, rather than tool warnings, which flag many things that do not matter.

How to score and prioritise

Score the gates first. A missing robots or indexation score means some important pages cannot appear in search, and that outranks every efficiency gain. Use the crawling and indexing guide to separate pages excluded on purpose from pages excluded by accident before you decide the score.

Then rank the remaining weaknesses by reach and importance: how many priority URLs does the fault affect, and does it come from a template? A Canonical Tag error on the product template outranks a broken link on an old blog post, even though a crawler lists both at the same severity. Crawl efficiency and Crawl Budget problems rank high only on large or fast-changing sites; on a small site they rarely limit anything. Speed fixes are worth doing for users as much as for search, so they often rank high when the slow templates carry revenue.

Reading the result: what to do with each band

Red means a crawl or indexation gate scored missing. Stop content and link-building work aimed at the affected sections until the blocking fault is fixed, request recrawls through Search Console once it is, and rescore the gates when the indexing report reflects the change.

Amber means the gates hold but several rows are partial or missing. Build a short, template-ordered fix list with the development team, bundle related fixes into a single release where possible, and track each one against the affected report.

Green means the foundation is sound. Keep a lighter rescore every quarter and after every release that changes templates, and move the effort to content and internal linking strategy.

From audit to action plan

Every partial or missing row becomes a ticket written for a developer: the finding, the affected template, a sample of URLs, the expected behaviour and how to verify it. Order tickets by the prioritisation above, and attach the rescore date to each. Where the fix list changes URLs, for example when old redirects are collapsed into single hops or a section is restructured, list every affected URL in a redirect map so each change is decided, implemented and tested row by row. Report the band and the top tickets to stakeholders; the full table stays with the team.

Illustrative example — not a real result

A retailer's faceted navigation

An outdoor-gear retailer with around 6,000 products is audited after organic sessions fall for three months. Robots and indexation gates score partial, not missing: product pages are indexed, but Search Console lists roughly 140,000 crawled-but-not-indexed URLs, almost all filter combinations. Duplicate handling scores missing and crawl efficiency missing; logs show over half of crawler requests hitting filter URLs. The band is amber. The first ticket controls filter parameters at template level, the second fixes canonicals on colour variants, the third trims the sitemap to canonical URLs. Six weeks after release, filter URLs drop out of the crawl and new products are indexed within days rather than weeks.

Common mistakes

  • Scoring the tool's warnings. Crawlers report hundreds of issues at the same severity. Score against what affects indexing and users, not against the tool's colour coding.
  • Rating URLs instead of templates. A list of broken pages is a report. Find the template behind them and score that.
  • Treating speed as a gate. Slow pages still rank. Keep the gates for problems that stop pages appearing at all.
  • Changing crawler settings between audits. Different settings produce different counts, so the rescore measures the tool. Save the configuration.
  • Ignoring the business map. A fault on a section that earns nothing is not urgent. Weight by commercial importance.
  • Rescoring before recrawl. Fixes take time to show in the reports. Rescore once the affected URLs have been recrawled, not the day after release.

Frequently asked questions

Why does the scorecard rate templates rather than individual URLs?

Most technical problems come from a template, a plugin or a server rule, so one fault repeats across every page built from it. Rating the pattern keeps the audit focused on fixes that move many URLs at once, while a list of single broken pages belongs in a crawl report.

Should Core Web Vitals be a gate criterion?

No. Speed matters for users and is one of many page experience signals, but a slow site still gets crawled and indexed. Crawlability and indexation are the gates because a page that cannot be reached or indexed cannot rank at all.

How does this scorecard relate to the Search Console error triage procedure?

The triage procedure handles individual errors as they appear in Search Console, day to day. This scorecard is the periodic review that asks whether the site as a whole is healthy, and a persistent pattern of triaged errors is evidence to score here.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. SEO Starter Guide — Google Search Central

Related