The 80-Point Technical SEO Audit Checklist: Fix What’s Holding Your Site Back

A technical SEO audit separates sites that rank from sites that stall. You can publish exceptional content, earn quality backlinks, and still watch competitors outrank you — because Googlebot can’t crawl your pages properly, Core Web Vitals are tanking your rankings, or duplicate content is splitting your link equity. This 80-point technical SEO audit checklist covers every variable that matters, organized the same way top agencies run audits for enterprise clients. Work through it systematically, and you’ll find the exact issues holding your site back.

Why Technical SEO Audits Make or Break Rankings

Content and links get the credit. Technical SEO does the work that makes them matter. Google’s crawlers operate on a fixed budget per domain — if they’re wasting crawl budget on duplicate URLs, redirect chains, and blocked resources, your best pages go unindexed. Core Web Vitals directly affect rankings. Structured data affects how your listings appear in search. Every technical failure has a measurable cost.

Top agencies run technical audits before touching content strategy. There’s no point optimizing pages that can’t be crawled, indexed, or rendered. This 80-point checklist replicates that process so you can self-audit with the same rigor.

Section 1: Crawlability and Indexability (Points 1–15)

1. Robots.txt Configuration

Check that your robots.txt is accessible at yourdomain.com/robots.txt and isn’t accidentally blocking important directories. Common errors: blocking /wp-admin/ (fine) alongside /wp-content/ (breaks CSS/JS loading for crawlers). Verify the file specifies the correct sitemap URL at the bottom.

2. XML Sitemap Completeness

Your sitemap should include all canonical, indexable URLs — nothing with noindex tags, nothing blocked in robots.txt, and no redirect URLs. Submit the sitemap to Google Search Console and check for errors. Sitemaps larger than 50,000 URLs need to be split into multiple files with a sitemap index.

3. Sitemap Freshness

Stale sitemaps omit recently published pages. Confirm your CMS auto-updates the sitemap on publish. For large sites, check the lastmod timestamps — they should reflect actual content changes, not server timestamps.

4. Crawl Budget Utilization

Use Google Search Console’s Crawl Stats report to check how many pages Googlebot crawls per day and where it spends the most time. If crawl demand is high but pages aren’t getting indexed, you have a crawl budget problem — usually caused by faceted navigation parameters, session IDs, or infinite scroll generating thousands of URLs.

5. URL Parameter Handling

E-commerce and large content sites often generate duplicate content through URL parameters (sorting, filtering, tracking). Use Google Search Console’s URL Parameters tool or implement canonical tags to consolidate these. ?sort=price&filter=blue and ?filter=blue&sort=price pointing to different URLs is a crawl budget disaster.

6. Canonical Tag Implementation

Every indexable page should have a self-referencing canonical tag. Paginated pages should canonicalize to themselves (not to page 1). Check for canonical chains — canonicals pointing to pages that themselves have canonicals — and for canonical mismatches between HTTP/HTTPS versions.

7. Noindex Tag Audit

Audit every noindex tag on the site. Staging environment pages, thank-you pages, and admin areas should be noindexed. Product archive pages and category pages usually shouldn’t. Check that noindex pages aren’t receiving internal links (wasted link equity) and aren’t in your sitemap.

8. HTTP Status Code Audit

Crawl the site with Screaming Frog or Ahrefs and export all non-200 status codes. Every 404 that receives internal links is equity evaporation. Every 5xx error is a crawl failure. Every 302 redirect (temporary) that should be a 301 (permanent) loses PageRank transfer efficiency.

9. Redirect Chain Analysis

Redirect chains (A→B→C) slow crawlers and dilute link equity. Every hop after the first loses roughly 15% of PageRank. Map all redirect chains and collapse them to single-hop redirects. Tools: Screaming Frog’s redirect chain report, or the Ahrefs site audit redirect section.

10. Orphan Page Detection

