Identity Legibility (BVAC Framework)

Identity Legibility is one of two prerequisite dimensions in the Brand Visibility for Agentic Commerce (BVAC) Framework, developed by Greg Kihlström, martech futurist and Principal at The Agile Brand. The dimension measures the degree to which a brand and its products exist as stable, distinct, and consistently identified entities that agents can resolve, retrieve, and cite as authoritative sources (Kihlström, 2026).

Identity Legibility is one of two prerequisite dimensions in the framework — the other is Attribute Completeness. Together they cap the effective score on every strategic dimension. A brand that scores Differentiated on Differentiation Encoding diagnostically still delivers a Comparable effective score on it if Identity Legibility (or Attribute Completeness) sits at Comparable. The remediation order is fixed by that dependency: prerequisites first, then the Trust Signal Density floor, then strategic dimensions in binding-constraint order.

The dimension answers a specific question. Before any other dimension scores, an agent must answer two preceding questions: what brand is this, and which product am I looking at? Inconsistent identifiers, drifting product names, fragmented URLs, and ambiguous entity references cause agents to either default to marketplace versions of the brand (authority erosion) or skip the brand entirely. Every downstream dimension depends on the agent being able to anchor the brand and its catalog to a stable, retrievable entity.

This is the dimension that determines whether a brand exists in the agent-readable world at all.

How It Relates to Marketing

Identity Legibility reframes brand identity as a structured-data problem before it’s a creative one. The brand book, the visual identity system, and the voice guidelines all matter for the human-facing surface. None of them reach the agent layer unless the brand and its products resolve to stable, citable entities in machine-readable form.

The shift creates several reframes marketing leaders need to internalize:

• Brand identity has a machine-readable layer. Organization schema, sameAs links to authoritative external sources, and disambiguation against name collisions are how the brand becomes citable. Without them, the brand exists in the agent’s view as a fragment or, worse, as the wrong entity.
• Product identifiers are a brand-integrity concern. GTIN drift across channels reads to an agent as multiple products at different prices. The brand experiences this as agents recommending competitors; the mechanism is that the brand’s own identifiers aren’t behaving as a coherent catalog.
• Marketplace authority is the most common identity failure. When the brand’s marketplace entity is more complete than its own, agents cite the marketplace as the authoritative source. The brand earned the identity; the marketplace owns the citation.
• Identity work caps everything else. The framework’s prerequisite cap formalizes the consequence. A brand can do strong differentiation, trust, and protocol work and remain invisible because the agent never reached any of it. The decision invisibility article in the framework’s library describes this directly: silent removal from the set, with no traffic decline and no campaign to diagnose (Kihlström, 2026).
• The work is unglamorous and decisive. Most of Identity Legibility remediation is schema and configuration work. None of it shows up in a campaign deck. All of it gates whether anything in the campaign deck reaches an agent.

The dimension typically sits under marketing in the assessment lead’s first 6–12 months of agentic commerce maturity, with engineering and data operations as required participants. Marketing has the visibility into competitive positioning, agent-query simulation, and customer experience that the role draws on. The execution of identifier reconciliation and schema implementation lives in engineering and data operations.

Sub-Components of Identity Legibility

The dimension is assessed across six sub-components.

Brand entity model. Structured declaration of the brand as an entity — Organization or Brand schema with sameAs links to authoritative external sources (Wikidata, Wikipedia, LinkedIn, verified social profiles). Without this, agents resolve the brand inconsistently or attach it to the wrong entity.

Stable product identifiers. GTINs, MPNs, and SKUs that are present, valid, and identical across the brand site, product feeds, marketplaces, and APIs. Drift across channels creates phantom products and undermines comparison.

Canonical product pages. URL stability and canonical tags so that a product resolves to a single authoritative page. Variant fragmentation across multiple URLs causes agents to treat the same product as different entities.

Schema.org entity declarations. Organization, Brand, and Product schema with sufficient detail for agents to extract and link entities without inference.

