GEO & AEO services · waitlist only

GEO and AEO services, run on evidence

The console is available today. Done-with-you engagements are not open yet; the waitlist only collects your domain and what you want fixed. The work itself is the same loop as software: audit what AI crawlers can fetch, baseline the AI Overview citations that matter, fix the machine-readable layer, then measure referrals.

What is available today

Four capabilities ship in the console now. None of them requires a call, a quote or a waitlist spot.

  • AEO check

    Test robots.txt, llms.txt, content signals, bot identity and agent discovery against the public crawler catalog — free, no account.

    Run the free AEO check →
  • AI Overview sampling

    Track whether Google shows an AI Overview for your queries, whether it cites your domain, and keep the cited URL as evidence.

    Open the AI Overview tracker →
  • AI traffic

    Separate AI referral visits from AI Overview clicks and read them per landing page, next to sessions and crawler behaviour.

    Read AI traffic analytics →
  • Reporting

    Put search, AI visibility, index status and audit findings into one client-ready dashboard with a frozen snapshot.

    See the SEO reporting dashboard →

The loop the console covers

Four steps, each with a checkable output. Every claim in a report traces back to a check, a sample or a referral record — not to a slide.

GEO, AEO and SEO are one loop

The labels change with the vendor, not the work. A page still has to be crawlable and useful; the difference is where the answer appears and how you prove it.

SEO

Earn a position in the classic result list. Measured with Search Console clicks, impressions and average position.

AEO

Make a page answerable: reachable, parsable, structured and trustworthy enough for an answer engine to cite. Measured with access checks and citation samples.

GEO

The same access and citation work across generative engines and their crawlers. The market uses GEO and AEO almost interchangeably; this console treats them as one loop.

Done-with-you engagements are in design

We are not taking engagements yet. When the first slots open, the model is fixed-scope: a short intake, a written quote, then the work below. No open-ended retainer, and no work or payment before the scope is agreed.

  1. Step 1

    Scope and fixed quote

    A short intake and a scoping call. The quote states the sites, pages, files and turnaround; no work starts and no payment is taken before it is signed.

  2. Step 2

    Baseline

    A free AEO scan, Search Console connection and the first AI Overview sample. No fixes before the starting point is recorded.

  3. Step 3

    Access fixes

    Work through the failing checks: robots rules, llms.txt, content signals, bot identity and agent discovery. Nothing is called fixed until the checker passes.

  4. Step 4

    Content surface

    Declare the pages worth citing, make answers extractable, and add the discovery files agents look for. Editorial work stays with your team.

  5. Step 5

    Monthly review

    Citation presence, citation rate, AI referrals and crawler behaviour, with last month's priorities re-ranked from the evidence.

Join the waitlist

Send the domain and what you want fixed. The waitlist creates no account and no charge; we use the email only to tell you when scope and pricing are published.

Email the waitlistsupport@visdenda.com

What we will not promise

The boundary is part of the product, and it will be part of any engagement. These are not gaps that a later proposal quietly fills.

  • No guaranteed citations or rankings. A sample says present or absent; it does not forecast what a fix will earn.
  • No link buying, directory spam or paid placements disguised as optimisation.
  • No ChatGPT, Claude or Perplexity rank tracking. The console measures Google AI Overviews, AI referrals and crawler behaviour.
  • No mass AI content. An engagement would fix the access and structure layer; what you publish stays your decision.

Frequently asked questions

What is generative engine optimization?

GEO is the practice of making a site readable and citable by generative AI answers: crawl access, machine-readable declarations, extractable structure and evidence. It overlaps with AEO; the difference is mostly which engine you name.

What is the difference between GEO and AEO?

AEO usually refers to answer engines — AI Overviews and direct answers. GEO usually refers to generative engines more broadly. The work is one loop: be fetchable, be parsable, be cited, then measure what changed.

Can I buy a done-with-you engagement today?

Not yet. The console is available today with a free tier; the done-with-you engagement is in design and the waitlist is open. Scope and pricing will be published before the first booking is taken.

Will this be an agency retainer?

No. The plan is a fixed-scope audit with a fixed price, then an optional implementation sprint — not an open-ended monthly retainer. Nothing is sold before the scope is written down.

What will the service cost?

Pricing is not published yet. The intent is a fixed price for a bounded audit, with implementation quoted separately after scope is confirmed. Waitlist members see the terms first.

Do you guarantee AI citations?

No. Citation depends on the engine, the query and the sources it chooses. The product, and any future engagement, promises a measured baseline and checks that pass — not a citation.

Can you work with our agency or in-house team?

The console supports multiple sites and white-label client delivery today. A done-with-you engagement, when it opens, would be scoped around your team rather than replacing it.

What happens when I join the waitlist?

You send one email with the domain and what you want fixed. We use it only to contact you about the service, and the waitlist creates no account and no charge.

The product is available

See what AI crawlers can fetch today

The waitlist is for done-with-you work; the console needs no call.