GEO AUDIT · BRAND-ONLY

Obot.

A look at how Obot is described, positioned, and quoted inside Google's AI Overviews, the AI answer box at the top of search results, and where the brand shows up versus goes missing.

Siteobot.ai

Where we lookedGoogle AI Overviews, US

Questions tested40 brand, category, and competitor queries

PreparedJune 18, 2026 · by AUQ

AI Visibility Score

out of 100. Critical band. Effectively invisible in Google AI Overviews for all commercial and category queries.

Verified AI Overview citations

Obot's brand is cited in 2 of the 22 AI-answer queries we tested.

AI answer trigger rate

55%

Google's AI answer box fires on 22 of 40 tracked queries.

Citation rate when AI answers

Share of AI-answer queries where the brand is actually quoted.

EXECUTIVE SUMMARY

Obot scores 11 of 100 for AI Overview visibility. The work is closing the citation and identity gaps.

Effectively invisible in Google AI Overviews for all commercial and category queries.

AI answers fire on 55% of tracked queries, yet Obot is quoted in only 9% of them. When it does appear, it sits Position data unavailable; homepage appears in only 1 of 20 cited pages.

AI Visibility Score

Critical band

BarelyLowCompetitiveDominant

What's in the score

How often AI answers appear15 / 100
Your pages being quoted5 / 100
How AI describes the brand15 / 100
Inclusion in category answers10 / 100
Quality of placement when cited10 / 100

THREE FINDINGS THAT MATTER

The brand is missing from most of AI-answer queries

Obot ranks first in AIO for its own brand name but the response is heavy with disambiguation prompts competing with TV and healthcare homonyms. No AIO triggers exist for core category queries like 'mcp security', 'ai agent governance', or 'enterprise mcp hosting'. Triggered queries are misaligned with business positioning, pulling from blog content about cloud storage, RAG, and prompt engineering.

AI misreads the category

AIO treats Obot as a generic open-source gateway rather than an enterprise AI governance platform. Homonym competition (TV personality, healthcare acronym) forces disambiguation, which dilutes the brand positioning. AIO does not reliably place Obot in any category-level queries related to enterprise AI security or MCP hosting.

TOP THREE MOVES

Publish authoritative entity-rich content on MCP gateway architecture and security patterns

Impact High · effort High · 30-45 days

Build a comprehensive MCP security and access control guide targeting enterprise IT and security teams

Impact High · effort Medium · 21-30 days

Create case studies and use-case pages showing Obot in enterprise AI agent governance scenarios

Impact High · effort Medium · 30-45 days

CONTENT AND ENTITY COVERAGE

The topics that matter to the brand, and where it shows up in AI answers today.

Topic	Presence in AI answers	Buyer intent
MCP gateway architecture	Partial	brand query only, disambiguation-heavy
MCP server security and access control	Invisible	problem-aware
Enterprise AI agent governance	Invisible	solution-aware
Skills registry and discovery	Invisible	solution-aware
MCP audit logging and compliance	Invisible	solution-aware
AI agent policy management	Invisible	solution-aware
MCP hosting and proxying	Invisible	solution-aware
Identity provider integration for AI systems	Invisible	solution-aware
MCP vs A2A protocol	Invisible	alternatives
Agentic AI security	Invisible	problem-aware

Buyer-journey coverage

Problem Aware. Absent. No AIO coverage of problem-discovery queries like 'how to secure MCP servers', 'AI agent compliance', or 'MCP access control'.

Solution Aware. Near-absent. Only brand-name AIO response exists, heavily disambiguation-focused. Zero AIO presence on category queries seeking solutions.

Alternatives. Absent. Obot does not surface when users search for 'MCP gateway alternatives' or competitive comparisons. AIO does not establish Obot as a market category contender.

IDENTITY IN AI OVERVIEWS

How the brand describes itself, and how Google's AI describes it.

What the brand says about itself

Open-source MCP gateway for enterprise AI agent governance

Obot is an open-source MCP gateway that manages MCP servers, Skills, access policies, audit, and integrations for AI agents.obot.ai, 2026

Differentiators it leads with: Skills registry and discovery, Fine-grained access control and policy management, Audit logging and compliance capabilities, GitOps-based configuration, Multi-tenant MCP hosting, Identity provider integration (Okta, Entra, Google, GitHub).

What Google's AI says

Functional open-source MCP gateway tool without enterprise or governance positioning

Open-source Model Context Protocol (MCP) gateway used by organizations to secure, host, and manage AI agents and chatbots

Tool for connecting AI systems to business tools

The core gap

Words AI uses for the brand

Correctly identifies Obot as an MCP gatewayMentions open-source status and security positioningDescribes core use case of managing AI agents and chatbots

The brand's own pillars that AI omits

No mention of Skills registry or discovery capabilitiesMissing enterprise governance and policy management framingNo coverage of audit logging or compliance featuresGitOps configuration approach not highlightedIdentity provider integration ecosystem omittedMulti-tenant hosting capability absent from AIO descriptions

