Why can an AI agent not fetch my homepage?

What it is

This is the first Check in a Scan and the one every other Check depends on. We send one GET to your homepage and read what comes back.

A 200 with HTML is a Pass. A 401, 403, 429 or 503 is a Fail, because those are the codes an edge returns when it has decided not to serve automation.

Any other non-200 status is a Warning: a redirect chain that never lands, a 500, an interstitial. The Evidence carries the exact status, the milliseconds and the byte count.

Why an agent needs it

Nothing on your site can be read, quoted or acted on by an agent that never received a page. When this Check fails, the Report has almost nothing else to measure.

The distinction the Evidence draws matters when you go to fix it. A refusal is a bot rule, a timeout is capacity, and a name that does not resolve is DNS.

The Fix

Serve the homepage over HTTPS on a 200, without a redirect loop and without an interstitial. Check that the address you gave us is the one that actually answers.

If the status was 401, 403, 429 or 503, the page exists and a rule refused us. Add an allow rule for agents that identify themselves, matched on user agent and verified where you can.

Then run the Scan again. Every Check downstream of this one is measured from the page we finally receive.

This one is a change in your own markup or edge configuration, so the Fix Pack cannot write it for you. A Report names every page it affects, with the Evidence.