A technical audit rarely fails because it misses issues. It fails because it finds too many. A crawl of a few thousand pages can easily report missing descriptions, long titles, redirect chains, images without alt text and slow pages, all in the same red color.
The useful question is not “what is wrong?” but “what is costing us visibility right now?”. This article proposes a simple triage in four tiers.
The principle: follow the order in which Google processes a page
Before a page can rank, Google has to be able to crawl it, then index it, then understand it, then choose it over other pages. Issues earlier in that chain block everything after them. A perfect meta description on a page that returns a 404 is worth nothing.
So the triage follows that order:
| Tier | Question | Typical issues |
|---|---|---|
| 1. Blockers | Can Google reach and index the pages that matter? | 5xx errors, 4xx on important pages, accidental noindex, robots.txt blocks |
| 2. Signals | Is Google indexing the right version? | Redirect chains, wrong canonicals, internal links to redirects |
| 3. Relevance | Does each page say clearly what it is about? | Missing or duplicate titles, missing H1, thin pages |
| 4. Refinements | Is the experience as good as it can be? | Core Web Vitals, minor markup, image optimization |
Tier 1: blockers to fix first
Server errors (5xx)
Server errors are the most urgent. Google documents that 5xx responses cause its crawlers to temporarily slow down crawling, and that URLs which persistently return a server error are eventually removed from the index. If your audit finds 5xx on templates or sections, treat it as an incident, not an SEO task.
Client errors (4xx) on pages that matter
A 404 is not a problem in itself: deleted products and old campaigns should return one. Google stops indexing URLs that return 4xx and gradually crawls them less often. The issue is when important pages return 4xx, or when your own internal links and sitemaps still point to them. Sort 4xx by internal links pointing to them and by past traffic, and fix the top of that list.
Also watch for the reverse case: an error page that returns a 200 status. Search Console reports these as soft 404s.
Accidental noindex and robots.txt blocks
A noindex left over from a staging environment can remove a whole section. Compare the list of non-indexable pages with the pages you actually want to rank.
Be careful with robots.txt. Google states that it is not a mechanism for keeping a web page out of Google, and that a blocked URL can still appear in results. If you want a page out of the index, use noindex, and do not block it in robots.txt: for noindex to be effective, the page must not be blocked by robots.txt, otherwise Google never sees the rule.
Tier 2: make sure the right version gets the signals
Redirects
Google treats a 301 (and 308) as a strong signal that the target should be processed, and a 302 (and 307) as a weak one. Its crawlers follow up to 10 redirect hops by default. In practice:
- use permanent redirects for permanent moves;
- collapse chains so each old URL points directly to its final destination;
- update internal links so they point to the final URL rather than through a redirect.
Canonicals
Google describes rel="canonical" as a strong signal, not an order: it decides which pages are duplicates based on content similarity and other signals. Common audit findings worth fixing: canonicals pointing to redirected or non-indexable URLs, canonicals pointing to the home page from every page, and parameter URLs without a consistent canonical. Google also advises against using robots.txt for canonicalization.
Depth and orphan pages
Pages that are many clicks from the home page, or that no internal link points to, are harder to discover. Google uses links to find new pages to crawl. An orphan page that matters commercially is a Tier 2 issue; an orphan page from 2017 that nobody needs is a candidate for removal.
Tier 3: relevance and on-page basics
This is where most audit line items live, and where volume can mislead.
- Titles: missing, empty or duplicated titles across important templates come first. Google recommends unique, descriptive and concise titles. A title that is a few characters “too long” is low priority: Google sets no length limit and simply truncates titles to fit the device.
- Meta descriptions: useful for snippets, but Google primarily uses page content to build snippets and only sometimes uses the meta description. Fix duplicates on key templates; do not hand-write 20,000 descriptions before fixing indexing.
- H1: missing or multiple competing main headings make it less clear what the page is about. Google may also use the main heading when it generates a title link.
Prioritize by template, not by URL. One fix on a category template can resolve thousands of line items at once.
Tier 4: refinements that can wait
Core Web Vitals
Google states that Core Web Vitals are used by its ranking systems, and also that it “always seeks to show the most relevant content, even if the page experience is sub-par.” The recommended thresholds are LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1. Work on them, especially for templates that receive most of your traffic, but not before pages can be crawled and indexed.
Crawl budget
Unless you run a very large or very fast-changing site, crawl budget is rarely the bottleneck. Google’s crawl budget guide says it is aimed at sites with roughly 1 million or more pages, or 10,000 or more pages changing daily, or with many URLs reported as discovered but not indexed. For most sites, an up-to-date sitemap and regular indexing checks are enough.
Turning the audit into a plan
A short list of rules keeps the audit actionable:
- Fix by template and section, not by individual URL.
- Weight each issue by the value of the pages affected (traffic, conversions, strategic importance).
- Separate incidents (5xx, accidental noindex) from backlog items.
- Re-run the audit on a fixed schedule so you can see whether issues are shrinking or coming back.
How SearchFirefly helps
SearchFirefly’s technical analysis groups issues by theme and severity and lists the pages affected, including broken links and redirects, so you can fix by template rather than by URL. Issues turn into prioritized recommendations with the exact fix and a check after release, read alongside your Search Console data so the pages that already matter come first.