APAC Webinar: AI Is Accelerating the Customer Journey. Is Your Brand Keeping Up?

Exclusive research on how AI search is reshaping discovery, visibility, and the customer journey.

Originally presented on Tuesday, May 26, 2026 at 1:00 PM AEST, this on-demand session explores how AI search is transforming the way your brand is discovered, evaluated, and chosen.

AI is collapsing the distance between early discovery and decision-making. Product recommendations, solution comparisons, and brand citations are now appearing directly inside AI-generated answers, often before a customer ever reaches a traditional search results page.

In this on-demand session, BrightEdge shares exclusive research on how AI search is reshaping customer journeys across industries, where visibility is being won and lost, and what marketers need to do to stay present in the moments that influence decisions. You'll also see the latest BrightEdge innovations designed to help teams measure, monitor, and optimize for the new prompt universe.

What You'll Learn

  • How AI search is compressing the funnel and what this means for measurement, content strategy, and planning
  • What BrightEdge research reveals about AI-driven discovery across key industries
  • How leading marketing teams are monitoring their prompt universe and adapting to the new customer journey
  • How BrightEdge innovations can help teams measure and optimize for AI search visibility
  • The difference between AI Catalyst, AI HyperCube, and AI Agent Insights — and how they work together

Why Watch

  • Rated 3.75/5 for overall satisfaction by live attendees, with 62% rating it 4 or 5 stars.
  • Get a practical breakdown of how prompt intent, AEO strategy, and AI HyperCube work together to help your brand stay visible in AI-generated answers.
  • The most-valued part of the session was insights on prompt intent, followed by BrightEdge research on AI-driven discovery and understanding the AEO ownership gap.

Featured Speakers:

  

Watch On-Demand Webinar

* indicates required

 
 

Where AI Engines Agree on Brands. And Where They Don't.

BrightEdge AI Catalyst analysis across five AI search engines shows that the brands AI engines recommend converge tightly in some categories and diverge sharply in others. Where consumers transact, the engines agree. Where consumers research, the engines

BrightEdge AI Catalyst analysis across five AI search engines shows that the brands AI engines recommend converge tightly in some categories and diverge sharply in others. Where consumers transact, the engines agree. Where consumers research, the engines develop distinct preferences for which brands belong in the answer.

BrightEdge AI Catalyst analysis reveals that ChatGPT, Perplexity, Gemini, Google AI Mode, and Google AI Overviews recommend a strikingly similar set of brands at the aggregate level. Pairwise overlap in top-named brands across the dataset falls in a tight 36% to 55% band. But that aggregate average masks meaningful category-level variance. In retail, travel, and tech, brand agreement across all five engines runs between 88% and 97%. In healthcare and finance, it drops to 60% and 71%. The same engines that converge on the same retailers, hotels, and consumer electronics brands disagree substantially about which hospitals, financial institutions, and authoritative publishers to recommend.

This is the follow-up to our recent BrightEdge AI Catalyst research on cross-engine source and brand convergence. The original study found that AI engines pull from wildly different sources but recommend the same brands. That finding holds at the dataset level. This installment splits the same dataset by category to show where the agreement is real, where the divergence concentrates, and what each engine's editorial signature looks like inside the categories where the engines part ways.

Data Collected

 

Data PointDescription
Brand mention share by engineShare of each engine's total brand mentions directed to each named brand, across all analyzed prompts
Category-level brand overlapPairwise top-30 overlap in named brands across all five engines, calculated within each category
Brand category classificationEach named brand classified by industry vertical: retail, travel, tech, finance, healthcare, education, news and editorial
Same-brand cross-engine comparisonShare of mentions for individual brands tracked across all five engines to surface dramatic treatment differences
Engine concentration by categoryShare of voice held by leading brands within each category, by engine
Brand absence patternsBrands present in one engine's top 15 within a category but missing from another engine's top 100 within the same category

 

Data PointDescription
Pairwise brand overlap rangeHighest and lowest overlap percentages across all 10 engine pairs, by category
Engine editorial signaturePattern of brand types each engine favors within high-divergence categories: associations, publishers, institutional players, editorial media
Average brand rank by categoryPosition at which engines name brands within each category, indicating engine commitment to a shortlist versus broad list
Industry coverageAnalysis spans retail, travel, tech, finance, healthcare, education, and news and editorial

Key Finding

The aggregate brand convergence finding is real, but it is not evenly distributed across categories. When the same dataset is split by industry vertical, the spread of pairwise top-30 brand overlap looks very different from category to category. Retail shows 97% average pairwise brand agreement across all five engines. Travel shows 94%. Tech shows 88%. Finance drops to 71%. Healthcare drops to 60%, with a low-to-high range of 40% to 77% across engine pairs. The categories where consumers transact directly with brands (retail, travel, tech) draw from a smaller universe of well-established brands, and the engines pick from that same shared pool. The categories where consumers conduct deep informational research (healthcare, finance) have a much wider universe of credible brands, and each engine has developed its own preferences for which brands belong in the answer. The implication for brand strategy is that one playbook works across all five engines in transactional categories, while research-driven categories require engine-by-engine measurement and category-specific positioning.

Brand Agreement Sits at Different Points by Category

The pairwise top-30 brand overlap across all five engines varies materially by category. Where the buying decision is the dominant query intent, the engines converge. Where the research process is the dominant query intent, they diverge.

CategoryPairwise Brand Overlap (Avg)Range
Retail97%92% to 100%
Travel94%90% to 100%
Tech88%83% to 97%
Finance71%60% to 90%
Healthcare60%40% to 77%

In retail, every engine pulls from a small, stable universe of major retailers and consumer brands. Amazon, Walmart, Target, Best Buy, Home Depot, and a handful of category leaders dominate every engine's top 30, leaving little room for divergence. Travel behaves the same way: a tight cluster of online travel agencies, hotel groups, and airlines (Expedia, Booking, Marriott, Hilton, Delta, United) carries across all five engines. Tech sits one step behind at 88% because the pool of relevant tech brands is slightly larger and the engines start to differentiate on which platforms, tools, and services they elevate. Finance and healthcare are the two categories where the divergence becomes the story.

Same Brand. Same Study. Different Treatment.

Inside the high-divergence categories, the same brand often receives dramatically different treatment from one engine to another. The gap is not subtle. Several flagship brands show share-of-mention differences of 9x to 22x across engines.

Mayo Clinic. Mayo Clinic is the most universally recognized healthcare brand in the dataset. Gemini directs 13.1% of its healthcare brand mentions to Mayo Clinic. Google AI Overviews directs only 1.5%. The same flagship authority commands roughly 9x more share on Gemini than on AI Overviews.

Cleveland Clinic. Cleveland Clinic captures 6.5% of Perplexity's healthcare brand mentions. On ChatGPT, that figure drops to 0.3%, a roughly 22x gap. Two engines querying the same healthcare prompts treat the same major medical institution very differently.

Goldman Sachs. Goldman Sachs ranks in the top 10 most-mentioned finance brands on Google AI Mode. On ChatGPT, Gemini, and Perplexity, Goldman Sachs does not crack the top 100. Institutional banking presence on AI Mode is materially different from institutional banking presence on the other engines.

Nasdaq. Nasdaq holds 4.5% share of finance brand mentions on ChatGPT. On AI Mode, that figure drops to 0.4%, an 11x gap. Engines that draw from exchange and regulatory sources elevate Nasdaq strongly. Engines that draw from institutional banking sources do not.

Bloomberg. Bloomberg captures 2.9% of finance brand mentions on Gemini. On AI Mode, Bloomberg has zero presence in the top 100. Editorial finance brands are heavily represented on Gemini and largely absent from AI Mode.