Orphan pages — pages with no internal links pointing to them — rarely get crawled or indexed. Pull your sitemap URLs and compare against your internal link structure. Pages in the sitemap that have zero internal links pointing to them are orphaned and need to be integrated into the site’s link architecture.

11. Crawl Depth Analysis

Pages more than 3-4 clicks from the homepage get crawled infrequently. Use Screaming Frog’s crawl depth report to identify important pages buried deep in your site architecture. High-value pages should be reachable within 2-3 clicks from the homepage.

12. JavaScript Rendering Check

Google renders JavaScript, but not on first crawl — rendering happens in a second wave that can take days or weeks for new content. Use Google Search Console’s URL Inspection tool and click “Test Live URL” to see what Googlebot actually renders. Critical content hidden behind JS that only executes client-side may never be indexed.

13. Hreflang Implementation (International Sites)

For multilingual or multi-regional sites, hreflang tags must be consistent across all language variants — every page in the cluster must reference every other page in the cluster. Missing return tags or incorrect language codes cause international targeting failures.

14. Mobile Googlebot Crawlability

Google uses mobile-first indexing, so Googlebot crawls your site primarily as a mobile user agent. Test all important pages with Google’s Mobile-Friendly Test and check that the mobile version of the page loads the same content as desktop — hidden content in mobile views doesn’t get indexed.

15. Blocked Resources

Check robots.txt isn’t blocking CSS, JavaScript, or image files that Google needs to render pages. If Googlebot can’t load your CSS, it can’t assess your page’s visual experience for Core Web Vitals. Use Search Console’s URL Inspection to check “Page Resources” for blocked items.

Section 2: Site Architecture and Internal Linking (Points 16–25)

16. Silo Structure Assessment

Topical authority builds through silo architecture — grouping related content under logical category hubs. Audit whether your URL structure and internal linking reflect a clear topical hierarchy. A flat site where everything lives at the root level misses the opportunity to concentrate topical signals in subject-matter clusters.

17. Internal Link Distribution

Run a crawl and check the internal link count per page. Cornerstone pages and high-value commercial pages should receive the most internal links. Blog posts and supporting content should link up to pillar pages. If your highest-traffic commercial pages have fewer internal links than random blog posts, redistribute equity deliberately.

18. Anchor Text Diversity

Anchor text sends ranking signals. Audit the anchor text distribution for your most important pages — you want a mix of exact-match, partial-match, brand, and navigational anchors. Over-optimization (90%+ exact match) can trigger algorithmic penalties. Under-optimization (all brand anchors) misses ranking signals.

19. Pagination Handling

Google deprecated rel="prev/next" pagination signals in 2019. The current best practice for paginated content: ensure each page is independently valuable and crawlable, use canonical tags appropriately, and link to paginated pages from relevant category pages so crawlers can discover them.

20. Faceted Navigation Control

Faceted navigation creates URL explosion on e-commerce sites. Audit which facets generate indexable URLs versus parameterized URLs. High-traffic filter combinations (e.g., “blue running shoes size 10”) may warrant indexed pages; low-volume combinations should be canonicalized or noindexed.

21. Broken Internal Links

Every broken internal link is a crawl signal degradation. Crawl the site and fix all internal 404s. This is basic hygiene — there’s no excuse for broken internal links on a maintained site.

22. Link Equity Leakage

Check that you’re not passing link equity to pages that don’t need it: privacy pages, login pages, terms and conditions. These often sit in global footer links and receive significant link equity that could be redirected to commercial pages. Use nofollow on footer utility links where appropriate.

23. Hub Page Authority

Your category/pillar pages should be among the most authoritative pages on the site by internal link count and external links. Audit whether your site architecture actually concentrates authority on the pages you most need to rank.

24. Click Path Efficiency

Important content should be reachable in the fewest clicks. Map your top-revenue product/service pages and count the click depth from homepage. If key pages require 5+ clicks, implement breadcrumbs, featured category sections, or site architecture restructuring.

