geoready.dev

mx

mx1.spacemail.com

mx2.spacemail.com

ns

ns1.vercel-dns.com

ns2.vercel-dns.com

caa

amazon.com

ssl.com

pki.goog

sectigo.com

letsencrypt.org

txt

7ec18087-716a-413a-9231-db1f7cfc7509

brevo-code:08dea99c99e5eaa55b50717fe52406bd

v=spf1 include:spf.spacemail.com ~all

google-site-verification=IRkrE6T_U3XMpEzXcoQcEgb6NVCsT4RkG7P_t2RwIOo

anthropic-domain-verification-zcytks=6sVKAv4tHOakfuEGIOz9PZaey

dmarc

v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com

# robots.txt for geoready.dev
#
# Why the named crawlers repeat the exclusions
# RFC 9309: a crawler obeys only the group that names it most specifically and
# ignores the "*" group. A named group that contained only "Allow: /" therefore let
# those crawlers fetch /api/, /health, /badge and /report/ even though the "*"
# group excludes them. The same rules now appear in the named group and in "*".
#
# Policy is unchanged: every crawler listed here is allowed on the public site.
# /report/demo stays crawlable on purpose (it is the public demo report).
# /api/public/benchmark and /api/stats stay readable: pages fetch them with a GET on
# load (state-of-geo, StatsBar) and the Dataset JSON-LD on /state-of-geo/ points its
# contentUrl at the benchmark. /api/stats answers with X-Robots-Tag: noindex, which a
# crawler can only see if robots.txt lets it fetch the URL.
# Rule order: specific rules first, "Allow: /" last, so parsers that stop at the
# first match behave like parsers that use the longest match.

User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: anthropic-ai
User-agent: ClaudeBot
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: claude-web
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: Google-Extended
User-agent: Google-CloudVertexBot
User-agent: Googlebot
User-agent: Bingbot
User-agent: Applebot-Extended
User-agent: cohere-ai
User-agent: DuckAssistBot
User-agent: Bytespider
User-agent: meta-externalagent
User-agent: Meta-ExternalFetcher
User-agent: facebookexternalhit
User-agent: Amazonbot
User-agent: AI2Bot
User-agent: AI2Bot-Dolma
User-agent: xAI-Bot
User-agent: Applebot
User-agent: PetalBot
User-agent: YouBot
User-agent: CCBot
Allow: /report/demo
Allow: /report/demo/
Allow: /api/public/benchmark
Allow: /api/stats
Disallow: /report/
Disallow: /api/
Disallow: /health
Disallow: /badge
Allow: /

User-agent: *
Allow: /report/demo
Allow: /report/demo/
Allow: /api/public/benchmark
Allow: /api/stats
Disallow: /report/
Disallow: /api/
Disallow: /health
Disallow: /badge
Allow: /

Sitemap: https://geoready.dev/sitemap.xml

# GeoReady

> AI visibility audit and monitoring platform built on the open-source GEO Optimizer engine. Score 0-100 across 9 scoring categories (rubric v2); the signals are derived from published research (Princeton KDD 2024; AutoGEO, arXiv:2510.11438 preprint) and from Google's documentation for search and AI features.

GeoReady helps developers, SEOs, and content teams measure and improve how discoverable, readable, and citable their websites are to AI answer engines such as ChatGPT, Perplexity, Claude, and Gemini.

Built in Italy by Auriti Labs. Designed for the global AI search ecosystem.

## What is Generative Engine Optimization (GEO)?

Generative Engine Optimization (GEO) is the practice of structuring and presenting web content so that AI language models can reliably retrieve, understand, and cite it when generating answers. Unlike traditional SEO — which targets keyword rankings in blue-link search engines — GEO targets citation signals: structured data, content hierarchy, machine-readable discovery files, and brand entity disambiguation.

The GEO Optimizer engine translates the academic research on GEO into GeoReady's practical audit tool with a 0-100 score and per-category breakdowns.

## Scoring categories (max 100 points)

Rubric v2 is the default since GEO Optimizer 4.19.0 and has nine categories. The earlier eight-category v1 rubric is still available with `geo audit --score-version 1`. Full weights: https://geoready.dev/methodology/ and https://geoready.dev/docs/scoring-rubric/

1. **Google AI readiness** (max 20 pts): the technical conditions Google documents for its search and AI features: indexable page (final status 200, no noindex, Googlebot not blocked), snippet controls, a single canonical URL matching the final URL, visible dates consistent with structured data, a byline, crawlable internal links, a viewport tag, and a Sitemap declared in robots.txt.

