Skip to content
MIZAN SEO
Technical SEO

Technical SEO Audit: A 10-Step Checklist and How to Prioritise the Fixes

A practical technical SEO audit in 10 steps: Search Console baseline, crawl, robots.txt and sitemaps, indexability, redirects, internal links, Core Web Vitals, structured data and ecommerce checks, with a scoring model to prioritise fixes.

MIZAN SEO · · 12 min read

Technical SEO Audit: A 10-Step Checklist and How to Prioritise the Fixes

A technical SEO audit is a structured check of everything that decides whether search engines can crawl, render, index and understand your pages: robots.txt, sitemaps, status codes, redirects, canonicals, internal links, page speed, mobile rendering, structured data and language settings. Content quality and backlinks matter too, but if the technical layer is broken, the rest never gets a fair chance. This guide walks through a technical SEO audit step by step, then shows how to rank the findings so you fix what moves the needle first.

It is written for site and store owners, in-house marketers, freelancers and agencies who need a repeatable process rather than a 300-item spreadsheet.

The short answer

  • A technical SEO audit answers four questions in order: can search engines crawl the page, render it, index it, and understand it?
  • Start with Google Search Console's indexing reports and a crawl of the site, then compare the two. The gaps between them are where most problems hide.
  • Rank every issue by impact and number of affected pages. One wrong noindex on a category template beats fifty missing alt attributes.
  • Ecommerce sites need extra checks for filter and sorting URLs, out-of-stock pages and duplicate product variants.
  • Run a full audit quarterly and after every redesign, migration or platform change, and monitor key pages in between.

What is a technical SEO audit (and what it is not)?

A technical SEO audit looks at the infrastructure of a site rather than the words on it. It checks whether pages return the right status codes, whether crawlers are allowed in, whether the right version of each page is the one being indexed, and whether the page loads and renders well on a phone.

It is not a content audit, which judges whether a page answers the search intent, and it is not a backlink audit. In practice a good audit flags content issues it can detect mechanically, such as thin pages, duplicate titles and missing descriptions, and hands deeper content questions to a separate review.

When you need a technical SEO audit

  • Before and after a migration: new domain, new platform, new URL structure or HTTPS switch.
  • After a redesign or theme change: templates often ship with noindex tags, broken canonicals or missing headings.
  • When traffic drops and there is no obvious algorithm update or seasonal reason.
  • When new pages are not getting indexed weeks after publishing.
  • Quarterly as routine, because plugins, apps and editors change sites quietly.

Technical SEO audit checklist: 10 steps

Step 1: Pull the baseline from Google Search Console

Open the Pages (indexing) report and note how many URLs are indexed and the top reasons pages are excluded: "Crawled – currently not indexed", "Duplicate without user-selected canonical", "Excluded by noindex tag", "Not found (404)". Note the Core Web Vitals report and any manual actions. This tells you what Google actually sees, which is the reference point for everything else.

Step 2: Crawl the site

Run a crawler over the whole site, or a representative sample for large stores. You want every URL with its status code, title, meta description, canonical, robots directives, H1, word count, internal links in and out, and response time. Compare the crawl with Search Console: pages you want indexed that are excluded, and pages indexed that you never meant to expose.

Step 3: Check crawlability (robots.txt and sitemaps)

  • robots.txt should block only what must not be crawled, such as cart, checkout, account and internal search pages. According to Google Search Central, blocking a URL in robots.txt stops crawling but does not guarantee it stays out of the index; use noindex for that, and leave the page crawlable so Google can see the tag.
  • XML sitemap should list only canonical, indexable URLs that return 200. A sitemap full of redirects, 404s or noindex pages wastes crawl attention and weakens trust in the file.
  • AI crawlers: decide deliberately whether to allow or block AI user agents in robots.txt. Blocking them may keep your content out of some AI answers; allowing them is a business choice, not a technical default.

Step 4: Check indexability (status codes, noindex, canonicals)

  • Every page you want ranked should return 200, have no noindex in the meta robots tag or X-Robots-Tag header, and point its canonical to itself or to the preferred version.
  • Look for soft 404s: empty category or search pages that return 200 but say "no products found".
  • Check for conflicting signals: a canonical pointing to a URL that redirects, or a page in the sitemap that is also noindex.

