Answer readiness
We look at whether the page answers the right things clearly, then show you the exact sections that are helping or getting in the way.
Enter a public URL including https://
See what search and AI systems can actually understand from your page.
Generative readiness
We check whether the page makes its subject, evidence and responsible entity clear enough for generative retrieval—not just whether a few tags exist.
Semantic review
An optional semantic pass looks at the meaning of the page: what it explains well, what feels generic, and what would be safer to quote.
Live audit
Running your audit
Connecting to the requested page…
00:00
Connecting to the public page
- Fetch pageResolve the URL, redirects and public HTML.
- Crawler filesCheck robots.txt, sitemap and llms.txt.
- Parse & scoreInspect content, schema, entities and answer signals.
- Semantic AIRuns separately after rule results are ready.
- Finalize reportMerge scores and prepare the full diagnostic report.
You will see the deterministic results first. Groq semantic analysis runs independently, so the deterministic results appear first and remain usable even if AI reaches a rate limit.
Want help turning the report into actual fixes?
Send us this saved report. We can work from the same URL, the same scores and the same evidence you are looking at, so the conversation starts with the real problems instead of a sales checklist.
Score diagnostics
AEO breakdown
Website preview will appear here
Preview image selected from the audited site metadata
0–4950–8990–100
Key metrics
Priority actions
Diagnostics
Checks that most affect AEO and GEO readiness.
Answer Engine Optimization
How easily can a search or answer system identify the page topic, find a direct answer, and extract it with enough context?
Generative Engine Optimization
How clearly does the page expose entities, evidence, citations, authorship and reusable factual passages for generative retrieval systems?
Technical readiness
Fetchability, indexability, crawler discovery and the machine-readable signals that determine whether the page can be reliably processed.
Collected technical evidence
Technical diagnostics
Open a check to see the exact evidence and the recommended fix.
SEO Knowledge Base
A place to understand the “why” behind the checks.
The Knowledge Base is where we write down the reasoning behind the auditor: what a signal means, when it matters, and what we would actually change on a live site.
Measure SEO After Launch: Search Console, Analytics and Iteration
A launch is the start of measurement, not the moment SEO becomes ‘done.’ The useful work is noticing what changed and deciding what deserves a response.
Read guide
Citation-Worthy Content: Data, Sources and Original Insight
A page becomes worth citing when it contains something specific enough to be useful and supported well enough that someone else can safely repeat it.
Read guide
SEO-Friendly UX: Navigation, Readability and Accessibility
SEO-friendly UX is not a special design style. It is a site that makes the next useful thing obvious to people and leaves the same structure understandable to crawlers.
Read guide
Image SEO: Formats, Alt Text, Dimensions and Lazy Loading
Image SEO is mostly good image engineering: send the right file, at the right size, with useful context, without making the page wait for it.
Read guide
Robots.txt, XML Sitemaps, Canonicals and Indexability
Robots rules, sitemaps and canonicals solve different problems. A lot of indexing trouble starts when they are treated as three versions of the same switch.
Read guide
E-E-A-T and Trust Signals: Authors, Sources and Editorial Transparency
Trust is rarely created by adding an author box at the bottom of a weak article. It comes from showing who is responsible, how claims were supported, and where experience came from.
Read guide
Built by Imagine it
We build websites to work, not just to look finished.
Imagine it is a digital agency, but the part we care about most starts after the mockup looks good. A site has to be easy to use, fast enough to stay out of the way, understandable to search engines, and useful enough to earn the client something in return. We built AEO & GEO Insights because we wanted a public version of the checks we keep doing during real projects: what can a crawler see, what can a person understand, and where is the page making either of them work too hard?
The process is deliberately connected. UX comes first because a beautiful page that makes the next step confusing is still a bad page. Design gives that experience a clear visual language. Engineering has to preserve both without burying the site under unnecessary plugins, scripts and workarounds. Technical SEO is part of the build, not something we bolt on the night before launch. Once the site is live, we keep looking at search data and real visitor behaviour, then we change the parts that are not doing their job.
UX before decorationWe want the first-time visitor to understand the page before we ask them to admire it. The visual layer should make the journey clearer, not compete with it.
Performance in the implementationWe would rather solve a problem in the build than hide it behind three more plugins. Smaller dependencies and sensible assets are easier to measure, maintain and improve.
Search is part of the productCrawlability, content structure, schema and indexing decisions are discussed while the site is being built. They should not arrive as a cleanup project later.
The launch is a checkpointAfter launch we watch what people search for, where they land, what they do next and where they drop off. That evidence becomes the brief for the next round of improvements.
When we say quality guarantee, we mean the work we can actually be accountable for. We set the standard before the build, test against it, and fix the parts that miss it. We will not promise a ranking position or pretend we control an algorithm. We can promise that we will measure our own work and keep working on the gaps we find.
imagineit.onlineSupport the project
If the tool helped you, you can help us keep building it.
The public auditor costs real hosting time and a surprising amount of maintenance. Donations go back into crawl reliability, documentation, testing and the next features we want to ship. There is no paywall attached to the report—this is simply a way to support the project if it has been useful to you.
Methodology
We measure readiness. We do not invent an “AI rank.”
Most of the report comes from things we can verify directly on the page. The semantic AI pass is a second opinion and its weight changes with model confidence. None of that proves a page is currently cited by ChatGPT, Gemini, Perplexity or an AI search feature. To measure that, you have to run real prompts repeatedly and record what those products actually return.
1Crawl & parseWe fetch the public page and the supporting crawl files, then record what the server really returns.
2Rule engineThe rule engine scores checks we can explain, with evidence beside every warning instead of a mystery number.
3Semantic AIThe optional semantic pass reviews meaning and evidence, then gets confidence-weighted before it can influence the final score.
What the scores mean
AEO Score is about answer clarity and page structure. GEO Score focuses more on entities, evidence, retrieval and reusable passages. AI Readiness is the semantic review; if the model is uncertain, its influence on the hybrid scores is reduced.