WordPress generates pages dynamically: each request hits a PHP interpreter, queries a MySQL database, runs through theme templates and plugin hooks, and assembles the HTML before serving it. On shared hosting, this process takes 200-800ms per page request under light load — longer under heavy crawl conditions.
A flat-file PHP architecture serves pre-generated HTML directly from disk. Response times are typically under 50ms. When a ClaudeBot or ChatGPT-User crawler sweeps through 130 pages in a session, the flat-file architecture handles the load without slowing down. A WordPress installation on shared hosting under the same crawl load frequently produces timeouts and incomplete page loads.
WordPress installations attract automated probing because WordPress is the most commonly targeted CMS for vulnerabilities. The IEO Engine gate logs show dozens of WordPress fingerprint probes daily — requests for wp-login.php, xmlrpc.php, wp-json, ?p= queries. These probes target WordPress-specific endpoints that do not exist in a flat-file architecture.
When a probe hits a flat-file site looking for wp-login.php and receives a 404 or a bomb response, the probe reveals that the site is not WordPress. This is an intelligence signal — attackers and scrapers that assume WordPress are immediately disoriented by a non-WordPress architecture.
WordPress pages contain significant non-content markup — theme CSS classes, plugin-generated HTML, widget areas, dynamic menu structures, comment systems, and administrative overhead. This non-content markup reduces the signal-to-noise ratio for AI crawlers parsing the page for citation-relevant content.
A flat-file PHP page contains exactly the content it is designed to contain — no plugin overhead, no theme bloat, no dynamic elements that can confuse parsers. The HTML structure is predictable, the schema markup is explicit, and the content is immediately accessible. This clarity produces better citation outcomes because inference engines can extract the relevant information without filtering out extraneous markup.
The MM deployment achieved a Day-4 AI Overview citation on GoDaddy shared hosting — widely considered suboptimal infrastructure — using flat-file PHP. The infrastructure was not the advantage. The architecture was. A WordPress site on premium cloud hosting with the same content and schema markup would not necessarily produce the same outcome, because the content delivery architecture is a meaningful input to the crawl and citation process.