A technical SEO audit identifies the structural, crawlability, and content issues that prevent a site from ranking. Done correctly, it gives you a prioritized list of fixes that move the needle. Done poorly, it produces a spreadsheet nobody acts on.
This guide covers every layer of a technical audit, from crawl configuration and HTTPS verification to on-page metadata and schema validation. Each section explains what to check, why it matters, and who owns the fix.
Two roles drive a technical audit: the SEO specialist or copywriter handles indexability signals, content quality, metadata, and structured data. The developer owns server-level configuration, redirects, HTTPS, and performance. Both roles share responsibility for the final audit report.
1. Indexing and Crawlability: Where Every Technical SEO Audit Starts
Crawlability determines whether Googlebot can reach your pages. Indexability determines whether it chooses to include them. Problems at either layer will suppress rankings regardless of content quality.
Google Index Checks
Start with Google Search Console (GSC). Open the Coverage report and check for pages with Crawled but not indexed or Discovered but not indexed status. Both signal that Googlebot found the URL but decided not to include it. The cause is almost always a quality signal, a crawl budget issue, or a misconfigured directive.
Verify the homepage appears in Google cache by searching cache:yourdomain.com. A stale or missing cache entry means Google has not crawled the page recently, which is a red flag for crawl frequency.
Run a branded keyword search. If the homepage does not rank in position 1 for its own brand name, there may be a deeper indexability problem or a trust issue worth investigating.
Indexability Signals
Open the robots.txt file at yourdomain.com/robots.txt. This file tells search engine crawlers which pages or directories they are allowed to access. Look for Disallow directives that block important pages. A common error is blocking /wp-admin/ incorrectly and accidentally catching CSS or JS directories that Googlebot needs to render pages.
Check every important page for noindex tags in the head section. A noindex tag is a directive that tells Google not to include the page in its search results. A single misplaced noindex on a category hub can silently remove hundreds of pages from the index. Screaming Frog flags these at scale under the Directives tab.
Review nofollow tags on important pages. A nofollow attribute tells Google not to pass ranking credit through that link. Nofollow on internal links reduces PageRank flow (the signal Google uses to determine how authoritative a page is) to the linked page. It is rarely appropriate on navigation links or cornerstone content.
X-Robots-Tag headers work the same way as meta robots tags, but operate at the HTTP response level rather than in the page’s HTML. They are harder to spot and can block entire directories. Check them via a curl request: curl -I https://yourdomain.com/page-url/.
Google Search Console Configuration
GSC is the primary data source for any technical SEO audit. It provides direct data from Google about how the crawler sees and indexes the site. Check the Indexing report weekly, not just during audits. Configure geographic targeting under Legacy Tools if the site serves a single market.
Submit the XML sitemap under Sitemaps. Monitor its indexing rate. A sitemap with a low indexed percentage signals that Googlebot is finding URLs it does not want to include.
Review Manual Actions under Security and Manual Actions. A manual penalty will suppress all rankings until resolved. These are rare but severe.
Canonical Tags
Every indexable page should carry a self-referencing canonical tag pointing to its own URL. A canonical tag is an HTML element that tells Google which version of a page is the preferred one for indexing. Pages without canonicals are more susceptible to duplicate content issues.
Check for conflicting canonical signals. A page with a canonical pointing to Page A but also included in a sitemap pointing to Page B sends contradictory signals. Google may ignore the canonical entirely.
On WordPress sites, attachment pages for uploaded media are indexed by default. These are thin pages that dilute crawl budget and add zero ranking value. Redirect them to the parent post or noindex them at scale.
2. SSL and HTTPS Audit Checks
HTTPS (the secure version of the HTTP protocol) is a confirmed Google ranking signal and a prerequisite for browser security indicators. An SSL (Secure Sockets Layer) certificate enables HTTPS by encrypting data between the server and the user’s browser. A site running on plain HTTP in 2025 will display a Not Secure warning in Chrome, which depresses user trust and click-through rates before a ranking issue even enters the picture.
Verify the SSL certificate is installed and valid. Check the expiration date. Certificates that expire without renewal cause Chrome to block the page entirely. Set a calendar reminder 30 days before the expiry date.
Confirm a 301 redirect (a permanent redirect that passes full link equity) is in place from HTTP to HTTPS for every page. A 302 redirect signals a temporary move and passes less link equity. Redirect chains through multiple hops bleed ranking credit with each additional step.
Scan for mixed content warnings using Chrome DevTools or a tool like Why No Padlock. Mixed content occurs when an HTTPS page loads assets over HTTP. Images, scripts, and stylesheets are the most common culprits. Google treats pages with mixed content warnings as insecure.
3. Duplicate URL Management in a Technical SEO Audit
Duplicate URLs dilute PageRank and confuse Googlebot about which version of a page to index. Choose one canonical version and redirect all alternatives to it with a 301.
Decide between www and non-www at the outset. Both resolve to the same site for users, but Google treats them as separate domains without a redirect. Implement a 301 from the non-preferred version to the preferred one, then confirm the canonical matches.
Redirect duplicate homepage patterns. URLs like /index.php, /index.html, and /default.aspx create multiple versions of the homepage. Each one splits link equity and adds a duplicate content signal.
Audit for cloned websites or duplicate subdomains. Staging environments left public, microsites mirroring the main domain, or translated versions without hreflang tags (the HTML attribute that tells Google which language and region a page is intended for) are the most common sources.
4. Website Security Checks in Your SEO Audit
A compromised site will lose rankings before you notice the hack. Google’s Safe Browsing system flags sites hosting malware, and a manual security action in GSC removes pages from the index entirely.
Check the Security Issues report in GSC regularly. It flags hacked content, malware, and deceptive pages. A clean report does not guarantee security, but an active report demands immediate action.
Scan for suspicious outbound links by crawling the site with Screaming Frog and exporting the external links report. Injected outbound links to gambling, pharma, or adult sites are a common indicator of a successful hack.
Verify the site still ranks for its primary branded keyword. A sudden drop in branded rankings can indicate a penalty, a hack, or a de-indexation event before the GSC report surfaces the issue.
5. Auditing Redirects, Errors, and Broken Links
Redirect issues are among the most common causes of lost PageRank on established sites. Each unnecessary redirect hop reduces the equity passed to the destination page.
Audit all 302 redirects. Temporary redirects do not pass link equity the way 301 redirects do. A 302 in place for more than a few days should almost always be converted to a 301.
Check for redirect loops. A loop occurs when Page A redirects to Page B, which redirects back to Page A. Googlebot will abandon the crawl after a limited number of hops.
Configure a custom 404 page that returns a true 404 server status code. Soft 404s are a separate problem: they occur when a page returns a 200 OK status (meaning the server thinks the page exists) but displays content that clearly signals the page does not. Google treats soft 404s as low-quality pages and may index them.
Fix broken internal links. A crawl with Screaming Frog will export all 4XX responses. Work through the list from the highest internal link count down.
Review external links pointing away from the site. Remove or disavow links to irrelevant or low-trust destinations. An excessive number of outbound links to spammy domains is a trust signal problem.
6. Website Performance and Core Web Vitals in a Technical Audit
Core Web Vitals are a direct ranking factor. Google uses field data from Chrome users to assess Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) at the URL level.
Run the URL Inspection tool in GSC for key pages. Check the Core Web Vitals report for URLs flagged as Poor or Needs Improvement. The Page Experience report groups URLs by issue type so fixes can be batched.
Compress images before upload. Uncompressed images are the single most common cause of slow LCP scores. Use next-gen formats like WebP and AVIF. Configure lazy loading for below-the-fold images.
Enable browser caching for static assets. A browser that caches CSS, JavaScript, and image files does not re-download them on subsequent visits, which reduces load time for returning users.
Test responsive layouts on multiple devices using Chrome DevTools. Mobile usability errors in GSC will suppress mobile rankings. Common problems include text too small to read, clickable elements too close together, and viewport not configured.
7. On-Page SEO Audit: Metadata and Headings
On-page SEO signals tell Google what a page is about and whether it satisfies the search query. Missing or duplicated metadata is the fastest audit win because it is cheap to fix and directly affects click-through rates.
Export a full list of title tags from Screaming Frog. Flag duplicates, missing tags, and titles over 65 characters (which truncate in SERPs). Each title tag should include the primary keyword near the front and match the page’s search intent.
Check meta descriptions. They are not a ranking factor, but they influence click-through rate. A compelling meta description under 155 characters, written to match the user’s intent, earns more clicks than an auto-generated one.
Audit H1 tags. Each page should have exactly one H1 that matches the title tag intent. Multiple H1s on a single page create ambiguity about the primary topic. No H1 at all wastes the clearest on-page relevance signal available.
Review ALT text on all images. Empty ALT attributes are missed indexing opportunities. Write a descriptive text that explains what the image shows. Avoid keyword stuffing: the ALT attribute is for accessibility first, SEO second.
8. How to Audit Structured Data and Schema Markup
Schema markup helps Google understand what a page represents and can generate rich results in SERPs (search engine results pages). Errors in schema implementation suppress eligibility for these enhancements.
Use Google’s Rich Results Test to validate schema on key page types. Check for errors and warnings separately. Errors mean the markup is invalid and the page is ineligible for rich results. Warnings mean optional fields are missing and enhancements could be improved.
The schema types with the highest SERP impact for most sites are Organization, LocalBusiness, Product, FAQPage, and BreadcrumbList. Implement the ones relevant to the site’s content and business model.
FAQPage schema is worth specific attention. It generates accordion-style rich results that take up significantly more SERP real estate. Each question and answer must match the visible content on the page.
BreadcrumbList schema supports sitelinks in search results. Implementing it consistently across category and subcategory pages improves navigational clarity for both Googlebot and users.
9. XML Sitemap Audit: What to Check and Fix
The sitemap is your communication channel with Googlebot. It tells the crawler which URLs you consider important and want indexed. A poorly maintained sitemap sends conflicting signals.
Confirm sitemap.xml exists and is accessible at yourdomain.com/sitemap.xml. Submit it in GSC under Sitemaps. Monitor the ratio of submitted URLs to indexed URLs in the report. A significant gap signals quality or crawl budget issues — crawl budget being the number of pages Googlebot will process on a site within a given timeframe.
Include only indexable URLs in the sitemap. Noindexed pages, paginated duplicates, and redirected URLs should not appear. A sitemap that includes noindexed pages contradicts itself: you are simultaneously telling Google to include the page and to exclude it.
Remove broken URLs and redirected URLs from the sitemap. Every URL in the sitemap should return a 200 status and be the canonical version of that page.
10. Pagination SEO Audit Checks
Paginated pages are a common source of duplicate content and crawl budget waste. Google’s guidance since 2019 is to let paginated pages be indexed individually and use canonical tags to signal the primary version.
Audit canonical tags on paginated URLs. Each paginated page, /page/2/, /page/3/, and so on, should carry a self-referencing canonical rather than a canonical pointing back to page 1.
Ensure paginated pages remain crawlable. Blocking paginated URLs in robots.txt prevents Googlebot from discovering linked products or content, which reduces the crawl depth of the site.
11. Content Quality Audit: Search Intent and Thin Content
Content quality is a ranking factor through Google’s Helpful Content system, which is now incorporated into the core algorithm. Thin, duplicated, or intent-mismatched content affects the entire domain, not just the individual page.
Check the homepage for unique, substantive content. A homepage that exists only for navigation or brand messaging, with no content that answers user queries, misses a high-authority ranking opportunity.
Identify keyword stuffing across category and product pages. Unnatural repetition of the focus keyword raises a spam flag in Google’s quality review process. The target is natural readability with keyword placement that matches how users search.
Scan for hidden SEO content by comparing the rendered DOM with the raw HTML source. Content that is hidden via CSS or JavaScript from users but visible to Googlebot is a cloaking signal.
Verify that keyword targeting matches search intent at the page level. A page targeting a commercial keyword with purely informational content will not rank because it does not satisfy what the query implies the user wants.
12. Internal Linking: A Key Part of Any Technical SEO Audit
Internal links distribute PageRank and tell Google which pages the site considers most important. Weak internal linking leaves high-value pages under-supported, regardless of their content quality.
Add footer links to key category pages and promoted content hubs. Footer links appear on every page and create a consistent crawl path to the pages that matter most.
Use Screaming Frog’s internal link report to find orphaned pages. An orphaned page has no internal links pointing to it. Googlebot relies on internal links to discover and crawl pages. An orphaned page may be discovered through the sitemap, but it receives no PageRank flow.
Use descriptive anchor text for internal links. Generic anchors like click here or read more pass no topical signal. Anchors that include the target page’s focus keyword reinforce relevance for that keyword.
13. Auditing Trust Signals and E-E-A-T
Google’s quality raters use E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) as the framework for evaluating content quality on YMYL topics. YMYL — Your Money or Your Life — covers any content where inaccurate information could affect a reader’s financial decisions, legal standing, or business outcomes. A site without visible trust signals scores lower in quality reviews.
Confirm the following pages exist and contain substantive content: Terms of Use, Privacy Policy, Cookie Policy, About Us, and Contact Us. Missing any of these is a basic trust failure.
Ensure social media profiles match the information on the website. Name, address, and phone number (NAP) inconsistency between the website and social profiles undermines local trust signals.
Encourage user reviews where appropriate. Verified third-party reviews on platforms like Trustpilot or Google Business Profile support the Authoritativeness dimension of E-E-A-T.
14. Local SEO Audit: Google Business Profile and NAP Consistency
Local SEO applies to any business with a physical location or geographic service area. A mismatch between the information on the site and the Google Business Profile will suppress local pack rankings.
Verify NAP consistency across every touchpoint. NAP stands for Name, Address, and Phone Number — the three data points Google uses to confirm a business’s identity across the web. The NAP must be identical on the website, Google Business Profile, social media profiles, and local directories.
Claim and fully populate the Google Business Profile. A complete profile with accurate categories, business hours, photos, and a description ranks significantly better in local pack results than an incomplete or unclaimed one.
Implement the LocalBusiness schema on the contact page. Include the business name, address, phone, URL, and geo-coordinates. This reinforces the NAP signal at the structured data level.
15. The Final Audit Report: How to Prioritize and Present Fixes
An audit that produces a list of 200 issues in no particular order will not get acted on. The deliverable that moves the needle is a prioritized roadmap tied to estimated ranking impact.
Document every issue with three details: what the problem is, where it appears, and what the fix requires. Vague audit items like fix duplicate content or improve site speed get deprioritized because nobody knows where to start.
Group issues by severity: critical (blocks indexing or ranking), high (PageRank loss or content quality impact), medium (trust and UX signals), and low (marginal improvements). Address critical and high-priority items in the first sprint.
Assign each fix to the correct role. Developers handle server-side changes. Copywriters and SEO specialists handle content, metadata, and schema.
Re-test the site after each fix batch is deployed. Technical SEO issues interact with each other. Fixing a redirect chain may reveal a canonical conflict that was previously masked.
Tools for a Technical SEO Audit
Screaming Frog SEO Spider handles crawl data, internal link analysis, redirect chains, broken links, metadata exports, and canonical tag audits. It covers the majority of technical checks listed above.
Google Search Console provides index coverage, Core Web Vitals, manual actions, and sitemap status directly from Google’s own data. No audit is complete without it.
Google PageSpeed Insights or Lighthouse gives lab data for Core Web Vitals on individual URLs. Use it to diagnose specific performance issues on key pages.
Google’s Rich Results Test validates schema markup and shows whether a page is eligible for rich results.
Chrome DevTools is the go-to tool for checking rendered HTML versus source HTML, testing mobile responsiveness, and diagnosing mixed content warnings.
Where to Start
Open GSC and run a Screaming Frog crawl in parallel. Check the Coverage report first. If there are pages with indexing errors, that is your starting point.
Work through the 15 sections in this guide in order. Crawlability and indexability problems cascade into every other area of the audit. Fix those first, then move to HTTPS, redirects, and content quality.
A technical audit is not a one-time task. The sites that rank consistently are the ones where crawl health, indexability, and content quality are maintained on a regular schedule.
Technical SEO Audit FAQs
How long does a technical SEO audit take?
A focused audit of a site with under 500 pages takes 4 to 8 hours, including crawl time. Larger sites with 10,000+ pages require a staged approach: crawl configuration first, then indexability, then content quality checks. Factor in time to document and prioritize findings.
How often should you run a technical SEO audit?
Run a full audit quarterly on active sites. Monitor GSC weekly for indexing errors, manual actions, and Core Web Vitals regressions. After any major site migration or CMS update, run an immediate full audit before the changes propagate fully.
What is the most important part of a technical SEO audit?
Indexability comes first. If Google cannot crawl and index your pages, nothing else in the audit matters. Start with the GSC Coverage report, robots.txt, and noindex tags before looking at any other signal.
Can a copywriter perform a technical SEO audit without a developer?
A copywriter can handle the content layer of an audit: metadata, on-page signals, schema validation, content quality, and canonical tags. The server-side checks, HTTPS configuration, redirect implementation, and performance optimization require developer access. Both roles are needed for a complete audit.
