A technical SEO audit is a systematic check of whether search engines can crawl, render, index, and trust your site, worked from the foundation up: crawlability and indexation first, then site architecture and internal linking, Core Web Vitals, mobile and JavaScript rendering, and structured data. You can run it yourself with a free Google Search Console account and a crawler such as Screaming Frog, whose free tier handles up to 500 URLs.
Most B2B marketing leaders discover their site has a technical problem the same way: a quarter of strong content ships, rankings stay flat, and nobody can explain why. The usual answer is to write more. The better answer is to run a technical SEO audit first, because no amount of new content will rank if Google can’t crawl, render, or trust the pages you already have. This checklist walks through the audit we run on B2B sites before we touch strategy, and it’s deliberately built so you can run it yourself without enterprise tooling.
You don’t need a six-figure platform to find the issues that actually move the needle. You need a free Google Search Console account, a crawler, and a methodical way to work through the layers. Below is the order we work in, because fixing things out of sequence wastes time.
How do you run a technical SEO audit? Start with crawlability and indexation
Before anything else, confirm that Google can find and store your pages. This is the layer where the most expensive mistakes hide, and it’s the one teams skip because it feels too basic.
Open Google Search Console and go to the Pages report under Indexing. You’re looking for the gap between pages you want indexed and pages that actually are. In our engagements, we typically find one of three culprits:
- Accidental noindex tags left over from a staging environment or a CMS template
- Robots.txt rules blocking directories that should be crawlable (often
/blog/or/resources/) - Canonical tags pointing the wrong way, so Google consolidates the wrong version
Verify your robots.txt and sitemap
Pull up yourdomain.com/robots.txt directly in a browser. Confirm it isn’t blocking anything important and that it references your XML sitemap. Then check the sitemap itself: it should contain only canonical, indexable, 200-status URLs. A sitemap stuffed with redirects, 404s, and noindexed pages sends Google a confused signal about what matters.
If Google can’t crawl it, nothing else on this list matters. Fix indexation before you optimize a single title tag.
Run a crawl and compare
Run a crawl with Screaming Frog (the free tier handles up to 500 URLs, which covers most B2B sites) or a similar tool. Export the list and compare it against your sitemap and your Search Console indexed count. The discrepancies are your work order. Orphan pages with no internal links, pages buried five clicks deep, and large blocks of indexed-but-thin pages all surface here.
Audit Site Architecture and Internal Linking
Once crawling is clean, look at how pages connect. Architecture is where technical SEO and content strategy overlap, and it’s usually the highest-leverage area for B2B sites that have published for years without a plan.
The principle is simple: important pages should be reachable in a few clicks and should receive internal links from related content. In practice, B2B sites accumulate hundreds of blog posts that link to nothing and receive links from nothing. That’s wasted authority.
Map your most important commercial pages, then check how many internal links each one receives. If your highest-intent service page has three internal links and a two-year-old blog post has forty, your link equity is flowing to the wrong place. This is exactly the problem a deliberate hub-and-spoke topic cluster structure is designed to solve, and it’s why we treat internal linking as an ongoing discipline rather than a one-time fix.
A quick architecture checklist:
- Every commercial page is within three clicks of the homepage
- Pillar pages link down to their supporting articles, and those articles link back up
- No important page is an orphan (zero internal links)
- Navigation and footer links point to pages you actually want to rank
Measure Core Web Vitals and Page Performance
Performance is a confirmed ranking factor and, more importantly, a conversion factor. Slow pages lose leads regardless of where they rank. This part of the technical SEO audit uses real-world data, not lab estimates.
In Search Console, open the Core Web Vitals report. It groups your URLs by status across the three metrics that matter:
- Largest Contentful Paint (LCP) — how fast the main content loads. Aim for under 2.5 seconds.
- Interaction to Next Paint (INP) — how responsive the page feels to input. Aim for under 200 milliseconds.
- Cumulative Layout Shift (CLS) — how much the layout jumps around. Aim for under 0.1.
For B2B sites, the most common offenders are unoptimized hero images, render-blocking third-party scripts (chat widgets, marketing tags, A/B testing tools), and web fonts that load late and shift text. Run a few key templates through PageSpeed Insights to get specific diagnostics, then prioritize fixes by template rather than by individual URL. Fixing one blog template often fixes a thousand pages at once.
Don’t optimize in a vacuum
Performance work has diminishing returns. Once you’re in the green for the bulk of your URLs, stop chasing milliseconds and move on. The goal is removing friction, not winning a benchmark.
Check Mobile Rendering and JavaScript
Google indexes the mobile version of your site, so the audit has to account for what mobile users and mobile crawlers actually see. Two issues recur in B2B audits.
First, content parity. Some sites hide sections on mobile or load them only after interaction. If important content or links aren’t in the mobile DOM, Google may not weight them. Use the URL Inspection tool in Search Console to see the rendered HTML Google actually receives, and confirm your key content and links are present.
Second, JavaScript rendering. If your site is built on a heavy client-side framework, content that depends on JavaScript may render slowly or inconsistently for crawlers. The URL Inspection tool’s rendered screenshot tells you quickly whether Google sees a finished page or a blank shell. If you see gaps, that’s a flag to discuss server-side rendering or static generation with your engineering team.
Validate Structured Data and Metadata
Structured data won’t make a bad page rank, but it helps Google understand your content and can earn richer search results. For B2B sites, the highest-value schema types are Organization, Article or BlogPosting for content, FAQPage where genuinely relevant, and BreadcrumbList for navigation context.
Run your key templates through Google’s Rich Results Test. Fix errors first (they can suppress eligibility), then warnings. Don’t add schema you can’t justify with real content on the page; markup that misrepresents the page invites manual penalties.
While you’re in the page source, sweep the basics that still matter:
- Title tags that are unique, descriptive, and front-load the topic
- Meta descriptions that read like ad copy, not boilerplate
- One H1 per page that matches search intent
- Canonical tags that are self-referential unless you have a deliberate reason otherwise
These fundamentals are unglamorous, but in audit after audit they’re where quick wins live. When you tie them to a coherent keyword approach like the one in our B2B SEO strategy framework, the technical cleanup compounds with the content work instead of running parallel to it.
Turn the Audit Into a Prioritized Backlog
The audit isn’t the deliverable. The fixes are. Once you’ve worked through the layers above, you’ll have a list that’s longer than your team can ship in a sprint, so prioritize ruthlessly.
We sort findings into three buckets:
- Critical — anything blocking indexation or breaking a commercial page. Fix this week.
- High-value, low-effort — title tags, internal links to commercial pages, sitemap cleanup. Fix this month.
- Structural — architecture, rendering strategy, performance overhauls. Plan and resource these deliberately.
The mistake we see most often is treating a technical audit as a one-time project. Sites drift. New templates ship, plugins update, redirects pile up. The teams that win treat technical health as a recurring check, the same way they treat the content production process behind a durable content engine. Schedule a lightweight version of this audit quarterly and a full pass twice a year. You’ll catch regressions before they cost you rankings.
Where to Go From Here
A clean technical foundation is what makes everything else in SEO actually work. Run this checklist, fix the critical issues first, and you’ll often see indexation and rankings respond before you publish anything new. If you’d rather have a team handle the audit, the fixes, and the strategy that follows, that’s what we do at Urion Studio. See how we approach SEO and content infrastructure, or get in touch and we’ll take a look at your site together.