Step 5: Fix redirects and duplicate versions

  • One preferred version of the site: HTTPS, with or without www, and the other variants permanently redirecting (301) to it.
  • No redirect chains longer than one hop, and no loops.
  • Internal links should point to the final URL, not to a redirect.
  • Important pages should be reachable within about three clicks from the home page.
  • Find orphan pages with no internal links pointing to them; they often exist only in the sitemap.
  • Fix broken internal links (4xx) and links to redirected URLs.
  • Use descriptive anchor text, not "click here".

Step 7: Check on-page technical elements

  • Unique <title> and meta description per indexable page.
  • One clear H1 that matches the page topic.
  • Image alt text on meaningful images.
  • Duplicate titles across many pages usually point to a template problem, not an editorial one, which makes them cheap to fix at scale.

Step 8: Test speed, Core Web Vitals and mobile rendering

Google uses mobile-first indexing, so the mobile version is the one that counts. Per web.dev, the "good" thresholds for Core Web Vitals are Largest Contentful Paint (LCP) at 2.5 seconds or less, Interaction to Next Paint (INP) at 200 milliseconds or less, and Cumulative Layout Shift (CLS) at 0.1 or less, measured at the 75th percentile of real visits. The usual fixes are compressed and correctly sized images, fewer third-party scripts and apps, and reserved space for banners and embeds.

Also check that content and links are present in the rendered HTML. If key text or navigation only appears after heavy JavaScript runs, search engines may index less than you expect.

Step 9: Validate structured data and language settings

  • Structured data (Product, Organization, LocalBusiness, BreadcrumbList, Article) should match what is visible on the page and validate without errors.
  • On multilingual sites, hreflang annotations must be reciprocal: each language version links to the others and to itself, with an x-default where it makes sense.
  • Right-to-left languages such as Arabic need lang="ar" and dir="rtl" set correctly; a missing dir attribute breaks layout and confuses language detection.

Step 10: Ecommerce-specific checks

  • Filter and sorting URLs: colour, size, price and sort parameters can generate thousands of near-duplicate URLs. Decide which filtered pages deserve to be indexable landing pages and keep the rest out of the index.
  • Product variants: one canonical product URL rather than a separately indexed URL per colour, unless each variant has real search demand.
  • Out-of-stock and discontinued products: keep temporarily unavailable pages live; redirect permanently discontinued ones to the closest relevant product or category.
  • Pagination: paginated category pages should be crawlable and self-canonical, not all canonicalised to page one.

Platform guides go deeper: see our Shopify SEO fixes and WooCommerce SEO guide.

Run it for free first: start a free technical SEO audit in MIZAN. One free audit per domain, up to 25 pages, no credit card. You get a score out of 100 and a list of issues with severity and affected URLs in minutes.

How to prioritise technical SEO audit findings

Most audit reports fail at this step. They list 200 issues with the same red icon, and the team fixes the easy ones instead of the important ones. Use a simple scoring model instead:

PriorityWhat qualifiesExamples
CriticalBlocks indexing or ranking of pages that earn moneynoindex on a template, robots.txt blocking /products/, canonical to the wrong domain, 5xx errors
HighWeakens many important pagesDuplicate titles across a category template, redirect chains on main navigation, LCP over 4 seconds on mobile
MediumAffects a subset of pages or a secondary signalMissing meta descriptions on blog posts, orphan pages, missing breadcrumbs markup
LowCosmetic or marginalMissing alt text on decorative images, minor HTML validation warnings

Then sort within each level by pages affected × value of those pages. A high issue on twenty product pages that drive sales comes before a high issue on two hundred tag archives nobody visits.

Finally, separate fixes by who does them: template fixes for a developer, settings changes for the site owner, content fixes for a writer. A finding with no owner never gets fixed.

Worked example: auditing a 400-page home goods store

This is an illustrative example, not a real client. A home goods store on WooCommerce has about 400 URLs: 300 products, 40 categories, a blog and standard pages. Organic traffic has been flat for six months, and new products take weeks to appear in Google.

What the audit found:

  1. Search Console shows 1,900 URLs discovered, far more than the 400 real pages. The crawl explains why: colour and price filters create parameter URLs that are linked from every category page.
  2. Thirty products are canonicalised to their parent category because of a theme setting.
  3. The XML sitemap includes 60 tag archive pages that are thin and duplicate category content.
  4. Category pages have LCP around 4 seconds on mobile because of an uncompressed hero banner.
  5. Product pages have Product structured data, but it is missing price on variable products.
  6. Twelve blog posts are orphans, linked from nowhere except the sitemap.

