Technical SEO Checklist for B2B Websites: 47 Issues That Kill Rankings Even With Great Content

Quick Summary

• What this covers: Practical guidance for building and scaling your online presence.
• Who it's for: Business operators, consultants, and professionals using AI + search.
• Key takeaway: Read the first section for the core framework, then apply what fits your situation.

Forty-three percent of B2B websites have technical SEO issues preventing their content from ranking. You've published comprehensive guides, built backlinks, and targeted the right keywords—yet rankings plateau. The problem isn't content quality; it's technical infrastructure. Slow page speeds, broken redirects, duplicate content, and crawl errors silently suppress rankings while you focus on publishing more content that can't rank either.

Technical SEO operates beneath the content layer—the foundation determining whether Google can crawl, index, and rank your pages. A perfect article published on a site with poor technical health might reach position 30-50 when it should rank top 10. Fix the technical foundation and watch existing content rise without changing a word.

Site Speed and Core Web Vitals

Largest Contentful Paint (LCP) - Target: <2.5 seconds

What it measures: Time until main content renders on screen.

Common issues:

• Unoptimized images (large file sizes, wrong formats)
• Render-blocking CSS and JavaScript
• Slow server response time (TTFB >600ms)
• Missing resource preloading for critical assets

Fixes:

• Compress images using WebP/AVIF formats (80-90% size reduction versus JPG/PNG)
• Implement lazy loading for below-fold images (only load when scrolling near them)
• Inline critical CSS (first viewport styles embedded in HTML)
• Use CDN for static asset delivery (Cloudflare, Fastly, AWS CloudFront)
• Upgrade hosting if TTFB consistently exceeds 400ms

First Input Delay (FID) - Target: <100ms

What it measures: Time until page responds to first user interaction (click, tap, key press).

Common issues:

• Large JavaScript bundles blocking main thread
• Unoptimized third-party scripts (analytics, chat widgets, ads)
• Synchronous script loading

Fixes:

• Code-split JavaScript (load only what's needed per page)
• Defer non-critical JavaScript (use defer or async attributes)
• Audit third-party scripts—remove unused ones, lazy-load remainder
• Use web workers for heavy JavaScript operations (offload from main thread)

Cumulative Layout Shift (CLS) - Target: <0.1

What it measures: Visual stability—how much content shifts during load.

Common issues:

• Images without width/height attributes (browser doesn't reserve space)
• Ads or embeds injected without placeholder
• Web fonts causing FOIT/FOUT (flash of invisible/unstyled text)
• Dynamically injected content pushing existing content down

Fixes:

• Add explicit width and height to all images (<img width="800" height="600">)
• Reserve space for ads/embeds using CSS aspect-ratio or min-height
• Use font-display: swap with preload for web fonts
• Avoid inserting content above existing content (append below or use fixed positioning)

Page size and request count

Targets:

• Total page size <3MB (ideally <1.5MB)
• Total HTTP requests <50 (ideally <25)

Common issues:

• Dozens of external scripts (analytics, tracking, widgets)
• Uncompressed CSS/JS files
• Multiple font variations loaded (8+ font files)

Fixes:

• Audit with WebPageTest or Lighthouse to identify heavy resources
• Combine CSS/JS files where possible (balance against HTTP/2 multiplexing)
• Subset web fonts (include only characters used, only weights needed)
• Remove redundant scripts—do you really need 5 analytics platforms?

Crawlability and Indexation

Robots.txt configuration

Critical checks:

• Robots.txt doesn't accidentally block CSS/JavaScript (prevents rendering)
• Doesn't block critical sections (product pages, blog)
• Sitemap location declared correctly

Test: Google Search Console > robots.txt Tester tool.

XML sitemap health

Checks:

• Sitemap exists and is submitted to GSC
• Sitemap contains only indexable URLs (200 status, not blocked by robots.txt)
• Sitemap excludes paginated pages or uses rel=canonical correctly
• Image sitemap exists for image-heavy sites
• Video sitemap exists if you host videos
• Last modified dates are accurate and recently updated

Fixes:

• Generate sitemap using CMS plugin or static site generator
• Submit via GSC and monitor Index Coverage report for errors
• Update sitemap whenever site structure changes

Indexation status

Critical checks:

• site:yourdomain.com query shows expected page count (not 10x more or 50% less)
• Important pages are indexed (spot-check top 50 pages)
• Duplicate pages aren't multiply indexed (check for www vs non-www, http vs https, trailing slash variants)

Diagnosis via GSC:

• Navigate to Index > Coverage report
• Identify "Excluded" and "Error" pages
• Common issues: Duplicate content, soft 404s, redirect errors, crawl anomalies

Canonical tag implementation

Every page should have canonical tag:

• Self-referential canonical on unique pages (<link rel="canonical" href="https://example.com/page" />)
• Cross-domain canonical if syndicating content
• Canonical tags point to preferred HTTPS version
• Paginated pages canonicalize to view-all page OR use rel=next/prev

Common mistakes:

• Missing canonical tags entirely (creates ambiguity for Google)
• Canonical pointing to wrong page (Google ignores canonical chain)
• Conflict between canonical and robots meta tag (one says index, other says noindex)

Internal link structure

Health checks:

• All pages reachable within 3 clicks from homepage
• No broken internal links (404s)
• Important pages have 10+ internal links pointing to them
• Orphan pages (zero internal links) are either intentional or reconnected

Tools: Screaming Frog, Sitebulb, Ahrefs Site Audit.

Fixes:

• Add navigation links, related content modules, contextual in-body links
• Fix broken links (update to correct URL or remove link)
• Prune or redirect orphan pages that should be connected

Duplicate content resolution

Common B2B duplicate content scenarios:

• Product pages accessible via multiple category URLs
• Blog posts syndicated on Medium/LinkedIn without canonical back to origin
• Printer-friendly versions creating duplicate URLs
• Session IDs or tracking parameters in URLs creating infinite variations

Fixes:

• Use canonical tags to declare preferred version
• Implement parameter handling in GSC (tell Google to ignore session IDs)
• Use 301 redirects to consolidate duplicate URLs to single canonical version
• Block low-value pages with robots meta noindex if they shouldn't rank

Mobile Optimization

Mobile-friendly test

Critical checks:

• Passes Google's Mobile-Friendly Test (search "Google mobile friendly test")
• Text readable without zooming (minimum 16px font size)
• Tap targets adequately spaced (minimum 48px × 48px, 8px spacing)
• No horizontal scrolling required
• Content fits viewport width

Mobile-specific issues:

• Desktop-only features (hover effects required for navigation)
• Interstitials and popups that cover content on mobile
• Mobile-unfriendly forms (tiny input fields, no autofill support)

Responsive design vs separate mobile site

Google's stance: Responsive design preferred over separate mobile site (m.example.com).

If using separate mobile site:

• Implement rel=alternate and rel=canonical correctly (desktop to mobile, mobile to desktop)
• Ensure feature parity (mobile site has same content as desktop)
• Configure mobile sitemap correctly

Better approach: Use responsive design. Single URL simplifies technical SEO and consolidates link equity.

HTTPS and Security

SSL certificate

Non-negotiable checks:

• Entire site serves via HTTPS (not just homepage)
• No mixed content warnings (HTTP assets on HTTPS pages)
• Certificate is valid (not expired, not self-signed)
• HTTP redirects to HTTPS via 301 (not 302)

Diagnosis: Check Chrome DevTools Console for mixed content errors.

Fixes:

• Install SSL certificate via hosting provider (often free with Let's Encrypt)
• Update all internal links to HTTPS
• Use protocol-relative URLs or HTTPS URLs for external resources
• Implement HSTS header (forces HTTPS in browsers)

Security headers

Advanced technical SEO for security and performance:

• HSTS (HTTP Strict Transport Security)
• Content Security Policy (CSP)
• X-Content-Type-Options: nosniff
• X-Frame-Options: DENY or SAMEORIGIN

Test via securityheaders.com. These don't directly affect rankings but prevent attacks that could compromise site (and destroy SEO).

URL Structure and Redirects

Clean URL architecture

Best practices:

• URLs use hyphens, not underscores (hyphens are word separators, underscores aren't)
• URLs are lowercase (avoids case-sensitivity issues)
• URLs are descriptive (/seo-consulting/ not /services/page2/)
• URL structure reflects site hierarchy (/blog/category/post-title/)

Redirect hygiene

Critical checks:

• No redirect chains (A → B → C) — consolidate to direct redirect (A → C)
• No redirect loops (A → B → A) — breaks crawling entirely
• 301 (permanent) used for moved pages, not 302 (temporary)
• Old URLs from site migrations still redirect correctly

Diagnosis: Crawl site with Screaming Frog, review "Redirect Chains" and "Redirect Loops" tabs.

Parameter handling

Common B2B parameter issues:

• Tracking parameters create duplicate content (?utm_source=email versus ?utm_source=linkedin)
• Sorting/filtering creates infinite URL variations (?sort=price&filter=category)

Fixes:

• Configure parameter handling in GSC (tell Google which parameters to ignore)
• Use canonical tags to declare parameter-free URL as preferred
• Block parameter variations in robots.txt if they shouldn't be indexed

Schema Markup and Structured Data

Organization schema

Essential for brand visibility:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-555-555-5555",
    "contactType": "Sales"
  },
  "sameAs": [
    "https://linkedin.com/company/yourcompany",
    "https://twitter.com/yourcompany"
  ]
}
</script>

Implement on homepage and about page.

Article schema for blog posts

Helps Google display rich snippets:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Your Post Title",
  "description": "Meta description",
  "image": "https://example.com/featured-image.jpg",
  "datePublished": "2026-02-08",
  "dateModified": "2026-02-08",
  "author": {
    "@type": "Person",
    "name": "Victor Valentine Romo"
  }
}
</script>

FAQPage schema

Enables FAQ rich snippets in SERPs:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What is technical SEO?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Technical SEO ensures search engines can crawl, index, and rank your site effectively..."
    }
  }]
}
</script>