Cross-channel reference integrity. The same product on the brand site, Amazon, Walmart, and Google Shopping resolves to the same entity. Inconsistencies cause agents to cite whichever source is most internally coherent, often a marketplace.

Disambiguation handling. When the brand name or product name overlaps with other entities, the brand’s entity model resolves the ambiguity explicitly. A two-character or three-character brand name (the AMP case in the framework’s worked B2B example) is particularly exposed without explicit disambiguation.

Maturity Stages

Identity Legibility uses the BVAC Framework’s shared five-stage maturity scale.

Stage	What it looks like for Identity Legibility
Invisible	No structured entity declarations. Identifiers missing or inconsistent. URLs fragmented. Products appear under multiple names across channels. Agents cannot reliably resolve the brand.
Discoverable	Basic Product schema in place. GTINs assigned to most SKUs. Canonical URLs stable. Agents can find and parse the brand, but entity context is thin.
Comparable	Full Organization, Brand, and Product schema. Stable identifiers consistent across all channels. sameAs links to authoritative external sources. The brand resolves cleanly as an entity.
Differentiated	Entity model carries context — brand origin, category positioning, structured references to verifiable third-party sources. Disambiguation handled. The brand functions as a citable entity in its category.
Agent-native	Brand and product entities recognized and resolved correctly by all major agent systems. The brand operates as an authoritative source — agents cite the brand’s own catalog rather than marketplace proxies.

How Identity Legibility Functions as a Prerequisite

The prerequisite tier has different mechanics from the strategic tier, and the distinction is one of the most important structural features of the framework.

Prerequisite cap. The effective score on every strategic dimension (Differentiation Encoding, Brand-Agent Representation, Trust Signal Density, Protocol Readiness, Latency and Data Freshness, Governance Maturity) is capped by the lower of the two prerequisite scores. If Identity Legibility sits at Comparable, every strategic dimension’s effective score is capped at Comparable, regardless of its diagnostic score.

The gap between diagnostic and effective. A brand can score Differentiated on Differentiation Encoding diagnostically — encoding every USP, anchoring every claim — and deliver Comparable effective if Identity Legibility is at Comparable. The diagnostic score reflects the dimension’s quality in isolation; the effective score reflects what actually reaches an agent. The gap between them is the foundational work required.

Why prerequisites instead of weighting. The framework treats Identity Legibility (and Attribute Completeness) as prerequisites rather than weighted dimensions because their failure isn’t a partial degradation — it’s a structural block. An agent can’t evaluate a brand it can’t resolve. Weighting would average the prerequisite gap with the strategic strength; capping reflects the actual behavior, which is that the strategic strength doesn’t reach the agent.

The remediation consequence. Most of the framework’s worked examples include a brand with strong strategic work and a prerequisite gap. The remediation sequence always starts with the prerequisite, not because the strategic work is wrong, but because the strategic work returns nothing in effective score until the cap is lifted.

How to Assess Identity Legibility

An Identity Legibility assessment combines four inputs.

1. Schema audit. Inventory of entity declarations (Organization, Brand, Product) and the sameAs graph. Map which external authority sources the brand anchors to and where the entity model is thin or absent.
2. Identifier consistency check. Compare GTINs, MPNs, and SKUs across site, feeds, marketplaces, and APIs. Identify drift, gaps, and reconciliation issues. The check runs at the SKU level against the top 20 SKUs by revenue.
3. Entity resolution test. Query major agents with brand and product names. Record whether the correct entity is returned and which source is cited. Marketplace-cited responses are flagged as authority erosion, not entity resolution.
4. Disambiguation review. Identify name collisions and assess how the brand’s entity model resolves them. Short or generic brand names face higher disambiguation risk and need stronger anchor work.

The diagnostic questions used during assessment include:

• For the top 20 SKUs, are GTINs present and identical across site, feeds, marketplaces, and APIs?
• Does the brand have complete Organization and Brand schema with sameAs links to authoritative external sources?
• When agents query the brand name in category contexts, do they return the correct entity?
• Are product variants modeled correctly (as variants of a parent product, not as separate entities)?
• When agents cite product attributes, do they cite the brand site or a marketplace?
• Are there name collisions with other entities? How are they handled?

The output is an Identity Legibility score with a gap map showing where entities are missing, fragmented, or anchored incorrectly. Most Identity Legibility gaps fall in the 90-day horizon — schema and configuration work that fits within existing systems and teams — with cross-channel reconciliation extending into 6–12 months.

Common Failure Modes

Six failure modes recur across Identity Legibility assessments.

• GTIN drift. GTINs present but inconsistent across channels, so agents see what looks like multiple products. The brand has the identifiers; the identifiers don’t behave as a coherent catalog.
• URL fragmentation. Same product across multiple URLs without canonicals, splitting entity signals. Variant pages, regional pages, and campaign landing pages all dilute the canonical signal.
• Marketplace authority. The marketplace’s entity for the brand is more complete than the brand’s own, so agents cite the marketplace. The brand earned the identity; the marketplace owns the citation.
• Variant confusion. Product variants modeled as separate products or merged incorrectly, breaking comparison logic. Agents either over-count the catalog or fail to surface the right variant.
• Name collision without disambiguation. Brand or product shares a name with another entity, and the agent resolves to the wrong one. Common with short, generic, or acronym brand names.
• Schema present but thin. Organization schema exists but has no sameAs links or context, so the entity has no anchor. Present and parseable but unconnected.

How to Utilize Identity Legibility

Common applications of the dimension within a BVAC assessment include:

• Prerequisite-gap diagnosis. Identifying whether Identity Legibility (or Attribute Completeness) is the binding cap on the strategic tier. Most strategic-tier underperformance traces back to one or the other.
• GTIN reconciliation across channels. Building the data pipeline that ensures GTINs, MPNs, and SKUs match across site, feeds, marketplaces, and APIs. The work is unglamorous and high-leverage — a 6–12 month structural investment that unlocks the strategic tier.
• Brand entity anchoring. Publishing Organization or Brand schema with sameAs links to Wikidata, Wikipedia, LinkedIn, and verified social profiles. The work is 90-day schema implementation and produces immediate citability gains.
• Canonical URL consolidation. Implementing canonical tags and resolving URL fragmentation. The work is largely 90-day with variant-page consolidation extending longer depending on the depth of fragmentation.
• Disambiguation against name collisions. For brands with short, generic, or acronym names, building explicit disambiguation in the entity model. The framework’s B2B worked example (AMP) illustrates the cost of skipping this work.
• Marketplace authority recovery. Mapping where agents currently cite the brand’s marketplace entity rather than the brand’s own catalog, and building the entity-model and identifier work that redirects the citation back to the brand.

A worked case makes the dimension concrete. AMP, a B2B agentic marketing platform, presents a strong narrative surface — positioning as the agentic marketing platform with confident category-leadership claims. The structured reading is weaker. Identity Legibility scores Comparable with an entity-collision risk: “AMP” is an ambiguous token that collides with unrelated entities (the music format, the molecular biology term, several other commercial brands), and without strong sameAs disambiguation a buyer agent may resolve the wrong entity or deprioritize on ambiguity. The fix is concrete: structured Organization schema with sameAs anchors to the company’s authoritative third-party records, explicit disambiguation in the entity model, and stable identifiers across surfaces. None of it is creative work; all of it determines whether the rest of the brand’s strategic investment reaches the agent layer at all.

Comparison to Similar Concepts

