Tutorial v1.0, updated 2026-07-07

Find why an AI cannot read your page

A few minutes to see what a non rendering AI crawler actually gets, and why.

The outcome: you know whether AI answer engines can read your page at all, and if not, why. This is the first thing to get right, because nothing else matters if an engine cannot read the page.

  1. Run See as bot on the page. It fetches the page as GPTBot, a non rendering AI crawler, and as a browser, and shows the two side by side.
  2. Compare the word counts. If the bot column has far fewer words than the browser, or is near empty, your content is added by JavaScript after load and the AI crawler is not getting it. See server and client rendering.
  3. Read the red lines in the diff. Those are lines the browser gets and the bot does not. That is your missing content.
  4. If the bot is blocked entirely, run AI access to see where: robots.txt, or a WAF or CDN returning a 403. See robots.txt.
  5. Fix it by server rendering the content that matters, then run See as bot again. When the two columns match, an AI crawler can read the page.

Read next

Why AI cannot see content behind JavaScript

Non-rendering crawlers get the shell, not the content and how to fix it.

What internal PageRank is

How link equity flows through your own site, and why buried pages lose out.

What crawl budget is

The finite attention a crawler gives your site, and how it gets wasted.

All topics