◀ All articles

Authority

How to create a Wikidata item for your company

August 19, 2026 · 4 min read

Notability rules stated plainly, then the properties to fill, then how to link it from schema without pretending you have a Wikipedia page.


Teams hear "get on Wikidata" and picture a free Wikipedia page. Wikidata is a different thing: a structured knowledge base with notability rules, property IDs, and volunteer editors who will delete thin stubs. You can create a company item when the sources exist. You cannot invent notability with schema alone.

This guide states the notability bar plainly, lists the properties that matter for brand identity, and shows how to link the item from Organization schema without pretending you have a Wikipedia article.

Notability, without the sugarcoat

Wikidata is not a marketing directory. Items need reliable, independent sources. For companies, that usually means coverage in notable press, filings, or established databases — not your own blog and not a press release alone.

Practical translation:

  • If independent journalists, regulators, or major databases already describe your company, you may have enough to create or improve an item.
  • If the only sources are your website, your LinkedIn, and a guest post you paid for, wait. Create the item later when third-party sources exist.
  • A Crunchbase or LinkedIn page helps as a reference, but it is not a substitute for independent coverage.

BrandKnown covers the wider map in Wikidata, Crunchbase, and Wikipedia. Wikipedia has a higher bar still. Do not create a Wikipedia article to "feed" AI. Do Wikidata only when sources support it.

Before you create anything

  1. Search Wikidata for your legal name, former names, and product brands.
  2. If an item exists, improve it. Do not create a duplicate.
  3. Gather two or three independent URLs that state the company name, what it does, and preferably founding or headquarters facts.
  4. Decide the primary label (usually the customer-facing brand that matches your schema name).
  5. Create a Wikidata account and read the current organization notability guidance — rules evolve.

If search returns nothing and your sources are weak, stop here. Spend the afternoon on Crunchbase and on-site entity clarity instead.

Create the item (when sources support it)

  1. From Wikidata, start a new item.
  2. Set the English label to your canonical brand name.
  3. Add a short description like "American software company" or "analytics software company" — factual, not promotional.
  4. Add aliases for common misspellings and former names.
  5. Add statements (properties) with references pointing at your independent sources.
  6. Publish, then wait. Watch for talk page notes or challenges.

Never copy marketing adjectives into the description. "Leading," "innovative," and "best-in-class" get removed and signal that the item was written for SEO.

Properties worth filling

Fill what you can source. Empty is better than unsourced.

PropertyMeaningExample value
instance of (P31)Type of thingbusiness, enterprise, or software company as appropriate
official website (P856)Canonical sitehttps://www.northstaranalytics.example
inception (P571)Foundedyear with reference
headquarters location (P159)HQcity item, if known
industry (P452)Sectorsoftware industry, etc.
official name / short nameLegal vs brandonly if sourced
social media / ID propertiesProfilesLinkedIn, etc., when properties exist
Crunchbase IDExternal IDif you have a claimed profile

Exact property availability changes. Use Wikidata's property search rather than inventing custom fields. Always attach a reference URL to statements that assert facts.

Link from schema without faking Wikipedia

Once the item URL is stable (https://www.wikidata.org/wiki/Q…), add it to Organization sameAs alongside LinkedIn and Crunchbase:

"sameAs": [
  "https://www.linkedin.com/company/northstar-analytics",
  "https://www.crunchbase.com/organization/northstar-analytics",
  "https://www.wikidata.org/wiki/Q123456789"
]

Do not:

  • Put a Wikidata URL in a field meant for Wikipedia.
  • Claim sameAs Wikipedia if no article exists.
  • Point sameAs at a person item when the brand is an Organization.

Your on-site Organization schema should still carry name, url, and logo. Wikidata is a corroborating node, not a replacement for a clear About page.

How assistants use (and ignore) Wikidata

Knowledge graphs and some retrieval stacks use Wikidata for entity resolution — matching "Northstar Analytics" to one organization instead of a similarly named consultancy. That helps when names collide. It does not mean ChatGPT will recite your Wikidata description verbatim, and it does not mean a BrandKnown readiness score will jump because you added Q-ID.

Honest ceiling: Wikidata improves the chance that systems resolve your brand correctly when they already care. It does not buy citations on demand.

Common failure modes

MistakeWhat happensFix
Duplicate itemSplit entityMerge per Wikidata process; keep one Q-ID
Unsourced claimsStatements removedAdd references or delete the claim
Promo descriptionEditor revertsRewrite as neutral category phrase
Wrong instance ofMiscategorizedUse the type that matches sources
Linking person as companyEntity merge confusionSeparate Person and Organization items

After you publish

  • Add the Q-ID URL to sameAs on the live site.
  • Confirm the official website property matches your canonical URL.
  • Recheck in a month; community edits happen.
  • Do not refresh dates or bump statements just to look "active."

If you later earn a Wikipedia page, link Wikipedia and Wikidata correctly — they are related but not interchangeable. Until then, a sourced Wikidata item plus clean on-site identity is enough of a knowledge-graph story.

Create only what sources support. Fill properties with references. Link the Q-ID from schema. Skip the rest of the theater.

See how your own site scores

One scan checks your homepage, robots.txt, llms.txt, About page and JSON-LD, then hands you the copy-paste fixes. Free, no account needed for the first run.

Keep reading