What a Technical SEO Audit Actually Covers
A technical SEO audit checks the machinery under your pages: how crawlers reach your content, how fast it loads, and whether search engines understand what each URL is for. It is not a keyword report and it is not a content plan. It is the plumbing that decides whether your best pages ever get seen at all.
You do not need paid tools to start. A crawler, Search Console, and a spreadsheet will carry you through most of this list. Plan for a few hours per site, and expect the fixes to matter more than the finding. Here is the twelve-step walkthrough we use.
Steps 1 to 3: Crawl, Index, and Robots
Step one is the crawl. Run a full crawl and compare the URLs it finds with what Search Console reports in the Pages section. Any URL that appears in one list but not the other is either blocked, orphaned, or not linked. Step two is indexing. Confirm your important pages are in the index and that no key URL is marked noindex by mistake.
Step three is robots and sitemaps. Open your robots.txt file and read every rule out loud. A single stray disallow can hide a whole folder. Then make sure your XML sitemap lists only canonical, indexable pages, and that its last-modified dates are honest rather than stamped automatically.
Steps 4 to 6: Site Speed and Core Web Vitals
Steps four through six dig into speed. Start with Core Web Vitals field data, because lab scores can flatter a page that feels slow on a real phone. Fix the largest contentful paint first, then the interaction delay, then the layout shift. The official thresholds are spelled out in the Core Web Vitals guide.
Step five is image weight. Compress oversized files, serve modern formats, and set explicit width and height on every image so the layout does not jump. Step six is render-blocking script. Move heavy scripts out of the critical path, defer what can wait, and remove any tag you cannot explain.
A technical audit is not a one-time cleanup but a habit, because every new page, plugin, and redesign quietly changes how search engines read your site.
Steps 7 to 9: Structure, Canonicals, and Duplicates
Step seven is site structure. Every important page should sit within a few clicks of the home page and be reachable through a normal link, not only through a menu script. Step eight is canonicals. Check that each page points to itself, and that no two URLs serve the same content without a clear canonical winner.
Step nine is duplicate and thin content. Look for pages that differ only by filters, tags, or tracking parameters, and decide which one should rank. For more on how structure and content meet, see our website guides and read our about us page for how we test.
Steps 10 to 12: Schema, Mobile, and Monitoring
Step ten is structured data. Validate your schema, and only mark up what the page truly contains. Fake review stars can earn a manual penalty that costs far more than the rich result was worth. Step eleven is mobile. Load every template on a real device and check tap targets, font sizes, and that nothing important hides below a broken menu.
Step twelve is monitoring. Set up alerts for crawl errors, indexing drops, and speed regressions, then check them weekly. An audit is a snapshot, but the site keeps changing, so the last step is really a loop back to the first.
How to Prioritize the Fixes You Find
Not every finding deserves the same attention. Rank each issue by how many pages it touches and how much traffic those pages earn. A problem on your top landing pages outranks the same problem on a tag page nobody visits.
| Priority | Example issue | Fix window |
|---|---|---|
| High | Key page blocked or noindex | Same day |
| Medium | Slow template on mobile | This sprint |
| Low | Missing schema on old posts | Next month |
Running the Audit Without Breaking the Site
Make changes in a staging copy first whenever you can, and change one thing at a time so you know what caused a shift. Keep a log of every edit with a date, because ranking changes lag by days or weeks and your memory will not be reliable.
After you launch, re-crawl the site and watch Search Console for a week. Most fixes show up as steadier indexing rather than a sudden jump. Patience plus a written checklist beats a frantic round of edits every time.