Technical SEO Audit: 12 Things to Fix Before You Build Links
Why Technical Issues Cancel Out Good Links
Googlebot evaluates authority and crawlability together. A link passes PageRank through a crawl path. If that path is blocked, broken, or penalised by slow server response, the authority never arrives at the destination page.
Think of it this way. You spend three months earning links from strong referring domains. Meanwhile, your robots.txt file is blocking the /blog/ directory, and Google hasn’t indexed a single post. Every link pointing at those posts is wasted. The equity exists in theory but goes nowhere in practice.
Fix the technical layer first. Then build links into a site Google can actually read.
Crawlability and Indexation: What Google Can Actually See
These three items come first because they determine whether anything else matters.
1. Robots.txt misconfigurations. A single misplaced Disallow rule can silently exclude an entire section of your site from Google’s index. Check your robots.txt manually and cross-reference it against Google Search Console’s URL Inspection tool. Look for broad wildcard rules that accidentally block CSS, JavaScript, or entire subdirectories.
2. Noindex leaks. Staging pages, paginated archives, and category filters are common sources of accidental noindex tags that migrate into production. Audit your meta robots tags across templates, not just individual URLs.
3. XML sitemap errors. Your sitemap should list only indexable, canonical URLs. Sitemaps that include noindexed pages, redirect chains, or 404s confuse Googlebot and waste crawl budget on URLs that will never rank.
Site Architecture and Internal Linking Problems
PageRank flows through internal links. Poor architecture bleeds that authority before any external links even arrive.
4. Orphan pages. An orphan page has no internal links pointing to it. Google may discover it via a sitemap, but without internal equity flowing in, it rarely ranks. Run a crawl with a tool like Screaming Frog, then cross-reference against your sitemap to surface pages with zero internal links.
5. Shallow link depth. Pages buried four or five clicks from the homepage receive very little crawl priority. Important content should sit within two to three clicks of the root. If your most valuable service pages are buried in a submenu behind a category page, restructure the navigation.
6. Broken internal links. A 404 from an internal link is a dead end for both users and crawlers. These are easy to find and easy to fix. Patch them before you start funnelling external authority toward pages connected by broken paths. You can read more about how web hosting choices that quietly kill your SEO compound these crawl problems at the infrastructure level.
Page Speed, Core Web Vitals, and Render Blocking
Google uses Core Web Vitals as a ranking signal. More importantly, slow pages lose users before they convert, regardless of ranking position.
7. Time to First Byte (TTFB). A TTFB above 600ms signals a slow server or an unoptimised hosting environment. Google’s own guidance targets under 200ms. TTFB problems often sit at the hosting or caching layer, not the code layer.
8. Largest Contentful Paint (LCP). LCP measures how long the main content block takes to load. A poor LCP score, above 4 seconds, tells Google the page feels slow to real users. Common culprits are uncompressed images, render-blocking scripts, and no lazy loading. For a detailed breakdown of what these numbers actually mean, see Google PageSpeed: What the Numbers Actually Tell You.
9. Render-blocking resources. JavaScript and CSS files that load synchronously in the delay everything the user sees. Defer non-critical scripts and inline only what the above-the-fold content needs.
Duplicate Content, Canonicals, and Hreflang Errors
Duplicate content doesn’t just confuse Google. It actively splits the authority you’re trying to consolidate.
10. Unresolved duplicate content. URL parameters, trailing slashes, HTTP versus HTTPS variants, and print-friendly page versions all create duplicate URLs. Each one dilutes the signal that should point at a single canonical page.
11. Misplaced canonical tags. A canonical tag pointing at the wrong URL quietly buries the page you intend to rank. This happens when CMS templates apply canonical tags dynamically and get the logic wrong, or when a developer copies a canonical from a staging environment into production.
12. Hreflang errors. If you serve content to multiple regions or languages, hreflang mismatches send the wrong page to the wrong audience. Missing return tags are the most common error. Every hreflang declaration needs a reciprocal tag on the target page or the whole implementation breaks. Read more about how content-level decisions affect SEO performance once the technical layer is sound.
How to Prioritise Fixes When Everything Looks Broken
A technical SEO audit almost always surfaces more than a dozen issues. Prioritise by crawl impact, not by effort.
Start with anything that blocks Google from seeing your pages, robots.txt rules, noindex tags, and sitemap errors. These have a binary effect. Fix them and pages enter the index. Leave them and nothing else matters.
Next, address architecture issues, orphan pages, broken internal links, and shallow depth. These affect how authority distributes across the site once pages are crawlable.
Then move to performance. TTFB and LCP fixes improve both rankings and conversion rates, so they pay twice.
Finally, resolve duplicate content and canonical errors. These are signal-dilution problems rather than visibility problems, so they matter most once you’re actively building authority.
Work the list in that order. Audit first, fix the foundations, then build links into a site that’s actually ready to rank.