AI OVERVIEW PERFORMANCE

Where the brand shows up in Google's AI, and the high-value queries it is missing.

Tracked keywords

Brand, category, and comparison queries analyzed.

AI answers fired

55% of tracked queries trigger an AI Overview.

Times brand cited

9% citation rate when AI answers.

Total brand mentions

Across all observed AI responses.

HIGH-VALUE QUERIES WHERE THE BRAND RANKS BUT IS NOT QUOTED

Query	Volume	Organic rank	What happens
mcp security	<UNKNOWN>	#Not in AIO	Core category query with zero AIO presence
mcp architecture	<UNKNOWN>	#Not in AIO	Enterprise IT query with zero AIO presence
mcp registry	<UNKNOWN>	#Not in AIO	Skills discovery query aligned with key differentiator
ai agent governance	<UNKNOWN>	#Not in AIO	Enterprise governance and compliance query
enterprise ai security	<UNKNOWN>	#Not in AIO	Decision-maker query with zero Obot presence

Case Studies

This playbook has already worked. Here's the proof.

Executed by AUQ for B2B SaaS teams with the same gaps this audit found.

1,000+ Fraud.net AI citations earned in 6 months through GEO prompt research and content automation. Read the case study → +173% Microblink Organic traffic growth from technical SEO, content automation, and GEO-focused linkbuilding. Read the case study → +30,000 AKOOL Visits in 6 months via technical optimizations and content strategy we executed end-to-end. Read the case study → +200% DeepInfra Technical blog traffic growth from a blog redesign, author training, and SaaS linkbuilding. Read the case study →

Get results like these for Obot → See all case studies

WHERE GOOGLE'S AI GETS ITS ANSWERS

The sources Google's AI cites in this category, and what it tells you about earning citations.

Domain AI cites	Pages	Context
porchlighthealth.com		Healthcare OBOT (Office-Based Opioid Treatment) homonym
abtcounseling.com		Healthcare OBOT treatment services
cedarrecovery.com		Healthcare OBOT treatment services
en.wikipedia.org		General disambiguation for 'Obot' term
www.netflix.com		TV show homonym (Married at First Sight cast member)
www.instagram.com		TV cast member social media
www.reddit.com		TV show fan discussion
aspina-robotics.com		Unrelated robotics content
carf.org		Healthcare accreditation body for OBOT treatment

Reading

Obot AI's own domain captures only 1 of 20 cited pages in AIO results associated with the 'obot' keyword cluster. The brand is losing citation share almost entirely to homonym content dominated by healthcare treatment providers (55%), TV entertainment (30%), and unrelated robotics (15%). This represents a severe homonym penalty in which the brand term itself triggers disambiguation rather than brand authority.

AI-REVEALED PEERS

The competitive set drawn by Google's AI itself. Observed, not chosen.

True category peers (other MCP gateway solutions, enterprise AI agent orchestration platforms) have not been identified in AIO results. The organic traffic competition (Rancher, Nextcloud) indicates misalignment between Obot's marketing positioning and the content attracting actual visitors.

Peer	How AI frames it
Rancher Desktop	Appears in container orchestration and docker comparison queries where Obot content ranks organically
Nextcloud	Appears in self-hosted cloud storage queries where Obot blog content ranks organically
OwnCloud	Appears in self-hosted cloud storage queries where Obot blog content ranks organically

Key observation

AIO does not surface Obot in any category-level queries for MCP gateway, enterprise AI security, or AI agent management. The MCP gateway category is nascent in AIO, representing both low competition and low current engagement. This is a strategic opportunity for early-mover positioning if Obot can establish AIO presence before category consolidates.

90-DAY ROADMAP

Three sprints from first wins to compounding category presence.

Month 1 · Days 1 to 30

Audit all product documentation pages for entity density and MCP security terminology
Publish three authoritative how-to guides on MCP server security, access control policies, and audit logging
Create a comprehensive MCP gateway vs alternatives comparison guide targeting category awareness
Launch brand disambiguation meta tags and internal linking strategy to boost Obot AI in SERP visibility

Month 2 · Days 31 to 60

Develop 2-3 detailed case studies highlighting enterprise AI agent governance use cases
Build a Skills registry best practices guide with entity-rich examples and discovery patterns
Establish backlinks from authoritative AI governance and enterprise security publications
Create identity provider integration guides (Okta, Entra, Google, GitHub) as standalone, indexable resources

Month 3 · Days 61 to 90

Publish a state-of-the-art MCP security whitepaper targeting C-suite and security decision-makers
Build interactive compliance and audit logging documentation with real-world scenario walkthroughs
Expand AIO trigger coverage through topic clustering around MCP hosting, policy management, and agentic AI security
Analyze AIO performance gains and refine content strategy for the next 90-day cycle