25. XML Sitemap vs. Crawled Pages Gap

Compare the number of URLs in your sitemap against the number Google has crawled and indexed (visible in Search Console). A large gap means Google is choosing not to index submitted pages — a signal to investigate crawl budget, duplicate content, or thin content issues.

Section 3: On-Page Technical Elements (Points 26–40)

26. Title Tag Optimization

Every page needs a unique title tag under 60 characters that leads with the primary keyword. Audit for duplicate title tags (common on e-commerce sites with filtered URLs), missing title tags, and title tags that exceed the pixel width Google displays (~580px). Screaming Frog exports these in bulk.

27. Meta Description Coverage

While meta descriptions don’t directly affect rankings, they influence click-through rates, which affect traffic. Audit for missing meta descriptions — Google auto-generates them when absent, usually poorly. Pages with CTRs below the average for their SERP position are candidates for meta description rewrites.

28. H1 Tag Audit

Every page should have exactly one H1 tag that includes the primary keyword. Audit for: missing H1s, multiple H1s (common with CMS themes adding H1s around the site title), and H1s that don’t match the title tag intent.

29. Heading Hierarchy

Heading structure (H1→H2→H3) should be logical and nested correctly. Skipped heading levels (H1→H3, no H2) signal poor document structure to crawlers. Audit heading hierarchies across high-value pages.

30. Keyword Cannibalization Detection

When multiple pages target the same keyword, they compete with each other and confuse Google about which to rank. Use Ahrefs’ “Top Pages” report filtered by keyword to find cannibalization. Fix by consolidating pages, using canonical tags, or differentiating content focus.

31. Duplicate Content Analysis

Run a site crawl and check for near-duplicate or exact-duplicate content. Common sources: printer-friendly page versions, tag/category overlap with post content, thin category pages, and product descriptions copied from manufacturer specs. Each duplicate case needs a canonical, redirect, or noindex solution.

32. Image Alt Text Coverage

Images need descriptive alt text for both accessibility and search visibility (image search, accessibility signals). Audit for images with empty alt attributes, generic alt text (“image1.jpg”), and keyword-stuffed alt text. Informational images need descriptive alt text; decorative images should use alt="".

33. Image File Optimization

Oversized images are one of the most common Core Web Vitals killers. Audit image file sizes — hero images above 200KB need compression. Convert to WebP/AVIF format. Implement lazy loading for below-the-fold images. Check that images are properly sized for their display dimensions.

34. Structured Data Implementation

Structured data (Schema.org JSON-LD) enables rich results in SERPs — review stars, FAQ snippets, breadcrumbs, product prices. Audit what structured data exists, validate it with Google’s Rich Results Test, and identify opportunities where structured data could enhance SERP appearance for high-traffic pages.

35. Open Graph and Twitter Card Tags

Social sharing metadata affects how your content appears when shared on social platforms. Missing OG tags result in poorly formatted share previews that reduce CTR from social channels. Audit for missing OG:title, OG:description, OG:image, and Twitter Card tags across key page types.

36. Thin Content Pages

Pages with fewer than 300 words of meaningful content are typically thin content. Audit for these using Screaming Frog’s word count report. Decision matrix: if the page serves a user need (contact page, checkout page), it’s fine thin; if it’s a content page competing for keywords, it needs expansion or consolidation.

37. Content Freshness Signals

For evergreen content competing in queries where freshness matters (news, product categories, comparison queries), Google factors in update dates. Audit whether high-priority pages have been recently updated and whether their lastmod in the sitemap reflects genuine content updates.

38. E-E-A-T Signals

Experience, Expertise, Authoritativeness, Trustworthiness signals affect how Google’s Quality Raters assess content, which influences algorithmic treatment. Audit: author bios with credentials, bylines on all content pages, contact information visibility, privacy policy and terms presence, citations for statistics and claims.

