Hostinger Quietly Blocks ChatGPT, Claude, and Perplexity from Reading Your Site. Their Support Confirmed It.
If your store is on Hostinger's shared or Cloud Startup plans, ChatGPT Search probably can't see your products. Neither can Perplexity. Neither can Claude. And here's the part that makes it nasty: it isn't your robots.txt. It's the hosting plan itself, doing this to you by default.
The story broke when SEO consultant Marin Popov asked Hostinger support why AI crawlers were being challenged on his sites, then published the transcript on LinkedIn.
Stay in the loop
Get news and updates about GEO, AI search and new features. Unsubscribe anytime.
Is your brand a Ghost or a Guide on AI?
See if AI knows your brand. We ask Gemini and Claude live - in ~5 seconds, no signup.
The bot-protection layer that injects a reCAPTCHA challenge in front of OpenAI, Anthropic, and Perplexity datacenter IP ranges is enabled by default on shared and Cloud Startup plans. The disable toggle is only available on VPS plans. Shared customers cannot opt out without upgrading.
That lines up with a months-long technical investigation by Stonegate Web Security, which fingerprinted the same pattern across multiple Hostinger-hosted sites: a server-injected <script src="https://www.google.com/recaptcha/..."> challenge served only when the request came from a published OpenAI, Anthropic, or Perplexity datacenter IP range. In any normal browser the sites looked completely fine. That's the trap.
Why this is a GEO problem, not just an SEO problem
OpenAI's OAI-SearchBot hit 55.67% web coverage in Hostinger's own 2026 crawler study - so if you're not reachable to it, you're sitting in the 44% of the web ChatGPT Search literally cannot cite. ChatGPT-User and PerplexityBot are in the same boat: when a user asks the assistant to browse your URL, the assistant fetches it from their cloud IPs. Those IPs hit the reCAPTCHA wall, and the user gets "I can't access that page." End of your visibility for that query.
And here's the cruel part. Googlebot and human visitors pass straight through. From your analytics, nothing looks wrong. From ChatGPT's point of view, you don't exist. You can't fix a problem your dashboard is actively hiding from you.
How to check yours in 60 seconds
We shipped a tool for exactly this. The new Hosting Checker tab inside GEOlikeaPro takes a URL and runs three independent layers in parallel:
- Real fetch via the AI itself. ChatGPT Search and Perplexity each try to fetch your URL with their own browsing tool, from their own IPs. If they get a challenge page, they report the exact error string they saw. This is ground truth - not user-agent spoofing, the actual AI telling you what it actually got.
- Origin fingerprint. We resolve your domain, look up the ASN via Team Cymru, match it against known-problematic hosts (Hostinger AS47583 / AS214572, Cloudflare, Imperva, Sucuri, Akamai), and inspect response headers plus the first 8 KB of HTML for bot-protection vendor signatures, including the Hostinger reCAPTCHA injection pattern.
robots.txtparse. Per-bot allow/disallow for the eight crawlers that actually matter today: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Google-Extended, Applebot-Extended.
What comes out: a per-bot verdict, an Access Score, and - if your host has a known issue - a callout panel naming it. The reason we can say "likely blocked" with confidence even when robots.txt is permissive is that the AI itself is telling you it couldn't reach the page. Three layers agreeing beats one layer guessing.
What to do if your Hostinger site fails the check
Three options, in order of effort:
- Move to a VPS plan on Hostinger. The bot-protection toggle exists there and you can turn it off. Cheapest path if you're already invested in their dashboard.
- Front your origin with Cloudflare. Point your DNS at Cloudflare, set AI Crawl Control to "Allow" for the search bots (OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, Google-Extended) and "Block" for training-only bots (GPTBot, anthropic-ai, CCBot, Bytespider) if you care about that split. Cloudflare's edge serves crawler requests from cache and the Hostinger origin layer never sees them. Mind the Cloudflare default-block trap while you're in there - turning AI bots on is a manual setting since July 2025, so you can swap one silent block for another if you're not careful.
- Move hosts. Most VPS providers (DigitalOcean, OVH, AWS Lightsail, Linode) don't run an inline bot-challenge layer against AI crawler IPs. If you were eyeing a migration anyway, this is the forcing function.
The Hosting Checker can't guarantee a bot will be blocked tomorrow - bot-protection rules change, and Hostinger has been quietly walking back some of the more aggressive defaults under public pressure. What it can do is tell you whether, right now, today, ChatGPT Search and Perplexity can fetch your page when they try. That's the only signal that matters for AI search visibility, and it's exactly the one your hosting dashboard will never show you.
Hat tip to Marin Popov for getting Hostinger to put this on the record.
FAQ
Does Hostinger block ChatGPT and Perplexity from accessing my site?
On shared and Cloud Startup plans, yes — Hostinger runs an inline bot-protection layer that injects a reCAPTCHA challenge in front of published AI crawler IP ranges. Hostinger support has confirmed the disable toggle is only available on VPS plans. <a href="https://stonegatewebsecurity.com/articles/hostinger-bot-protection-blocking-ai-crawlers/" target="_blank" rel="noopener">Source</a>
Will my Google rankings be affected?
No. Googlebot is not part of the affected IP ranges. The block specifically targets datacenter IPs published by OpenAI, Anthropic, and Perplexity. Your Google organic rankings are unaffected — only AI search visibility is.
How do I know if my Hostinger site is affected?
Run the Hosting Checker tool inside GEOlikeaPro. It asks ChatGPT Search and Perplexity to fetch your URL via their own browsing tools, fingerprints your origin's ASN and response headers for the Hostinger reCAPTCHA injection pattern, and parses your robots.txt for the eight AI crawlers that actually matter.
Can I fix this on a Hostinger shared plan?
Not directly — the bot-protection toggle is gated to VPS plans. Workarounds: upgrade to a Hostinger VPS plan, front your origin with Cloudflare and configure AI Crawl Control there, or migrate to a host without an inline bot-challenge layer (DigitalOcean, OVH, AWS Lightsail, Linode).
Is user-agent spoofing a reliable way to test this?
No. The Hostinger block targets crawler IP ranges, not user-agent strings. Spoofing GPTBot from your edge or browser will pass through cleanly because it isn't coming from an OpenAI datacenter IP. The only reliable test is asking the AI itself to fetch the URL via its own browsing tool — which is what GEOlikeaPro's Hosting Checker does.