How to Run a Technical SEO Audit: The 30-Point Checklist

A technical SEO audit helps you find the problems that prevent search engines from properly crawling, understanding, indexing, and ranking your website. For a B2B website, technical SEO is especially important because a site may have hundreds of product pages, category pages, industry pages, case studies, and articles that all need to work together. In this guide, I’ll walk through a practical 30-point technical SEO audit checklist, covering crawlability, indexing, site architecture, URLs, redirects, canonical tags, mobile experience, page speed, structured data, internal links, and other technical issues. You can use this checklist for a new website, an existing B2B website, or a site that has recently experienced an organic traffic or ranking drop.

What Is a Technical SEO Audit?

A technical SEO audit is a systematic review of the technical elements that affect how search engines access and understand a website. Unlike content SEO, which focuses heavily on keywords, search intent, and content quality, technical SEO focuses on the infrastructure behind the pages.

This includes questions such as: Can Google crawl your important pages? Are they allowed to be indexed? Are your canonical URLs configured correctly? Are there broken internal links? Does your sitemap contain the right URLs? Are redirects working properly? Does the website work well on mobile devices? Are pages loading efficiently? Can search engines understand your structured data?

Google provides several tools that can help with this process. The Google SEO Starter Guide provides general SEO guidance, while Google Search Console provides reports for indexing, performance, HTTPS, and individual URL inspection.

Technical SEO is not about making every technical metric perfect. The goal is to remove meaningful obstacles between your website, search engines, and potential customers.

Before You Start the Audit

Before opening an SEO crawler, define what you are auditing. A small company website with 30 pages requires a different process from a B2B manufacturer with thousands of product URLs. You should also understand the website’s business goals, important landing pages, target countries, product categories, and existing organic traffic.

For a B2B website, I normally start with the pages that matter most commercially: the homepage, product category pages, product detail pages, solution pages, industry pages, case studies, and high-performing articles. This makes it easier to connect technical SEO issues with actual business value instead of simply producing a long list of warnings.

Crawlability and Accessibility

The first part of a technical SEO audit is making sure search engines can actually access your website. If Google cannot crawl an important page, everything else becomes secondary.

1. Check Robots.txt

Review your robots.txt file and make sure it is not accidentally blocking important sections of the website. A common problem is adding a broad Disallow rule during development and forgetting to remove it when the website goes live.

Remember that robots.txt controls crawling, not necessarily indexing. Google explains that a URL blocked by robots.txt can still potentially appear in search results if Google discovers information about that URL elsewhere. If you need to prevent a page from being indexed, a noindex directive is generally the appropriate mechanism rather than simply blocking the page in robots.txt.

2. Check XML Sitemap

Your XML sitemap should contain the URLs you actually want search engines to discover and index. Remove unnecessary URLs such as redirected pages, obvious duplicates, and URLs that should not be indexed.

For larger B2B websites, the sitemap can become particularly useful because it gives search engines a structured list of important URLs. Submit the sitemap through Google Search Console and monitor whether Google can access it successfully.

3. Check Server Accessibility

A website can look perfectly normal in a browser while still experiencing server problems during crawling. Check for recurring 5xx errors, timeouts, DNS problems, hosting outages, and excessive server response times.

Google’s documentation recommends using Search Console and crawl-related reports to investigate server connectivity problems. Persistent server errors can prevent Google from reliably crawling your site.

4. Check HTTP Status Codes

Important pages should normally return a successful 200 status code. Redirected pages should return appropriate 3xx responses, while genuinely unavailable pages should return an appropriate 4xx response.

Pay special attention to internal links that point to 404 pages. A 404 page itself is not automatically an SEO problem, but an important page that has been removed without a replacement, or internal links that continue sending users and crawlers to dead URLs, should be reviewed.

5. Check Crawlability of Important Resources

Search engines need access to the resources required to understand and render your pages. Check whether important CSS, JavaScript, images, and other resources are accidentally blocked or inaccessible.

This is particularly important for modern WordPress websites that rely heavily on JavaScript, page builders, dynamic navigation, or third-party integrations. If the HTML contains little useful information and the important content only appears after complex JavaScript execution, investigate how search engines see the rendered page.

Indexing and Search Visibility

Crawling and indexing are related but different. A page can be accessible to Google and still not appear in the index. The next part of the audit is therefore checking whether your important pages are actually eligible for indexing.

6. Check the Page Indexing Report

Open Google Search Console and review the Page Indexing report. Do not assume that every excluded URL is a problem. Google explicitly notes that some pages should not be indexed, including duplicates, pages with intentional noindex directives, and removed URLs that correctly return 404 responses.

