Digital Marketing

DIY Technical SEO Audit: A 10-Point Checklist You Can Run Yourself

DIY Technical SEO Audit: A 10-Point Checklist You Can Run Yourself
TECHNICAL SEO DIY Technical SEO Audit 10-Point Checklist blogshog.com

A useful technical SEO audit checks ten things, in this order: indexing, canonicals, sitemap, robots.txt, redirects, mobile rendering, speed, internal links, structured data and duplicate content. The order matters more than the list. Most audits start with speed scores because they are easy to generate, and a site with a canonical error is not helped by a faster-loading page nobody can find.

You do not need a paid crawler for a first pass. Google Search Console, the free tier of a crawler like Screaming Frog, PageSpeed Insights and your browser’s view-source are enough to find almost everything that genuinely costs you traffic. What follows is the sequence, with what to look for and what to ignore at each step.

Fix from the bottom up, not the top down Speed, schema Rendering and mobile Can the page be seen as intended? Crawl directives: robots, canonicals, redirects Are you telling Google the right thing? Indexing: is the page in the index at all? Nothing above this layer matters until this one is sound

1. Is your content actually indexed?

Open Search Console → Pages. Compare the indexed count against the number of pages you believe you have published. If indexed pages are a small fraction of your real total, stop the audit here and fix that first; nothing else on this list will produce traffic until it is resolved.

Read the reasons under “Why pages aren’t indexed” in order of count. “Discovered – currently not indexed” usually means a crawl-budget or quality signal issue. “Crawled – currently not indexed” means Google saw the page and chose not to store it. “Alternate page with proper canonical tag” is often fine. “Excluded by noindex tag” is either correct or a disaster, depending on which pages are in the list — check it page by page, because an accidental sitewide noindex is one of the few errors that can erase a site’s traffic overnight.

The two patterns that cost the most are worth naming. First, a site relaunched on a different hostname — moving from www to non-www, or http to https — while Search Console still reports on the old property. Second, a staging site’s noindex rule shipped to production. We cover the diagnosis in detail in crawled but currently not indexed.

2. Do your canonical tags point where you think?

View the source of five pages — homepage, a post, a category, a tag archive and a paginated page — and find the rel="canonical" line. Each should point to itself, in the exact form you want indexed: right protocol, right host, no trailing-slash inconsistency, no query strings.

Canonical patterns: what is fine and what is not Broken Every page canonicals to the homepage Canonical uses http:// on an https site Canonical uses www on a non-www site Page 2 of a series canonicals to page 1 Two canonical tags on the same page Correct Each page canonicals to its own clean URL Filtered or sorted views point to the base URL Paginated pages canonical to themselves Tracking-parameter URLs point to the clean one Exactly one canonical tag per page

The classic failure is a plugin or theme setting that canonicals every page to the homepage. It is rare but catastrophic, and it looks like nothing is wrong until you check the source. Spend the two minutes.

A step-by-step technical SEO checklist covering the same ground in video form.

3. Does your sitemap load, and does it tell the truth?

Open your sitemap index URL in a browser. Three things to confirm: it returns XML rather than an error or an HTML page, every URL inside uses your canonical hostname, and it contains only pages you want indexed. A sitemap listing noindexed pages, redirects or 404s sends contradictory instructions and wastes crawl budget.

A WordPress quirk worth knowing: if your SEO plugin’s sitemap returns a 404 while the plugin is clearly active, the usual cause is stale rewrite rules rather than a broken setting. Visiting Settings → Permalinks and saving without changing anything regenerates them and commonly fixes it on the spot.

4. What is your robots.txt blocking?

Load yourdomain.com/robots.txt and read every line. You are looking for rules that block more than intended — a Disallow: /wp-content/ will stop Google loading your CSS and images, which breaks how it renders your pages. You are also checking that your sitemap is declared, and deciding deliberately whether AI crawlers are allowed.

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://yourdomain.com/sitemap_index.xml

That is a complete, correct robots.txt for most WordPress sites. If yours is substantially longer, read the extra lines carefully — long robots files accumulate rules nobody remembers adding, and each one is a chance to block something you need crawled.

5. Are your redirects clean?

Collapse chains into one hop Chain — slow, leaks signals http://old https://old https://www/old https://new One hop — fast, keeps signals http://old https://new 301

Test a handful of old URLs with a redirect checker and note the number of hops. Every extra hop adds latency and, in Google’s own guidance, risks diluting the signals you are trying to pass. Rewrite multi-step chains as single 301s to the final destination. Also check for redirect loops, and for 302s used where a move is permanent — a temporary redirect tells Google to keep the old URL indexed.

6. Does the mobile version contain everything?

Google indexes the mobile version of your site. If your mobile template hides content, collapses sections that never load, drops structured data or omits internal links present on desktop, then as far as Google is concerned that content does not exist.

Test it properly: use Search Console’s URL Inspection tool, run a live test, and open the rendered HTML tab. Read what is actually there rather than trusting a visual check. Then confirm tap targets are large enough to use — a 15-pixel icon is technically present and practically broken, and these failures show up in behaviour data long before anyone calls them SEO problems.

The performance and speed portion of a technical audit, walked through on a live site.

7. Which speed numbers are worth chasing?