39. URL Structure Quality

URLs should be short, descriptive, and keyword-relevant. Audit for: URLs with parameters that should have static structures, excessively long URLs (>100 characters), URLs with stop words, and date-based URL structures for evergreen content that artificially date the page.

40. Canonical URL Consistency

Canonical URLs should be consistent across all references to a page — the canonical tag, the sitemap URL, the internal links, and the preferred URL in Google Search Console. Inconsistencies cause Google to make its own canonicalization decisions, which often differ from what you intend.

Section 4: Page Speed and Core Web Vitals (Points 41–55)

41. Largest Contentful Paint (LCP)

LCP measures how quickly the largest visible element loads. Target: under 2.5 seconds. Common LCP elements: hero images, large text blocks, video thumbnails. Audit LCP for your top 10 landing pages using PageSpeed Insights. Fixes: preload the LCP element, optimize image delivery, eliminate render-blocking resources.

42. Cumulative Layout Shift (CLS)

CLS measures visual stability — how much page elements shift during loading. Target: under 0.1. Common CLS sources: images without dimensions, ad slots loading after content, web fonts causing text reflow, dynamically injected content. Audit CLS in Google Search Console’s Core Web Vitals report.

43. Interaction to Next Paint (INP)

INP replaced FID in 2024 and measures responsiveness to user interactions. Target: under 200ms. Heavy JavaScript execution, long tasks blocking the main thread, and third-party scripts are the primary INP culprits. Audit using Chrome DevTools’ Performance panel and web.dev/measure.

44. Time to First Byte (TTFB)

TTFB measures server response time. Target: under 800ms, ideally under 200ms. High TTFB indicates server-side issues: slow database queries, no page caching, unoptimized hosting, lack of CDN. Check TTFB across multiple geographic locations using WebPageTest.

45. JavaScript Execution Audit

Excessive JavaScript is the root cause of most Core Web Vitals failures. Use Chrome DevTools Coverage tab to identify unused JavaScript — it’s common to find 40-60% of loaded JS is never executed. Audit third-party scripts: analytics, chat widgets, ad networks, heat mapping tools all add significant JS overhead.

46. CSS Delivery Optimization

Render-blocking CSS delays First Contentful Paint. Inline critical CSS (above-the-fold styles) in the <head> and defer non-critical stylesheets. Use Chrome DevTools’ Coverage tab to identify unused CSS — large CSS frameworks often load 80%+ unused rules.

47. Font Loading Strategy

Web fonts cause flash of unstyled text (FOUT) or flash of invisible text (FOIT), contributing to CLS and perceived performance degradation. Implement font-display: swap or font-display: optional. Preload critical fonts. Self-host fonts instead of loading from Google Fonts to eliminate cross-origin requests.

48. CDN Coverage

A CDN serves static assets from nodes geographically close to users, reducing TTFB significantly. Audit whether static assets (images, CSS, JS) are being served from a CDN. For global sites, check CDN performance from multiple regions using tools like Catchpoint or WebPageTest’s location selection.

49. Browser Caching Headers

Proper cache-control headers allow browsers to cache static resources and avoid re-downloading them on subsequent visits. Audit cache headers for static assets — images, CSS, and JavaScript should have long max-age values (1 year for fingerprinted assets). Missing or short cache headers cause repeat visitors to download the full page assets on every visit.

50. Server Compression

Gzip or Brotli compression should be enabled for HTML, CSS, and JavaScript files. Brotli achieves 15-25% better compression than Gzip. Test with: curl -I -H "Accept-Encoding: br" https://yourdomain.com and check the Content-Encoding response header.

51. Mobile Page Speed

Core Web Vitals are measured separately for mobile and desktop. Most sites have significantly worse mobile CWV than desktop. Run PageSpeed Insights on your top 20 pages specifically in mobile mode. Mobile issues are often amplified by large images not served at mobile-appropriate dimensions.