The important question is whether your valuable canonical pages are indexed. If product pages, service pages, or important articles are unexpectedly excluded, investigate the reason rather than focusing only on the total number of indexed URLs.

7. Inspect Important URLs

Use the URL Inspection Tool to check important pages individually. You can see whether Google has indexed the URL, whether crawling was allowed, which canonical URL Google selected, and whether structured data was detected.

Google’s URL Inspection documentation explains that the tool can show both information from Google’s index and results from a live test. This makes it useful when troubleshooting specific indexing problems.

8. Check Noindex Tags

Search your important pages for accidental noindex directives. This problem can happen during website development, migration, staging, plugin configuration, or bulk SEO setting changes.

If a page is supposed to rank but contains a noindex directive, fix the configuration and then use Search Console to request another crawl when appropriate.

9. Check Canonical Tags

Review the rel=”canonical” tags on important pages. The canonical URL should normally point to the preferred version of the page rather than an unrelated page, an old URL, or a redirected URL.

Canonicalization helps Google select a representative URL when multiple URLs contain duplicate or substantially similar content. Google considers signals such as redirects, sitemap inclusion, HTTPS, and canonical annotations when choosing canonical URLs.

10. Check Duplicate and Near-Duplicate Pages

Look for duplicate URLs created by parameters, filters, tracking parameters, tags, archives, pagination, or different versions of the same content. Not every duplicate URL requires aggressive action, but large numbers of unnecessary variations can make a website harder to manage and understand.

For B2B websites, common examples include duplicate product pages, manufacturer specifications repeated across multiple URLs, translated versions without proper language targeting, and old URLs left behind after a website migration.

Site Architecture and URLs

Technical SEO is not only about crawl errors. The way your website is structured affects how search engines and users understand the relationship between pages.

11. Review Website Architecture

Review whether your website has a logical hierarchy. A typical B2B manufacturing website might follow a structure such as Home → Products → Product Category → Product → Contact, while industry content may follow a separate path such as Home → Industries → Application → Solution.

A clear structure makes it easier to connect related pages and build an effective internal linking system.

12. Check URL Structure

URLs should be readable, consistent, and reasonably descriptive. Avoid unnecessarily complicated URLs containing meaningless IDs, excessive parameters, or multiple levels that do not represent the actual website structure.

For example, a URL such as /products/industrial-filtration/liquid-filter/ communicates more information than a URL such as /page?id=8274. The URL is only one SEO signal, but clean URLs make website management and reporting easier.

13. Check Redirects

Audit your 301 and 302 redirects and look for redirect chains, redirect loops, and irrelevant redirect destinations. A redirect should generally send visitors to the most relevant current page rather than automatically sending every old URL to the homepage.

This becomes particularly important after a website redesign or domain migration. Valuable old URLs with backlinks or organic traffic may need carefully mapped 301 redirects to relevant new URLs.

14. Find Orphan Pages

An orphan page is a page that has little or no internal links pointing to it from other pages on the website. These pages can be difficult for both users and search engines to discover through normal site navigation.

Use a crawler such as Screaming Frog to identify pages that exist in the XML sitemap or database but are not connected through the site’s internal linking structure. Important pages should normally have a clear place within the website architecture.

15. Audit Internal Links

Internal linking connects your content and helps users move from informational pages to commercial pages. It also gives search engines additional context about the relationship between pages.

For example, a B2B article about industrial filtration can naturally link to a filtration product category, while the product page can link back to relevant technical guides, applications, or case studies. This creates a stronger content-to-conversion path.

If you are building a B2B website from the ground up, the article What Pages Should a B2B Manufacturing Website Have? explains how different page types can work together as part of a broader website structure.

Technical Page Optimization

Once the site’s basic crawlability and architecture are under control, review the technical elements on individual pages. These issues are often easier to identify with a crawler and can affect both search visibility and user experience.

16. Check Title Tags

Every important indexable page should have a relevant and descriptive title tag. Avoid duplicate titles across large groups of pages and make sure the title accurately represents the page’s primary topic and search intent.

For B2B websites, product and service pages should usually be specific enough to communicate what the company actually offers instead of relying on generic titles such as “Products” or “Solutions.”

17. Check Meta Descriptions

Meta descriptions are not simply a place to repeat keywords. They should summarize the page clearly and give searchers a reason to understand what they will find after clicking.

For commercial B2B pages, a useful description can naturally include the product category, target application, supplier or manufacturer context, and a clear value proposition.

18. Check Heading Structure

Review the H1, H2, and H3 structure of important pages. A page should have a clear main topic, while subheadings should organize supporting information logically.

Do not treat heading tags as a place to insert every possible keyword. The goal is to create a structure that is useful for both users and search engines.