Concept	Focus	Relationship to Identity Legibility
Master Data Management (MDM)	Centralized management of authoritative business entities	MDM is the infrastructure that operationalizes Identity Legibility; the dimension scores the output MDM produces for agents
Product Information Management (PIM)	Centralized management of product attribute data	PIM overlaps with Identity Legibility on identifiers and with Attribute Completeness on attribute data
Schema.org markup	Structured-data vocabulary for web content	Schema.org is the implementation layer for several sub-components (Organization, Brand, Product schema, sameAs links)
Entity Resolution	Determining whether different records refer to the same real-world entity	Entity resolution is the technical discipline; Identity Legibility scores whether the brand has solved entity resolution well enough for agents to do it correctly
Search Engine Optimization (SEO)	Ranking in human-facing search engine results	SEO and Identity Legibility share concerns (canonical URLs, schema markup) but diverge on purpose; SEO optimizes for human-readable rankings, Identity Legibility for machine-readable entity resolution
Knowledge Graph	Networked representation of entities and their relationships	The brand’s structured entity model is a node in larger knowledge graphs that agents query; sameAs links connect the brand’s node to the broader graph

Identity Legibility extends past any single implementation discipline to whether the brand exists as a stable, distinct, and citable entity in the form agents resolve — and it carries the prerequisite-cap mechanic that gates the effective score of every strategic dimension downstream.

Best Practices

• Resolve Identity Legibility before investing in strategic dimensions. Strategic work above an unresolved prerequisite returns nothing in effective score. The remediation sequence is fixed by dependency, not by perceived urgency.
• Score down on borderline stages. When the brand sits between two stages, score to the lower stage and note the partial progress in the gap map. Prerequisites are the wrong place to declare readiness the brand hasn’t earned, because every strategic effective score depends on the prerequisite.
• Audit identifiers at the SKU level. GTIN drift hides in aggregate. The top 20 SKUs by revenue should each be checked individually across site, feeds, marketplaces, and APIs.
• Anchor the entity model to authoritative external sources. sameAs links to Wikidata, Wikipedia, LinkedIn, and verified social profiles are what make the Organization or Brand schema connectable. Schema without anchors is present and unconnected.
• Treat marketplace authority as the structural problem it is. A more complete marketplace entity isn’t just a citation pattern; it’s a sign the brand’s own catalog isn’t doing the work the brand thinks it’s doing.
• Build explicit disambiguation for short, generic, or acronym names. Name-collision risk scales inversely with name length and specificity. A two-character brand name carries different disambiguation costs than a five-word brand name.
• Use the 90-day horizon for schema work and the 6–12 month horizon for cross-channel reconciliation. Most Identity Legibility work fits the 90-day horizon. Identifier reconciliation across systems is the exception and takes longer because it requires data pipelines.
• Sequence with Attribute Completeness in parallel where possible. Both prerequisites cap the strategic tier. Working them in parallel — rather than sequentially — minimizes the time the strategic tier is held below its diagnostic potential.

Future Trends

• Knowledge graph integration deepening. As agents increasingly query knowledge graphs (Wikidata, Google Knowledge Graph, category-specific graphs) for entity resolution, the brands that anchor their entity model strongly to those graphs gain citation advantages. The work is 90-day schema implementation and the advantage compounds.
• GTIN and identifier hygiene becoming a competitive surface. As agent-mediated commerce scales, brands with clean, reconciled identifiers across all channels gain selection advantages that brands with drift don’t. Identifier hygiene moves from infrastructure baseline to competitive surface.
• Disambiguation as a category-level concern. Categories with high name-collision rates (acronym-heavy categories like B2B SaaS, generic-name categories like commodity goods) are expected to develop category-specific disambiguation patterns. Brands that invest early in disambiguation gain durable resolution advantages.
• Marketplace authority erosion. As agents develop better recognition of brand-owned catalogs, the cost of marketplace authority dependence rises. Brands that build their own canonical surfaces reclaim citation authority; brands that don’t continue losing it.
• Entity model context becoming a competitive surface. The Differentiated stage of the dimension involves carrying brand origin, design philosophy, and category positioning in the entity model in structured form. This crosses into Differentiation Encoding territory (narrative preservation in entity model) and is expected to become a more contested layer as agents extend beyond attribute comparison into context-aware recommendation.

