The Technical SEO Health Checklist: What Every Agency Should Audit First

You've hired an SEO agency, or maybe you're the one doing the hiring. Either way, there's a moment when the conversation shifts from "we'll improve your rankings" to the actual work—the crawl logs, the server headers, the JavaScript rendering issues. That's where technical SEO lives, and it's where most campaigns either gain traction or bleed momentum.

Technical SEO isn't about tricks. It's about making sure search engines can find, understand, and index your content efficiently. If your site has structural problems, no amount of keyword stuffing or link buying will fix it. Google's systems—including Search Generative Experience (SGE)—are increasingly sophisticated at detecting when a site is technically sound versus when it's held together with duct tape and wishful thinking.

This checklist walks through the core technical areas an agency should audit during onboarding and revisit quarterly. Each section explains what to look for, why it matters, and how to fix common issues. By the end, you'll have a repeatable process for evaluating site health and performance.

Crawl Budget and Indexation: Where Google Wastes Time

Every site has a crawl budget—the number of URLs Googlebot will crawl in a given timeframe. For small sites (under a few thousand pages), this rarely matters. But for e-commerce stores, news sites, or any domain with tens of thousands of URLs, crawl budget allocation becomes a performance bottleneck.

What to check first: Log into Google Search Console and review the Crawl Stats report. Look at the average crawl requests per day and the total crawl time. If Google is spending 80% of its crawl budget on parameterized URLs, paginated archives, or thin content pages, you're losing opportunities for important pages to be discovered and indexed.

Common issues:

• Infinite crawl spaces (calendar filters, sort parameters, session IDs)
• Orphaned pages that no internal link points to
• Redirect chains longer than three hops
• Soft 404s returning "page not found" content with a 200 status code

Fix strategy: Use robots.txt to block low-value URL patterns, implement noindex on thin pages you don't want indexed, and ensure your XML sitemap contains only canonical, indexable URLs. For large sites, consider a tiered sitemap structure with a primary sitemap index file pointing to category-specific sitemaps.

Core Web Vitals: The User Experience Scorecard

Google's Core Web Vitals—LCP (Largest Contentful Paint), FID/INP (First Input Delay / Interaction to Next Paint), and CLS (Cumulative Layout Shift)—are direct ranking signals. But more importantly, they correlate strongly with user satisfaction. A site that loads slowly or shifts content while the user is reading will lose visitors regardless of where it ranks.

What to check first: Run a report in Google Search Console's Core Web Vitals section. Filter by "Poor" status and look at the specific URLs affected. Then cross-reference with real user monitoring data from tools like Lighthouse or PageSpeed Insights.

Common issues:

• Large hero images without proper dimensions (causes CLS)
• Third-party scripts blocking main-thread rendering (affects FID/INP)
• Unoptimized font loading that delays text visibility (affects LCP)
• Missing lazy loading for below-the-fold images

Fix strategy: Start with the low-hanging fruit: compress images, defer non-critical JavaScript, and set explicit width/height attributes on all media elements. For more complex issues like server response time or render-blocking resources, you may need to involve your hosting provider or development team. The goal is to move all URLs from "Poor" to "Good" or at least "Needs Improvement" within the first 30 days of engagement.

XML Sitemaps and Robots.txt: Your Site's Welcome Mat

These two files are the first things Googlebot reads when it arrives at your domain. If they're misconfigured, you're essentially sending the wrong directions to your most important visitor.

What to check first: Open your robots.txt file (usually at domain.com/robots.txt) and verify that it's not accidentally blocking critical resources like CSS, JavaScript, or images. Also confirm that it points to your XML sitemap location. Then open your sitemap.xml and check that it contains only indexable, canonical URLs—no paginated pages, no parameterized variants, no thin content.

Common issues:

• Multiple sitemaps with overlapping URLs
• Sitemap includes noindex URLs (a contradiction that confuses crawlers)
• robots.txt disallows entire directories that contain important content
• Missing sitemap for large sites (Google recommends one sitemap per 50,000 URLs or 50MB uncompressed)

Fix strategy: Consolidate your sitemaps into a single sitemap index file. Use robots.txt to block only what's truly unnecessary (admin panels, staging environments, duplicate content generators). And always test changes using Google's robots.txt tester in Search Console before deploying.

Canonicalization and Duplicate Content: Choosing the Right URL

Duplicate content isn't a penalty—it's a confusion signal. When Google sees the same content at multiple URLs, it has to guess which version is canonical. If it guesses wrong, your preferred page loses ranking potential.

What to check first: Run a site:domain.com search and look for URL patterns that suggest duplication. Common culprits include HTTP vs HTTPS, www vs non-www, trailing slash vs no trailing slash, and parameterized URLs. Then check your canonical tags to ensure they point consistently to the preferred version.

Common issues:

• Missing canonical tags on key pages
• Canonical tags pointing to 301-redirected URLs
• Self-referencing canonicals on paginated pages (should point to the first page or use rel="prev"/"next")
• Internationalization errors (e.g., hreflang tags conflicting with canonicals)

