Technical SEO Audit Checklist: What Agencies Miss
Your traffic dropped, your rankings slid, and the report from your last agency said everything looks "healthy." We hear this almost every week. A site that ranked fine six months ago quietly loses ground, and nobody can point to the cause because the obvious boxes were already ticked.
The problem is rarely the thing that gets checked first. Most technical SEO audits stop at broken links and missing meta descriptions, then call it done. The issues that actually drag a site down sit one layer deeper, and they are the ones we end up fixing again and again.
What a stalled site usually means
When organic traffic flattens or drops without a clear penalty, the cause is almost always crawl and indexing related, not content quality. In most sites we audit, the pages are fine. Google just isn't treating them the way the owner assumes it is.
Here is the pattern we see constantly. A site has 400 URLs the owner cares about, but Google has discovered 12,000, most of them filter combinations, session parameters, paginated archives, and tag pages nobody wanted indexed. Crawl budget gets spent on junk, the pages that matter get crawled less often, and updates take weeks to register.
The symptom looks like a ranking problem. The cause is an indexing problem. That distinction matters, because no amount of new content fixes a site that is drowning Google in low-value URLs.
The crawl and indexing checks most audits skip
Start here, because this is where the real damage hides. Open Google Search Console and look at the Pages report under Indexing. Pay attention to the "Crawled - currently not indexed" and "Discovered - currently not indexed" buckets.
If those numbers are large relative to your real page count, Google is choosing not to index pages you care about. That is a quality and architecture signal, not a technical glitch you can wave away.
- Index bloat: Thousands of thin or duplicate URLs from faceted navigation, search result pages, or parameter variations. These compete with your real pages and waste crawl budget.
- Orphaned pages: URLs in the sitemap that no internal link points to. Google sees them as low priority because nothing on the site vouches for them.
- Soft 404s: Pages returning a 200 status code while showing little or no real content. Google treats these as wasted crawls and trust erodes.
- Conflicting signals: A page blocked in robots.txt but also listed in the sitemap, or a canonical tag pointing one direction while internal links point another.
The fix is usually subtraction, not addition. Noindex the junk, consolidate duplicates with proper canonicals, and make sure your sitemap only contains URLs you actually want to rank. We have watched sites recover within a crawl cycle once the noise was removed, though timelines depend on how often Google crawls your site to begin with.
Core Web Vitals that fail on the pages that matter
Speed reports get misread all the time. A site scores 90 on the homepage in PageSpeed Insights, the owner relaxes, and the product and category pages that actually convert are scoring 40 on real mobile devices.
Lab scores and field data are not the same thing. The number that affects ranking is the field data Google collects from real Chrome users, shown in the Core Web Vitals report in Search Console. Check that report, not a one-off lab test on your fastest page.
The recurring culprits we find: oversized hero images served without modern formats, layout shift from ads or embeds loading late, and render-blocking scripts from tag managers stuffed with tools nobody removed. Largest Contentful Paint and Cumulative Layout Shift are where most sites lose points, and both are usually fixable without a rebuild.
[TESTIMONIAL INSERTION NEEDED: Insert a real client testimonial here, pulled from Upwork, YouTube, email, or direct feedback. Ideally one that mentions diagnosing a problem the previous provider missed, or a measurable improvement in speed/indexing. Do not fabricate.]
[Real client name and source]
Mobile rendering and JavaScript issues you cannot see in a browser
Google indexes the mobile version of your site first. If your content depends on JavaScript that renders after load, you need to confirm Google actually sees the rendered result, not an empty shell.
Use the URL Inspection tool in Search Console and view the rendered HTML, not just the page in your own browser. We regularly find product descriptions, reviews, and internal links that exist for human visitors but are missing from what Google renders. The page looks complete to you and half empty to the crawler.
This is one of the most expensive issues to miss, because the site appears perfect during a casual review. The only way to catch it is to inspect rendered output directly.
Structured data, canonicals, and the signals you are sending by accident
Two sites can have identical content and rank very differently because of the signals their code sends. Canonical tags are the most common place this goes wrong. A misconfigured canonical can tell Google to ignore your best pages in favor of a duplicate or a parameter version.
Check that every important page canonicalizes to itself, that paginated series are handled cleanly, and that your hreflang setup, if you have one, is reciprocal and error-free. Structured data should validate without errors in the Rich Results Test, and it should describe what is actually on the page, not what you wish was there.
For a deeper walkthrough of the issues that get overlooked in routine reviews, see our technical SEO audit checklist agencies miss.
[TESTIMONIAL INSERTION NEEDED: Insert a second real testimonial here. A short one focused on clear communication or being shown exactly what was wrong works well in this position. Do not fabricate.]
[Real client name and source]
How to run the audit in the right order
Order matters more than people expect. Fixing speed before fixing index bloat means you are optimizing pages Google is ignoring anyway. Work from the foundation up.
- First, crawl and indexing: Confirm Google is finding and indexing the right pages and nothing else.
- Second, site architecture: Check internal linking, orphaned pages, and how authority flows through the site.
- Third, rendering: Verify Google sees the same content your visitors do on mobile.
- Fourth, performance: Address Core Web Vitals on the templates that matter, using field data.
- Last, signals: Tidy canonicals, structured data, and any international setup.
If you want to start with the highest-leverage step today, pull up your Search Console indexing report and compare the indexed count to the number of pages you actually want ranking. The gap usually tells the whole story. For the structural side, our guide to internal linking and site architecture fixes covers what to do once you know the gap exists.
Frequently asked questions
How long does a proper technical SEO audit take?
A thorough audit of a small to mid-sized site usually takes us a few days to a week, depending on size and how messy the indexing situation is. The crawl and analysis are quick. The time goes into verifying rendered output, confirming field data, and separating real problems from noise that looks alarming but does not affect ranking.
Why did my traffic drop if my content is fine?
In most cases we see, the content genuinely is fine and the issue is indexing or crawl related. Google may be spending its crawl budget on low-value URLs, treating your real pages as duplicates, or failing to render content that depends on JavaScript. The content quality is a red herring until the technical signals are sorted.
Can I fix these issues myself?
Some of them, yes. Reading your Search Console indexing report and spotting bloat is something any owner can do. Fixing canonicals, faceted navigation, and rendering issues usually needs developer access and an understanding of how the signals interact, because a wrong fix can make things worse than the original problem.
Will fixing technical SEO guarantee my rankings come back?
No, and anyone promising that is guessing. Technical fixes remove the things holding a site back so your content can compete on merit. If the underlying content and authority are there, recovery is common. If they are not, technical work alone will not manufacture rankings that were never earned.
How often should I run a technical audit?
A full audit once or twice a year is reasonable for most sites, with a quick monthly check of the Search Console indexing and Core Web Vitals reports in between. Run an extra audit after any major change: a redesign, a migration, a CMS switch, or a big content restructure, since those are when new issues quietly appear.
Want to know what is actually holding your site back
If your rankings have stalled and the usual explanations have not added up, the cause is probably sitting in one of the layers above, unseen. We will run the checks in the right order and show you exactly what we find, in plain language, with the issues ranked by impact so you know what to fix first. You will walk away with a clear picture of what is wrong, whether or not you work with us on the fixes. Send us your domain and we will take a look.
Send us your domain