Tutorial · Practitioner
Wikidata for Brands: How and When
Wikidata is a free, collaboratively edited knowledge base that many systems use as structured entity data. A brand belongs there only if it meets Wikidata's notability policy, for example being describable with serious, publicly available references ([Wikidata](https://www.wikidata.org/wiki/Wikidata:Notability)). Creating an item about your own organization is strongly discouraged ([Wikidata](https://www.wikidata.org/wiki/Wikidata:Self-promotion)). If an item exists, accurate, sourced statements help machines identify your brand.
Facts are from Wikidata and Wikimedia, accessed 30 Oct 2026. Points marked "Our view" are interpretation. No search engine has published that a Wikidata item improves AI citations.
On this page
- Does your brand qualify?
- Should you edit it yourself?
- Which properties matter for brands?
- How should statements be sourced?
- How do you connect Wikidata to your site?
- How do you fix errors?
- Which edits cause problems?
- How is Wikidata different from Wikipedia?
- Why might AI systems care?
- How do you check what machines see?
- Exercise
- Checklist
- From MentionX data: why consistent entity facts matter
- Worked example: Ledgerline corrects its Wikidata item
- What does a good brand item contain?
- Who should do the editing?
- How do you find your item?
- What if you don't have an item?
- How often should you check it?
- How does Wikidata connect to your schema?
- How do you handle product items?
- What if an edit is reverted?
- Which identifiers are worth adding?
- Common questions
- Related
- Sources
Checked on 31 October 2026. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.
Does your brand qualify?
Wikidata's notability policy says an item is acceptable if it meets at least one of three criteria (Wikidata):
- It has at least one valid sitelink to a Wikimedia project page, such as a Wikipedia article.
- It refers to a clearly identifiable entity that can be described using serious and publicly available references.
- It fulfills a structural need, for example making statements in other items more useful.
The policy notes the guidelines are intentionally vague and that the community decides in disputed cases.
Our view: if independent press, industry databases or official registries describe your company, criterion 2 may apply. Your own website and press releases aren't enough.
Should you edit it yourself?
Wikidata's self-promotion page, an essay rather than a policy, says (Wikidata):
- Creating an item about yourself, your organization or your work is a form of self-promotion and strongly discouraged.
- Wikidata only includes topics already notable in independent, reliable sources.
- Self-created items are likely to be deleted.
Wikimedia's Terms of Use require disclosure of paid contributions (Wikimedia). Our view: if you or an agency are paid to edit, disclose it on your user page and prefer talk-page requests.
Which properties matter for brands?
| Property | ID | Example value |
|---|---|---|
| Official website | P856 | https://www.example.com |
| Logo image | P154 | File on Wikimedia Commons |
| Inception | P571 | Founding date |
| Headquarters location | P159 | City item |
| Founder | P112 | Person item |
| Industry | P452 | Industry item |
| X (Twitter) username | P2002 | Handle |
| LinkedIn company or organization ID | P4264 | Company slug |
Property labels verified on Wikidata, 30 Oct 2026. Example values are fictional.
How should statements be sourced?
Wikidata's sources guideline says most statements should be verifiable and supported by a source; references usually use "stated in" (P248) for publications or "reference URL" (P854) for websites (Wikidata). External identifiers that link to an authority database generally don't need an extra source.
Our view: source each statement with an independent reference where possible, such as a company registry, reputable press or an industry database.
How do you connect Wikidata to your site?
- Add the Wikidata item URL to your Organization
sameAs(Schema.org). - Make your site's name, founding date and HQ match the sourced Wikidata facts.
- Keep official website (P856) pointing to your canonical domain.
See sameAs links and Organization schema.
How do you fix errors?
Our view, consistent with the self-promotion essay:
- Find the item and check its history to see who added the wrong value.
- Gather an independent source for the correct value.
- Post on the item's talk page, disclose your affiliation, state the change and link the source.
- For clear, uncontroversial fixes, such as a changed website URL, a disclosed direct edit with a reference is usually accepted.
- Don't remove sourced statements you dislike; add better-sourced ones instead.
Which edits cause problems?
- Creating an item before independent coverage exists.
- Marketing language in descriptions; Wikidata descriptions are short and neutral.
- Unsourced statements, or citing only your own site.
- Duplicate items; merge instead of creating new ones.
- Undisclosed paid editing.
How is Wikidata different from Wikipedia?
Wikipedia articles are prose with their own, stricter notability rules per language edition. Wikidata items are structured statements, and a Wikipedia sitelink is just one of three ways to meet Wikidata notability (Wikidata). Our view: that makes Wikidata reachable for some companies that don't yet have a Wikipedia article, provided independent references exist. The two are linked: a Wikipedia article usually has a Wikidata item, and the item's sitelinks point to articles in each language.
Why might AI systems care?
Our view: Wikidata is openly licensed, machine-readable and widely reused, so it's a plausible source of entity facts for search engines and language models. But no AI search provider has said how much it relies on Wikidata for answers, so treat a correct item as good entity hygiene, not a visibility lever. Accurate data still matters: wrong founding dates or headquarters can propagate into other datasets.
How do you check what machines see?
Our view: use the Wikidata API to fetch your item's data the way software would, e.g. https://www.wikidata.org/wiki/Special:EntityData/Q42.json with your item's ID. Check that labels, aliases and descriptions are correct in your main languages, since many systems read the label in the user's language first.
Exercise
Search Wikidata for your brand and two competitors. Note whether each has an item, which brand properties are present, and whether statements have references. If yours has errors, draft a disclosed talk-page request with sources.
Checklist
- Notability checked honestly
- Affiliation disclosed for any edits
- Key properties present and sourced
- Wikidata URL in Organization sameAs
- Site facts match Wikidata
- Labels correct in main languages
From MentionX data: why consistent entity facts matter
Method. Read-only aggregate queries over MentionX scans from 22 August to 29 October 2026 (UTC): 2,217 engine runs (2,154 completed) across 18 anonymised projects and six engines.
Our sample doesn't measure Wikidata use directly. It does show that engines differ in how often they cite sources, which affects how they get facts:
| Engine | Brand mentioned | Answers with no citations |
|---|---|---|
| Gemini | 47.3% | 50.7% |
| OpenAI | 42.9% | 30.2% |
| Perplexity | 31.5% | 4.1% |
| AI Mode | 31.3% | 12.6% |
| Copilot | 26.0% | 47.0% |
| DeepSeek | 24.0% | 99.0% |
Reference sources such as Wikipedia appear among cited page types:
| Cited URL type | Share of 9,750 citations |
|---|---|
| Blog or article | 19.6% |
| Homepage | 10.0% |
| Review page | 2.7% |
| Docs | 2.6% |
| Pricing | 1.9% |
| Wikipedia | 1.6% |
Our view: when an engine gives no citation, its description of your brand may rest on structured sources and training data rather than a page it fetched. Accurate, referenced facts in public knowledge bases are one way to keep those descriptions right.
Limits. A convenience sample of mostly B2B software projects, run through engine APIs, which can behave differently from the consumer apps. Perplexity, Copilot and DeepSeek figures come from a single day (26 October 2026), so treat them as a snapshot, not a trend.
Worked example: Ledgerline corrects its Wikidata item
Ledgerline is a fictional accounts-payable tool. Figures are illustrative.
Ledgerline's brand audit shows two engines giving the wrong founding year and headquarters city. The team checks Wikidata and finds an item for the company with an old headquarters and no official website.
An employee creates an account, declares the conflict of interest on her user page and adds the official website and the correct headquarters, each with a reference to an independent news article. She doesn't add marketing descriptions. The team also adds the Wikidata URL to sameAs in its Organization schema. Over the following months, answers more often give the right city.
What does a good brand item contain?
A clear label and short neutral description, an "instance of" statement such as business or software, official website, country and headquarters location, founding date, founders where documented, industry, and identifiers that link to other databases. Each statement should have a reference. Avoid adjectives; Wikidata isn't a marketing channel.
Who should do the editing?
Ideally, independent volunteers. In practice, many companies need to fix errors themselves. If you do, use a personal account, state that you work for the company, keep edits to factual corrections with references and accept community decisions. Don't use agencies that promise to create or manage items for a fee; that often leads to deletion.
How do you find your item?
Search Wikidata for your company name and check the results carefully; there may be several items with similar names. If there's a Wikipedia article about your company, its sidebar links to the Wikidata item. Note the item ID, which starts with Q, and use it in your schema.
What if you don't have an item?
If your company is covered by reliable independent sources, you may be able to create one. Check Wikidata's notability guidelines first. If you can't point to independent coverage, wait until you can. Our view: building real coverage first, through press and reviews, is a better use of time than trying to create an item too early.
How often should you check it?
Quarterly, and after major changes such as an acquisition, rebrand or headquarters move. Others can edit the item at any time, and errors can creep in. Watchlisting the item on Wikidata sends you notifications when it changes.
How does Wikidata connect to your schema?
Your Organization schema's sameAs property can list your Wikidata URL alongside your social profiles. That tells systems reading your site which knowledge base entry describes you. It doesn't guarantee anything, but it helps make your entity unambiguous, especially if your name is common.
How do you handle product items?
Major products sometimes have their own items. The same rules apply: notability, references and neutral facts. Link product items to the company item with a statement such as "developer" or "manufacturer". Don't create items for minor features.
What if an edit is reverted?
Read the edit summary and any message left on your talk page. Often the reason is a missing reference or a promotional tone. Fix the issue and try again, or ask on the item's discussion page. Don't keep reverting; persistent edit wars can get accounts blocked.
Which identifiers are worth adding?
Identifiers connect your item to other databases: an official company register number, a stock ticker if listed, and profile IDs on major business directories that Wikidata supports. Add only those you can reference. They help systems confirm that different records describe the same company, which reduces confusion with similarly named organisations. Check each identifier links to the right record before adding it, since a wrong ID spreads confusion rather than reducing it. Record your edits and their dates in your brand fact sheet. That way the whole team can see what changed and why.
Common questions
Can I edit my company's Wikidata item? Yes, with care: declare your conflict of interest and reference every change.
Is Wikidata the same as Wikipedia? No. Wikidata stores structured facts; Wikipedia articles are prose. They're linked.
Does Wikidata help AI answers? Many systems use it for entity facts, though vendors rarely document exactly how.
Related
- Wikipedia and AI for brands
- MCP servers and agent readiness
Sources
- Wikidata, Notability; Self-promotion (essay); Help:Sources; Introduction
- Wikimedia Foundation, Terms of Use: paid contributions
- Schema.org, sameAs
All accessed 30 Oct 2026.
Questions
Can I create a Wikidata item for my company?
Wikidata's self-promotion essay strongly discourages creating items about yourself or your organization. Items need to meet the notability policy, e.g. serious, publicly available references.
Which Wikidata properties matter most for a brand?
Common ones are official website (P856), logo image (P154), inception (P571), headquarters location (P159), founder (P112), industry (P452) and social IDs such as P2002 and P4264.
What if my brand's Wikidata item is wrong?
Our view: if you're affiliated, disclose it and propose corrections with sources on the item's talk page, rather than editing contested facts yourself.