Fix strategy: Implement a strict canonical policy: every indexable page should have a self-referencing canonical tag unless you explicitly want to consolidate signals to another URL. For e-commerce sites, use canonical tags to point variant URLs (color, size) back to the parent product page.

On-Page Optimization and Intent Mapping: Beyond Keywords

Technical SEO isn't just about server configs and crawl logs. It also includes how you structure content for both users and search engines. This is where keyword research meets intent mapping.

What to check first: Review your top 20 landing pages by organic traffic. For each page, ask: Does the content match the search intent of the keywords it's targeting? A page optimized for "buy running shoes" shouldn't read like a blog post about running techniques. Similarly, an informational query like "how to tie running shoes" shouldn't lead to a product category page.

Common issues:

• Title tags and meta descriptions that don't reflect page content
• Heading hierarchy violations (e.g., jumping from H1 to H3 with no H2)
• Thin content (under 300 words) on pages that should be comprehensive
• Missing schema markup for relevant content types (product, article, FAQ, etc.)

Fix strategy: Create a content brief for each key page that includes the primary keyword, related semantic terms, and the intended user journey. Then optimize the page structure: one H1 that matches the title tag, logical H2s for subtopics, and descriptive H3s for supporting details. Add schema markup using JSON-LD format—it's easier to maintain and less error-prone than microdata.

Link Building and Backlink Profile: Quality Over Quantity

Link building remains a significant ranking factor, but the game has changed. Google's algorithms now evaluate link quality through multiple lenses: topical relevance, domain authority, trust flow, and the naturalness of the link profile.

What to check first: Use a backlink analysis tool to review your link profile. Look for patterns that suggest manipulation: sudden spikes in link acquisition, links from unrelated niches, or links from sites with low trust flow. Also check for toxic links—those from spammy directories, link farms, or hacked sites.

Common issues:

• Paid links that pass PageRank (violates Google's guidelines)
• Excessive exact-match anchor text in backlinks
• Links from sites with poor domain authority (DA under 20)
• Missing disavow file for confirmed toxic links

Fix strategy: Before starting any link building campaign, audit your existing profile and disavow any links you can't remove manually. Then focus on earning links through content marketing: create shareable assets (original research, infographics, interactive tools) and reach out to relevant sites in your niche. Avoid any agency that promises "guaranteed links" or uses automated outreach tools—those tactics are detectable and can lead to manual actions.

Technical SEO Audit Tools and Comparison

The table below summarizes common tools for technical SEO audits, their primary use cases, and what to watch out for.

Each tool has strengths and blind spots. For a thorough audit, combine data from at least two sources—for example, Google Search Console for official indexation data and Screaming Frog for on-page technical issues.

What Can Go Wrong: Risk-Aware Implementation

Technical SEO is precise work. A single misconfigured redirect or incorrect robots.txt directive can take weeks to recover from. Here are the most common risks and how to mitigate them.

Wrong redirects: Using 302 (temporary) instead of 301 (permanent) when moving a page permanently splits link equity. Using 301 for temporary redirects tells Google to cache the redirect indefinitely, making it harder to revert. Always match the redirect type to the actual intent.

Black-hat links: Buying links from private blog networks (PBNs) or using automated link-building software can trigger manual actions from Google. Even if you don't get caught immediately, these links tend to decay as the source sites get penalized. The cost of cleaning up a toxic link profile often exceeds the cost of legitimate link building.

Poor Core Web Vitals: Over-optimizing for a single metric (e.g., compressing images to the point of quality loss) can hurt user experience. Similarly, deferring all JavaScript to improve LCP might break critical functionality. Always test changes in a staging environment before deploying to production.

Crawl budget mismanagement: Blocking too many URLs via robots.txt can prevent Google from discovering new content. Conversely, allowing infinite crawl spaces can waste budget on low-value pages. Use robots.txt to block only what's clearly unnecessary, and monitor crawl stats weekly after making changes.

Final Checklist for Agency Onboarding

Before you sign off on any technical SEO campaign, run through this checklist with your agency or internal team:

1. Crawl budget analysis: Review Google Search Console crawl stats and identify wasted crawl allocation.
2. Core Web Vitals baseline: Document current LCP, CLS, and FID/INP scores for top pages.
3. Sitemap and robots.txt verification: Confirm both files are correctly configured and pointing to the right resources.
4. Canonical tag consistency: Ensure every indexable page has a self-referencing canonical tag.
5. Duplicate content audit: Use a crawler to find and resolve URL duplication issues.
6. On-page structure review: Check title tags, meta descriptions, heading hierarchy, and schema markup.
7. Backlink profile health: Audit existing links and disavow toxic ones before starting new campaigns.
8. Performance monitoring setup: Establish a weekly or bi-weekly reporting cadence for technical metrics.

Technical SEO isn't a one-time fix. It's an ongoing process of monitoring, adjusting, and improving. The sites that succeed are the ones that treat technical health as a continuous investment—not a checkbox to tick off during onboarding.

For more guidance on specific technical topics, explore our resources on technical SEO audits, Core Web Vitals optimization, and link building best practices.