How it was prioritised:

  • Critical: fix the theme canonical on the thirty products, because those pages cannot rank at all.
  • High: stop indexing filter URLs and remove links to sorting variants; compress and resize the category banner.
  • Medium: remove tag archives from the sitemap and set them to noindex; fix the price field in structured data.
  • Low: link orphan blog posts from relevant categories.

Then: resubmit the sitemap, request indexing for the fixed products in Search Console, re-run the audit to confirm, and turn on monitoring for the category templates so a future theme update cannot silently break them again.

Get started: pick your MIZAN plan. Every yearly plan includes all available tools: SEO audit, keyword research, competitor analysis, AI Content Studio, monitoring and Google Search Console data in one place.

What you do in MIZAN for a technical SEO audit

Here is how the process above maps to what you see in MIZAN:

  • SEO Audit: enter your domain and MIZAN runs 64 checks across eight categories, returning a score out of 100. Each issue shows its severity and the affected URLs, covering indexability, canonicals, duplicate titles, missing descriptions, broken links, structured data, language and RTL settings.
  • Fix in order: start with the critical items in the report, then high. Re-run the audit after each batch of fixes to confirm the issue count drops.
  • Google Search Console: see clicks, impressions, CTR and average position by query, page, country and device over 7, 28 or 90 days, so you can check whether fixed pages start earning impressions.
  • SEO Monitoring: daily or weekly snapshots of key pages, with alerts when a title, description, canonical, indexability or robots.txt changes. This is what catches the next theme update that adds noindex to your categories.
  • Competitor Analysis: compare your technical setup, content depth, headings, structured data and internal linking with up to five competitors.
  • AI Content Studio: once the technical layer is clean, draft better titles, meta descriptions, category copy and FAQs, and review them before publishing.

The full list is on the features page. For the store-specific loop of audit, fix and monitor, read our ecommerce SEO audit guide.

Earn with MIZAN: if you run audits for clients as a freelancer, agency or creator, join the MIZAN affiliate program and earn commission for every customer you refer.

Tool, consultant or both?

A tool is enough when your site has a few hundred pages, runs on a mainstream platform and you or a developer can apply the fixes. A consultant earns their fee on large migrations, complex JavaScript frameworks, international sites with many hreflang clusters, or when no one in-house can interpret the findings. Many teams combine the two: a tool for the recurring audit and monitoring, and an expert for one-off projects. If you are weighing that choice, see when to hire an SEO audit consultant.

Next step

Run your free technical SEO audit, fix critical and high issues first, then re-run it to confirm. When you are ready to keep the site healthy with monitoring and Search Console data, choose a MIZAN plan.

FAQ

What is included in a technical SEO audit?

A technical SEO audit covers crawlability (robots.txt, sitemaps), indexability (status codes, noindex, canonicals), redirects, site structure and internal links, on-page technical elements, page speed and Core Web Vitals, mobile rendering, structured data and language settings such as hreflang.

How often should I run a technical SEO audit?

Run a full audit at least quarterly and after any redesign, migration, theme change or major plugin update. Between audits, monitor your most important pages so changes are caught within days.

How long does a technical SEO audit take?

An automated audit of a small site takes minutes. Reviewing the findings, prioritising them and planning fixes usually takes a few hours for a site of a few hundred pages, and longer for large stores or international sites.

Can I do a technical SEO audit myself?

Yes, for most small and mid-sized sites. Use Google Search Console plus an audit tool, follow the checklist above, and prioritise by impact. Bring in a specialist for migrations or complex setups.

What is the difference between a technical SEO audit and a full SEO audit?

A technical audit focuses on infrastructure: crawling, indexing, rendering and speed. A full SEO audit adds content quality, keyword targeting, search intent, competitors and backlinks.

Is the free MIZAN audit a full technical SEO audit?

The free audit covers up to 25 pages, once per domain, with no credit card, which is enough to surface the core technical issues of a small site. Larger sites, recurring audits, monitoring and Search Console data come with a yearly plan.

  • #Technical SEO
  • #MIZAN SEO
  • #SEO Audit

Audit your site for free

Find the technical issues affecting your Google visibility in minutes.

Start audit

Related tools and guides

Explore all blog articles