This is the third article in a 3-part series on how brands can measure the effectiveness and ROI of their AI visibility.
- Part 1: Direct ROI
- Part 2: Search Halo
- Part 3: Sub-Entity Halo
A property developer we worked with had a strong parent brand.
It appeared in AI answers regularly. Branded search was healthy. On the surface, AI visibility looked like it was working.
But when we looked at their individual property projects, something more revealing showed up.
Some projects were being recommended by name. AI was surfacing them specifically with their own location, features, and positioning clearly understood.
Others were not. They were only referenced as “a project from [brand].” No project name. No independent recognition. Just the parent brand carrying them into the answer.
That gap mattered but not just because one type of buyer is closer to converting than another.
The deeper problem is this: if AI only knows the brand but not the individual project, it cannot match that project to a specific user query.
When a user asks:
“Which condominium around [location] has [specific features/requirements]?”
AI needs to know the project’s location, features, and positioning to answer that question. If it only knows the parent brand exists, the project doesn’t get recommended.
Not because it isn’t a good fit. Because AI doesn’t have enough information about it to know that it is.
The project isn’t just losing a conversion. It is being excluded from the conversation entirely at the exact moment a qualified buyer is asking the exact right question.
The data wasn’t just telling us how AI was performing. It was telling us which projects had built enough independent signals to stand on their own…and which ones hadn’t.
That is a brand architecture question. And Sub-Entity AI visibility data answered it.
That is where Sub-Entity Halo comes in.
Why Brand-level Measurement is not Enough
Brand-level measurement is useful. But it can hide exactly this kind of gap.
A company may own multiple sub-brand products (iPhone, XBox) or services (AWS, YouTube, Apple Music). Even if the parent brand appears consistently in AI answers, that does not tell you which specific offerings AI understands well enough to recommend and which ones it cannot match to a user’s actual query.
Users are often far more specific than brand-level measurement accounts for. They do not always ask AI about a brand. They ask about:
- a product with specific features
- a service that fits a specific use cases
If AI does not have enough detail about a specific product or service, it cannot surface the brand nor its product/service in those queries even if the parent brand is well-known. The sub-entity is invisible at the exact moment it is most relevant.
And that invisibility does not show up at the parent-brand level. The overall brand may look stable in AI answers, while individual offerings are being systematically excluded from the queries that matter most to the business.
That is why brands need a third layer of measurement.
What Sub-Entity Halo Means in Plain Terms
Sub-Entity Halo answers two connected questions:
- Is AI surfacing our specific products or services in the queries where they are most relevant?
- And when AI does surface them, does that lead to downstream search intent and conversions for that exact offering?
It is called a halo because, like Search Halo, AI does not always own the final click. It creates awareness and shapes consideration upstream. That influence later shows up as product-specific search behaviour and product-page conversions.
The journey looks like this:
- A user asks AI for the best option in a specific category or use case.
- AI has enough specific information about your product/service to match it to the query and recommends it by name.
- The user leaves the AI interface.
- The user searches for that product or service name specifically.
- The user lands on the relevant product or service page.
- The user converts.
If Step 2 fails — if AI does not have enough detail to match the product to the query — the rest of the journey never happens. A competitor fills that slot instead.
That is Sub-Entity Halo. The measurement layer that makes this visible.
Sub-Entity Halo in Practice
The concept becomes clearer with real brands. Here are two examples, one for a physical product, one for a service, that show how Sub-Entity Halo plays out depending on what you sell.
Note: These are not actual performance, just an example to illustrate the concept
Example 1: Nike (Physical Product)
Parent brand: Nike
Sub-entity (named product): Nike Air Max 270
Nike is one of the most recognised brands in the world. But when a user goes to AI with a specific question, brand recognition alone may not be enough to get a product recommended.
User query: “What’s a good everyday sneaker with maximum cushioning for long walks?”
To answer this, AI needs to know that the Air Max 270 has Nike’s largest heel Air unit, that it was designed for all-day comfort, and that it sits in a specific price range. It needs to know this specific sub-entity, not just the brand.
When the sub-entity signal is strong: AI recommends the Air Max 270 by name, describes its cushioning technology, and matches it to the user’s use case. The user then searches “Nike Air Max 270” and lands directly on the product page.
When the sub-entity signal is weak: AI only knows Nike makes sneakers. It mentions Nike generically but cannot match a specific model to the query. A competitor’s product with clearer feature-level information available to AI may fill the slot instead.
The Air Max 270 page may get strong direct and paid traffic. But Sub-Entity Halo only appears when AI can surface it specifically which requires AI to know it well enough to make the match.
What this means for Nike: If AI visibility data shows the Air Max 270 is not being named in cushioning or comfort-related queries, that is a signal quality problem, not a product problem. The fix is building richer, more specific content around this product so AI can accurately represent it in the conversations where it should be winning.
Example 2: HubSpot (Service / Solution)
Parent brand: HubSpot
Sub-entity (named solution): HubSpot Marketing Hub
HubSpot is widely known as a CRM and marketing platform. But the platform is made up of distinct named Hubs where each targeting a different team, problem, and buyer. A user evaluating solutions is rarely asking about HubSpot the brand. They are asking about a specific solution for a specific problem.
User query: “What’s the best tool for managing email campaigns, landing pages, and lead nurturing in one place for a mid-size B2B company?”
To answer this, AI needs to know that Marketing Hub covers email marketing, landing page creation, lead nurturing workflows, and marketing analytics. AI also needs to know that it is built specifically for teams that want those capabilities integrated within a CRM. It needs to know Marketing Hub, not just HubSpot.
When the sub-entity signal is strong: AI recommends HubSpot Marketing Hub by name, explains what it covers, and matches it to the user’s B2B mid-size context. The user searches “HubSpot Marketing Hub” and lands on the dedicated solution page.
When the sub-entity signal is weak: AI knows HubSpot is a marketing platform but cannot describe Marketing Hub’s specific capabilities in enough detail to match it to the query. It mentions HubSpot generically or recommends a competitor whose solution page is better represented in AI’s knowledge.
HubSpot’s overall brand signal is strong. But if Marketing Hub is not well-represented as a named sub-entity with its own clear positioning, feature detail, and use-case coverage, it can be passed over in the exact queries it was built to win.
What this means for HubSpot: Each Hub needs to be treated as its own AI visibility challenge. Marketing Hub, Sales Hub, and Service Hub each have different buyers, different queries, and different signals AI needs to make accurate recommendations. A strong parent brand does not automatically transfer to strong sub-entity visibility. Each one has to earn its own place in AI answers.
What if the Brand alone is not Enough to Enter the Conversation
The previous examples show what happens when AI knows a brand but not its sub-entity well enough to make the match. The brand may still get recommended although in a more broad/general term.
But there is a bigger and more invisible version of this problem.
Sometimes a user’s query is too specific for the parent brand to answer but one of its sub-entities is actually the right fit. But because AI doesn’t know that sub-entity well enough, it has nothing specific enough to surface.
Thus, neither the brand nor the sub-entity enters the conversation at all. This is where relying only on parent brand visibility becomes a strategic blind spot.
Sub-entity tracking is what surfaces them. Showing you precisely which sub-entities are losing queries they should be winning, and where focused investment would actually make a difference.
Note: This is not an actual performance, just an example to illustrate the concept
Example: Moxy Hotels by Marriott (Physical / Location-based product)
Parent brand: Marriott
Sub-entity (named product): Moxy Hotels
Marriott is one of the world’s largest hotel groups, with a broad portfolio spanning luxury, business, and lifestyle accommodation. A user asking a general hotel question might reasonably end up with Marriott in the answer.
But not every query is general.
User query: “What are some fun, affordable hotels for a solo trip to Amsterdam in my 20s?”
This query has specific requirements: affordable pricing, a social atmosphere, a design-forward feel, and an audience of younger independent travellers.
Marriott as a brand is too broad to answer this with confidence. AI doesn’t know whether any specific Marriott property fits so it surfaces brands and properties it knows meet those criteria clearly.
What happens without sub-entity knowledge: Neither Marriott nor any of its properties get mentioned. AI surfaces hostels, boutique budget hotels, or lifestyle brands whose positioning clearly matches the query. The opportunity disappears entirely.
What should happen: Moxy Hotels is Marriott’s answer to exactly this query. Built specifically as an affordable, design-led, social hotel brand targeting younger travellers, it has properties across Europe including Amsterdam. It fits the user’s requirements precisely.
But if AI doesn’t know Moxy Hotels as a distinctly named sub-entity with its own positioning, price range, audience, and property-level detail, it has no way of knowing a Marriott sub-entity is the right fit. The brand alone cannot carry that answer.
What sub-entity tracking reveals: Queries about affordable lifestyle hotels, social accommodation, and budget travel in cities where Moxy has properties represent a category of missed opportunities. Tracking Moxy as a sub-entity makes those misses visible — and makes it clear where content and PR investment would actually move the needle, rather than investing in Marriott’s broader brand presence that was never going to win these queries.
Why Sub-entity Halo Matters for Brands
This is especially important for brands with:
- named product lines or service offerings
- named category-specific landing pages
- named solutions for different audiences or use cases
Notice the “named” part. Because without a name, it’s not an entity the user can easily search or AI can easily associate with.
And if you only measure AI impact at the parent-brand level, you risk missing where value is being created and where it is being lost.
A brand may see stable overall AI performance while one specific product is quietly excluded from every relevant query. Or a high-margin offering is being recommended consistently and no one on the team knows because they are only looking at top-level brand signals.
AI visibility does not create value evenly across a portfolio. It may favour:
- one product over another
- one service line over another
- one sub-brand over the rest
The difference often comes down to how much specific, structured information AI has about each sub-entity. The ones with stronger signals get matched to more queries. The ones without it stay invisible regardless of how well-known the parent brand is.
How Brands can Measure Sub-entity Halo in Practice
The logic is similar to Search Halo, but applied at the product or service level. The model works in three steps.
Step 1: Isolate the sub-entity
Define the product, service, or business line you want to measure. You need a clear name and a dedicated landing page.
The cleaner this definition, the better the measurement.
Step 2: Measure search intent for that sub-entity
In Google Search Console, look at search traffic tied specifically to that product or offering, using both the landing page people clicked on and the product or service name in the search query.
This isolates visits where the search intent was genuinely about that specific offering, not just any visit to the page.
Step 3: Estimate conversion impact
In GA4, measure organic conversions on that specific landing page. Then apply the product-intent ratio from Step 2 to estimate how many of those conversions were driven by genuine product-level search intent.
Sub-Entity Halo = product-intent share of organic traffic × organic conversions on that product page
So if 30% of organic clicks to a product page come from searches clearly about that product, and the page generates 50 organic conversions, the estimated conversion impact is 15 conversions.
The point is not that every one of those 15 conversions definitively came from AI. The point is that if AI visibility for that specific product rises, and product-intent search and product-page conversions move with it, you now have a practical way to estimate its downstream impact and track it over time.
What Brands Should Look For
- Primary input: AI visibility for the specific product or service by name
- Query coverage: Appearance in feature-specific and location-specific queries
- Demand signal: Search lift for that specific product or service name
- Traffic signal: Organic traffic to the matching landing page
- Intent signal: Product-intent share of organic traffic to that page
- Output: Estimated product-level halo conversions over time
The first signal matters most: is the sub-entity appearing in the specific, feature-level, location-level queries where it is most relevant?
If it is not, the downstream metrics will reflect that absence regardless of how strong the parent brand signal is.
When all signals move together (AI visibility rises, product-intent search increases, product-page conversions follow), you are seeing where AI is creating value at the offering level, not just the parent-brand level.
The Deeper Implication of Sub-entity Halo
Sub-Entity Halo is not just a measurement model. It is diagnostic.
When the property developer saw which projects were being named by AI and which were not, they had an answer to a harder question:
Which of our projects have built enough independent signals to stand on their own. And which ones are entirely dependent on the parent brand to carry them into AI answers?
That distinction has direct commercial consequences. A project that AI cannot describe in sufficient detail (its location, features, connectivity, positioning) will be excluded from every query where those details are what the buyer is actually searching for. It will not appear because the brand itself is not relevant enough to be considered.
Knowing this changed where the developer invested. More content and PR behind the weaker project brands, not based on instinct, but based on what the AI visibility data was revealing about which sub-entities had the signal to compete independently, and which ones did not.
That is what Sub-Entity Halo enables. Not just attribution. Strategic prioritisation grounded in how AI actually discovers and recommends specific offerings.
How Sub-entity Halo Completes this AI Visibility Measurement Series
Part 1 (Direct ROI) answered: did AI drive direct attributable conversions?
Part 2 (Search Halo) answered: did AI increase branded demand that later showed up through search and indirect traffic?
Part 3 (Sub-entity Halo) answers: is AI surfacing specific sub-entities (named products and services) in the queries where they are most relevant — and is that leading to measurable demand and conversions for those exact offerings?
Together, these three layers create a complete view of AI Visibility ROI: direct conversion impact, indirect brand-level halo impact, and indirect product-level halo impact.
That is a significantly better framework than relying on last-click traffic alone.
Final Thought
In the AI search era, attribution is no longer only about where the click came from.
It is about understanding where demand started, whether AI had enough specific information to match your offerings to the right queries, and which parts of the business are actually being discovered or quietly excluded.
Sub-Entity Halo matters because it gives brands that precision. It moves the conversation from “is AI helping us?” to “what exactly is AI helping us sell, and what does it not know well enough to recommend?”
That is where measurement becomes genuinely strategic.
Author: April Cheong
Chief Product Officer, Co-Founder of Zicy.com
Head of AEO/GEO, Growth.pro