Product schema for B2B SaaS/products

Displays pricing and ratings in search:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Your SaaS Product",
  "description": "Product description",
  "brand": "Your Company",
  "offers": {
    "@type": "Offer",
    "price": "99.00",
    "priceCurrency": "USD"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "127"
  }
}
</script>

Test all schema with Google's Rich Results Test tool.

JavaScript and Rendering

Server-side rendering (SSR) vs client-side rendering (CSR)

SEO implications:

• CSR (React/Vue/Angular without SSR): Google must execute JavaScript to see content—slower indexing, potential rendering failures
• SSR (Next.js, Nuxt.js, Angular Universal): Content exists in HTML immediately—better for SEO

If using CSR-only framework:

• Implement dynamic rendering (serve pre-rendered HTML to bots, interactive version to users)
• OR migrate to SSR framework
• Test with Google's Mobile-Friendly Test (uses rendering engine, reveals if content is visible to Google)

Critical rendering path optimization

Checks:

• Minimize render-blocking JavaScript (defer non-critical scripts)
• Inline critical CSS (first-paint styles embedded in HTML)
• Preload key resources (<link rel="preload" href="font.woff2" as="font">)

Internationalization (if applicable)

Hreflang implementation

For multi-language or multi-region sites:

• Hreflang tags declare language/region versions
• Tags are reciprocal (if page A links to page B, page B must link to page A)
• Self-referential hreflang included (<link rel="alternate" hreflang="en-us" href="..." />)

Common mistakes:

• Missing return links (hreflang must be bidirectional)
• Wrong language codes (use ISO 639-1 format: "en-US", "es-MX")
• Hreflang pointing to redirecting URLs (must point to final destination)

Test with Ahrefs Site Audit or Screaming Frog hreflang validation.

Frequently Asked Questions

How often should you run technical SEO audits?

Quarterly for most B2B sites; monthly for high-traffic or frequently updated sites. Technical issues accumulate over time—new pages launch, developers make changes, plugins update. Quarterly audits catch problems before they compound. Use Screaming Frog, Sitebulb, or Ahrefs Site Audit to crawl entire site, then prioritize fixes by impact (issues affecting 100+ pages > issues affecting 5 pages).

What's the fastest technical SEO fix with highest impact?

Implement HTTPS if you haven't, then fix Core Web Vitals. HTTPS is mandatory (non-HTTPS sites get "Not Secure" warnings, users bounce, rankings suffer). After HTTPS: optimize images and implement lazy loading—these two actions alone improve LCP by 40-60% on most sites. Quick wins that Google measures directly.

Should you fix all technical issues or prioritize?

Prioritize by impact and effort. Use 2x2 matrix: High Impact + Low Effort = do immediately (optimize images, fix broken links). High Impact + High Effort = schedule deliberately (migrate to SSR, redesign URL structure). Low Impact = defer indefinitely unless trivial. Don't let perfectionism delay launching fixes for critical issues.

How do you know if technical issues are actually hurting rankings?

Compare similar content on healthy versus unhealthy pages. If one blog post with great technical health ranks position 4 and another with poor Core Web Vitals ranks position 28—despite similar content quality and backlinks—technical SEO is the differentiator. Use GSC to compare impressions and average position for groups of pages, segmented by Core Web Vitals status.

Can you rank well despite technical SEO issues?

Temporarily yes, long-term no. If you have dominant authority and minimal competition, you can rank despite technical problems—for a while. As competitors improve their technical foundations, they'll overtake you. Technical SEO is the tie-breaker when content quality and backlinks are roughly equal. Better to fix proactively than scramble when rankings suddenly drop due to algorithm update targeting technical issues.

---

When This Doesn't Apply

Skip this if your situation is fundamentally different from what's described above. Not every framework fits every business. Use the diagnostic in the first section to determine whether this approach matches your current stage and goals.