# Visibility Score

Understand and optimize your brand's mention rate across AI search engines.

## What is Visibility Score?

Visibility score measures how often AI platforms mention your brand when responding to tracked prompts. It's the primary metric for AI visibility, calculated as (queries with brand mentions ÷ total queries) × 100.

## How It's Calculated

**Formula**: (Queries with mentions ÷ Total queries) × 100

**Example**:

* Total queries run: 200
* Queries mentioning your brand: 90
* Visibility score: 45%

The calculation runs across all active prompts and all AI providers (ChatGPT, Claude, Perplexity, Gemini). If you track 50 prompts and each prompt queries 4 providers, you have 200 total queries. If your brand appears in 90 of those responses, your visibility is 45%.

## Score Ranges

**80-100% (Dominant)**: AI consistently recommends you. Market leader positioning. Maintain through continued citation building and content quality. Watch for complacency—competitors will target your position.

**60-80% (Strong)**: Top contender in your category. Strong brand awareness among AI platforms. Focus on improving position and sentiment to maximize impact from high visibility.

**40-60% (Good)**: Competitive positioning with significant presence. Opportunities to close gaps on specific prompts. Identify underperforming queries and build targeted citations.

**20-40% (Moderate)**: Emerging visibility but substantial work needed. Many prompts don't mention you. Prioritize citation building on high-authority domains and expand content coverage.

**0-20% (Low)**: Critical visibility gap requiring immediate strategy overhaul. AI platforms either don't know about you or don't find you relevant. Start with fundamental brand building and basic citations.

## Improving Visibility

**Citation Building**: Get featured on domains AI trusts—TechCrunch, Forbes, G2, Reddit, Product Hunt. One high-authority citation can boost visibility across dozens of prompts. Focus on editorial (credibility), UGC (social proof), and corporate (control).

**Content Optimization**: Create comprehensive content answering common user queries. Structure with clear brand positioning, include specific use cases, and provide factual information AI can cite. Update stale content regularly.

**Prompt Strategy**: Add prompts where competitors dominate but you're absent. Test variations of high-performing prompts. Balance broad category queries with niche use-case queries. Deactivate persistently low-performing prompts.

**Provider-Specific Optimization**: If one provider mentions you significantly less (e.g., ChatGPT 60%, Claude 20%), build citations on sources that provider prefers. Study their response patterns and create aligned content.

## Tracking Trends

**Weekly**: Monitor for 5%+ changes in either direction. Spot emerging patterns early before they become significant.

**Monthly**: Analyze visibility by prompt category. Identify which prompt types perform best and double down. Review competitor movements.

**Quarterly**: Measure ROI from visibility improvements. Connect visibility gains to traffic, conversions, and revenue. Adjust annual strategy.

**Healthy Growth**: 5-10% increase per month during active optimization. 2-5% during maintenance phase. Plateaus normal after 6-12 months—indicates need for new strategies.

## Common Issues

**Visibility Dropping**: Check deactivated prompts (reduces total queries), lost citations (domains stopped mentioning you), new underperforming prompts (pull down average), or competitor improvements (displaced you).

**Stuck at Low Score**: Likely insufficient citations. AI platforms need authoritative sources to reference. Build presence on 10+ high-value domains before expecting significant visibility.

**High Variability**: Normal for new projects (<30 days) or small prompt counts (<20). Add more prompts to stabilize. Scores become reliable after 50+ total queries.

**Provider Imbalance**: One provider dominates (>70% of visibility). Diversify citation sources to improve across all providers. Different AI platforms trust different domains.

## Benchmarking

Compare your visibility score against competitors to understand relative performance. If competitor has 75% and you have 45%, that's a 30-point gap representing significant opportunity. Focus on prompts where gap is smallest (easier to close) or where you're completely absent (high impact potential).

Visibility alone doesn't guarantee success—pair with position and sentiment analysis. A brand with 50% visibility, 1.5 avg position, and +0.7 sentiment outperforms one with 70% visibility, 4.0 position, and +0.2 sentiment.

## FAQ

**What's a good visibility score?** Depends on market maturity and competition. 50%+ is strong for most B2B SaaS. 70%+ for niche markets. 30%+ acceptable for highly competitive categories.

**How fast can I improve?** Realistic: 5-10% per month with focused effort. Aggressive: 15-25% per quarter with major initiatives (PR, content, citations). Plateaus expected after 6-12 months.

**Does visibility directly correlate to traffic?** Not always. High visibility with poor position or negative sentiment won't drive clicks. Optimize all metrics together.

## Next Steps

[Understanding Metrics](/metrics/understanding-metrics.md) | [Position Guide](https://github.com/guimsh/tweet-genius-ai-assist/blob/main/docs/metrics/position.md) | [Sentiment Analysis](https://github.com/guimsh/tweet-genius-ai-assist/blob/main/docs/metrics/sentiment.md) | [Dashboard Overview](/features/dashboard-overview.md)

## Support

📧 <hello@geonimo.com> | 📅 [Book Demo](https://cal.com/team/geonimo)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.geonimo.com/metrics/visibility-score.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.