19. Check Image SEO

Review image file names, alternative text, image dimensions, formats, and loading behavior. Large unoptimized images are a common cause of slow pages, particularly on image-heavy manufacturing and product websites.

Use descriptive alt text when an image provides meaningful information. Avoid filling alt attributes with keyword variations that do not describe the actual image.

20. Check Broken Links

Run a full crawl to identify internal links pointing to 4xx pages, redirecting URLs, and other problematic destinations. Broken internal links create unnecessary friction for users and make your site architecture less reliable.

For a deeper explanation of when to keep a 404, when to fix an internal link, and when to use a 301 redirect, see Broken Links and 404 Errors: What Should You Fix?.

Performance and Mobile SEO

Technical SEO also includes the experience users have after they reach your website. A technically crawlable site can still provide a poor experience if pages are slow, unstable, or difficult to use on mobile devices.

21. Check Core Web Vitals

Review your Core Web Vitals, including Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. These metrics provide insight into loading performance, responsiveness, and visual stability.

Use Google PageSpeed Insights to test individual URLs and identify performance opportunities. For larger websites, combine page-level testing with real-user data where available.

22. Check Mobile Experience

Open your important pages on actual mobile devices and review navigation, buttons, forms, images, menus, tables, and content spacing. A responsive website should not simply shrink the desktop version; important interactions should remain easy to use on smaller screens.

Google’s Search Console documentation includes mobile usability as part of the information available for individual URLs.

23. Check HTTPS

Make sure the website consistently uses HTTPS and that important pages are not accessible through conflicting HTTP versions. Check redirects, canonical URLs, internal links, images, scripts, and other resources for mixed-content or protocol problems.

Google recommends HTTPS for websites, and Search Console provides an HTTPS report that can help identify indexed HTTP URLs.

24. Review JavaScript Rendering

Check whether important content, navigation, links, and metadata depend heavily on JavaScript. Modern search engines can render JavaScript, but unnecessary complexity can still create technical problems and make troubleshooting more difficult.

Use Google’s URL Inspection Tool and the rendered page view to compare what users see with what Google can access. This is particularly useful for JavaScript-heavy WordPress themes and websites built with dynamic page builders.

25. Check Server and Page Load Performance

Page speed problems do not always come from images. Hosting quality, server response time, excessive plugins, database queries, third-party scripts, large CSS files, JavaScript, fonts, and poorly optimized themes can all contribute to slow pages.

For WordPress B2B websites, I normally look at hosting performance, caching, image compression, WebP or modern image formats, CDN configuration, unnecessary plugins, script loading, and database efficiency rather than trying to solve everything with a single optimization plugin.

Structured Data and Search Signals

The final group of checks focuses on helping search engines understand the content and relationships represented on your pages.

26. Check Structured Data

Review whether your website uses appropriate structured data and whether the implementation contains errors. Depending on the page type, this may include Organization, BreadcrumbList, Article, Product, or other supported structured data types.

Structured data provides a standardized way to describe page content. Google recommends validating structured data and checking how Google sees the page through tools such as the Rich Results Test and URL Inspection.

27. Check Breadcrumbs

Breadcrumb navigation can be useful on websites with multiple levels of content. A B2B product website, for example, might use a structure such as Home → Products → Filtration → Industrial Filters.

Breadcrumbs are not required on every page. They are most useful when they reflect a real hierarchy and help users understand where they are within the website.

28. Check International SEO

If your company targets multiple countries or languages, review international SEO carefully. Check language versions, hreflang implementation where appropriate, country targeting, localized URLs, translated metadata, and internal links between language versions.

A common problem is creating multiple language versions without making the relationship between those versions clear. International SEO should support the actual market structure of the business rather than simply duplicating one website into several languages.

29. Check Search Console Performance Data

Technical SEO should not be separated completely from performance data. Review Google Search Console for impressions, clicks, average position, indexing changes, and query patterns.

Look for unusual drops or increases after technical changes such as website migrations, URL restructuring, theme changes, large-scale content updates, or robots.txt modifications. Search Console’s reports are particularly useful for connecting technical changes with changes in search visibility.

30. Crawl the Website Again After Fixes

A technical SEO audit should not end with a spreadsheet of problems. After implementing fixes, crawl the website again and compare the new results with the original audit.

This final step is often overlooked. A developer may fix one problem while accidentally creating another, especially when making changes to redirects, templates, canonical tags, navigation, or robots.txt. A second crawl gives you an opportunity to verify that the fixes actually worked.

The 30-Point Technical SEO Checklist

Here is the complete checklist in a more compact format:

