AI Search Visibility Tools: What the Top 10 Pages Do
Measured 27 September 2026; every fetch below completed between 03:35 and 03:40 SGT. Raw scan file: aisight_serp_scan_20260927.json.
The answer: Measured 27 September 2026, all 10 pages ranking on Google Singapore for “AI search visibility audit tool” answered a browser with HTTP 200. Only 2 of 10 published FAQPage schema, 6 of 10 any structured data, and 4 stated a price. One page — a Reddit thread — answered GPTBot with HTTP 403.
If you are choosing a tool to show you how AI engines read your site, it helps to know what the pages Google already trusts actually ship. A tool page that cannot be read by GPTBot has a hard time being recommended by ChatGPT — and two thirds of the pages ranking for this buyer question publish no question-and-answer markup at all, which is the one format answer engines lift most cleanly.
What the top 10 serve today
| # | Page | HTML | Words | FAQ schema | GPTBot |
|---|---|---|---|---|---|
| 1 | reddit.com/r/seogrowth (thread) | 8 KB | 1 | No | 403 |
| 2 | webaloha.co/tools | 134 KB | 2,177 | Yes | 200 |
| 3 | chromewebstore.google.com | 652 KB | 1,980 | No | 200 |
| 4 | adamigo.ai/free-tools | 302 KB | 2,555 | Yes | 200 |
| 5 | wix.com/studio | 2.5 MB | 2,690 | No | 200 |
| 6 | seranking.com | 636 KB | 2,552 | No | 200 |
| 7 | discoveredlabs.com (comparison) | 321 KB | 3,960 | No | 200 |
| 8 | zapier.com/blog | 664 KB | 5,216 | No | 200 |
| 9 | youtube.com (video) | 1.6 MB | 40 | No | 200 |
| 10 | ahrefs.com/blog | 892 KB | 3,596 | No | 200 |
Sizes are the bytes served to a browser user-agent, uncompressed as delivered. Word counts are the visible text a no-JavaScript fetch returns, which is why app pages (positions 1, 3, 5 and 9) look light or textless — their content arrives by script after load, and an answer engine that does not run scripts sees the shell.
How we tested
- The set: the 10 organic results for “AI search visibility audit tool” on Google Singapore (gl=sg, hl=en), pulled on 27 September 2026 at 03:35 SGT. AISight itself was not in that top 10, so nothing here is self-promotion.
- The fetches: every URL fetched three times inside the same minute from the same connection, changing only the user-agent — a Chrome 128 browser string, the GPTBot string (
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; GPTBot/1.2; +https://openai.com/gptbot), and the PerplexityBot string. - The rule: the browser fetch is the control, so any difference is caused by the user-agent and not by the IP or the time of day. The one difference we found was re-fetched twice more, two seconds apart, and reproduced both times.
What we found
- 10 of 10 answered a browser with HTTP 200. Nothing in this top 10 is broken for human visitors.
- 9 of 10 answered GPTBot with HTTP 200; 10 of 10 answered PerplexityBot with 200.
- 1 of 10 served an AI crawler something different: the Reddit thread at position 1 returned 403 to GPTBot on two fetches while serving a browser 8,473 bytes of the same page.
- 2 of 10 published FAQPage markup (webaloha.co, adamigo.ai); 6 of 10 published valid JSON-LD of any type.
- 4 of 10 stated a price anywhere on the page.
- Median served HTML: 659,374 bytes (about 644 KB). Median visible text: 2,553 words.
How this compares to AISight's own pages
We measure ourselves on the same dimensions, at the same time, so the comparison is checkable: on 27 September 2026, 11 of AISight's 17 sitemap pages carried FAQPage schema, and our pages serve 5–15 KB of HTML each with the content present in the raw HTML rather than rendered by script afterwards. We are not in the top 10 for this query yet — that is the honest position — so what we publish here is what we can show: the measurement and the method behind it.
See what an AI engine actually gets when it fetches your pages: plain HTML, no script.
Run Your Free AI Visibility Audit →Questions
How many AI visibility tools publish FAQ schema?
Two of the ten pages ranking on Google Singapore for “AI search visibility audit tool” on 27 September 2026 published FAQPage markup in the served HTML (webaloha.co and adamigo.ai). Six of the ten published any JSON-LD at all, and four stated a price on the page.
Can ChatGPT read the top-ranking AI visibility tool pages?
Nine of the ten answered GPTBot with HTTP 200 on 27 September 2026, and all ten answered PerplexityBot with 200. The one exception was the Reddit thread at position 1: it returned HTTP 403 to GPTBot on two fetches while serving a browser 200 in the same minute.
How heavy is a typical AI visibility tool page?
The median page in the top ten served 659,374 bytes of HTML (about 644 KB) and 2,553 words of visible text on 27 September 2026. Two of the ten were JavaScript shells — the Reddit thread served 8 KB and the YouTube result 1.6 MB with 40 words of text — so the median is pulled in both directions by app pages rather than by content pages.
Related measurements and guides: which Singapore sites block AI crawlers, which sources AI models actually cite, how ChatGPT picks pages to quote, how to read your AISight score, AEO ranking and GEO ranking. Ready to check your own site? See the plans.