How to Do a Technical SEO Audit Step by Step (Without an Agency)
A technical SEO audit step by step is one of the highest-leverage activities any site owner or marketer can run—and you do not need to hand it off to an agency to do it well. With the right process and tools, you can systematically surface crawl errors, indexing gaps, Core Web Vitals failures, and structured data problems in a single focused session, then prioritize fixes that directly move organic rankings.
Quick answer: A technical SEO audit step by step means working through six core areas in order: crawlability and indexation, XML sitemap health, robots.txt configuration, canonical tags, Core Web Vitals, and structured data. Start in Google Search Console to confirm what Google can and cannot index. Then run a site crawl to surface broken links, redirect chains, and missing metadata. Check your robots.txt and sitemap for blocking errors. Validate canonical tags to prevent duplicate-content dilution. Measure Core Web Vitals via PageSpeed Insights. Finally, audit structured data for errors that suppress rich results. Document every issue by severity, fix in priority order, and re-crawl to verify.
Why You Should Audit Your Own Site Before Calling an Agency
Agencies earn their fees on large, complex sites with legacy architecture and ongoing remediation needs. For most small-to-mid-size sites, the audit itself is learnable, repeatable, and far more actionable when the person running it also controls the CMS.
Running the audit yourself also builds institutional knowledge. You learn why a redirect chain hurts crawl budget, not just that it does. That understanding changes how you make decisions on every future site change.
If you want to compare your tooling options before diving in, the how to choose an SEO audit tool guide covers the decision framework in detail.
What Matters Most: How to Evaluate Audit Findings
Before walking through each step, here is the prioritization framework used throughout this guide:
| Severity | Impact | Examples |
|---|---|---|
| Critical | Blocks indexing entirely | Robots.txt disallowing Googlebot, noindex on key pages |
| High | Suppresses rankings or rich results | Broken canonical tags, missing structured data, LCP > 4 s |
| Medium | Wastes crawl budget or dilutes signals | Redirect chains, duplicate title tags, orphaned pages |
| Low | Incremental improvement | Missing meta descriptions, image alt text gaps |
Fix Critical issues before anything else. High-severity issues should be resolved within the same sprint. Medium and Low issues can be batched.
Step 1: Start in Google Search Console
Google Search Console is free, authoritative, and reflects what Google actually sees—not what your crawl tool infers.
Check the Coverage Report First
Open the Index > Pages report. Look at the "Not indexed" tab and categorize every reason listed. Common culprits include:
- "Crawled – currently not indexed" (quality or thin-content signal)
- "Excluded by 'noindex' tag" (intentional or accidental)
- "Blocked by robots.txt" (often accidental on staging configs pushed to production)
- "Redirect error" (broken redirect chains)
Export the full list. Any page that should be indexed but is not becomes a Critical or High priority fix.
Review Core Web Vitals in Search Console
The Experience > Core Web Vitals report segments URLs into Poor, Needs Improvement, and Good. Note which URL groups are failing—this tells you where to focus PageSpeed work later in the audit.
The Google SEO Starter Guide is the canonical reference for understanding how Google evaluates these signals.
Step 2: Audit Your XML Sitemap
Your XML sitemap tells search engines which URLs you want indexed. A poorly maintained sitemap actively misleads crawlers.
What to Check
- Does the sitemap URL (typically
/sitemap.xml) return a 200 status? - Are all submitted URLs returning 200 status codes? Sitemaps should never include 301s, 404s, or noindexed pages.
- Is the sitemap submitted in Google Search Console under Sitemaps?
- For large sites, is the sitemap split into a sitemap index file?
Google sitemap guidance specifies that sitemaps should only list canonical URLs. If your sitemap includes paginated URLs, parameter variants, or staging URLs, clean them out.
Step 3: Review Your Robots.txt File
Fetch yourdomain.com/robots.txt directly in a browser. A misconfigured robots.txt is one of the most common causes of catastrophic ranking drops after a site migration.
Check for:
- Any
Disallow: /directive that could block all crawlers - Disallow rules that accidentally block CSS, JavaScript, or key page directories
- Whether your sitemap URL is declared at the bottom of the file
Use Google Search Console's robots.txt tester (under Settings > Crawling) to test specific URLs against your current rules.
Step 4: Validate Canonical Tags
Canonical tags (<link rel="canonical">) tell search engines which version of a page is the authoritative one. Misconfigured canonicals are a leading cause of duplicate-content dilution and wasted crawl budget.
Common Canonical Errors
- Self-referencing canonicals missing: Every indexable page should have a canonical pointing to itself.
- Canonicals pointing to noindexed pages: This creates a contradictory signal.
- Canonicals pointing to 404 or redirected URLs: Wastes the signal entirely.
- Paginated pages canonicalizing to page 1: This tells Google to ignore pages 2–N entirely, which is usually wrong.
Run your crawl tool and filter for canonical mismatches. For deeper context on how internal linking reinforces canonical signals, see the guide on internal linking as an AI SEO signal.
Step 5: Measure Core Web Vitals
Core Web Vitals are Google's user-experience metrics: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).
How to Measure
- Run your key landing pages through Google PageSpeed Insights.
- Check both mobile and desktop scores—mobile is the primary signal under mobile-first indexing.
- Note the specific elements causing LCP delays (typically unoptimized hero images or render-blocking scripts).
- Check CLS for layout shifts caused by ads, embeds, or fonts loading after content.
Quick Wins
- Serve images in WebP format with explicit width and height attributes.
- Defer non-critical JavaScript.
- Preload your LCP image element.
- Use a CDN for static assets.
Step 6: Audit Structured Data and Schema Markup
Structured data helps search engines understand entity relationships on your pages and enables rich results (star ratings, FAQs, breadcrumbs, product prices). Errors in your schema suppress these enhancements.
How to Audit Schema
- Use Google Search Console's Enhancements section to see which schema types are detected and whether any have errors or warnings.
- Run individual pages through Google's Rich Results Test.
- Check that your schema types match your actual content (do not mark up a blog post as a Product).
The Google Search Central structured data guide covers every supported schema type and the required/recommended properties for each.
For sites that want to automate schema deployment at scale, the post on AI schema automation for SEO and AI answer engines explains how structured data also feeds AI-driven retrieval systems like Google AI Overviews and Perplexity.
Step 7: Assess Crawl Budget Efficiency
Crawl budget matters most for sites with thousands of pages, but the habits that protect it are worth building early.
Signs of Crawl Budget Waste
- Large numbers of low-value URLs being crawled (parameter URLs, session IDs, faceted navigation)
- Redirect chains longer than one hop
- Orphaned pages with no internal links pointing to them
- Duplicate pages accessible via multiple URL paths
Review your crawl log data if your hosting environment supports it. Google Search Console's Crawl Stats report (under Settings) shows how many pages Googlebot crawls per day and the response time distribution.
If you want to go deeper on how AI-powered tools can accelerate this analysis, the guide on using AI for technical SEO audits covers the workflow in detail.
Technical SEO Audit Checklist
Use this checklist to track progress through each audit session:
- Confirm Google Search Console access and review Coverage report
- Export all non-indexed URLs and categorize by reason
- Check Core Web Vitals report in Search Console
- Fetch and validate robots.txt for blocking errors
- Submit and validate XML sitemap in Search Console
- Run a full site crawl and export broken links, redirect chains, and missing metadata
- Audit canonical tags for mismatches, missing tags, and contradictory signals
- Run key pages through PageSpeed Insights (mobile and desktop)
- Validate structured data in Rich Results Test and Search Console Enhancements
- Review Crawl Stats for anomalies
- Prioritize all findings by severity (Critical → High → Medium → Low)
- Implement fixes and re-crawl to verify resolution
For a side-by-side look at which tools handle each of these steps best, the best SEO audit tools compared post covers the current landscape.
Frequently Asked Questions
How long does a technical SEO audit take to do yourself?
A thorough DIY technical SEO audit typically takes 2–4 hours for a site under 500 pages. Using an automated audit tool can compress the crawl and analysis phase to under 30 minutes, leaving you time to prioritize and fix issues.
What is the most important thing to check in a technical SEO audit?
Indexability is the single most critical check—if Google cannot crawl and index your pages, no other optimization matters. Start with Google Search Console's Coverage report and your robots.txt file before anything else.
Do I need to hire an agency to run a technical SEO audit?
No. With the right checklist and a site audit tool, most site owners and in-house marketers can complete a professional-grade technical SEO audit without an agency. Agencies add value for large, complex sites or ongoing remediation work.
What tools do I need for a technical SEO audit?
At minimum you need Google Search Console (free), a crawl tool such as Screaming Frog or an all-in-one platform, and Google PageSpeed Insights for Core Web Vitals. An AI-powered audit platform can consolidate all of these into a single workflow.
How often should I run a technical SEO audit?
Run a full technical SEO audit at least once per quarter, and after any major site change such as a redesign, CMS migration, or significant content restructure. Continuous monitoring via automated tools is ideal for catching regressions early.
Sources and Further Reading
Your Next Step
The fastest way to move from this checklist to actual fixes is to run your site through an audit tool that surfaces all seven areas in a single report. Work through the Critical findings first—resolve any indexing blocks before touching on-page or performance issues. Then schedule a re-crawl within two weeks to confirm the fixes registered. A technical SEO audit step by step is only valuable if the findings turn into resolved issues, not a spreadsheet that ages in a shared drive.
← All posts