2. **robots.txt** (max 14 pts): presence and configuration for AI crawlers including GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, Bytespider, meta-externalagent, xAI-Bot, and others. A misconfigured robots.txt can silently block AI crawlers from reading your content.

3. **Schema JSON-LD** (max 14 pts): structured data markup per Schema.org. Checks for Organization, WebSite, FAQPage, and Article types, validates required fields and measures attribute richness, and checks that the schema name or headline appears in the visible text.

4. **Content Quality** (max 14 pts): heading hierarchy, concrete numbers, lists and tables, word count, front-loaded answer structure, and image alt text coverage. AI systems tend to prefer content that delivers the answer before the context.

5. **Brand & Entity Signals** (max 12 pts): brand name consistency across title, H1, og:title, and Organization schema; Knowledge Graph readiness (sameAs links to Wikipedia, Wikidata, LinkedIn, Crunchbase); visible /about link; Organization contactPoint; geographic identity; and topic authority via FAQ depth.

6. **Meta Tags** (max 11 pts): title, meta description, and Open Graph tags. The canonical check moved to Google AI readiness in v2.

7. **llms.txt** (max 6 pts): presence and quality of the llms.txt standard. The GEO Optimizer engine checks for headings, description, sections, links, and the companion llms-full.txt. llms.txt is useful to other AI agents; Google states that its AI features do not use it.

8. **Technical Signals** (max 6 pts): HTML lang attribute, RSS/Atom feed, and freshness indicators (dateModified in schema or article:modified_time meta tag).

9. **AI Discovery** (max 3 pts): presence of /.well-known/ai.txt, /ai/summary.json, and markdown content negotiation. These machine-readable endpoints let AI agents understand your site's purpose without crawling all pages.

## Additional diagnostic checks (no score impact)

- **Prompt Injection Detection**: detects 8 categories of manipulation patterns including hidden text, invisible Unicode, ARIA-hidden injections, and LLM instruction injections.
- **Citability Analysis**: 47 research-backed methods measuring quotation density, statistics, fluency, authoritative tone, answer-first structure, and more. Total citability score 0-100.
- **Trust Stack Score**: composite across technical trust (HTTPS, CSP, HSTS), identity trust, social trust, academic trust, and consistency trust.
- **Negative Signals**: excessive CTAs, thin content, broken links, keyword stuffing, popup indicators.
- **CDN Crawler Access**: detects whether Cloudflare, Akamai, or Vercel is blocking AI crawlers.
- **JS Rendering Check**: flags content that requires JavaScript to be visible to crawlers.
- **WebMCP Readiness**: evaluates the site's machine-readable interface for MCP-compatible AI agents.
- **RAG Chunk Readiness**: measures how well the page content can be chunked for retrieval-augmented generation.
- **Content Decay Detection**: identifies stale version numbers, expired year references, and temporal inconsistencies.
- **Platform Citation Score**: per-platform readiness for ChatGPT, Perplexity, and Google AI Overviews.

## Score bands

- 86–100: Excellent — well-optimized for AI search
- 68–85: Good — strong foundation, minor gaps
- 36–67: Foundation — significant improvements possible
- 0–35: Critical — major barriers to AI visibility

## CLI commands

Install: `pip install geo-optimizer-skill`

- `geo audit --url <URL>`: full GEO audit with nine-category score and recommendations
- `geo audit --url <URL> --format json`: machine-readable JSON output for CI/CD pipelines
- `geo audit --url <URL> --format html`: standalone HTML report
- `geo fix --url <URL>`: generate fix files (robots.txt, llms.txt, JSON-LD schema)
- `geo llms --url <URL>`: check llms.txt readiness and generate a template
- `geo schema --url <URL>`: validate JSON-LD schema markup

## MCP server integration

The GEO Optimizer engine is available as an MCP (Model Context Protocol) server. AI coding assistants that support MCP can use it to run audits, compare URLs, check AI bot access, validate schema, and more — directly within the coding session.

Available MCP tools: `geo_audit`, `geo_compare`, `geo_fix`, `geo_llms_generate`, `geo_check_bots`, `geo_schema_validate`, `geo_citability`, `geo_trust_score`, `geo_gap_analysis`, `geo_ai_discovery`, `geo_negative_signals`, `geo_factual_accuracy`.

## Trust signals

