Do Identifier Registries Like Wikidata, ISNI and LEI Affect Search Visibility?

What an identifier registry is actually for

A registry exists to solve a disambiguation problem, not a promotion problem. When two companies share a trading name, or an author publishes under three variants of their own, systems that need to reconcile records require something more stable than a string. A registry issues a persistent identifier and maintains the mapping between that identifier and the entity it designates.

The five we examined were built for different institutional purposes. ISNI is “an ISO standard, in use by numerous libraries, publishers, databases, and rights management organizations around the world”, identifying “persons and organizations or groups involved in creative activities, as well as public personas of both”. ORCID identifies researchers and connects them to their scholarly output.

The Legal Entity Identifier is “a unique 20-character alphanumeric code that enables anyone, anywhere in the world, to access clear, unique identification data about a legal entity”, built for financial regulation. The D-U-N-S Number is “a unique nine-digit identifier used exclusively for businesses”, used by counterparties to “evaluate your business credit profile, maintain their records, onboard your company, and maintain compliance”.

Wikidata is the outlier, because it is not an identifier authority in the same sense. It is a collaboratively edited knowledge base that stores structured statements about entities and, in practice, functions as a hub linking many of the other identifiers together on a single item.

What it takes to get each one

Two of the five are free and quick. Dun & Bradstreet states plainly that “Getting a D‑U‑N‑S Number is free”, and notes it is “entirely separate from a personal identity”. ORCID says researchers “will be able to create, edit, and maintain an ORCID identifier and record free of charge”, sustained instead by “fees from our member organizations”, with researchers controlling “the defined privacy settings of their own ORCID record data”.

ISNI is materially harder, and this is the detail most often glossed over by vendors selling identifier packages. Its guidance tells you first to check whether an ISNI already exists for you, then to “contact one of the ISNI Registration Agencies that provide this service”. It describes no self-registration route. Supporting an application means supplying “details of creative works with which you are associated or other information that will help us confirm your public identity”, and fees and eligibility vary by agency rather than being set centrally.

The LEI is not obtained for convenience at all. It is issued by LEI Issuers, also called Local Operating Units, under GLEIF's governance, and the identifier exists because regulation requires it: GLEIF cites the Dodd-Frank Act, EMIR, MiFID II and MiFIR, and mandates from central banks in India, South Korea and Japan for particular transaction types. GLEIF describes the underlying reference data as “a public good, available free of charge to all users”, which concerns access to the data rather than issuance being costless.

A Wikidata item has no issuing authority and no fee. Its creation is governed by a community policy rather than an application, which is a genuinely different model and is covered in detail in our separate report on how that bar compares with Wikipedia's.

What the registries themselves claim

This is the finding that matters most, and it is uniform. Across the five registries, we found no claim of a search engine benefit, no claim of Knowledge Graph inclusion, and no claim of improved visibility in AI systems.

ISNI comes closest to the territory, describing itself as “a critical component in Linked Data and Semantic Web applications” — a statement about machine-readable data infrastructure, not about ranking or retrieval. GLEIF's material covers cross-border payments, ownership transparency, sustainability and regulatory compliance, and makes no search claim. ORCID's material concerns researcher identification and interoperability between institutions.

Dun & Bradstreet's page is instructive because it does market benefits, just not these ones. It describes credibility with counterparties, partnerships, loans and contracts. Digital discoverability does not appear. The registries are not being coy about a search advantage they know they confer; they are describing infrastructure that was built for other reasons entirely.

So when a package is sold on the promise that registering identifiers will produce a knowledge panel or make an AI assistant recognise a brand, that promise originates with the seller. It does not come from the registries, and it is not in their documentation.

What Google actually accepts

There is nonetheless a documented connection, and it runs through markup rather than through the registries. Google's Organization structured data reference lists the properties it supports, and four of them are registry identifiers: duns, leiCode, iso6523Code and naics, alongside vatID, taxID and globalLocationNumber.

Google explains why they are there. Adding the markup “can help Google better understand your organization's administrative details and disambiguate your organization in search results”, and some properties “are used behind the scenes to disambiguate your organization from other organizations (like iso6523 and naics)”. That is the clearest published statement linking registry identifiers to Google's entity understanding.

The sameAs property does related work for non-registry references. Google defines it as “The URL of a page on another website with additional information about your organization, if applicable”, offers a profile page as the example, and confirms “You can provide multiple sameAs URLs”.

All of it sits beneath one sentence that should govern expectations: “Google does not guarantee that features that consume structured data will show up in search results.” Declaring an LEI in your markup is a way of stating unambiguously which legal entity you are. Google does not say it produces a panel, a ranking change or an AI mention, and we are not going to imply otherwise.