These are not measurement noise. They are systematic patterns that reflect the editorial signature each engine has developed inside high-divergence categories.

Each Engine Has a Personality Inside High-Divergence Categories

Inside the categories where the engines part ways, each engine favors a recognizable type of brand. The patterns hold up across the dataset and offer a usable mental model for predicting how each engine will treat brands in any high-divergence category.

ChatGPT favors specialty associations and exchanges. ChatGPT's healthcare top brands include the American Academy of Orthopaedic Surgeons (AAOS), the American Urological Association (AUA), the American College of Gastroenterology (GI), the American Academy of Pediatrics (AAP), and the American Academy of Family Physicians (AAFP). Its finance top brands lead with Nasdaq, the SEC, and major brokerages (Fidelity, Schwab, Vanguard). The pattern is consistent: ChatGPT elevates professional associations, regulatory bodies, and exchanges that carry institutional weight within their specific subcategory.

Perplexity leans on consumer health publishers and trading research tools. Perplexity is the only engine where consumer health publishers (Healthline, WebMD, Medical News Today) appear prominently in healthcare mentions. In finance, Perplexity uniquely elevates trading research tools like Stock Analysis, http://Investing.com , and Marketbeat alongside the standard exchanges. The pattern reflects Perplexity's broader posture as a research-oriented engine that surfaces both institutional and consumer-facing reference sources.

Gemini hyper-concentrates on flagship authorities and editorial finance. Gemini directs 13.1% of healthcare brand mentions to Mayo Clinic and 9.5% to NIH, two brands that account for nearly a quarter of all Gemini healthcare mentions. In finance, Gemini elevates Bloomberg, Wall Street Journal, Reuters, Forbes, and Investopedia, the editorial finance media set. The pattern is consistent: Gemini behaves like a concentrated authority recommender that leans heavily on a small set of flagship brands rather than producing broad lists.

Google AI Mode quietly favors institutional banks. AI Mode's finance top brands lead with JPMorgan, Wells Fargo, UBS, Goldman Sachs, Barclays, and Citigroup. The institutional banking presence is unique to AI Mode and is not mirrored on any other engine in the dataset. This pattern is not visible in aggregate share-of-voice reports, but it is clearly visible when finance brand mentions are isolated by engine.

Google AI Overviews spreads thin across providers. AI Overviews has the lowest brand concentration in high-divergence categories. No single brand commands more than 1.5% of healthcare mentions, and no finance brand exceeds 0.8%. The engine's top-15 lists in these categories include a wider variety of brands at lower share-of-voice levels, consistent with AIO's broader UGC-first sourcing posture.

What Marketers Need to Know

Brand agreement is real, but it is category-dependent. The aggregate finding that AI engines mostly agree on brands holds up. But the agreement is not evenly distributed. Retail and travel converge at 94% to 97% pairwise overlap. Healthcare and finance drop to 60% and 71%. Where your category sits on that spectrum determines whether one strategy works across all five engines or whether you need to look engine by engine.

Where consumers buy, engines converge. Where consumers research, engines diverge. Transactional categories pull from a small pool of well-established brands, and the engines pick from the same pool. Research-heavy categories have a much wider universe of credible brands, and each engine has developed its own preferences inside that universe. The strategic implication is straightforward: a single AI search strategy is portable across engines if you operate in retail, travel, or tech. If you operate in healthcare, finance, or other research-driven categories, you need to think harder about which engine is treating your brand how.

Each engine has a recognizable personality inside high-divergence categories. ChatGPT favors specialty associations and exchanges. Perplexity favors consumer health publishers and trading research tools. Gemini favors flagship authorities and editorial finance media. AI Mode favors institutional banks. AI Overviews spreads thin across providers. Knowing the editorial signature of the engines that matter to your buyers is half the work of building visibility in a high-divergence category.

Audit by engine within your category, not just in aggregate. The aggregate share-of-voice number can hide a lot if you are operating in a high-divergence category. A flagship competitor "missing" from one engine but dominant on another is not a measurement error. It is that engine's editorial signature in your space, and it is actionable. Brand teams operating in healthcare, finance, or any research-driven category should be measuring share of voice engine by engine and treating the divergence as a strategic input rather than a reporting inconvenience.

Match your authority strategy to the engines that matter. If your buyers rely heavily on Gemini, your strategy should prioritize being covered by the flagship authorities and editorial media that Gemini elevates. If your buyers use ChatGPT, your priority is presence in the specialty associations, regulatory bodies, and exchanges relevant to your subcategory. If your buyers use AI Mode in finance, institutional banking visibility is the lever that moves the needle. The three-layer source framework from the prior study still applies. The category-level engine personalities tell you where to put the emphasis.

A flagship competitor missing from one engine is signal, not noise. When a major brand in your category dominates one engine and is absent from another, that is meaningful information about how each engine has built its editorial signature. Mayo Clinic at 13.1% on Gemini and 1.5% on AIO is not random. Goldman Sachs in AI Mode's top 10 and absent from ChatGPT, Gemini, and Perplexity is not random. These patterns reflect each engine's source layer weighting and editorial posture. They are also the most actionable input for prioritizing PR, content, and authority-building investment.

Technical Methodology

ParameterDetail
Data SourceBrightEdge AI Catalyst
Engines AnalyzedChatGPT, Perplexity, Gemini, Google AI Mode, Google AI Overviews
Industries CoveredRetail, travel, tech, finance, healthcare, education, news and editorial
Brand CategorizationEach named brand classified into an industry vertical using a domain-level taxonomy
Overlap MethodologyPairwise top-30 brand mention lists compared across all 10 engine pairs within each category
Same-Brand ComparisonShare-of-mention values for individual brands tracked across all five engines to identify dramatic treatment differences
Engine Personality AnalysisTop-15 brand lists per engine per category analyzed for systematic patterns in brand type and editorial posture
Data CleaningCitation artifacts attributable to search engine result page disclaimers were removed from Google surfaces to avoid inflation

Key Takeaways

FindingDetail
Brand agreement is category-dependentAggregate pairwise overlap (36% to 55%) masks category-level variance from 60% in healthcare to 97% in retail
Transactional categories convergeRetail (97%), travel (94%), and tech (88%) show high pairwise brand agreement across all five engines
Research categories divergeHealthcare (60%) and finance (71%) show meaningfully lower agreement, with healthcare ranging from 40% to 77% across engine pairs
Same-brand treatment varies by 9x to 22xMayo Clinic (9x), Cleveland Clinic (22x), Nasdaq (11x), Goldman Sachs (top 10 vs absent), Bloomberg (2.9% vs zero)
ChatGPT favors specialty associations and exchangesAAOS, AUA, GI, AAP, Nasdaq, SEC, major brokerages
Perplexity favors consumer health publishers and trading researchHealthline, WebMD, Medical News Today, Stock Analysis, http://Investing.com , Marketbeat
Gemini concentrates on flagship authorities and editorial financeMayo Clinic, NIH, Bloomberg, WSJ, Reuters, Forbes, Investopedia
AI Mode favors institutional banksJPMorgan, Wells Fargo, UBS, Goldman Sachs, Barclays, Citigroup
AI Overviews spreads thin across providersLowest brand concentration of any engine in high-divergence categories
Audit by engine in research-driven categoriesAggregate share-of-voice hides engine-specific treatment that matters for strategy

 

Download the Full Report

Download the full AI Search Report — Where AI Engines Agree on Brands. And Where They Don't.

Click the button above to download the full report in PDF format.

Published on  May 07, 2026

The Google Analytics 'Blind Spot'

English, British
News Item Title
The Google Analytics 'Blind Spot'
News Item Author Name
Media Post
News Item Published Date
News Item Summary

MediaPost examined how AI agents are reshaping web traffic measurement and exposing gaps in traditional analytics platforms. Jim Yu was cited on the rapid growth of AI agent activity and how platforms like ChatGPT, Google Gemini, and Perplexity AI increasingly retrieve information without generating direct site visits. The article underscores how AI-driven discovery is redefining attribution, visibility, and performance measurement in search.

BrightEdge MCP

Connect AI Tools to BrightEdge Data

Overview

What is an MCP Server?

MCP stands for Model Context Protocol - an open standard that lets AI assistants (like Claude and ChatGPT) securely connect to external data sources and tools.

Before MCP, getting data into an AI workflow meant manual exports, spreadsheet uploads, or writing custom code. MCP removes that friction. Once a connection is established, you simply ask a question in plain language, and AI is leveraged to fetch the data, perform the analysis, and return an insight, all in a single step.

Key properties of a BrightEdge MCP connection:

  • Secure: Authentication uses OAuth 2.0.
  • Read-only: BrightEdge MCP tools retrieve data only. Nothing in your BrightEdge account is modified.
  • Real-time: Data is pulled live from your BrightEdge account at query time.

Why BrightEdge MCP?

BrightEdge has spent over a decade building the industry's most comprehensive SEO and AEO datasets. The MCP server puts that data directly inside your AI workflow, so you spend less time pulling reports and more time acting on insights.

BrightEdge data + LLM intelligence

The BrightEdge MCP combines proprietary data — DataCube X, AI HyperCube, Keyword Reporting, Share of Voice, Analytics Reporting, Google Search Console, AI Catalyst, Recommendations, and AI Agent Insights with the reasoning capabilities of a large language model. Questions that used to require opening multiple dashboards, running several exports, and combining results in a spreadsheet can now be answered with a single, well-structured prompt.

Faster time to action

The biggest cost in AEO and SEO workflows is not the analysis itself; it is the time between a question arising and an answer being ready to act on. BrightEdge MCP compresses that gap dramatically:

Without MCPWith BrightEdge MCP
Export keyword, prompt, and other data from BrightEdgeAsk a question in plain language
Export GSC data from Google, or analytics data from your web analytics platformMCP fetches from both sources simultaneously
Combine datasets in a spreadsheetLLM cross-references and synthesizes automatically
Interpret results and write a summaryReceive a ready-to-act insight
Hours per analysisSeconds/minutes per analysis

Connection Details

Use the following endpoints depending on your platform's transport requirements:

SettingValue
MCP Endpoint (HTTP)https://mcp2.brightedge.com/mcp
SSE Endpointhttps://mcp2-sse.brightedge.com/sse
Use the MCP Endpoint for platforms that support standard HTTP/MCP transport (ChatGPT, Claude, Copilot, Lovable). Use the SSE Endpoint for platforms that require Server-Sent Events transport (Manus, OpenClaw).

Who Can Access BrightEdge MCP?

All BrightEdge customers with a valid set of BrightEdge login credentials (including username and password) can connect to the MCP server. For any questions or concerns, please reach out to the BrightEdge team at .


Authentication

All platforms use OAuth 2.0 authentication. When prompted during setup, you will sign in with your BrightEdge account credentials. BrightEdge uses Auth0 as its identity provider — you will see a BrightEdge-branded login screen hosted on auth0.com.


Available Setup Guides

  • ChatGPT: OAuth setup via ChatGPT Settings → Plugins
  • Claude: Custom connector via Claude Settings → Connectors
  • Gemini Enterprise: Custom MCP server in Gemini Enterprise
  • Lovable: Custom connector via Lovable Settings → Connectors
  • Manus: Custom MCP via SSE transport + Bearer token
  • Microsoft Copilot: MCP tool in Copilot Studio with OAuth
  • n8n: MCP Client node with OAuth2 — HTTP Streamable transport
  • OpenClaw: Mcporter middleware + terminal configuration
  • Relevance AI: MCP tool added via agent configuration with OAuth
  • Slack: Pre-configured app, connect account via Slack desktop

ChatGPT

Platform 1 of 10

Connect BrightEdge MCP to ChatGPT on the web to query BrightEdge data directly within your ChatGPT conversations.

Option 1Use the pre-built OpenAI Plugin

BrightEdge's MCP server is available in OpenAI's Plugin repository. You can access it directly via Plugins, and enter your BrightEdge credentials to authenticate and start prompting. The Plugin available in OpenAI's Plugin marketplace has the MCP Endpoint: https://mcp.brightedge.com/marketplace/v2

While the BrightEdge Plugin is currently up to date, future updates require further review and OpenAI approval.
Option 2Set up a custom plugin

Alternatively, customers can set up a custom plugin for BrightEdge using the instructions below, and that would always reference the most up-to-date tools. Please note that to create a custom plugin, you need to have Developer mode turned on via Settings → Security and login → Developer mode.

Note: MCP connector support in ChatGPT requires a Pro or Plus account. The feature is currently in beta and is available via ChatGPT Settings → Apps.
Prerequisites
  • An active BrightEdge account
  • A ChatGPT Pro or Plus account
Connection Details
SettingValue
Server URL / MCP Endpointhttps://mcp2.brightedge.com/mcp
Setup Steps
1
Open ChatGPT Settings

Navigate to chatgpt.com and log in. Click your profile icon in the bottom-left corner and select Settings.

2
Navigate to Apps

In Settings, select the Apps section, then click Create app.

3
Enter the BrightEdge Connection Details

Fill in the following fields. Leave all other pre-populated fields as they are:

  • Server URL: https://mcp2.brightedge.com/mcp
  • OAuth Client ID

    Please reach out to your Customer Success Manager or the Support team to request the OAuth Client ID, which is required to complete the MCP server setup.
  • OAuth Client Secret

Leave the Resource with DNS URL field as pre-populated, then click Create.

Note: You may need to click into Advanced Auth settings to view all the required fields.

4
Authenticate with BrightEdge

A BrightEdge login screen will appear. Enter your BrightEdge account credentials and click Log In. Once authenticated, the connector will be added to your account.

5
Activate the Connector in Chat

Close the settings dialog. In the chat interface, click the + icon in the message input area, then select More. Select the BrightEdge connector you just created to activate it for the current conversation.

6
Start Prompting

With the connector active, you can now query BrightEdge data directly in ChatGPT.

For best results, mention BrightEdge explicitly in your prompt, e.g. 'Using BrightEdge, show me the top 10 keywords by traffic this month.'

Claude

Platform 2 of 10

Connect BrightEdge MCP to Claude on the web (claude.ai) or via the Claude desktop application. Claude uses OAuth authentication and provides per-tool permission controls once connected.

Prerequisites
  • An active BrightEdge account
  • A Claude account (any paid plan)
SettingValue
Remote MCP Server URL (Web)https://mcp2.brightedge.com/mcp
AuthenticationOAuth (Auth0)
Setup Steps
1
Open Settings

Launch Claude and click on your profile name in the bottom-left corner. Select Settings from the dropdown.

2
Navigate to Connectors

In the Settings menu, locate and click Connectors. You will see existing integrations (such as Google Drive and GitHub).

3
Add a Custom Connector

Click Add custom connector and fill in the following fields:

  • Name: BrightEdge MCP
  • Remote MCP Server URL: https://mcp2.brightedge.com/mcp
  • OAuth Client ID

    Please reach out to your Customer Success Manager or the Support team to request the OAuth Client ID, which is required to complete the MCP server setup.

Expand Advanced settings if the Client ID field is not immediately visible. Click Add to save the connector.

4
Authenticate with BrightEdge

The BrightEdge connector will now appear in your connectors list. Click Connect. Claude will redirect you to a BrightEdge OAuth/Auth0 login screen. Enter your BrightEdge email and password, then click Log In. Once authenticated, Claude will securely link the connector to your account.

5
Configure Tool Permissions

After connecting, Claude will display the list of tools exposed by the BrightEdge MCP server. For each tool you can set the permission to Allowed, Blocked, or Ask every time. For uninterrupted use, set Read-only tools to Allowed.

6
Start Prompting

The BrightEdge connector is now active. In any chat, ensure the BrightEdge connector is enabled (visible in the chat toolbar), then start prompting.

Gemini Enterprise

Platform 3 of 10

Connect BrightEdge MCP to Gemini Enterprise as a custom MCP data store, giving Gemini agents access to live BrightEdge data. Setup happens in two stages: an admin registers the connector once at the organization level in the Google Cloud console, then each user authorizes their own access from the Gemini Enterprise chat interface.

Note: Custom MCP server support in Gemini Enterprise is a newer capability and can behave inconsistently - connections may need to be retried, and results can vary between users on the same setup. See Troubleshooting below.
Prerequisites
  • An active BrightEdge account
  • Gemini Enterprise admin access, to register the connector as a data store
  • Discovery Engine Editor role (roles/discoveryengine.editor) on the relevant Google Cloud project
Connection Details
SettingValue
MCP Server URLhttps://mcp2.brightedge.com/mcp
AuthenticationOAuth 2.0 (Auth0)
Setup Steps
1
Register BrightEdge as a Data Store

In the Google Cloud console, go to Gemini Enterprise → Data Stores. Click Create data store, then search for and select Custom MCP Server.

2
Enter the BrightEdge Connection Details

Fill in the following fields:

  • MCP Server URL: https://mcp2.brightedge.com/mcp
  • Authorization URL
  • Token URL
  • OAuth Client ID
  • OAuth Client Secret
  • Scope: openid profile email
Contact your Customer Success Manager or the BrightEdge Support team at integrations@brightedge.com for the Authorization URL, Token URL, and OAuth credentials.
3
Add an MCP Server Description

In the MCP Server Description field, describe what BrightEdge MCP does and when the agent should use it — for example, "Provides SEO and AI visibility data, including keyword rankings, competitor gaps, and AI citation tracking, for the connected domain." Gemini relies heavily on this field to decide when to invoke the connector, so avoid vague descriptions. Optionally, use the MCP Agent Instructions field to tell the agent which tool to call for which type of question.

Click Continue, choose a location, name the data store (e.g. "BrightEdge MCP"), and click Create.

4
Enable Actions

Once the data store status changes to Active, open it and select the Actions tab. Click Reload custom actions to pull in BrightEdge's tool list, select the tools you want available (up to 100 at a time), then click Enable actions.

5
Connect the Data Store to a Gemini Enterprise App

Navigate to Apps, select the app you want to use (or create one), then go to Connected data sources. Click Add existing data stores, select the BrightEdge data store you just created, and click Connect.

6
Authorize the Connector (per user)

Each user needs to authorize the connection individually. Open the Gemini Enterprise chat, click the connector icon in the message input area, and locate BrightEdge in the list. If it shows Authorize, click it and sign in with your BrightEdge account credentials on the Auth0-hosted login screen. Once authorized, the connector will show a toggle in place of the Authorize button — make sure it's switched on.

To avoid confusing results, toggle off other connectors you're not using for this task (e.g. Google Search), especially while testing.

7
Start Prompting

Reference the connector by name rather than the term "MCP" — the agent reliably invokes tools when prompted with phrasing like "Using BrightEdge connector, find server info", but can fail to recognize "MCP" as a trigger. If the connector doesn't respond, try re-running the same prompt or starting a new chat.

Troubleshooting

Tool list looks incomplete: Asking for the full list of tools may return only a handful, seemingly at random. This appears to be an output-length limitation rather than a connection issue — ask for tools related to a specific task instead of requesting the full list.

Connector won't authenticate or respond: If Authorize doesn't redirect to a login screen, try the flow in an incognito window, or sign out and back into your Google session first. If a query times out or returns a server error, retry the same prompt, or start a new chat if retrying doesn't help.

Works for one user but not another on identical setup: This has been observed intermittently and doesn't appear tied to configuration. Retrying after a short wait has resolved it in past cases.

Lovable

Platform 4 of 10

Connect BrightEdge MCP to Lovable via its personal connector's settings. Lovable uses OAuth authentication and supports both HTTP and SSE endpoints.

Prerequisites
  • An active BrightEdge account
  • A Lovable account (lovable.dev)
SettingValue
Server URL (SSE)https://mcp2-sse.brightedge.com/sse
AuthenticationOAuth
Setup Steps
1
Log Into Lovable

Navigate to lovable.dev and sign in with your account credentials.

2
Open Settings

Click Settings in the navigation menu or from your profile dropdown.

3
Navigate to Connectors

In Settings, select Connectors. In the Personal connectors section, click Custom.

4
Enter the BrightEdge Connection Details

Fill in the connector form with the following values:

  • –  Server URL: https://mcp2-sse.brightedge.com/sse
  • –  Authentication: OAuth
  • –  OAuth Client ID
  • –  OAuth Client Secret

Click Add (or Connect) to proceed.

5
Authorize Access

A BrightEdge authorization screen will appear. Select your workspace and click Allow to grant Lovable access.

6
Confirm the Connection

Once connected, BrightEdge MCP will appear as "Enabled" in your Personal Connectors list. You can now use BrightEdge data in your Lovable projects and prompts.

If you need to disconnect or reconnect the BrightEdge connector, return to Settings → Connectors → Personal connectors and manage it from there.

Manus

Platform 5 of 10

Connect BrightEdge MCP to Manus using a direct SSE configuration. Manus supports custom MCP servers via its Connectors panel, with Bearer token authentication.

Prerequisites
  • An active BrightEdge account
  • A Manus account (web or desktop)
SettingValue
Server URL (SSE)https://mcp2-sse.brightedge.com/sse
Auth Header ValueBearer <your-brightedge-token>
Setup Steps
1
Open the Connect Apps Panel

In the Manus interface, locate the prompt input area. Click the Connect apps button (the second icon in the toolbar below the prompt input). This opens the connector options.

2
Open Add Connectors

A list of available connectors will appear. Scroll to the bottom and click + Add connectors. This opens the full Connectors dialog.

3
Navigate to the Custom MCP Tab

In the Connectors dialog, click the Custom MCP tab at the top. If no custom MCPs have been added yet, you will see a message saying 'No custom MCP added yet'.

4
Open Direct Configuration

Click the + Add custom MCP dropdown button and select Direct configuration from the options (the alternative is Import by JSON). This opens the MCP configuration form.

5
Enter the BrightEdge Configuration

Fill in the MCP configuration form with the following values:

  • Server Name: BrightEdge
  • Transport Type: SSE
  • Server URL: https://mcp2-sse.brightedge.com/sse

In the Custom headers section, click + Add custom header and enter:

  • Header name: Authorization
  • Header value: Bearer <your-brightedge-token>

The Icon and Note fields are optional.

Replace <your-brightedge-token> with your BrightEdge API token. Contact your BrightEdge team if you do not have a token.
6
Save the Configuration

Click Save or Try it out to test before saving. BrightEdge will appear in the Custom MCP tab, confirmed with a green checkmark.

7
Start Prompting