FAQs

1. Who created Identity Legibility as a framework dimension? Greg Kihlström, martech futurist and Principal at The Agile Brand, developed Identity Legibility as one of the two prerequisite dimensions of the Brand Visibility for Agentic Commerce (BVAC) Framework, introduced in 2026.

2. What does Identity Legibility measure? The degree to which a brand and its products exist as stable, distinct, and consistently identified entities that agents can resolve, retrieve, and cite as authoritative sources.

3. Why is Identity Legibility a prerequisite instead of a strategic dimension? Before any other dimension scores, an agent must answer two preceding questions: what brand is this, and which product am I looking at? If the agent can’t resolve the brand, no downstream evaluation happens. Treating identity as a prerequisite — not a weighted dimension — reflects the actual behavior, which is that strategic strength doesn’t reach the agent when identity is broken.

4. What is the prerequisite cap? The effective score on every strategic dimension is capped by the lower of the two prerequisite scores (Identity Legibility and Attribute Completeness). A brand at Comparable on Identity Legibility caps every strategic dimension’s effective score at Comparable, regardless of the strategic dimension’s diagnostic score.

5. What’s the most common failure mode? Marketplace authority. The brand’s marketplace entity is more complete than the brand’s own, so agents cite the marketplace as the authoritative source. The brand earned the identity; the marketplace owns the citation.

6. What’s GTIN drift? GTINs are present but inconsistent across channels (site, feeds, marketplaces, APIs). An agent reading the inconsistent identifiers sees what looks like multiple products. The brand has the identifiers; the identifiers don’t behave as a coherent catalog.

7. How is Identity Legibility different from SEO? SEO and Identity Legibility share concerns — canonical URLs, schema markup — but diverge on purpose. SEO optimizes for human-readable rankings in search results. Identity Legibility optimizes for machine-readable entity resolution by agents. The two can coexist or compete depending on implementation choices.

8. What’s sameAs linking? A Schema.org property that links a brand’s entity declaration to authoritative external sources (Wikidata, Wikipedia, LinkedIn, verified social profiles). The links anchor the brand to entities agents already trust and make the brand citable.

9. How long does Identity Legibility remediation take? Most Identity Legibility gaps fall in the 90-day horizon — schema and configuration work that fits within existing systems and teams. Cross-channel identifier reconciliation extends into 6–12 months because it requires data pipelines. Brand entity enrichment with structured context falls in the 6–12 month horizon.

10. Can a brand have strong Identity Legibility and weak Attribute Completeness? Yes, and it’s a common pattern. A brand can resolve cleanly as an entity (sameAs-anchored, GTINs consistent, canonical URLs stable) and still lack the category-standard attributes agents expect for product evaluation. Both prerequisites need to resolve before the strategic tier returns full value, and the lower of the two binds the cap.

Related Terms

1. Brand Visibility for Agentic Commerce (BVAC)
2. Agentic Commerce
3. Master Data Management (MDM)
4. Product Information Management (PIM)
5. Identity Resolution
6. Universal Product Code (UPC)
7. Stock Keeping Unit (SKU)
8. Search Engine Optimization (SEO)
9. Generative Engine Optimization (GEO)
10. Answer Engine Optimization (AEO)
11. Product Detail Page (PDP)
12. Product Listing Page (PLP)

Sources

• Kihlström, G. “How Purchase Decisions Now Form Before the Customer Is Involved.” The Agile Brand, May 2026. https://www.gregkihlstrom.com/martech-futurist-blog/purchase-decisions-form-before-customer-involved
• Molino Sánchez, M. “7 Signs Your Brand Is Losing Ground in Agentic Commerce.” Stibo Systems, 2026. https://www.stibosystems.com/blog/7-signs-your-brand-is-losing-ground-in-agentic-commerce