Where Wikidata sits apart

Wikidata occupies a different position for a historical reason. Freebase, the first source Google named when it launched the Knowledge Graph in 2012, was closed and its resources offered to Wikidata, with the platform going read-only on 31 March 2015. That lineage is why Wikidata is routinely treated as a back door into Google's entity data.

The lineage is real, but the inference is weaker than it looks. Google's current knowledge panel documentation names no source at all — not Wikidata, not Wikipedia — and the migration of Freebase content into Wikidata was partial rather than complete. A Wikidata item is a public structured record; treating it as a submission form for Google's graph reads a guarantee into a lineage.

Where Wikidata does earn its place is as a reconciliation hub. Items commonly carry ISNI, ORCID, LEI, VIAF and other identifiers as properties on a single record, which is exactly the cross-referencing that disambiguation systems consume. That is a real function, independent of any claim about panels.

It is also the one entry on this list that anyone can edit, which cuts both ways: an item can be created or corrected without an issuing authority, and it can equally be edited by people who do not share your view of your own organisation.

What this means for anyone buying coverage

The practical position is that registry identifiers are cheap identity hygiene with a documented role in disambiguation, and are not a visibility product. A D-U-N-S Number and an ORCID iD cost nothing. An LEI is worth having if regulation requires one of you, and largely pointless if it does not. An ISNI is meaningful if you genuinely operate in the creative and publishing ecosystem that uses it.

The marketing failure mode is bundling: an “entity establishment package” that registers free identifiers, adds markup you could have added yourself, and attributes any subsequent change in search appearance to the package. Since Google publishes no threshold for a panel and explicitly guarantees nothing about structured data, such a package cannot be falsified by its buyer, which is what makes it sellable.

If you want the checkable version: obtain the free identifiers that genuinely apply to you, record them in Organization markup on your home page, point sameAs at profiles you actually control, and keep legal name, trading name and identifiers consistent everywhere they appear. Then stop, because the documentation does not support doing more.

Media Morpheus sells media and podcast placement, and none of the above is a service we are selling you here. The registries make no search claims; we are not going to make those claims on their behalf.

Methodology and limitations

We reviewed the primary documentation of five identifier systems on 23 September 2026 — ISNI (about and registration pages), ORCID, GLEIF's Legal Entity Identifier introduction, Dun & Bradstreet's D-U-N-S page, and Wikidata's notability policy — and read each for claims about search engines, the Google Knowledge Graph or AI visibility. We then compared those against Google's Organization structured data reference, which enumerates the identifier properties Google accepts. The limitation is that this is a documentation review, not an experiment: we did not register identifiers and measure downstream search behaviour, and such a test would in any case struggle to isolate one variable amid ordinary index churn. Absence of a search claim in a registry's own material is strong evidence about what the registry asserts, and weak evidence about what search systems do with the data. Fee statements vary by issuing agency and may change; we quote only what the published pages state. Every URL cited was retrieved successfully before publication.

Conclusion

Identifier registries are infrastructure for telling entities apart, built for libraries, researchers, financial regulators and credit counterparties. Not one of the five we checked claims that holding an identifier improves search visibility. The only documented link to Google runs the other way: Google accepts four registry identifiers as properties in Organization structured data and says some are used behind the scenes to disambiguate one organisation from another, while stating that it guarantees no search feature as a result. Registering what genuinely applies to you and declaring it accurately is sound, inexpensive practice. Buying it as a visibility product is paying for a claim nobody in the chain has actually made.

Frequently Asked Questions

Sources

1. official Google Search Central. Organization structured data: supported properties including duns, leiCode, iso6523Code and naics, the sameAs definition, the disambiguation statement and the no-guarantee caveat.
2. official ISNI. About ISNI: the ISO standard, what it identifies, and its description as a component in Linked Data and Semantic Web applications.
3. official ISNI. Obtaining an ISNI: registration agency route, evidence expected in support of an application, and variation in fees and eligibility by agency.
4. official ORCID. What is ORCID: free creation and maintenance of an iD, funding via member organisations, and researcher control of record privacy settings.
5. official GLEIF. Introducing the Legal Entity Identifier: the ISO 17442 code, GLEIF's G20 and Financial Stability Board backing, issuance via Local Operating Units and the regulatory mandates cited.
6. official Dun & Bradstreet. D-U-N-S Number: the nine-digit business identifier, the statement that obtaining one is free, and the stated uses in credit, onboarding and compliance.
7. official Wikidata. Notability policy: the three criteria under which an item may be created.
8. official ORCID. What does an ORCID identifier look like?: the 16-digit iD, compatible with ISO 27729. The page carries a notice that it is more than three years old. Read October 10, 2026.