The three lenses
GEOBee scores every URL through three independent lenses. Each lens is a weighted set of signals that sum to 100, so a lens score is simply the share of its weight the page earned — kept as three separate numbers and never blended together.
AEO — Answer Engine Optimization
Can an assistant read this page and lift a clean, correct answer out of it? AEO rewards a direct answer up top, clear structure, and content that's easy to extract.
| Signal | Weight | What it checks |
|---|---|---|
| Answer block | 20 | A concise, 40–60 word direct answer within the first few paragraphs. |
| Headings | 15 | A single H1, at least two H2s, and question-style headings. |
| FAQ / Q&A | 15 | FAQPage structured data, or several question headings. |
| Answer-relevant schema | 10 | FAQPage, Article, BlogPosting, HowTo, Product, or QAPage. |
| Extractability | 15 | Enough real text (aim for 300+ words) versus HTML noise. |
| Lists & tables | 10 | Lists and tables that assistants can lift cleanly. |
| Title & meta | 10 | Title and meta description within healthy length windows. |
| Conciseness | 5 | Readable sentences — averaging under ~25 words. |
GEO — Generative visibility
Is this page the kind of source a generative engine will retrieve, trust, and reproduce in an answer? GEO leans on citability, author trust, freshness, and — importantly — whether AI crawlers are even allowed in.
| Signal | Weight | What it checks |
|---|---|---|
| Citability | 25 | Statistics, outbound citations, and quotable blockquotes. |
| Author / E-E-A-T | 15 | A visible author byline or Person schema. |
| Freshness | 15 | A recent published or modified date. |
| Entity clarity | 15 | Organization or Person schema with sameAs links. |
| Trust | 10 | HTTPS, valid schema, and a visible way to make contact. |
| Depth | 10 | Substantive coverage — more credit past ~800 words. |
| AI bot access | 10 | robots.txt allows the AI crawlers to reach the page. |
SEO — Classic
The technical foundation a serious crawler already checks, scored so it travels alongside AEO and GEO instead of being a separate tool. Highest-weighted signals first:
| Signal | Weight |
|---|---|
| HTTPS & mixed content | 15 |
| Title | 15 |
| H1 | 12 |
| Meta description | 10 |
| Canonical | 10 |
| Image alt text | 8 |
| html lang | 5 |
| Viewport | 5 |
| Heading hierarchy | 5 |
| Thin content | 5 |
| Charset | 3 |
| Security headers | 3 |
| Anchor text | 2 |
| Link count | 2 |
Structured data it detects
GEOBee reads each page's JSON-LD and reports the type it finds, validating required fields (for example, an Article needs a headline; a Product needs a name and offers). When schema is absent or broken the page reads as None, Invalid, or Partial. Detected types:
AI crawlers it checks
AI bot access looks at your robots.txt for the crawlers that feed today's
assistants and answer engines — GPTBot, OAI-SearchBot,
ChatGPT-User, ClaudeBot, anthropic-ai,
Claude-Web, PerplexityBot, Google-Extended,
CCBot, Bytespider, and Amazonbot — and flags any that
are blocked from a page you'd want to be cited from.