Free tool
The WisWes AEO checker fetches any page the way ChatGPT, Perplexity and Google AI Overviews do — raw HTML, no JavaScript — and runs 25 live checks: crawler access, answer-first content, question-shaped headings, structured data, extractability and freshness. You get a 0–100 score and the exact fixes, in impact order.
Checks run live: we fetch your page the way an AI crawler does — raw HTML, no JavaScript — plus your robots.txt and a GPTBot-user-agent probe. Nothing is stored.
Answer engines do three things with your page: fetch it, extract a passage from it, and decide whether to trust it enough to cite. The six categories map onto that pipeline:
sameAs profiles, breadcrumbs, and honest dates.New to the topic? Read the companion guide: What is AEO — and why your best pages get skipped by AI answers.
An AEO score measures how well a page is prepared for AI answer engines — ChatGPT Search, Perplexity, Google AI Overviews, Gemini, Copilot. The WisWes checker scores 0–100 across six areas: crawler access, answer-first content, question-shaped headings, structured data, metadata & extractability, and freshness & authorship. 80+ means the page has the shape answer engines cite.
The checker fetches your page the way an answer engine does — raw HTML, no JavaScript rendering — then runs 25 machine checks on it. It also fetches your robots.txt to see whether AI crawlers like GPTBot, ClaudeBot and PerplexityBot are allowed, and probes your page with a GPTBot user-agent to detect CDN or firewall blocking. Nothing is stored.
SEO and AEO reward different things. Google ranks a whole page; an answer engine extracts a passage. A page can rank #1 while being hard to quote — no self-contained answer in the first paragraph, no FAQ schema, headings that are labels rather than questions, or a Cloudflare setting silently blocking AI crawlers. The checker flags exactly which of those apply.
Crawler access. If GPTBot, ClaudeBot, PerplexityBot or OAI-SearchBot get a 403 from your CDN or are blocked in robots.txt, no amount of content work matters — the engines that would cite you cannot read you. After that: lead every key page with a 40–60 word direct answer, and add page-scoped FAQPage schema.
No — deliberately. Most answer-engine crawlers and live-retrieval fetchers read the server HTML and render little or no JavaScript. If your content only appears after client-side rendering, it is invisible to them, and the checker will show that with a low word count in the "readable without JavaScript" check.
No. The score covers the machine-checkable layer: crawlability, structure, schema, extractability, freshness. Whether you actually get cited also depends on things no tool can score — whether your content contains genuinely useful answers, original data, and a trusted entity. A high score removes the technical reasons you would be skipped.
WisWes turns your catalog, FAQs and policies into an AI agent that answers shoppers on your site — the same answer-first content answer engines reward. Free plan — no card.