SEO & GEO/AEO

Verified against ChatGPT · 2026-07-30

Check whether ChatGPT and Perplexity can see a specific page right now

A direct test that forces ChatGPT or Perplexity to use their live browsing tool on one exact URL and prove it with a verbatim title and heading quote, instead of answering from stale training data.

ChatGPTPerplexity2 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

Use your live browsing or search tool now — do not answer from memory or training data. If you cannot fetch the URL live, say so plainly instead of guessing or answering as if you had.

URL TO CHECK: https://example.com/pricing

Fetch this exact URL right now and report:

1. Can you access it — yes or no. If no, state the exact error: blocked by robots.txt, a 404, a timeout, JavaScript-only content with nothing present in the initial HTML, a login wall, or anything else specific — not a vague "couldn't access it."
2. Quote the literal page title tag and the first visible heading, verbatim, in quotation marks. This is the actual proof of a live fetch — a model without real access cannot reliably reproduce those exact strings, so a paraphrase here instead of a verbatim quote is itself a signal something didn't work as claimed.
3. Check each of these expected facts and confirm present / not found / contradicted, one at a time, rather than a single blanket verdict: starting price is $49/month, page has a heading called "Simple, transparent pricing", last updated July 2026
4. State today's date as you understand it while performing this fetch, so this result isn't confused with a cached or training-data answer that reflects an earlier point in time.
5. If the page redirected before you reached final content, name the redirect chain — the original URL requested versus where you actually landed — since a redirect changes what "this page" means for the rest of the report.

Do not soften a "not found" into "likely" or "probably" — report exactly what you could and couldn't retrieve, and don't fill a gap with a plausible guess dressed up as an observation.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

A chat model without an active browsing or search call will often answer confidently from stale training data rather than admit it can't see the live page — the exact trap this category most needs to catch, since the model's default failure mode isn't refusing to answer, it's answering fluently and wrongly. Forcing it to quote the literal title tag and first heading verbatim, rather than describe or paraphrase the page, is a built-in hallucination check with real teeth: a model that hasn't actually fetched the page cannot reliably produce those exact strings, so a paraphrase where a verbatim quote was asked for is itself diagnostic, independent of whatever confident prose surrounds it. Naming the redirect chain separately matters because a page that 301s somewhere else means "this page" silently became a different page partway through the check — a report that answers about the final destination while calling it the original URL has quietly changed what was being tested without saying so, and that distinction gets lost entirely without an explicit prompt to surface it. This also catches failure modes a static homepage crawl can't fully simulate for an in-product search experience — a robots.txt block on one specific deep path, JavaScript-only rendering with nothing in the initial HTML, or a noindex tag on any URL, not just the homepage an automated checker typically inspects.

What you get back

1. Access: Yes. 2. Title: "Pricing — Example" / First heading: "Simple, transparent pricing" 3. Starting price $49/month: confirmed. Heading text: confirmed, exact match. Last updated July 2026: not found — no visible update date on the page. 4. Today's date (per this fetch): August 2026. 5. No redirect — the requested URL and the landed URL are identical.

Verified against

ChatGPT GPT-5.1 (Search) · 2026-07-30

Perplexity Sonar Pro · 2026-07-30

Changelog

  • 2026-07-30 Initial publish, built around the verbatim-title-and-heading check after seeing both engines occasionally answer from stale cached knowledge instead of admitting a fetch failed.
  • 2026-08-01 Added the redirect-chain disclosure step after a test case silently reported on a redirected destination page while still labeling it as the originally requested URL.
Pairs with our free AI Visibility Checker — no signup, runs in your browser.

Building this for real?

This is a free starting point. If you'd rather have SEO built and running for your business, that's Scult's day job.

EXPLORE SEO
All SEO & GEO/AEO prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY