Your site looks fine. ChatGPT sees an empty page. Here is how to check

Open your site in a browser and everything is there: listings, prices, copy. Now picture ChatGPT opening the same page. It does not run JavaScript, it does not wait for anything to load, and it does not click buttons. It takes the raw HTML. If your text only appears after scripts run, the bot gets an empty shell and a few lines from the footer. Then it answers the user by citing someone else.

We found this on our own site, wse.am (real estate in Yerevan, five languages). We built a check for ourselves and then put it on the Apify Store so anyone can use it.

GEO in two lines

SEO answers the question "will Google find me?". GEO (generative engine optimization) answers "can ChatGPT, Perplexity or Claude read my site and cite it in an answer?".

What the auditor checks

It fetches your pages the way Googlebot, GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot get them, and compares the results. You see whether the server blocks any of them, or hands one of them an empty page or different HTML.
It reads robots.txt and shows whether 15 AI and search bots are allowed in, including Google-Extended (the one used for Gemini).
It checks llms.txt and llms-full.txt: whether they exist and whether the links inside work.
The technical basics: status codes, redirects, canonical, noindex, sitemaps, headings, title and description, JSON-LD structured data, broken links, image weight.
Language versions: two-way hreflang, x-default, the html lang attribute and the actual language of the text. It catches Russian text sitting on an /en/ page, which happens more often than you would think.
Every page gets a score from 0 to 100 with a plain-language note on what is wrong and how to fix it, plus one prioritized fix list for the whole site.

What it found on wse.am

On October 29 we ran it on wse.am. First run, 150 pages: site score 96, GEO 97. Good numbers, but the report found something unpleasant. On 18 of the 150 pages (12%) all of the text sat inside noscript, and the main content block was empty. That was the Chinese version and the blog feed. It also found English and Armenian investment pages with Russian text inside, hreflang links that did not point back, and Russian titles on /en/ and /hy/ pages.

In parallel we did a strict expert review of the whole site: mobile speed, copy, the path to an enquiry. That one came out at 65 out of 100. The gap is honest. The auditor measures whether bots can read your site, not how fast it is or how well it sells. More on that under limits.

Within the day we fixed what the auditor flagged: the same prerender for every bot, translations on the language pages, hreflang links, titles. That evening we ran it again, this time on 300 pages:

site score: 96 → 98
GEO: 97 → 100
pages with real text in the raw HTML: 82% → 99%
pages with text only inside noscript: 12% → 1%
average score of the English version: 83 → 95, Kazakh: 68 → 94

The samples differ (150 vs 300 pages), so treat the comparison as approximate. The direction is clear, though.

Why we care. Since October 22 the site records the source of every enquiry. On October 24, 4 of 5 enquiries with a known source came from ChatGPT; on October 25, 5 of 8. This week ChatGPT became the number one source of enquiries for wse.am. Server logs for October 28 show ChatGPT opening our pages for its users 1,206 times in one day. The audit did not create that traffic. It showed us where AI was still seeing empty pages.

Who it is for

Site owners who want to know why ChatGPT does not cite them, or why pages are stuck in search.
Agencies and freelancers. The fix list drops straight into a client proposal or a developer's ticket queue.
Multilingual sites. Most audit tools skip hreflang and real-language checks; here they are part of the base price.
Developers. Run it before and after a release, put it on a schedule and compare the scores.

Price

$0.025 per audited page, no subscription. The GEO check, hreflang, robots.txt, sitemaps and the Markdown and CSV reports are included.

Example: 50 pages cost $1.25, 200 pages cost $5. If the site cannot be reached at all, you are not charged. You can set a maximum charge per run, and the auditor will cut the page count to fit.

The page budget is split evenly across the site's languages, then across sections within each language. So even 50 pages cover every language version, not just the home page and a couple of articles.

How to run it in 3 steps

Open the auditor on the Apify Store: apify.com/eilitine/seo-geo-site-auditor. You need an Apify account; signing up is free.
Paste your home page URL, set the number of pages (50 is enough for most sites) and pick the report language: English, Russian or both.
Start it. A 50-page run usually takes 2-5 minutes. You get a table of pages from worst to best, a summary with the site and GEO scores, and Markdown and CSV reports for Excel or Google Sheets.

What it does not do

It does not run JavaScript. That is deliberate: it shows what bots actually get. If your content only appears after scripts run, the report shows it as missing, and that is exactly the thing to fix. If you need a "what the browser shows" view, this is not the tool.
It does not measure speed by default. You can add Core Web Vitals with your own free PageSpeed Insights key.
It does not look at backlinks, rankings or traffic. It audits the site itself; use it alongside Search Console.
The GEO score measures technical readiness. It does not promise your brand will show up in ChatGPT answers; that also depends on mentions on other sites.
Pages behind a login, or blocked for bots by a firewall, appear in the report with their status code only.
Links and images are checked on a sample to keep runs fast and cheap.

Our 65 vs 96 is exactly this. A high auditor score means bots can read the site properly. It will not catch a slow mobile catalog or weak calls to action in the blog.

Try it on your site

Run 20 to 50 pages, which costs 50 cents to $1.25. See how much of your text GPTBot and ClaudeBot actually get.

Open the SEO + GEO auditor on the Apify Store

Found a false positive or missing a check? Post it on the Issues tab of the auditor page. Built by the team behind wse.am; we use it on our own site.