52. Third-Party Script Audit

Third-party scripts are the hardest Core Web Vitals problem to solve because they’re outside your control. Audit all third-party scripts loading on key pages — Google Analytics, HubSpot, Intercom, heat mapping tools, chat widgets, ad pixels. Each adds latency. Load non-critical scripts asynchronously and defer them where possible.

53. Image Lazy Loading

Below-the-fold images should use the loading="lazy" attribute to defer loading until the user scrolls toward them. Implement this across all images not in the initial viewport. Critical warning: don’t lazy-load your LCP image — that defeats the purpose and hurts your LCP score.

54. Resource Hints Implementation

Resource hints (preload, prefetch, preconnect) signal to browsers what resources they’ll need next. Implement <link rel="preconnect"> for critical third-party domains (Google Fonts, analytics endpoints). Use <link rel="preload"> for your LCP image and critical web fonts. These yield measurable LCP improvements.

55. CWV Field Data vs. Lab Data

PageSpeed Insights shows both lab data (simulated, consistent) and field data (real user data from Chrome UX Report). Rankings are based on field data, not lab data. A page can pass lab tests and still fail field data thresholds. If you have limited real-user traffic, lab data is your proxy — but monitor field data as volume grows.

Section 5: HTTPS and Security (Points 56–62)

56. SSL Certificate Validity

Expired or misconfigured SSL certificates cause browser security warnings and block crawling. Check certificate validity and expiration date. Set up automated renewal with Let’s Encrypt or your hosting provider’s certificate management. Also check that the certificate covers all subdomain variants you use.

57. HTTP to HTTPS Redirects

All HTTP URLs should redirect to HTTPS with a 301 redirect. Check that http://yourdomain.com, http://www.yourdomain.com, and https://www.yourdomain.com all resolve to your canonical HTTPS non-www (or www) URL without multiple redirect hops.

58. Mixed Content Warnings

Mixed content occurs when HTTPS pages load resources over HTTP. Browsers block mixed active content (scripts, iframes) and display warnings for mixed passive content (images). Check the browser console on key pages for mixed content warnings and update all resource URLs to HTTPS.

59. Security Headers Audit

Security headers (HSTS, Content-Security-Policy, X-Content-Type-Options) are increasingly factored into quality assessments. Use securityheaders.com to audit your security header implementation. HSTS is particularly important — it tells browsers to always use HTTPS, preventing downgrade attacks.

60. Safe Browsing Status

Check your domain in Google’s Safe Browsing Transparency Report. Sites flagged for malware, phishing, or unwanted software lose rankings immediately. If flagged, identify and remove the offending content, then submit a reconsideration request through Search Console.

61. Uptime Monitoring

Frequent downtime damages crawl efficiency and creates poor user experience signals. Implement uptime monitoring (UptimeRobot, Pingdom) and track your site’s availability. Target: 99.9% uptime. Downtime events during Googlebot crawl attempts are logged in Search Console.

62. WHOIS Privacy and Domain Authority

Domain registration details and history affect trust signals. Check that your domain isn’t flagged in spam databases, that WHOIS privacy is properly configured, and that the domain has a clean registration history. Newly registered domains and recently expired-and-reregistered domains face ranking trust deficits.

Section 6: Mobile Optimization (Points 63–68)

63. Mobile-First Indexing Compliance

Google indexes the mobile version of your site first. Verify in Search Console that your site is mobile-first indexed. Check that mobile pages contain the same content as desktop — don’t hide content on mobile that exists on desktop if you want it indexed.

64. Viewport Meta Tag

Every page must have <meta name="viewport" content="width=device-width, initial-scale=1">. Missing viewport tags cause mobile browsers to render at desktop width, creating terrible user experience and failing Google’s mobile-friendliness test.

65. Touch Target Sizing

