# What GPTBot sees on your page

> Fetches your page with GPTBot's published user agent and no JavaScript, then shows the text a non-rendering crawler actually receives.

- Canonical page: https://lantad.co/tools/what-gptbot-sees
- This file: https://lantad.co/tools/what-gptbot-sees.md

## Key facts

- **Method:** A robots.txt check first, then one fetch as GPTBot with no JavaScript.
- **What it proves:** Whether your words exist before hydration.

## Why this is the fastest way to see the problem

A site built on client-side rendering looks complete in a browser and can be close to empty to a crawler. This shows the crawler copy directly, so the gap is visible in one fetch rather than argued about.

## Related

- https://lantad.co/glossary/prose-parity (markdown: https://lantad.co/glossary/prose-parity.md)
- https://lantad.co/fix (markdown: https://lantad.co/fix.md)
- https://lantad.co/ (markdown: https://lantad.co/index.md)

---

Lantad measures whether AI crawlers can actually read a page: it fetches as a non-rendering
crawler, renders as a browser, and reports the gap. Free scan, one URL, no signup.

Method and weights: https://lantad.co/methodology | All pages as markdown: https://lantad.co/md | Crawler policy: https://lantad.co/bot