If Google and AI can’t properly crawl your site, nothing else you do for SEO matters
The technical issues silently killing your local SEO in 2026
Technical SEO is the foundation that everything else sits on. A fast, crawlable, properly structured site amplifies every on-page and off-page signal. A slow, misconfigured site suppresses them. In 2026, there’s a new technical layer: AI crawler access. Most local business websites are accidentally blocking GPTBot, ClaudeBot, and PerplexityBot — making them completely invisible in AI search without ever knowing it.
Site Speed & Core Web Vitals
I target sub-200ms TTFB (server response time) — the threshold at which AI crawlers begin dropping your content mid-crawl. I compress images, implement browser caching, optimise hosting configuration, enable lazy loading, and fix any render-blocking resources. A fast site ranks better, converts better, and gets crawled more completely.
Sub-200ms targetAI Crawler Access
This is 2026’s most commonly missed technical fix. Most robots.txt files either accidentally block or simply don’t permit GPTBot (ChatGPT), ClaudeBot (Claude), PerplexityBot, and BingBot. I explicitly permit all four — because blocking them removes you from AI search entirely, silently, with no warning in Google Search Console.
2026 critical fixSchema Markup (JSON-LD)
I implement the full schema stack for local businesses: LocalBusiness (with areaServed and GeoCoordinates), FAQPage on every service and blog page, Person (for EEAT), HowTo on process pages, Service, and AggregateRating. Crucially, all schema goes in the page head — not body — for faster AI indexing and AIO eligibility.
Head placement mattersMobile-First Optimisation
60%+ of local searches happen on mobile devices. Google uses mobile-first indexing — what your mobile site shows determines your rankings, not your desktop version. I audit responsive layouts, fix tapability issues, ensure text is readable without zooming, and verify that click-to-call is above the fold on every service page.
60%+ local searches on mobileHTTPS & Security
HTTPS is non-negotiable in 2026. Google flags HTTP sites as insecure, users see browser warnings, and both human visitors and Google’s crawlers trust you less. I verify your SSL certificate is active, properly configured, and covers all subdomains — then check for mixed content errors that can break HTTPS protection.
Non-negotiableSitemap & Crawlability
I submit your XML sitemap to Google Search Console, fix any crawl errors, remove or redirect broken pages (404s), ensure your most important pages are indexed, and set up Search Console alerts so I catch any new crawl issues the moment they appear rather than weeks later.
Index coverageMost local business sites are invisible in AI search without knowing it
What most robots.txt files look like:
Disallow: /wp-admin/
# GPTBot — not mentioned
# ClaudeBot — not mentioned
# PerplexityBot — not mentioned
# Result: AI engines crawl at their discretion
# or skip entirely
What I implement for every client:
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Bingbot
Allow: /
# All AI search engines explicitly permitted
This single fix — which takes less than 5 minutes to implement — is the difference between appearing and not appearing in AI-generated local business recommendations.
Technical SEO — the questions I get asked most
What is the most important technical SEO fix for local businesses in 2026?
In 2026, the highest-impact technical fix for most local businesses is AI crawler permissions in robots.txt — explicitly permitting GPTBot, ClaudeBot, PerplexityBot, and BingBot. Most local business sites haven’t updated their robots.txt since these AI crawlers launched, meaning they’re either blocking or not explicitly permitting AI search engines. The second most impactful fix is schema markup — LocalBusiness and FAQPage schemas in the page head. These two fixes often produce visible improvements in both organic and AI search visibility within weeks.
How does site speed actually affect local SEO rankings?
Google uses Core Web Vitals — including server response time (TTFB), largest contentful paint (LCP), and cumulative layout shift (CLS) — as ranking signals. For AI crawlers specifically, a sub-200ms TTFB is important because crawlers set aggressive timeouts and may abandon slow pages mid-crawl, resulting in incomplete indexing. Beyond rankings, a faster site reduces bounce rates — visitors who don’t leave before the page loads — which is itself a user experience signal that influences long-term rankings.
Do I need technical SEO if my website was just professionally built?
Almost always yes — because web designers optimise for visual appearance, not search engine accessibility. A professionally designed website often has no schema markup, no explicit AI crawler permissions, default robots.txt settings, non-compressed images, and generic title tags. These are not design failures — they’re simply outside a web designer’s scope. Technical SEO bridges the gap between a well-designed site and a search-engine-optimised one.
Stop losing customers to competitors who outrank you
I’ll audit your current situation — GBP, citations, website, competitors, and AI search visibility — and send you written findings within 5 business days. No pitch. Just the honest picture your previous agency never gave you.
100% free · Written findings in 5 days · I respond within 24 hours · Month-to-month if you proceed
Technical SEO Unlocks Everything Else
Technical SEO for Small Businesses — Speed, Schema and AI Crawlability