Shared hosting vs. dedicated: what AI crawlers notice

The price of cheap hosting

I am going to say something hosting providers would rather not hear: shared hosting is the biggest invisible saboteur of your AI visibility.

There. Said it.

I see it with at least half the clients who come to Kobalt. Beautiful website. Solid content. Even Schema.org markup. But an AEO score that disappoints. And then I look at the server. Shared hosting. 8 euros a month. "It works fine, right?" Sure. Until an AI crawler shows up.

Look, shared hosting is popular. Understandable. It is cheap, it works, you do not have to think about anything. But what you do not see is that you share that server with dozens, sometimes hundreds of other websites. You are not the only resident. You are a flatmate. And you have no say in what your neighbors do.

What makes AI crawlers different from regular visitors

A human will wait. Three seconds to load? Annoying, but okay. They scroll through their phone in the meantime.

An AI crawler does not do that. GPTBot has a built-in timeout. Too slow? Next URL. Your page does not get indexed, does not get cited, does not get picked up. Done. No warning.

And it gets worse. AI models crawl in waves. They send multiple requests simultaneously to your domain. On a VPS with sufficient resources: no problem. On an overloaded shared server, that causes throttling, connection errors and HTTP 503 responses. The crawler thinks: this website is unavailable. And it is right, because at that moment, it is.

• Shared hosting: typical TTFB of 800ms to 3 seconds under load. That is an eternity for a crawler.
• VPS or cloud hosting: TTFB generally below 300ms, even with concurrent requests.
• Dedicated server: TTFB consistently below 100ms. No noisy-neighbor effect.
• Managed WordPress hosting (Kinsta, WP Engine): comparable to VPS for AI crawlability.

The noisy-neighbor effect

This is my favorite analogy (I am a nature person, so bear with me). Shared hosting is like a birdwatching hide you share with a group of noisy hikers. You are sitting quietly waiting for that one kingfisher. But your neighbors are making so much noise that every bird within 200 meters has left.

In hosting terms: it is Tuesday afternoon. A webshop on the same server as you just sent a newsletter to 40,000 subscribers. Visitors flood in. The server groans. At that exact moment, ClaudeBot decides to visit your website. What happens? The server drops the connection.

You pay for hosting. But the available capacity is determined by what your neighbors are doing. And you have zero control over that. You can optimize your code until you go cross-eyed (speaking from experience), but if the server is full, none of it matters.

Which hosting type fits your situation?

I am not going to give one-size-fits-all advice. But I can give you an honest framework.

1. Shared hosting: fine for a hobby website or a site with fewer than 500 visitors per day and zero AI ambition. For business websites that want AI visibility? No.
2. Managed WordPress hosting (Kinsta, WP Engine, Pressable): good choice for WordPress sites that are serious about AI. Fast servers, isolated environments, no noisy neighbors.
3. VPS or cloud (DigitalOcean, Hetzner, Vultr): for websites with a technical team. Full control, excellent performance, scalable.
4. Managed cloud (Laravel Cloud, Render, Railway): ideal for framework applications. Automatic scaling, no server management.
5. Dedicated server: only for extreme volumes. Overkill for most websites.

My rule of thumb? If your website generates revenue (directly or indirectly), you should not be on shared hosting. Sometimes you just need to invest in better foundations rather than endlessly tinkering with the superstructure.

Frequently asked questions

You save 20 euros a month on shared hosting and lose thousands in missed AI visibility. That is not being frugal. That is saving in the wrong place.