Google’s mobile usability checks flag touch targets (buttons, links) smaller than 48×48 pixels. Audit your mobile pages for small touch targets — especially in navigation menus, footer links, and CTAs. Targets too close together also fail the test.

66. Intrusive Interstitials

Google penalizes intrusive interstitials on mobile — pop-ups that cover the main content when users arrive from search results. Exceptions: cookie consent banners, age verification, legally required notices. Time-delayed pop-ups that appear after page interaction are generally safe; immediate full-page pop-ups are not.

67. AMP Implementation (If Applicable)

AMP (Accelerated Mobile Pages) is largely deprecated as a ranking factor since Core Web Vitals became the mobile performance benchmark. If you’re still serving AMP pages, audit for correct canonical implementation and whether the AMP overhead is worth maintaining versus investing in standard CWV improvements.

68. Mobile User Experience Signals

Google’s page experience signals include mobile usability as a ranking factor. Run a bulk mobile usability test through Search Console’s “Mobile Usability” report. Fix all flagged issues before moving to performance optimizations — usability failures directly reduce mobile rankings.

Section 7: Structured Data and Rich Results (Points 69–74)

69. Article Schema

News, blog, and editorial content should implement Article or BlogPosting schema with author, datePublished, dateModified, headline, and image properties. This supports rich results in Google News and helps establish E-E-A-T signals at the structured data level.

70. Product Schema

E-commerce product pages should implement Product schema with name, description, offers (price, currency, availability), brand, and AggregateRating (if you have reviews). Proper product schema enables rich results with prices and ratings in standard Google SERPs.

71. Local Business Schema

Local businesses benefit from LocalBusiness schema with name, address, telephone, openingHours, and geographic coordinates. This reinforces local SEO signals and can enhance Google Business Profile data. Ensure the schema data matches exactly what’s in your Google Business Profile.

72. FAQ Schema

FAQ schema was previously a major source of SERP space expansion. Google significantly reduced FAQ rich result display in 2023, but the schema still provides structured content signals and occasionally renders for highly authoritative sites. Implement on FAQ sections where the markup is semantically accurate.

73. Breadcrumb Schema

Breadcrumb schema creates breadcrumb trail display in SERPs, replacing the URL with a clean hierarchical path. This improves CTR and reinforces site architecture signals. Implement BreadcrumbList schema on all pages below the homepage.

74. Schema Validation

Invalid structured data doesn’t just fail to generate rich results — it can generate manual action penalties for misleading markup. Validate all schema implementations through Google’s Rich Results Test and Schema.org Validator. Check Search Console’s “Enhancements” section for structured data errors across the site.

Section 8: Analytics and Tracking (Points 75–80)

75. Analytics Implementation Verification

Verify that Google Analytics 4 (GA4) is correctly implemented — firing on all pages, correctly configured for your domain, and not double-firing. Common issues: GA4 firing twice (once from header, once from GTM), analytics not firing on AJAX page loads, and events misattributing to sessions.

76. Search Console Verification and Setup

Both www and non-www versions of the domain should be verified in Search Console, with the preferred domain set. All site sections (including subdomain properties if applicable) should be connected. Check that the GSC property is receiving data — missing data usually indicates verification problems.

77. Goal and Conversion Tracking

Technical SEO improvements need measurable outcomes. Verify that key conversions are tracked: form submissions, phone calls, purchases, account signups. Without conversion tracking, you can’t demonstrate the business impact of technical SEO improvements or properly attribute organic search value.

78. Search Console Error Monitoring

Check Search Console weekly for new errors: coverage issues, mobile usability failures, Core Web Vitals regressions, and manual actions. Set up email notifications for critical Search Console alerts. New errors should be investigated within 48 hours before they compound.

79. Log File Analysis Setup

Server logs show exactly which URLs Googlebot crawls, how frequently, and with what status codes — data that Search Console doesn’t expose at this granularity. Set up log file analysis using Screaming Frog Log Analyzer or custom scripts. For large sites, log analysis often reveals crawl budget problems invisible in other tools.

80. Ongoing Audit Schedule

A technical SEO audit is not a one-time event. Establish a recurring audit cadence: crawl the site monthly with Screaming Frog, review Core Web Vitals data weekly in Search Console, and run a full 80-point audit quarterly. Sites that don’t monitor technical health accumulate debt that compounds into ranking losses.

How to Prioritize Your Technical SEO Audit Findings

After completing this audit, you’ll have a list of issues. Not all are equal. Prioritize by impact and effort using this framework:

Tier 1 — Fix immediately: Indexation blocks (robots.txt errors, mass noindex, SSL failures), manual actions in Search Console, Core Web Vitals failing across site-wide data, mass 404 errors on linked pages.

Tier 2 — Fix within 30 days: Redirect chains, crawl budget waste from parameter URLs, duplicate content without canonicalization, missing structured data on high-traffic pages, significant LCP/CLS failures on top landing pages.

Tier 3 — Fix within 90 days: Missing meta descriptions, minor CWV improvements, schema enrichment, internal linking restructuring, orphan page resolution.

Work through Tier 1 first, then batch Tier 2 into a development sprint, then schedule Tier 3 as part of ongoing site maintenance. Document every fix with before/after data so you can demonstrate impact.

Tools Used in a Professional Technical SEO Audit

Top agencies use a consistent toolkit for technical audits:

• Screaming Frog SEO Spider — site crawling, redirect mapping, duplicate content detection
• Google Search Console — indexation data, CWV field data, manual actions, coverage reports
• Ahrefs Site Audit — automated issue detection, internal link analysis, broken link mapping
• Google PageSpeed Insights — CWV lab and field data per page
• Chrome DevTools — JavaScript execution analysis, network waterfall, coverage reports
• WebPageTest — advanced performance testing from multiple locations and devices
• Semrush Site Audit — crawlability issues, HTTPS checks, duplicate content
• Rich Results Test — structured data validation

Frequently Asked Questions

How long does a full technical SEO audit take?

A thorough 80-point technical SEO audit takes 8-20 hours depending on site size. Small sites (under 1,000 pages) can be audited in a day. Enterprise sites with hundreds of thousands of URLs need 3-5 days minimum, primarily for crawl data collection and log file analysis. The audit itself is faster than the fix prioritization and implementation planning.

How often should you run a technical SEO audit?

Run a full audit quarterly and a partial crawl-based check monthly. Trigger an immediate audit after any major site changes: CMS migrations, URL restructuring, template changes, server moves, or significant traffic drops. Don’t wait for a quarterly cycle if rankings drop suddenly — that’s a signal to audit now.

What are the most impactful technical SEO fixes?

The highest-impact fixes, roughly in order: resolving indexation blocks (robots.txt errors, mass noindex), fixing Core Web Vitals failures on top landing pages, eliminating redirect chains on linked URLs, and resolving canonical mismatches. These directly affect whether your pages appear in search results and how they rank when they do.

Can I do a technical SEO audit without paid tools?

Yes, with limitations. Google Search Console (free), Google PageSpeed Insights (free), and the free version of Screaming Frog (500 URL limit) handle most small-site audits. For sites over 500 pages, Screaming Frog’s paid license ($259/year) is the most cost-effective professional-grade tool. The time saved over manual checking justifies the cost within the first audit.

What’s the difference between a technical SEO audit and an on-page SEO audit?

Technical SEO audits focus on crawlability, indexability, site speed, structured data, and the infrastructure that enables pages to be found and ranked. On-page SEO audits focus on content quality, keyword optimization, metadata, internal linking strategy, and user experience signals. Both matter — but technical issues create absolute barriers (pages can’t rank if they can’t be indexed), while on-page issues create optimization opportunities on already-crawlable pages. Fix technical first, then optimize on-page.