1. Check robots.txt
2. Check the XML sitemap
3. Check server accessibility
4. Check HTTP status codes
5. Check crawlability of important resources
6. Review the Page Indexing report
7. Inspect important URLs
8. Check noindex tags
9. Check canonical tags
10. Check duplicate and near-duplicate pages
11. Review website architecture
12. Check URL structure
13. Audit redirects
14. Find orphan pages
15. Audit internal links
16. Check title tags
17. Check meta descriptions
18. Check heading structure
19. Check image SEO
20. Check broken links
21. Check Core Web Vitals
22. Check mobile experience
23. Check HTTPS
24. Review JavaScript rendering
25. Check server and page load performance
26. Check structured data
27. Check breadcrumbs
28. Check international SEO
29. Check Search Console performance data
30. Crawl the website again after fixes

How to Prioritize Technical SEO Issues

One of the biggest mistakes in a technical SEO audit is treating every issue as equally important. A crawler may return hundreds or even thousands of URLs with warnings, but that does not mean you need to fix everything immediately.

I recommend prioritizing issues according to SEO impact, business impact, and implementation difficulty. For example, an important product page accidentally blocked by noindex is usually much more urgent than a minor metadata warning on a low-value archive page.

A practical priority system can look like this:

• High priority: important pages cannot be crawled or indexed, incorrect canonical tags, major redirect problems, widespread 5xx errors, broken internal navigation, or serious website accessibility problems.
• Medium priority: duplicate metadata, orphan pages, weak internal linking, slow templates, missing structured data, and inconsistent URL structures.
• Low priority: minor warnings on low-value pages, cosmetic issues, or problems that do not affect important URLs or user experience.

This approach keeps technical SEO focused on business outcomes. The purpose of an audit is not to achieve a perfect crawler score. The purpose is to make sure your website can be discovered, crawled, understood, indexed, and used effectively by both search engines and potential customers.

Conclusion

A technical SEO audit is the foundation of a healthy B2B website. Before creating more blog posts or building more backlinks, make sure search engines can access your important pages, understand your website structure, identify the correct canonical URLs, and process your content without unnecessary technical obstacles.

The 30-point checklist above covers the areas I would review when auditing a B2B website: crawlability, indexing, URLs, redirects, internal links, on-page technical elements, mobile experience, performance, structured data, international SEO, and Search Console data.

Technical SEO also works best as an ongoing process rather than a one-time project. A website changes constantly as new products are added, old URLs are removed, content is updated, plugins are installed, and website designs evolve. Regular crawling and Search Console monitoring can help catch problems before they become larger SEO issues.

If your technical foundation is already solid, the next step is to connect it with keyword research, content strategy, internal linking, and conversion optimization. You can learn more in our guide to How to Create a Winning B2B SEO Campaign or explore our B2B Google SEO services.

FAQ

What is included in a technical SEO audit?

A technical SEO audit typically reviews crawlability, indexing, robots.txt, XML sitemaps, canonical tags, redirects, HTTP status codes, site architecture, internal links, page speed, mobile usability, HTTPS, structured data, JavaScript rendering, and other technical elements that can affect search visibility.

How often should I run a technical SEO audit?

For a small or medium-sized B2B website, a deeper technical SEO audit every few months can be useful, with ongoing monitoring through Google Search Console. Larger websites or websites that frequently add or remove pages may benefit from more frequent crawling and technical monitoring.

Can I run a technical SEO audit myself?

Yes. You can use Google Search Console for indexing and search performance data, while tools such as Screaming Frog can help crawl the website and identify technical issues. For larger websites, combining several data sources usually provides a more complete picture.

Does technical SEO improve Google rankings?

Technical SEO does not guarantee higher rankings by itself. Its main role is to make the website accessible, understandable, and technically sound so that search engines can properly process its pages. Rankings also depend on content quality, relevance, search intent, authority, competition, and other signals.

What should I fix first during a technical SEO audit?

Start with problems that affect important pages directly. Accidental noindex tags, blocked crawling, serious server errors, incorrect canonical tags, broken redirects, important 404 pages, and major internal linking problems generally deserve attention before minor metadata or low-value page warnings.

Is a 404 error always bad for SEO?

No. A 404 response is appropriate when a page genuinely does not exist and has no suitable replacement. The bigger problem is when important internal links point to 404 pages or when valuable old URLs with backlinks and organic traffic disappear without an appropriate redirect. You can read more in our guide to broken links and 404 errors.

What tools should I use for a technical SEO audit?

A practical technical SEO audit can use Google Search Console, Google PageSpeed Insights, Screaming Frog, and browser developer tools. Depending on the project, SEO platforms such as Semrush can also help identify technical issues, backlinks, keyword visibility, and competitor data.