The start page could not be crawled (403)
The site audit could not start: the start page did not answer 200, or the request failed, for example with a timeout, a DNS or connection error, or too many redirects. Redirects are followed, so only the final answer counts. With no start page there are no links to follow, and nothing else was checked.
What it means
The start page did not answer with a working HTML page, so no links could be followed. Check the URL and that the site is up.
Why it matters for AI search
The audit follows internal links outward from the start page, as a browser would, so it needs that page to load. A failure usually means the URL is wrong, the site is down, or a firewall, bot protection or rate limit answered the audit's server with a block or a challenge.
If a firewall blocks the audit, it may also block search and AI crawlers that come from data-centre addresses. Compare the status in the finding with what you see in a browser, and look for the request in your firewall logs.
How to fix it
- Open the start URL in a private browser window and check that it loads without a login.
- Use the address the site really serves, with
https://and the right host. - If the status is 403, 429 or 503, find the blocked request in your firewall, CDN or hosting bot-protection logs and allow it, or lower the challenge level for normal page requests.
- If the request timed out, check server load and how fast the page answers from outside your network.
- Run the site audit again from your account to confirm the result.
How to confirm the fix
After the change, press "Check again" on the report: it lists what was fixed and how the score changed.