Agency script

Client GEO Diagnostic Email Script

A practical outreach script for SEO consultants, GEO consultants, and small growth agencies starting client conversations from a public-domain diagnostic.

Opening

Keep the opening specific, short, and diagnostic.

  • Name the public domain or page reviewed.
  • State that the check looked at public evidence, not private analytics.
  • Mention one to three observed gaps such as crawler access, citation assets, or trust signals.
  • Make the next step a review of first fixes, not a promised AI outcome.

Evidence Boundaries

Make the limitation note visible before a client forwards the message.

  • Use phrases such as observed evidence, provider evidence may be limited, and not platform-wide ranking proof.
  • Avoid claiming official AI platform scores or assured placement.
  • Separate crawl readiness from answer evidence.
  • Invite validation through a re-scan after fixes ship.

Next Step

Turn interest into a report or implementation conversation.

  • Offer a short call to review the first fixes.
  • Use the Starter Snapshot when the client needs a protected PDF, Markdown, or shareable handoff.
  • Map fixes to founder, SEO, content, and dev owners.
  • Propose a repair sprint only after the client sees the diagnostic limits.

Copyable sections

Paste into a brief, proposal, or ticket

These snippets are intentionally plain so consultants and teams can reuse them without importing private report data.

Copyable Prospect Email

Subject: Quick GEO diagnostic for your public site

Hi [Name], I ran a public-domain diagnostic for [domain] to check AI crawler access, machine readability, citation assets, structured evidence, trust signals, and first fixes.

The early signal: [one observed gap]. This is diagnostic evidence, not platform-wide ranking proof, and provider evidence may be limited.

If useful, I can send a short first-fixes summary or package a $99 Starter Snapshot when the scan has enough evidence for a founder-ready handoff.

Copyable Follow-Up

The next practical step is to fix the highest-impact public-page blocker, then re-scan the same target. That keeps evidence comparable and avoids turning a limited diagnostic into an unsupported AI visibility claim.

Evidence limits

Keep the claim boundary visible

Evidence limitation: this script supports an outreach diagnostic. It does not promise recommendation, ranking, citation, or visibility in any AI answer product.

Can I forward this script to clients?

Yes. It is written for client-safe outreach and avoids claims about assured AI outcomes, platform-owned scores, citation, recommendation, or ranking.

Should I include raw answer output?

No. Keep outreach short and public-safe. Use summarized evidence, limitation notes, and report links only when access rules allow them.

When should I mention the Starter Snapshot?

Mention it when the client wants a founder-ready or client-ready handoff with expanded evidence when available, competitor context, and prioritized fixes.

Turn the checklist into a diagnostic

Run a free public-domain check, then use pricing to decide whether the $99 Starter Snapshot is worth unlocking.