Page Analyzer
Run an on-demand AEO audit of any URL — AEO score, entity signals, structured data coverage, and specific fix recommendations.
Overview
The Page Analyzer takes a single URL and runs a full AEO audit in seconds. Where Page Optimization gives you a project-wide view of every tracked page, the Page Analyzer is for the ad-hoc question "how well is this page optimized for AI engines right now?"
Use it when you're:
- Reviewing a draft before publishing
- Evaluating a competitor's page
- Debugging why a specific URL isn't showing up in AI responses
- Deciding which of several candidate pages to optimize next
What the analysis produces
When you enter a URL and click Analyze, the platform crawls the page and returns:
| Signal | What it measures |
|---|---|
| AEO Score | Overall 0-100 score for how well the page is optimized for AI citation |
| Structured data | Presence and validity of JSON-LD schema (Article, Product, FAQ, HowTo, etc.) |
| Entity clarity | How clearly the page identifies your brand, product, and key attributes |
| Content structure | Heading hierarchy, list density, Q&A patterns — things AI engines use to extract answers |
| Internal linking | Signals that help AI engines understand page context |
| External citations | Whether the page cites authoritative sources |
| Robots access | Whether AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) can actually fetch the page |
| Specific fix list | A prioritized list of concrete changes with estimated impact |
Running an analysis
- Open Page Analyzer from the sidebar
- Paste the URL
- Click Analyze
- Results appear inline in ~10-20 seconds
The page is fetched fresh each time — no cache. If you change the page and want a new score, re-run the analysis.
Each paragraph element on the page is read as its own paragraph. Every check that reads the whole page (word count, dates, figures, named terms) reads its visible text: the HTML without scripts, styles and noscript blocks, with every tag ending a word.
Interpreting the AEO Score
| Score | Meaning |
|---|---|
| 90-100 | Excellent. The page is well-structured for AI extraction. Focus on content quality, not structure. |
| 70-89 | Good. A few targeted improvements (schema, headings, entity clarity) will move the needle. |
| 50-69 | Average. Significant AEO gaps. The fix list will usually have 5-10 items. |
| 30-49 | Poor. The page is missing fundamental AEO signals. Start with structured data and entity clarity. |
| 0-29 | The page is effectively invisible to AI engines. Either the content is empty, blocked, or unstructured. |
Fix list
Each fix in the list has:
- Description — what to change
- Category — Structure / Schema / Entity / Content / Access
- Impact — 0-100 estimated score improvement if you apply this fix
- Effort — Low / Medium / High based on how much content needs to change
Fixes are sorted by impact-to-effort ratio so the first item is always the highest-leverage change you can make.
Difference from Page Optimization
| Page Analyzer | Page Optimization |
|---|---|
| Single URL, on-demand | All tracked URLs in the project |
| No history — run fresh each time | Historical scores over time |
| Works on any URL (including competitors) | Works on URLs you've added to tracking |
| Manual trigger | Re-scored automatically on schedule |
Use the Page Analyzer for ad-hoc reviews, and Page Optimization for ongoing monitoring of your site.
Best practices
- Analyze competitors. Comparing your AEO score against the best-ranked competitor tells you how much gap you have to close.
- Re-analyze after changes. Apply one fix at a time and re-analyze so you know which changes actually moved the score.
- Don't chase 100. A score of 85-90 on a well-written page is better than 100 on a page full of keyword-stuffed structured data.
- Check robots access first. If the robots check fails, nothing else matters — AI engines literally can't see the page. Fix that before anything else.