Run PageSpeed Insights on your homepage and two interior pages, and read the field data at the top rather than the lab score below it. Field data comes from real visitors; the lab score comes from a simulated device and moves around between runs. Chasing the lab number is the single most common waste of effort in technical SEO.

The only three speed numbers that count LCP under 2.5s How fast the main content appears. Usually an image. INP under 200ms How fast the page reacts to a tap. Usually JavaScript. CLS under 0.1 How much the layout jumps. Usually missing image sizes.

Each of those three has a predictable main cause, which makes them unusually tractable. Slow LCP is nearly always a large unoptimised hero image or a render-blocking stylesheet. Poor INP is nearly always too much JavaScript running on load. Layout shift is nearly always images and ads without declared width and height. Fix the cause rather than the score.

8. Can every page be reached by a crawler?

Crawl your site with the free tier of any crawler and look for orphan pages — URLs in your sitemap that no internal link points to. An orphan page is findable by Google only through the sitemap, which is a weak signal, and it almost never ranks. Equally, check your click depth: pages more than three clicks from the homepage are crawled less often and treated as less important.

Fixing this is editing, not engineering: add links from relevant existing posts, from category hubs, and from your most-visited pages. The full method is in our guide to internal linking and site structure.

9. Is your structured data valid?

Run one page of each template through the Rich Results Test, then open Search Console → Enhancements. Fix everything marked Invalid before anything marked Warning — warnings are missing recommended fields, errors mean the markup is being discarded. The detail is in our schema markup guide.

10. How much of your site is duplicated?

Sort your crawl by title tag and look for repeats. Identical titles across many URLs usually mean tag archives, filtered views, session parameters or paginated series are generating near-duplicate pages. Decide for each group: noindex it, canonical it to a single version, or block the parameter. Doing nothing is the only wrong answer, because Google will pick a canonical for you and may not pick the one you want.

The whole audit on one screen 1. Indexing coverageSearch Console 2. Canonical tagsView source 3. Sitemap validityBrowser, Search Console 4. robots.txt rulesBrowser 5. Redirect chainsRedirect checker 6. Mobile renderingURL Inspection 7. Core Web VitalsPageSpeed Insights 8. Orphans and depthAny crawler 9. Structured dataRich Results Test 10. Duplicate titlesAny crawler Work top to bottom. Stop and fix anything in steps 1 to 5 before continuing.

What should you ignore?

Automated audit tools generate hundreds of findings, most of which do not matter. A short list of things not to spend your afternoon on: meta keywords, which no search engine has used for over a decade; keyword density figures; a perfect 100 PageSpeed score; “too many internal links” warnings on a genuinely useful navigation; missing alt text on decorative images; and W3C HTML validation errors that do not affect rendering.

A tool that reports 400 issues is reporting its thresholds, not your priorities. The ten steps above cover the problems that actually suppress traffic. Everything else is housekeeping you can do when there is nothing important left.

Fixing technical SEO issues found during an audit, with prioritisation.

How often should you repeat this?

Quarterly for a stable site, and immediately after any of four events: a theme change, a migration or hostname change, a plugin update that touches SEO or caching, and a redesign. Those four cause most of the technical regressions that go unnoticed for months, because nobody thinks of a visual change as an indexing risk.

Keep the output as a dated one-page note: what you checked, what you found, what you changed. The value compounds — next quarter you will be comparing against a record rather than starting over, and you will catch the slow drift that single audits always miss. For the content side of the same work, see the on-page SEO elements that matter and SEO explained in simple steps; for the strategy layer, ranking factors in the GEO and AEO era. More in our technology and digital marketing section.

How long does a DIY technical SEO audit take?

Two to four hours for a site under a few hundred pages, if you follow the order above and resist the urge to fix things as you find them. Record everything first, then fix in priority order. Larger sites take longer mainly because the crawl itself takes longer, not because there is more to judge.

Do I need a paid crawler for a first audit?

No. The free tier of a desktop crawler handles up to a few hundred URLs, which covers most small sites completely, and Search Console plus PageSpeed Insights cover the rest. Paid tools help with large sites, scheduled monitoring and change tracking, but they find the same classes of problem.

Which technical issue costs the most traffic?

An indexing failure, by a wide margin. A page that is not indexed earns nothing regardless of its speed, markup or content quality. That is why indexing coverage is step one and why nothing further on the checklist should be addressed until it is sound.

Should I fix every issue a tool reports?

No. Automated tools report against generic thresholds and routinely flag things that have no effect on rankings, such as meta keywords, HTML validation warnings or alt text on decorative images. Work through the ten prioritised checks instead and treat the long tail as optional housekeeping.

My PageSpeed score is 60. Is that a problem?

Not necessarily. The lab score is a simulation that varies between runs; what Google uses is field data from real visitors. If your Core Web Vitals field data passes, a middling lab score is not costing you rankings. Read the field section at the top of the report, not the score below it.

What is an orphan page and why does it matter?

An orphan page is a URL that appears in your sitemap but has no internal links pointing to it. Google can discover it, but with no internal links it receives almost no signal of importance and rarely ranks. The fix is editorial: link to it from relevant existing posts and from its category hub.

When should I re-run the audit?

Quarterly for a stable site, and immediately after a theme change, a migration or hostname change, an SEO or caching plugin update, or a redesign. Those four events cause most unnoticed technical regressions, because a change that looks purely visual can alter indexing behaviour.