How to Run a Quick GEO Visibility Snapshot

Use the command /geo quick <url> to generate a 60-second GEO visibility snapshot that analyzes AI-search readiness and updates your prospect records instantly.

The zubair-trabzada/geo-seo-claude repository provides automated tools for Generative Engine Optimization (GEO) analysis. A GEO visibility snapshot offers the fastest way to assess a website's AI-search visibility without waiting for a full audit. This command performs inline analysis directly in your terminal, delivering immediate metrics and updating internal tracking data.

The /geo quick Command Syntax

According to the primary skill definition in geo/SKILL.md (line 38), the quick snapshot command follows a simple structure:

/geo quick <url>

The repository documentation in README.md (line 98) confirms this as the primary shortcut for rapid analysis. As detailed in docs/commands-reference.md (line 14), this command executes a 60-second inline scan that evaluates AI citation readiness and visibility scores without writing separate output files to disk.

Executing a Quick GEO Visibility Snapshot

To run an immediate health check on any website, replace <url> with your target domain:

/geo quick https://example.com

The terminal displays real-time progress and results:

▶ Running quick GEO snapshot for https://example.com …
✔ Visibility score: 78/100
✔ AI citation readiness: 85/100
✔ Updated prospect record: ~/.geo-prospects/prospects.json

The command automatically updates your local prospect database at ~/.geo-prospects/prospects.json while displaying the visibility score and AI citation readiness metrics in the console. No additional output files are created during this process.

What the Snapshot Measures

The quick analysis evaluates three core components:

• Visibility Score: Quantifies current AI-search presence on a 0-100 scale
• AI Citation Readiness: Assesses how likely content is to be cited by AI models
• Prospect Status: Updates the internal tracking record for the analyzed domain

This 60-second window provides sufficient data to determine if a site warrants deeper investigation through the full audit pipeline.

Integration with Full Workflows

While the quick snapshot runs independently, you can chain it with other /geo subcommands for comprehensive workflows. The command serves as an instant health check before committing resources to a complete GEO audit.

Use this snapshot when:

• Screening multiple prospects rapidly
• Monitoring existing client sites between full audits
• Validating recent SEO changes impact on AI visibility

Summary

• The /geo quick <url> command generates a 60-second GEO visibility snapshot
• Source definitions reside in geo/SKILL.md (line 38), README.md (line 98), and docs/commands-reference.md (line 14)
• Analysis updates ~/.geo-prospects/prospects.json without creating separate output files
• Results display visibility score and AI citation readiness immediately in the terminal
• Designed for rapid prospect screening before full audits

Frequently Asked Questions

What is the exact command syntax for a GEO visibility snapshot?

Use /geo quick <url> where <url> is the target website. This syntax is defined in geo/SKILL.md at line 38 and recognized as the primary shortcut for rapid analysis according to the repository's command reference.

Where is the quick command documented in the source code?

The command appears in three key locations: the primary skill definition in geo/SKILL.md (line 38), the top-level overview in README.md (line 98), and the detailed reference table in docs/commands-reference.md (line 14).

Does the quick snapshot save files to disk?

No. The quick snapshot performs inline analysis only, displaying results in the terminal. However, it updates the internal prospect record at ~/.geo-prospects/prospects.json to track the site's status for future reference.

Can I combine the quick snapshot with other GEO commands?

Yes. While designed for standalone rapid assessment, you can chain the quick snapshot with other /geo subcommands. Use it as an initial filter before running comprehensive audits that generate detailed output files.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}