Skip to main content

GEO Get Started

This guide is for GEO, AEO, and AIO

This Quick Start covers getting found by AI assistants like ChatGPT, Gemini, and Perplexity, GEO, AEO, and AIO. If you're looking to deploy the on-site AI Search and Digital Assistant instead, see Quick Start.

This walks through the GEO journey a partner actually runs: from prospecting a client who hasn't committed to anything, through sub-organization setup, ingestion, the first full report run, and the two optional steps that turn assumed demand into real, measured demand.

Before You Have a Client: Prospecting​

Think of this as step zero. Before a sub-organization exists, before a client has agreed to anything, run Prospect Snapshot: a branded, partner-only teaser PDF built entirely from a prospect's public website. It's one of the cheapest reports to generate and it's what starts the conversation, not a deliverable for an existing client. See The Low-Friction Go-to-Market Playbook for the full pitch this snapshot feeds into.

Once that prospect shows real interest, the steps below take over.

Once a Client Shows Interest​

1. Create a Sub-Organization​

  • Why This Matters: Keeps this client's data, reports, Beacon activity, and billing fully isolated from your own partner account and every other client you run GEO for.
  • Detailed Steps: From your partner account, go to Organizations → Create, enter the client's Name and Domain, and save. Click Use to switch into that sub-organization; everything from here forward happens inside that context.
  • Outcome: A clean, isolated workspace scoped to this one client.

Complete guide: Organization

2. "Add New Agent" → Create Agent​

  • Why This Matters: The Agent is the container every GEO report runs against, ingestion, system prompts, and (eventually) the on-site assistant all live here.
  • Detailed Steps: From inside the sub-organization, go to Agents, click Add New Agent, and select Create Agent. Enter the client's Organization name and URL of Organization accurately, the GEO reports use these values throughout.
  • Outcome: An agent record exists, ready for ingestion.

Complete guide: Agent Creation

3. Check "Automate Full Agent Creation"​

  • Why This Matters: This single checkbox kicks off everything GEO needs: it ingests the website, extracts the brand, and writes the system prompt automatically. It's also what gives Keyword Visibility something to query, the agent this creates is the same one Keyword Visibility tests against, even before anything is visible on the client's actual site.
  • Detailed Steps: On the Create Agent form, check Automate full agent creation before saving. It's recommended for every client.
  • Outcome: Ingestion starts automatically in the background.

4. Confirm Ingestion Is Actually Happening​

  • Why This Matters: A job that says "started" isn't the same as pages actually landing. Every GEO report depends on real, ingested content, and some sites silently block the crawler.
  • Detailed Steps: Check Documents to confirm pages are arriving as expected. If ingestion looks blocked or empty (common on sites behind Cloudflare, Akamai, or another WAF), you have three options, in order of how much access you have to the client's site:
    1. Whitelist the ai12z crawler with the client's hosting/CDN provider. See Whitelisting the ai12z Crawler.
    2. Use a CMS connector if the client runs a supported platform (Kentico, Optimizely, Sitecore, WordPress, and others), connectors sync content directly instead of crawling. See Introduction to Connectors.
    3. Easiest fix: run the ai12z Local Crawler, a small application you run on your own machine (built on the open-source Crawlee framework) that crawls the site locally and uploads the result directly, bypassing the block entirely. See Local Crawler.
  • Outcome: Wait until ingestion fully completes before moving on, every GEO report and the agent itself need the full content indexed first.

5. Run All Reports from the GEO Suite Dashboard​

  • Why This Matters: This is the fastest way from a freshly ingested site to a full GEO baseline, one wizard instead of configuring and running every report by hand.
  • Detailed Steps: Go to AI Discoverability GEO/AEO → GEO Suite Dashboard (the first item in that section) and click Run All Reports. Go through the five-step wizard, Company, Markets, Keywords & Citations, Competitors, Review & Run, then submit.
  • Outcome: Come back in about an hour. Every report, the Action Plan Dashboard, and the GEO Suite Dashboard are populated and ready to walk the client through. Remember: a new sub-organization can run this wizard once without a subscription.

Complete guide: Run All GEO Reports

6. Optional: Add Just the Beacon​

  • Why This Matters: If the client isn't ready for AI Search or a bot on their site yet, this is the smallest possible next ask, a single lightweight control that doesn't change anything a visitor sees or how the page looks.
  • Detailed Steps: Install the Beacon control on the client's site. It starts measuring who's actually arriving from AI engines like ChatGPT, closing the loop between a citation win and real traffic, without touching the page itself.
  • Outcome: AI Referral Analytics starts showing real sessions, with no other change to the site.

Complete guide: Beacon Control

7. Add the Full AI Search / Digital Assistant Control​

  • Why This Matters: This is the step that closes the real loop. What visitors actually type into the client's site is statistically the same thing they'd ask an AI answer engine like ChatGPT, no more guessing. See Why Our Score Predicts Real Citation for why that connection matters.
  • Detailed Steps: Add the full ai12z control (Knowledge Box, Search, Form, or the chatbot itself) to the client's site. It carries the same beacon object automatically, so referral tracking continues without any extra setup.
  • Outcome: Q&A Insights and Q&A Analysis start showing real visitor demand instead of the AI-assumed demand Keyword Visibility and Citation Monitor have been working from until now.

Complete guide: Chatbot Integration

Last updated on