- License: MIT
- Source code: https://github.com/Auriti-Labs/geo-optimizer-skill
- All scoring weights are public and documented in `src/geo_optimizer/models/config.py`
- No external API required for core audit functionality
- Zero data collection from audited URLs beyond the public HTTP fetch
- Test suite: 1,400+ unit tests, all mocked (no real network calls in tests)

## Known limitations

- JavaScript-heavy SPAs may receive lower scores if content requires client-side rendering
- The free web tool processes one URL at a time; batch processing is available via CLI
- Brand sentiment and embedding proximity features require optional dependencies
- Scoring reflects the state of the page at audit time; dynamic content may vary

## Update policy

The GEO Optimizer engine is actively maintained. Scoring weights and audit methods are updated as new research is published. Version history and changelogs are available at https://github.com/Auriti-Labs/geo-optimizer-skill/releases.

## Main sections

- [Audit](https://geoready.dev/): Run a GEO audit on any URL — free, no account required.
- [About](https://geoready.dev/about/): Who builds GeoReady and GEO Optimizer — Auriti Labs.
- [Book: AI Search Engineering](https://geoready.dev/book/): 992-page technical guide to Generative Engine Optimization, AI citations, and agent-ready websites by Juan Camilo Auriti (ISBN 979-8172934568, September 2026). Documents the methodology the audit engine implements.
- [AI SEO Guide](https://geoready.dev/ai-seo/): What AI SEO is, how it differs from traditional SEO, and how to audit a site for visibility in ChatGPT, Perplexity, Claude, and Gemini.
- [Free AI SEO Audit](https://geoready.dev/ai-seo-audit/): High-intent audit landing page with a no-account form for checking crawler access, llms.txt, schema, content quality, AI discovery, and entity signals.
- [AI SEO Audit for SaaS](https://geoready.dev/ai-seo-audit-for-saas/): Audit landing page for SaaS product, comparison, pricing, and docs pages — crawl access, schema, llms.txt, content citability, and entity signals.
- [ChatGPT Visibility Audit](https://geoready.dev/chatgpt-visibility-audit/): Audit landing page for crawler access, entity clarity, structured data, and prompt-level ChatGPT visibility signals.
- [ChatGPT Visibility Checker](https://geoready.dev/chatgpt-visibility-checker/): Readiness page explaining how to check whether a site can appear in ChatGPT-style answers, with a path from audit to source-backed citation checks.
- [Perplexity Citation Checker](https://geoready.dev/perplexity-citation-checker/): Commercial citation page for checking whether Perplexity-style answers cite the user's own domain or cite competitors instead.
- [Perplexity Citation Monitoring](https://geoready.dev/perplexity-citation-monitoring/): Monitor whether Perplexity-style answers cite a domain, mention the brand without citing it, or cite competitors instead.
- [GEO Monitoring Tool](https://geoready.dev/geo-monitoring-tool/): Monitor your GEO score over time — scheduled re-audits, score history, and regression alerts when a signal drops. Weekly on Pro, daily on Studio.
- [Citation Gap Analysis](https://geoready.dev/citation-gap-analysis/): See who AI engines cite instead of you, compare GEO-score readiness, and track the gap over time.
- [ChatGPT Citation Tracker](https://geoready.dev/chatgpt-citation-tracker/): Honest breakdown of ChatGPT citation tracking — what's automated (Perplexity/Studio), manual (Agency), and what no tool does yet.
- [AI Overviews Trend Tracking](https://geoready.dev/ai-overviews-trend-tracking/): A repeatable workflow for tracking AI Overviews trends over time — query sets, logging schema, cadence, and how to read real shifts vs. noise.
- [Compare](https://geoready.dev/compare/): Side-by-side comparison of two URLs.
- [Analyze Competitors](https://geoready.dev/analyze-competitors/): Multi-URL competitor analysis.
- [Research](https://geoready.dev/research/): Published research foundation.
- [Methodology](https://geoready.dev/methodology/): Transparent scoring weights, score bands, signal categories, and research-backed assumptions behind the GEO score.
- [State of GEO](https://geoready.dev/state-of-geo/): Live AI search readiness benchmark across sites audited by GeoReady — average and median GEO score, llms.txt and schema adoption, and the biggest readiness gap. Aggregated and anonymized; an audited sample, not a survey of the whole web.
- [State of GEO: September 2026](https://geoready.dev/state-of-geo/september-2026/): Monthly benchmark report — 704 domains audited, average GEO score 56.2/100 (flat, −0.2 points), 28.8% reach "Good" or above, llms.txt adoption 57.4% (a measured floor), AI-crawler blocking down to 8.8%; scored on four engine versions, so month-over-month deltas are indicative.
- [State of GEO: August 2026](https://geoready.dev/state-of-geo/august-2026/): Monthly benchmark report — 282 domains audited, average GEO score 56.4/100 (up 2.3 points), 29.1% reach "Good" or above, llms.txt adoption rebounded to 62.8%.
- [State of GEO: July 2026](https://geoready.dev/state-of-geo/july-2026/): Monthly benchmark report — 360 domains audited, average GEO score 54.1/100, only 24.7% reach "Good" or above.
- [State of GEO: June 2026](https://geoready.dev/state-of-geo/june-2026/): Monthly benchmark report — 288 domains audited, average GEO score 53.6/100, only 20.8% reach "Good" or above.
- [Best GEO Tools](https://geoready.dev/best-geo-tools/): Criteria-based guide to evaluating generative engine optimization software, including methodology transparency, audit vs monitoring, CI/CD support, and answer-engine citation checks.
- [Which GEO Tool Has a Transparent Methodology?](https://geoready.dev/transparent-geo-tool/): The scoring weights, the check logic and the test suite are public and MIT licensed. Reproduce any GEO Optimizer score on your own machine — plus what the score cannot tell you.
- [Open-Source Alternative to Profound & Otterly](https://geoready.dev/open-source-profound-otterly-alternative/): Why GEO Optimizer is a free, MIT-licensed, self-hostable alternative to commercial GEO platforms — audit, AI citation tracking, and CI/CD support.
- [Otterly Alternative](https://geoready.dev/otterly-alternative/): Otterly alternative comparison — entry pricing, the $29-to-$189 jump, engine coverage, and where Otterly is genuinely stronger. Sourced, dated Sep 2026.
- [Profound Alternative](https://geoready.dev/profound-alternative/): Profound starts at $99/mo and gates Enterprise behind sales. Where it shines, who should stay, and how GeoReady's $0-$49 plans compare. Sep 2026.
- [Veesie Alternative](https://geoready.dev/veesie-alternative/): Comparing Veesie and GeoReady for GEO monitoring — engine coverage, EUR vs USD pricing, and free-audit differences. Sourced, dated September 2026.
- [Semrush AI Visibility Toolkit Alternative](https://geoready.dev/semrush-ai-visibility-toolkit-alternative/): What Semrush's AI Visibility Toolkit costs, and when a dedicated $0-$19 GEO tool beats a bundled suite module. Facts dated September 2026.
- [Roadmap](https://geoready.dev/roadmap/): Planned and in-progress features.
- [GEO Readiness Manual](https://geoready.dev/geo-readiness-manual/): 160-page technical guide to AI search visibility, citations, and Generative Engine Optimization — access, schema, quotability, entity authority, measurement, and security.
- [Manifesto](https://geoready.dev/manifesto/): Why the open-source GEO Optimizer engine exists and what it stands for.
- [Pricing](https://geoready.dev/pricing/): Free and Pro plan comparison.
- [Privacy Policy](https://geoready.dev/privacy/): GDPR-compliant privacy policy.
- [Guides](https://geoready.dev/guides/): Index of practical, no-hype guides on AI search visibility and Generative Engine Optimization.

## Tools

- [Free AI Citation Checker](https://geoready.dev/tools/ai-citation-checker/): Check whether a brand is mentioned or cited by AI answer engines, with outcome labels for cited, mentioned, competitor-cited, or invisible.
- [Free llms.txt Generator](https://geoready.dev/tools/llms-txt-generator/): Generate a starter llms.txt from your sitemap — categorized, editable Markdown you can download and publish at your domain root. Free, no account required.
- [llms.txt Generator for WordPress](https://geoready.dev/llms-txt-generator-wordpress/): Generate a starter llms.txt for a WordPress site, then audit whether AI crawlers can discover and cite the important pages.

## Guides

- [Generative Engine Optimization: A Practical Guide to GEO](https://geoready.dev/guides/generative-engine-optimization/): Learn what Generative Engine Optimization is, how GEO differs from SEO, and how to make your site crawlable, understandable and citable by AI search engines.
- [What Is llms.txt? A Practical Guide for AI Search Visibility](https://geoready.dev/guides/what-is-llms-txt/): llms.txt is a Markdown file at your domain root that orients AI systems to your key pages.
- [GEO vs SEO: what changes when AI engines become the interface](https://geoready.dev/guides/geo-vs-seo/): SEO and GEO share technical foundations but optimize for different goals.
- [How to appear in ChatGPT and Perplexity: a practical guide for 2026](https://geoready.dev/guides/appear-in-chatgpt-perplexity/): Learn how to make your website appear as a source in ChatGPT, Perplexity, and other AI answer engines.
- [How to Improve AI Visibility](https://geoready.dev/guides/how-to-improve-ai-visibility/): Practical playbook to get cited by ChatGPT, Perplexity, Claude and Gemini: crawler access, llms.txt, JSON-LD schema, and entity signals.
- [llms.txt for WordPress and AI visibility: a practical guide](https://geoready.dev/guides/llms-txt-wordpress/): llms.txt helps AI tools understand your site.
- [AI visibility checklist: how to make your website easier to find, cite, and recommend](https://geoready.dev/guides/ai-visibility-checklist/): A practical checklist of the technical and content signals that decide whether AI answer engines can find, parse, and cite your site, organized by category.
- [How to tell if ChatGPT and Perplexity are citing your brand](https://geoready.dev/guides/ai-citations-check/): Three ways to know if AI engines cite your brand: a 10-minute manual check, a free automated check, and ongoing monitoring — plus what to do per verdict.
- [Entity-based authority: why five pages beat one strong page](https://geoready.dev/guides/entity-authority/): AI engines map entities and topic coverage, not keywords.
- [Multimodal GEO: making images and video citable](https://geoready.dev/guides/multimodal-geo/): Make images and video citable by Gemini and GPT-4o through alt text, captions, VideoObject schema, and transcripts.
- [What is Generative Engine Optimization (GEO)?](https://geoready.dev/guides/what-is-generative-engine-optimization/): Generative Engine Optimization makes your site citable by AI answer engines like ChatGPT and Perplexity.
- [GEO vs Traditional SEO: 7 Key Differences Explained](https://geoready.dev/guides/geo-vs-seo-7-key-differences/): Ranking vs citation, backlinks vs mentions, keywords vs entities: seven concrete ways Generative Engine Optimization differs from SEO.
- [Is AI Search Traffic Actually Growing? What the Data Shows](https://geoready.dev/guides/is-ai-search-traffic-growing/): ChatGPT Search, Perplexity, and Google AI Overviews are reshaping US search.
- [Do Backlinks Still Matter for AI Search Rankings?](https://geoready.dev/guides/do-backlinks-matter-for-ai-search/): Backlinks haven't disappeared as a trust signal, but AI answer engines weigh something else just as heavily: unlinked mentions across independent sources.
- [5 Signs Your Website Isn't Being Cited by AI (and How to Fix Each One)](https://geoready.dev/guides/signs-your-website-isnt-cited-by-ai/): Zero AI referrals, invisible in 'best X' answers, competitors cited instead.
- [Free Tools to Check Your AI Search Visibility in 2026](https://geoready.dev/guides/free-ai-search-visibility-tools-2026/): A practical roundup of free tools — crawler checkers, llms.txt generators, manual prompt tests — to check AI visibility.
- [How to Check If ChatGPT Can See Your Website (Free Test)](https://geoready.dev/guides/check-if-chatgpt-sees-your-website/): A 5-minute test to check if AI search engines can access and cite your site — plus exactly what to fix if they can't.
- [ChatGPT Search vs Google Search: What US Marketers Need to Know](https://geoready.dev/guides/chatgpt-search-vs-google-search/): ChatGPT Search synthesizes one cited answer; Google shows blue links plus an AI Overview.
- [How Long Does It Take to Get Cited by ChatGPT After Publishing?](https://geoready.dev/guides/how-long-to-get-cited-by-chatgpt/): There's no fixed timeline, but domain authority, crawl frequency, and structured data all shift it dramatically.
- [How Perplexity Chooses Sources: What We Know So Far](https://geoready.dev/guides/how-perplexity-chooses-sources/): Perplexity cites multiple sources per answer, but not randomly.
- [How Google's AI Overviews Actually Cite Sources (Technical Breakdown)](https://geoready.dev/guides/how-google-ai-overviews-cite-sources/): The citation carousel, multi-source attribution, and why there's no exported ranking behind an AI Overview.
- [Google AI Overviews vs. Featured Snippets: What Changed in 2026](https://geoready.dev/guides/ai-overviews-vs-featured-snippets/): Featured Snippets picked one page as the single winner.
- [AI Overviews and E-E-A-T: Does Author Authority Still Matter](https://geore