WP Engine AI Bot Blocks Put Fetchability at the Center of GEO Audits
A website can be indexed, receive search traffic, and show no obvious issue in standard SEO tools while some AI crawlers cannot retrieve its pages. That gap is the central finding in a documented case involving WP Engine, where platform-level controls reportedly block or rate-limit certain AI bots before their requests reach a customer's WordPress installation. Search Engine Land's investigation…
Managed WordPress platform WP Engine is blocking certain AI crawlers before their requests reach the customer's WordPress installation, according to a recent investigation by Search Engine Land. The blocked crawlers include GPTBot, ClaudeBot, and PerplexityBot. The issue is not that every managed host behaves the same way, but that WP Engine's platform-level restriction on AI bots is non-disableable and sits outside WordPress settings, robots.txt, and monitoring tools.
This creates a blind spot for traditional SEO measurement, which does not necessarily prove AI fetchability. Search visibility checks, such as indexing, traffic analytics, and application configuration, do not reveal how a hosting platform handles requests from specific AI crawlers. If the request is rejected at the infrastructure edge, WordPress never receives it.
To address this issue, businesses should include AI crawler fetchability checks in their SEO audits. This involves testing important pages using requests that identify as the relevant bot and recording the response at the platform level. By distinguishing between a discoverability constraint and content quality issues, teams can focus on resolving access problems with AI crawlers rather than revising content unnecessarily.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
