AEO Optima Docs
Features

GEO Audit

A comprehensive Generative Engine Optimization audit — crawl your site, score every page, find blockers, and produce a prioritized remediation plan.

Overview

The GEO Audit is a deep, site-wide audit designed to answer "is my website ready for generative AI engines?" It crawls your site, scores every reachable page, checks robots access for every major AI crawler, validates structured data, and produces a prioritized remediation plan you can work through over weeks or months.

Think of it as the big sibling of the Page Analyzer:

Page AnalyzerGEO Audit
One URL, on-demandWhole site, scheduled or on-demand
Fast (seconds)Slow (minutes to an hour for large sites)
Surface-level checkFull remediation plan with prioritized fixes
Free on all plansQuota-gated (see below)

Running an audit

  1. Open GEO Audit from the sidebar
  2. Enter the root URL of your site (e.g., https://yourdomain.com)
  3. Optionally set a crawl depth limit (default: 3 levels from the root)
  4. Click Start audit
  5. Progress updates live — you can leave the page and come back

When the audit finishes, you'll land on a results page with:

  • Overall site AEO score (0-100)
  • Per-page scores — a sortable table of every page crawled
  • Crawler access matrix — which AI crawlers can reach which pages
  • Structured data coverage — % of pages with valid schema, by type
  • Remediation plan — prioritized list of fixes with estimated impact

The remediation plan

This is the output most teams care about. Each item in the plan has:

  • Fix — what to change, written as an actionable task
  • Category — Structure / Schema / Content / Access / Performance
  • Pages affected — how many pages this fix would improve
  • Estimated impact — aggregate score lift if you apply this fix across all affected pages
  • Effort — Low / Medium / High

Fixes are sorted by aggregate_impact × affected_pages / effort, so the top of the list is always the highest-leverage change for the whole site.

Export the plan as PDF or CSV to share with your dev team.

Comparison mode

When you've run multiple audits over time, the Compare feature lets you pick two runs and see:

  • Which scores improved
  • Which fixes have been applied (based on remediation plan deltas)
  • Which new issues surfaced since the last audit
  • Whether overall visibility in AI engines correlates with audit improvements

Use this to prove to stakeholders that AEO work is moving the needle.

Plan gates and quotas

GEO Audit is quota-gated because it's a resource-intensive operation:

PlanAudits per month
Free0
Starter3
Professional20
Enterprise100

Running an audit uses one credit regardless of site size. If you need more audits, request a quota extension via Admin → Quota Requests or upgrade your plan.

What gets crawled

The audit respects your robots.txt and will not crawl blocked paths. It also:

  • Follows internal links up to the depth limit
  • Does not follow external links
  • Honors noindex directives (those pages are skipped from scoring)
  • Fetches each page with multiple user-agents to check AI crawler access

If you have a sitemap at /sitemap.xml, the audit will use it to discover pages even if they're not linked from the root.

Best practices

  • Run a baseline audit before starting AEO work. You can't prove improvement without a starting point.
  • Re-audit quarterly. Most AEO changes take 4-8 weeks to show up in actual visibility. Monthly audits often don't capture enough signal.
  • Work on one category at a time. Structural fixes first (schema, headings), then entity clarity, then content.
  • Use comparison mode for reports. Before/after audit snapshots are powerful evidence in executive reporting.
  • Check the crawler access matrix. If GPTBot or ClaudeBot is blocked on your site, fixing that single issue often outweighs all other work combined.

On this page