Methodology and limits
Free technical check
The checker fetches only the submitted public page and that origin’s /robots.txt. It records the HTTP response, redirects, title, description, canonical, a short readable-text sample, indexing directives, relevant robots rules, and whether JSON-LD parses. It does not follow page links or crawl a site.
Each URL and redirect is resolved and screened against private, reserved, loopback, link-local, and multicast address space before the selected public address is pinned for the request. Requests have redirect, time, and byte limits. TLS verification stays enabled.
How to read the evidence
A successful fetch proves only that this service reached the page from its network at that time. It does not prove OpenAI crawler reachability, indexing, a ChatGPT mention, citation, referral, purchase, or any level of placement. A robots failure can be inconclusive. JSON-LD is descriptive evidence, not a proven ranking factor.
Recorded observations in a paid audit
We agree on three unbranded prompts, run each twice in fresh ChatGPT search conversations under recorded conditions, and preserve both positive and negative observations. One later repeat uses the same method. The report separates mentions, citations, referrals, and purchases.
Primary sources
- OpenAI crawler documentation
- ChatGPT search help
- OpenAI publisher and developer FAQ
- Bing Webmaster Tools AI Performance documentation (a different, sampled source; not a ChatGPT rank report)