Close the connector dialog. Click Connect apps again — BrightEdge will now appear in the connector list and will be enabled by default. You can now include BrightEdge data in any Manus task or prompt.

Microsoft Copilot

Platform 6 of 10

Add BrightEdge MCP as a tool in Microsoft Copilot Studio to give your Copilot agents access to live BrightEdge data.

Prerequisites
  • An active BrightEdge account
  • Access to Microsoft Copilot Studio (copilotstudio.microsoft.com)
Connection Details
SettingValue
Server URLhttps://mcp2.brightedge.com/mcp
Setup Steps
1
Access Copilot Studio

Navigate to copilotstudio.microsoft.com and log in with your Microsoft credentials.

2
Create or Open an Agent

In the left panel, navigate to Agents and click New Agent (or open an existing agent). Provide a name, description, and select GPT-4o or your preferred model.

3
Add a New Tool

From within your agent, navigate to the Tools section and click Add Tool → Create New → Select MCP.

4
Enter the BrightEdge Connection Details

Fill in the following fields:

  • Server URL: https://mcp2.brightedge.com/mcp
  • OAuth Client ID
  • OAuth Client Secret

    Please reach out to your Customer Success Manager or the Support team at integrations@brightedge.com to request the OAuth Client ID and Client Secret, which are required to complete the MCP server setup.
  • Auth URL: https://mcp2.brightedge.com/authorize
  • Token & Refresh URL: https://mcp2.brightedge.com/token
  • Scope: openid profile email

Click Create. A Redirect URL will be generated.

Share the generated Redirect URL with the BrightEdge team to have it allowlisted before proceeding.
5
Connect the Tool to Your Agent

Return to your agent and add the BrightEdge tool from the Tools section. A login screen will appear — enter your BrightEdge credentials to establish the connection.

6
Verify the Installation

Navigate to the Tools section of your agent and confirm that the BrightEdge MCP tool is shown as installed and active.

7
Start Prompting

Navigate to your agent and begin prompting. The agent can now call BrightEdge tools to answer queries.

n8n

Platform 7 of 10

Connect BrightEdge MCP to n8n to incorporate live BrightEdge data into automated workflows and multi-step pipelines. n8n uses the MCP Client node with OAuth2 authentication.

Prerequisites
  • An active BrightEdge account
  • An n8n account (cloud or self-hosted)
Connection Details
SettingValue
Server TransportHTTP Streamable
MCP Endpoint URLhttps://mcp2.brightedge.com/mcp
AuthenticationMCP OAuth2
Setup Steps
1
Create a New Workflow

In n8n, navigate to Workflows and click Create workflow. This opens a blank workflow canvas.

2
Add an MCP Client Node

On the workflow canvas, click Add first step (or the + icon). In the node search panel, search for MCP Client and select it to add it as a step.

3
Configure the MCP Client — Transport & Endpoint

With the MCP Client node selected, open the Parameters tab and set the following:

  • –  Server Transport: HTTP Streamable
  • –  MCP Endpoint URL: https://mcp2.brightedge.com/mcp
  • –  Authentication: MCP OAuth2
4
Create the OAuth2 Credential

For the Credential for MCP OAuth2 API field, click Create New Credential. A credential form will open — enter the following values:

  • –  Use Dynamic Client Registration: Off (toggle off)
  • –  Grant Type: Authorization Code
  • –  Authorization URL: https://mrkt-0365.us.auth0.com/authorize
  • –  Access Token URL: https://mrkt-0365.us.auth0.com/oauth/token
  • –  Client ID
  • –  Client Secret
Ensure "Use Dynamic Client Registration" is toggled off before saving.
5
Save and Connect to BrightEdge

Click Save, then click Connect to MCP. A BrightEdge login page will open — enter your BrightEdge credentials to complete the OAuth flow.

6
Select a Tool and Configure Your Query

Once authenticated, return to the MCP Client node. In the Tool dropdown, select the BrightEdge tool you want to use. Set Input Mode to Manual and enter your prompt in the Values to Send field.

Example prompt: show me ranking between Jan to Feb 2026

7
Execute the Workflow

Click Execute step (or Execute workflow if you have multiple nodes) to run the workflow. BrightEdge data will be returned as the node output.

You can chain the MCP Client node output into further n8n nodes — for example, sending results to Slack, writing to a Google Sheet, or triggering further logic.

OpenClaw

Platform 8 of 10

Connect BrightEdge MCP to OpenClaw using mcporter, a middleware CLI that bridges OpenClaw with external MCP servers. Setup involves enabling mcporter in the OpenClaw UI and configuring it via the terminal.

Prerequisites
  • An active BrightEdge account
  • Access to OpenClaw
  • Node.js and npm installed
SettingValue
Server URL (SSE)https://mcp2-sse.brightedge.com/sse
Setup Steps
1
Enable mcporter in OpenClaw

In the OpenClaw UI, navigate to Skills in the left navigation menu. Locate mcporter in the Built-in Skills list and toggle it on.

2
Install mcporter via npm

Then install mcporter globally via npm by running the following command in your terminal:

npm install -g mcporter
3
Add the BrightEdge MCP Server

