How to Add Your Business to Wikidata (2026 Step-by-Step)

1 Search for an existing entry

Go to wikidata.org and search your company name. Wikidata items are sometimes auto-created by bots that scrape Wikipedia, business directories, or Crunchbase. If your business already has an entry, you do not create a new one, you edit and improve the existing one.

Search variations to try: exact business name, business name plus city, founder name, brand name. Look for an item with a Q-ID (e.g., Q12345). Click through to confirm it's actually your business.

Common scenario: a stub entry with just name and category exists. Your job becomes filling in the verifiable claims (founding date, HQ, founder, services, identifiers). This is faster and lower-friction than creating from scratch.

2 Verify your business meets one of three notability criteria

Self-check before creating: do you meet at least ONE of these?

• Sitelink criterion: Already have a Wikipedia article (any language)? Pass.
• Identifiable entity criterion: Verifiable physical address, founding date, founder name, business registration? Pass.
• Structural need criterion: Your business is referenced or needed to validate claims in other Wikidata entities (e.g., your business is a notable client mentioned in another company's entry)? Pass.

If none apply (you are a brand-new sole proprietor with no third-party documentation), wait 6 to 12 months until you accumulate documentary evidence (press, association memberships, registrations) before attempting.

3 Create a new item with label, description, aliases

Sign in to Wikidata (free account; SUL Wikipedia account works). On the left sidebar click "Create a new Item."

Required fields:

• Label: Your official business name as it appears on legal documents and your website.
• Description: A short disambiguating description. NOT marketing copy. Format: "[business type] in [city], [region/country], founded [year]." Example: "mattress retailer in Brantford, Ontario, Canada, founded 1987."
• Aliases: Common variations of your name. Including DBAs, abbreviations, and any historical names. These help disambiguation when AI engines or search algorithms try to match queries to entities.

Save. You now have a Q-ID (e.g., Q123456789). Note this for all your downstream schema and citations.

4 Add core verifiable statements

Statements are claims with properties (P-IDs) and values. Core statements every business entity should have:

• P31 (instance of): business, retailer, service company, professional services firm, etc.
• P17 (country): Canada (Q16), United States (Q30), etc.
• P159 (headquarters location): city item (Brantford, Q174416, etc.)
• P571 (inception): founding date as YYYY format
• P112 (founded by): founder name (link to Person item if exists)
• P856 (official website): your URL
• P452 (industry): your industry sector
• P625 (coordinate location): exact lat/long for local businesses
• P1454 (legal form): incorporated, sole proprietorship, etc.

Each statement gets a value, a qualifier where appropriate (e.g., start date, end date), and a reference (next step).

5 Add references to every statement

References are mandatory for credibility and for surviving review. Every claim should have at least one reference. Stronger references = better entity quality score in Google's view.

Reference quality hierarchy (best to weakest):

1. Government registries (provincial business registry, federal incorporation, BBB)
2. Established news media (local newspaper, industry trade publications)
3. Established business databases (Crunchbase, Bloomberg, LinkedIn company page)
4. Professional association directory listings
5. Your official website (acceptable for some basic facts but should not be sole reference)

Add references via the "add reference" link on each statement. Use property "reference URL" (P854) for web sources, "stated in" (P248) for databases, "publication date" (P577), "title" (P1476), and "publisher" (P123) where applicable.

Avoid: purely promotional content, paid placements, your own social media, press releases without third-party pickup.

6 Connect to related entities

Wikidata's value compounds when entities are connected. Link your business to:

• Your founder(s) as separate Person items (create them if they don't exist)
• Your headquarters city item (Brantford = Q174416)
• Your industry sector item
• Notable products or services as Product items where notable
• Notable subsidiaries, parent companies, or partners
• Notable awards or certifications you hold
• Industry association memberships

The connected graph is what AI engines extract for entity disambiguation and recommendation answers. Isolated entities with no connections rank lower than entities that sit inside a clear network.

7 Add identifiers

Wikidata supports hundreds of identifier properties that link to external systems. Adding these reinforces entity disambiguation across the web.

Identifiers to add when applicable:

• P2002 (Twitter/X username)
• P4264 (LinkedIn company ID)
• P2013 (Facebook page ID)
• P2003 (Instagram username)
• P3417 (Quora topic ID) where applicable
• P2397 (YouTube channel ID)
• P2429 (Crunchbase organization ID)
• P5046 (BBB business profile)
• P3220 (Yelp ID)
• P9931 (Google Business Profile place ID) if available

Each identifier reinforces the connection between your Wikidata entity and your real-world web presence. AI engines cross-reference these identifiers when matching queries to brands.

8 Maintain quarterly with substantive updates

Stale Wikidata entries lose entity-quality score over time. The maintenance discipline:

• Quarterly review of all statements for accuracy
• Add new statements as your business evolves (new locations, new services, new key staff, new awards)
• Update existing statements when facts change (new HQ address, new founder bio link)
• Add new references as new third-party coverage emerges
• Watch the "talk page" for any community discussion about your entity

Substantial maintenance is also a downstream signal: AI engines look at edit recency and depth as a quality indicator. A frequently-maintained entity outranks a one-time-create-and-forget entity.