Your Brand Has Three Names Online. A Machine Sees Three Companies.

In this article: the part of Interpretability Engine Optimization (IEO) that comes before everything else: identity. Before a machine can understand what a brand makes, where, or on what terms, it has to know which brand it's looking at. This part makes sure your brand is one thing, with one main name and its variants declared as yours, wherever a machine meets it.

Here is what happens without it.

Your company makes ceramic tableware and is called Ellery & Co. (a name made up for this example). On your site, the brand field says "Ellery & Co." In your Google feed, someone typed "Ellery". The Amazon listings an old distributor set up say "ELLERY HOME". Three names. On Instagram you're @elleryhome, which is a handle, not a fourth name, but it doesn't say which of the three it belongs to either. Your customers know they're all you. They've never had to think about it.

A shopper asks an AI assistant about "Ellery mugs". The assistant finds three brands with Ellery in the name, one with twelve reviews, one with two hundred, one with none, and it isn't sure they're related. Your reviews, your story and your products are split across three entities, and each one looks smaller than you are. The brand whose name and reviews sit in one place is the one the assistant can vouch for.

Why a machine shouldn't just assume

A person reads "Ellery", "Ellery & Co." and "Ellery Home" and merges them without noticing. A careful machine shouldn't do that on a guess. Merging two names into one brand is a claim, and a system that guesses wrong merges you with somebody else's company. So, without a connection it can check, it may keep them apart. Three strings, and nothing that says they're one.

Platforms that take product data work from a brand field, one string per product. Google's product data has a brand attribute. Meta's catalog requires brand. Shopify has a vendor field, which is the supplier and not always the brand. None of them will connect your spellings on their own. You make the connection explicit: one main name, used consistently where you control it, and the variants declared as yours where machines look for that.

The problem compounds. A mention of your brand that a machine can't attach to you can be a review you don't get credit for, a product that doesn't count toward your catalog, a fact about your company that stays orphaned.

The technical name: identity

In IEO, interpretation starts by resolving identity: which product, which brand, which thing is this record about. The Methodology defines interpretability as a machine's ability to resolve "identity, taxonomy, attributes, constraints and context well enough to act correctly", and identity comes first for a reason. Every other fact hangs off it. Get the brand wrong and the provenance, the certifications and the reviews attach to the wrong thing or to nothing.

For a brand, resolving identity means two things:

1. One main name, spelled one way, used in every brand field you control. The name customers use, chosen once.
2. One place that declares the variants and the connections. Your own site can describe the organization in structured form: the main name, the legal name if it differs, the alternate names, and the official profiles that belong to it. Google's documentation for organization markup supports exactly this kind of declaration. That's what lets a careful machine connect what it otherwise has no basis to merge.

Where it lands: one name, declared connections

Here is the brand, before and after:

Nothing about the brand changed. It was always one company. What changed is that a machine now has an explicit connection between the pieces, instead of three strings and a guess.

What to do this week

1. Search your own brand on Google, on Amazon, in your ad accounts and in your feeds. Write down every spelling you find.
2. Choose the main name. The one customers say. Write it down with its exact capitalization and punctuation.
3. Put it in every brand field you control. Site, feeds, catalogs. Only the fields that name your brand: in Shopify, the vendor field is for the supplier, so in a store that also sells other brands, leave their vendors alone. For marketplaces, use their correction process rather than editing on your own.
4. Declare the connections on your site. Structured organization information that names the brand once, gives its legal name if it differs, lists the alternate names you've found, and links the official profiles that are yours.
5. Check the old names don't come back. A distributor's feed, a template, a plugin default. Put the main name where the defaults live.

Practical example

A houseplant shop (also a made-up name) is listed as "Mira Botanicals" on its site, "MIRA" in its Google feed, "Mira Botanicals Inc." on its invoices and "mirabotanicals" on TikTok. A garden center that stocks its plants lists them as "Mira Plants".

Before you read on, decide which of these the shop can fix, and which name is the main one.

Main name: "Mira Botanicals". It's what customers say, and it's what the site uses. "MIRA" alone is ambiguous; it could be anyone. "Mira Botanicals Inc." is the legal name, and it has a place: the legal-name slot in the organization markup, not the brand field on a product.

The shop fixes: its own feed (MIRA → Mira Botanicals), and its site's organization markup, which names Mira Botanicals once, gives the legal name, lists "MIRA" as an alternate name and the TikTok profile as the brand's own.

The shop can't fix alone: the garden center's "Mira Plants". It can ask, and it can make the correct name easy to copy. Until then, that retailer still uses an inconsistent brand name, and the shop knows exactly where.

That's identity as the first thing interpretation resolves, from section 2 of the IEO Methodology, applied to the brand object in section 10.1.

Check what's explicit, what's missing and what contradicts itself on one of your products → Run the free audit

To go deeper → The IEO Methodology, sections 2 and 10.1 (doi.org/10.5281/zenodo.22416784) · nsolvia.com/ieo

Sources: Google Search Central, Organization structured data (name, legal name, alternate names, profile links) · Google Merchant Center product data specification (brand attribute) · Meta for Developers, "Catalog Fields" (brand required) · Shopify Help Center, product details (vendor).

← Shoppers Search Your Store for Things You Sell. And Find Nothing. · ⌂ IEO · Next: "Save 15%" Is on the Page. The Cancellation Policy Isn't. →

Series: Interpretability Engine Optimization · Knowledge Domain: Interpretability (IEO)

Interpretability Engine Optimization (IEO)
The UNDERSTAND Layer
nsolvia.com/ieo