Add the BrightEdge MCP server configuration to your local mcporter setup. Navigate to the .mcporter folder (create it if it doesn't exist):

cd $HOME/.mcporter/
4
Configure the .mcporter Directory

Create or update credentials.json with the following content:

{
  "version": 1,
  "entries": {
    "brightedge|fc7a79fb09a7771d": {
      "serverName": "brightedge",
      "serverUrl": "https://mcp2.brightedge.com/mcp",
      "clientInfo": {
        "client_id": "NM9It06JLxFxSASeXvxdoEveq01Uhohv"
      }
    }
  }
}

Create or update mcporter.json with the following content:

{
  "mcpServers": {
    "brightedge": {
      "baseUrl": "https://mcp2.brightedge.com/mcp",
      "auth": "oauth"
    }
  }
}
5
Authenticate with BrightEdge

Run the authentication command to link your BrightEdge account:

mcporter be-mcp auth

A BrightEdge login page will open in your browser. Enter your credentials and sign in. To verify the connection is active, run:

mcporter list
6
Invoke BrightEdge in OpenClaw

With authentication complete, use the /skill command in OpenClaw to query BrightEdge:

/skill <mcp_server_name> <query>
/skill brightedge Get me the top 3 keywords for this month.

BrightEdge data will be returned directly within your OpenClaw workflow.

Relevance AI

Platform 9 of 10

Connect BrightEdge MCP to Relevance AI to give your agents and tools access to live BrightEdge data within automated workflows.

Prerequisites
  • An active BrightEdge account
  • A Relevance AI account
SettingValue
Server URLhttps://mcp2.brightedge.com/mcp
Setup Steps
1
Open Your Agent or Tool

In Relevance AI, navigate to the Agent or Tool you want to connect BrightEdge MCP to. Open its settings or configuration panel.

2
Add a New Tool

Look for the Integrations, Tools, or MCP section within the agent configuration. Click Add tool or Add integration.

3
Select MCP as the Tool Type

When prompted for a tool type, choose MCP Server or Model Context Protocol.

4
Enter the BrightEdge Connection Details

Fill in the following fields:

  • –  Server URL: https://mcp2.brightedge.com/mcp
  • –  OAuth Client ID
  • –  OAuth Client Secret
  • –  Auth URL: https://mrkt-0365.us.auth0.com/authorize
  • –  Token URL: https://mrkt-0365.us.auth0.com/oauth/token
  • –  Scope: openid profile email
5
Authenticate with BrightEdge

Click Connect or Save. A BrightEdge login screen will appear — enter your BrightEdge credentials to complete the OAuth flow. Once authenticated, the connection will be confirmed.

6
Save and Test

Save the configuration. Test the connection by running a sample query within Relevance AI to confirm BrightEdge data is returned successfully.

If you encounter connection issues, verify the Server URL and OAuth credentials are entered exactly as shown above.

Using BrightEdge Data in Workflows

Once connected, your Relevance AI agents can query BrightEdge data as part of any workflow step. When building prompts or agent instructions, be specific about which BrightEdge data you need and how you want it used.

Example agent instruction:

When the user asks about keyword performance, use the BrightEdge
MCP tool to retrieve the relevant keyword data and summarise
the findings in plain language.

Slack

Platform 10 of 10

The BrightEdge Slack App connects BrightEdge data and actions directly into your Slack workspace using Slack's standard OAuth installation flow. Installation takes only a few minutes and requires no technical configuration.

Prerequisites
  • An active BrightEdge account
  • A Slack account with access to the workspace where the app will be installed
  • Workspace admin approval may be required if your organisation restricts third-party app installations
Installation URL

Use the following link to begin the installation. Open it in a browser while signed in to your Slack account:

https://slack.com/oauth/v2/authorize?client_id=10825199192177.11032644384785&scope=app_mentions:read,assistant:write,channels:history,chat:write,im:history,users:read&user_scope=
Note: This link launches Slack's official OAuth installation flow. You do not need a BrightEdge API token or OAuth credentials — Slack handles the authorisation automatically.
Setup Steps
1
Open the Installation Link

Open the installation URL above in any modern browser while signed in to your Slack account. This launches Slack's official OAuth installation flow.

2
Select Your Slack Workspace

Slack will prompt you to select the workspace where the BrightEdge App will be installed.

  • If you are signed in to multiple workspaces, choose the correct one from the workspace switcher.
  • If you are not signed in, Slack will ask you to sign in first.
3
Review Permissions

Slack will display the list of permissions (OAuth scopes) requested by the BrightEdge App. Review them before continuing. Permissions include:

  • Reading user and channel information
  • Reading message history (channels and direct messages)
  • Posting messages
4
Approve the Installation

Click Allow to grant the requested permissions and complete the installation. Once approved, Slack installs the app into your selected workspace. You may be redirected back to BrightEdge or to a Slack confirmation page.

5
Confirm the App is Installed

After installation, verify that the BrightEdge App is available in your workspace:

  • Open Slack.
  • Go to Apps in the left sidebar.
  • Search for BrightEdge.
  • Confirm the app is listed and accessible.

Troubleshooting

Missing Permissions: If installation fails, confirm the installer has the required role in the Slack workspace. Some permission scopes can only be approved by a workspace admin or owner.

Workspace Restrictions: Some Slack workspaces restrict third-party app installations. In that case, a workspace admin must approve the BrightEdge App before it can be installed.

Reinstalling the App: If the app was previously installed and its requested scopes have changed, a reinstall may be required for the new permissions to take effect. Simply open the installation link again and follow the same steps.

AI Is Accelerating the Customer Journey. Is Your Brand Keeping Up?

Exclusive research on how AI search is reshaping discovery, visibility, and the customer journey

Originally presented on Wednesday, May 20, 2026 at 10:00 AM PDT, this on-demand session explores how AI search is transforming the way your brand is discovered, evaluated, and chosen.

AI is collapsing the distance between early discovery and decision-making. Product recommendations, solution comparisons, and brand citations are now appearing directly inside AI-generated answers, often before a customer ever reaches a traditional search results page.

In this on-demand session, BrightEdge shares exclusive research on how AI search is reshaping customer journeys across industries, where visibility is being won and lost, and what marketers need to do to stay present in the moments that influence decisions. You'll also see the latest BrightEdge innovations designed to help teams measure, monitor, and optimize for the new prompt universe.

What You'll Learn

  • How AI search is compressing the funnel and what this means for measurement, content strategy, and planning
  • What BrightEdge research reveals about AI-driven discovery across key industries
  • How leading marketing teams are monitoring their prompt universe and adapting to the new customer journey
  • How BrightEdge innovations can help teams measure and optimize for AI search visibility
  • The difference between AI Catalyst, AI HyperCube, and AI Agent Insights — and how they work together

Why Watch

  • Rated 4.3/5 for overall satisfaction and 4.25/5 for relevance to role by live attendees, with 86% rating it 4 or 5 stars.
  • Get a practical breakdown of how prompt intent, AEO strategy, and AI HyperCube work together to help your brand stay visible in AI-generated answers.
  • The most-valued part of the session was insights on prompt intent, followed by BrightEdge research on AI-driven discovery and understanding the AEO ownership gap.

Featured Speakers:

Dave McAnally  

Watch On-Demand Webinar

* indicates required

 
 

Why AI Engines Cite Different Sources but Recommend the Same Brands

BrightEdge AI Catalyst analysis across five AI search engines shows that sourcing behavior varies dramatically from engine to engine, while the brands those engines ultimately recommend cluster in a tight, predictable band. The divergence is in the path.

BrightEdge AI Catalyst analysis reveals that ChatGPT, Perplexity, Gemini, Google AI Mode, and Google AI Overviews operate with fundamentally different editorial personalities when selecting the sources they cite. At the same time, the brands named in AI-generated answers remain far more consistent across engines than the sources those engines use to construct those answers. The gap between how engines source and what engines recommend is the single most important pattern for any brand building an AI search strategy.

The prevailing assumption in AI search is that each engine requires its own playbook because each engine behaves differently. The data confirms the engines do behave differently, in some cases by close to two orders of magnitude. But the consistency on the output side, which brands get named in the final answer, tells a different story. The playbook does not need to be fragmented by engine. It needs to be organized by source layer.

This is the latest installment in our BrightEdge AI Catalyst research series. We analyzed citations and brand mentions across ChatGPT, Perplexity, Gemini, Google AI Mode, and Google AI Overviews, drawn from prompts spanning ten industries including B2B technology, education, entertainment, finance, healthcare, insurance, restaurants, travel, and ecommerce. The patterns that emerged are directly relevant to any brand planning AI visibility at scale.

Data Collected

 

Data PointDescription
Citation share by engineShare of each engine's total citations directed to each cited domain, across all analyzed prompts
Citation source classificationEach cited domain categorized by source type: authoritative institutions, commercial and editorial sources, UGC and social platforms, and other layers
Brand mention trackingAll brand mentions extracted from AI responses and tracked by share of voice, average rank position, and sentiment
Cross-engine overlap analysisPairwise overlap in top-cited domains and top-named brands calculated across all five engines
TLD distributionShare of citations from .gov, .edu, .org, .com, and country-code domains, by engine
Concentration analysisShare of total citations captured by each engine's top 10 and top 25 sources

 

Data PointDescription
Authority layer shareShare of citations from government, academic, and major industry institutional domains, by engine
UGC layer shareShare of citations from video platforms, forums, community sites, and social networks, by engine
Commercial and editorial layer shareShare of citations from review sites, trade press, news media, finance data, and retailer listings, by engine
Brand positioning analysisAverage rank at which brands are named in AI responses, by engine
Sentiment classificationBrand mentions classified as positive, neutral, or negative, by engine
Industry coverageAnalysis spans B2B technology, education, entertainment, finance, healthcare, insurance, restaurants, travel, and ecommerce

Key Finding

AI search engines are often discussed as if they behave similarly because they produce a similar kind of output: a synthesized answer with citations. The BrightEdge AI Catalyst data shows that behind the surface, the five engines pull from meaningfully different parts of the web. The share of citations coming from authoritative sources ranges from 10% to 26%, depending on the engine. The share coming from user-generated content ranges from 0.2% to 18%, roughly a 90x spread across engines answering the same categories of questions. Despite that divergence in sourcing, the brands those engines recommend cluster in a much tighter range. Pairwise top-100 overlap in named brands across engines falls between 36% and 55%, a 19-point spread, while pairwise top-100 overlap in cited sources ranges from 16% to 59%, a 43-point spread. Source agreement between any two engines varies widely and inconsistently. Brand agreement is consistently steady. The implication for brand strategy is that the path AI takes to reach its answer matters less than most strategies assume, but being present across the three distinct source layers that feed those paths matters more than strategies typically account for.

Five AI Engines, Five Sourcing Personalities

Gemini functions as a formal institutional recommender. Gemini shows the strongest bias toward authoritative sources of any engine in the dataset. Approximately 26% of Gemini's citations come from government domains, academic institutions, and major industry institutional bodies combined. UGC and social content makes up only 0.2%. The authority-to-UGC ratio is roughly 130 to 1, the highest in the study. Gemini also shows the highest .gov share of any engine at roughly 13%, paired with a .org share of 23%. The engine behaves as a conservative, list-oriented recommender that leans on trusted institutional voices and tends to produce longer, more inclusive brand lists than other engines.

ChatGPT acts as a long-tail editorial engine. ChatGPT cites the flattest source distribution of any engine in the study. Its top 10 most-cited domains account for only 18.5% of total citations, meaningfully lower than Perplexity (26.7%), Gemini (26.3%), or AI Mode (19.4%). ChatGPT also has almost no UGC presence (0.5%) and pulls heavily from government and .org domains (12% and 20% respectively). The engine reads as a formal editorial assistant with a long, diverse tail of corporate, institutional, and government sources.

Perplexity behaves like a research librarian. Perplexity concentrates more of its citations in institutional medical, government, encyclopedic, and medical publisher sources than any other engine. Combined, those four categories account for approximately 30% of Perplexity's citations. Perplexity shows the highest share of .edu citations (3.2%) and the highest share of international country-code domains (4.4%) in the dataset, reflecting a more formal and globally sourced material mix. It also names brands earliest of any engine, with 86% of its brand mentions landing in position 5 or earlier. Perplexity behaves like an engine that commits to a short, authoritative shortlist rather than producing an exhaustive list.

Google AI Mode operates as a broad commercial aggregator. Google AI Mode pulls from a wider catalog of unique domains than most other engines, with a long-tail distribution that spreads citations across far more sources than its siblings. It also distributes its citations more evenly across source types than any other engine in the study, showing the strongest mix of review aggregators, finance data sources, and news media citations in the dataset. UGC exposure is moderate at roughly 7%, well above ChatGPT or Gemini but well below AI Overviews. AI Mode's top 10 citation concentration is among the lowest at 19.4%, reinforcing its identity as a long-tail, balanced commercial surface.

Google AI Overviews is a UGC-first engine. Google AI Overviews stands apart from every other engine in the study. Approximately 17.5% of its citations come from user-generated content platforms, 35x higher than ChatGPT (0.5%) and 87x higher than Gemini (0.2%). A single video platform accounts for roughly 10.6% of all AI Overviews citations on its own, and a single forum platform adds another 2.9%. Authoritative sources, including government, academic, and major institutional bodies, account for only 9.5% of AIO citations combined. AI Overviews is the only engine in the dataset where UGC citations outweigh authoritative citations.

Authority Share Versus UGC Share, by Engine

EngineAuthority ShareUGC Share
Gemini26%0.2%
Perplexity22%1.5%
ChatGPT18%0.5%
Google AI Mode14%7%
Google AI Overviews10%18%

The Two Google Engines Are Not the Same Engine

Among the five engines studied, the two most similar are Google AI Mode and Google AI Overviews, with a top-100 citation overlap of roughly 59%. But Gemini, also a Google product, behaves very differently from its siblings. Gemini's top-100 citation overlap with AI Mode is only 27%, and with AI Overviews only 34%. Gemini actually has more in common with ChatGPT (39% overlap) than with the Google search-embedded surfaces. In practical terms, "Google AI" is not one thing. The search-embedded surfaces lean heavily on commercial and UGC content, while standalone Gemini behaves like a conservative, authority-heavy reference engine. Any brand strategy that treats all three Google AI surfaces as interchangeable will miss the actual sourcing patterns driving visibility on each.

The Brand Convergence Signal

The most consequential finding in the study is not the divergence in sources. It is the convergence in brand recommendations despite that divergence. Pairwise top-100 overlap in cited sources across engines ranges from 16% to 59%, a 43-point spread. Pairwise top-100 overlap in named brands ranges from 36% to 55%, a 19-point spread. In every pairwise comparison, brand overlap falls in a tighter, more predictable range than source overlap. The engines disagree substantially and inconsistently about where to pull information from. They agree more consistently about which brands belong in the final answer. That pattern is what makes a unified strategy viable across all five engines, rather than five separate playbooks.

Sentiment Is Overwhelmingly Positive Across Every Engine

Brand sentiment in AI-generated answers skews positive on all five engines, but not uniformly. Gemini is the most positive at roughly 96% positive sentiment, with only 0.3% negative. ChatGPT sits at 94% positive with effectively zero negative mentions. Perplexity shows the highest neutral share at 11%, consistent with its more journalistic, reference-oriented posture. The Google search-embedded surfaces (AI Mode at 93% and AI Overviews at 89%) show slightly higher negative sentiment (1.7% and 2.1%), which reflects their deeper pull from UGC and commercial commentary sources where critical framing more commonly appears. Across the dataset, negative brand mentions remain a marginal share of total volume, which reinforces that visibility in AI answers is almost always presented in a positive or neutral frame.

What Marketers Need to Know

AI engines pull from three distinct source layers, and every engine uses all three. Authoritative sources include government, academic, and major industry institutional content. Commercial and editorial sources include review sites, comparison content, trade press, news media, finance data, and retailer listings. UGC includes video content, forum threads, community discussion, and creator coverage. No engine uses only one layer. The engines differ in how they weight each layer, not in whether they use it. A brand visibility strategy built around only one layer, no matter which layer, will underperform on engines weighted toward the other two.

Authority is category-relative. "Authoritative" does not mean .gov or .edu for every brand. Not every company can or should aim to be cited by federal agencies or academic institutions. Every category has its own authoritative layer: trade associations, analyst firms, expert publishers, standards bodies, professional associations, and institutional voices trusted within the vertical. The strategic question is which authoritative sources serve as the backbone of AI citations in your specific category, and whether your brand is covered by those sources.

Commercial and editorial presence is the widest visibility lever. Across all five engines, the brand/corporate and commercial/editorial source layer accounts for the largest share of citations, ranging from roughly 37% on Gemini to 51% on AI Overviews. Review sites, comparison content, trade press, retailer listings, and finance data are the sources AI most frequently reaches for. Investment in PR, trade coverage, review site visibility, and category comparison content translates into visibility across every engine, not just one.

UGC is non-negotiable for AI Overviews and still meaningful elsewhere. The AI Overviews surface draws roughly 18% of its citations from user-generated content, but UGC is not zero on other engines either. Perplexity pulls 1.5% of its citations from UGC, AI Mode pulls 7%, and both represent real retrievable impressions in categories where community and creator content is strong. A UGC strategy does not mean "produce short-form video." It means understanding which videos, forum threads, and community discussions AI is already citing in your category, and being present in that conversation with authority.

Weight investment based on which engines matter most to your buyers. The three-layer framework is universal. The emphasis is not. A B2B SaaS brand whose buyers rely heavily on ChatGPT and Perplexity will prioritize authority and commercial coverage, with UGC as a supplemental layer. A consumer brand whose buyers use AI Overviews heavily will prioritize UGC and commercial presence, with authority as reinforcement. Brand tracking at the engine level, not just in aggregate, is how those priorities get set and validated.

Engine overlap patterns should inform where you measure first. The two Google search-embedded surfaces share roughly 59% of their top-cited sources, so visibility gains on one frequently translate to the other. Gemini behaves more like ChatGPT than like its Google siblings, so brand teams should not assume that a Gemini strategy is a Google strategy. These overlap patterns are not intuitive, and brands that map their measurement plan against actual engine behavior will catch gaps that aggregate tracking hides.

Technical Methodology

ParameterDetail
Data SourceBrightEdge AI Catalyst
Engines AnalyzedChatGPT, Perplexity, Gemini, Google AI Mode, Google AI Overviews
Industries CoveredB2B technology, education, entertainment, finance, healthcare, insurance, restaurants, travel, ecommerce
Citation ClassificationEach cited domain categorized by source type (authority, commercial and editorial, UGC, other) using a domain-level taxonomy
Brand Mention AnalysisAll brand mentions extracted from AI responses and classified by share of voice, average rank position, and sentiment
Overlap MethodologyPairwise top-100 citation and mention lists compared using Jaccard similarity
Data CleaningCitation artifacts attributable to search engine result page disclaimers were removed from Google surfaces to avoid inflation

Key Takeaways

FindingDetail
Source mixes vary dramatically by engineAuthority share ranges from 10% to 26%, UGC share ranges from 0.2% to 18%
Source agreement between engines varies widelyPairwise top-100 citation overlap ranges from 16% to 59%, a 43-point spread
Brand agreement between engines stays tightPairwise top-100 brand overlap ranges from 36% to 55%, a 19-point spread
Gemini and Google AIO behave like opposite enginesGemini leans authority (130 to 1 ratio vs UGC), AIO is UGC-first (UGC outweighs authority)
The three Google surfaces are not interchangeableAI Mode and AIO overlap at 59%, but Gemini overlaps more with ChatGPT than with its own siblings
ChatGPT has the flattest source distributionTop 10 domains account for only 18.5% of citations, the widest long tail of any engine
Perplexity names brands earliest86% of Perplexity brand mentions land in position 5 or earlier, the tightest shortlist in the dataset
A coherent three-layer strategy wins across enginesCover authority, commercial and editorial, and UGC, weighted by engine priority, to maintain visibility across all five

Download the Full Report

Download the full AI Search Report — Why AI Engines Cite Different Sources but Recommend the Same Brands

Click the button above to download the full report in PDF format.

Published on  April 24, 2026

What is LLM Optimization (LLMO)?

Definition

LLM optimization, commonly abbreviated as LLMO, is the discipline of structuring, publishing, and distributing content so that large language models (LLMs) such as ChatGPT, Gemini, Claude, and Llama incorporate your brand, products, and expertise into their generated responses. As LLMs become the primary interface through which enterprise buyers research categories, evaluate vendors, and form purchase intent, appearing accurately and positively inside those responses is a business-critical objective. For a broader look at how AI has reshaped search, see How Has AI Changed Search Marketing?.

What is a large language model?

A large language model is an AI system trained on vast quantities of text data that generates human-like responses to natural language queries. LLMs power conversational AI tools including ChatGPT, Microsoft Copilot, Google Gemini, and Perplexity, as well as the AI Overviews that now appear at the top of many Google search results pages.

When someone asks one of these systems a question such as 'What is the best enterprise SEO platform?' or 'How does AI search work?', the model generates a response based on patterns learned during training and, in some cases, live retrieval from the web. Whether your brand appears in that response, and how accurately it is characterized, depends significantly on how well your content has been optimized for LLM consumption.

Why does LLMO matter to enterprise teams?

Enterprise buyers conduct significant research before entering a formal sales process. A growing share of that research now happens through AI-powered tools rather than traditional search. When a director of digital marketing or a VP of demand generation queries an LLM about platforms in your category, the response they receive shapes their consideration set before any salesperson or marketer has the opportunity to engage.

LLMO matters because:

  1. LLMs reference a fixed body of training data, which means brands that are well-represented in that data tend to appear more consistently in responses.

  2. Retrieval-augmented systems pull live web content, so current on-page optimization and structured content directly influence what gets surfaced.

  3. Negative or inaccurate representations of your brand in LLM responses are difficult to detect without systematic monitoring.

  4. Competitors investing in LLMO capture the definitional authority for your category, framing what products in your space do and what they should cost.

 

BrightEdge AI Catalyst monitors how your brand is represented across the major LLM platforms, tracking citation frequency, sentiment, and competitive share of voice at scale. It surfaces the specific prompts where competitors are named and you are not, so your team can prioritize content and optimization work with precision.

How do LLMs select content to include in responses?

LLMs do not rank pages the way a traditional search algorithm does. They learn associations between concepts, entities, and sources during training, and they retrieve and synthesize content based on relevance to the query at hand. Content tends to be incorporated into LLM responses when it exhibits the following characteristics:

  • Authority signals - it comes from a domain with strong topical depth and external references. Domain Authority is one foundational signal.

  • Clarity of entity - it clearly and consistently describes what a brand, product, or organization is and does.

  • Factual density - it contains specific data, definitions, and claims that are verifiable and citable.

  • Structural accessibility -it is organized in ways that make individual passages easy to extract and quote.

  • Breadth of coverage - it addresses a topic comprehensively rather than superficially. See How to Create Topic Clusters for the architecture that builds this kind of depth.

What does LLMO look like in practice?

Effective LLM optimization is not a separate content program. It is a set of principles applied to your existing content investment. The core practices include:

  1. Define your brand and product accurately in your own words. Create clear, authoritative definitions of what you do on pages that are likely to be indexed and referenced by AI systems. A well-built glossary is one of the highest-leverage investments here.

  2. Build topical depth across your domain. LLMs treat domains with comprehensive coverage as more authoritative. Use Data cube x to map the topic and keyword landscape around your core subject areas and find the coverage gaps that matter most.

  3. Publish original data and research. Original statistics and findings are among the most-cited content types in LLM responses.

  4. Maintain consistency across channels. Conflicting descriptions of your product, pricing, or capabilities across different pages create noise that reduces the accuracy of LLM representations. ContentIQ can identify inconsistencies across your site at scale.

  5. Monitor your AI presence actively. Knowing when and how your brand appears across LLM platforms is essential to understanding whether your LLMO efforts are working. AI Catalyst is built for exactly this.

How is LLMO different from SEO?

SEO and LLMO share many of the same underlying content requirements: authoritative, well-structured, factually accurate writing optimized around user intent. The difference is in what success looks like and how it is measured. In SEO, success is a ranking position that drives organic traffic. In LLMO, success is citation presence, sentiment accuracy, and share of voice across AI-generated responses for the queries your buyers are asking. For SEO fundamentals, see What is SEO?.

Use BrightEdge Recommendations to address on-page SEO gaps that also improve LLM citability, and SEO Copilot to accelerate optimization work across large content libraries.

What is the relationship between LLMO and GEO?

LLM optimization and generative engine optimization (GEO) are closely related and often used interchangeably. GEO tends to refer more specifically to optimization for AI-powered search surfaces such as AI Overviews and Perplexity, while LLMO is broader, encompassing optimization for LLMs in any context, including conversational AI, enterprise knowledge tools, and embedded AI assistants. The content strategies that support both goals are nearly identical, and both connect directly to the principles of Semantic SEO.

,