Discussion
  • Entity SEO

Is editing Wikidata still a legitimate entity strategy, or too risky given community moderation and conflict-of-interest rules?

Published 1 reply

Discussion starter: an entity SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    Editing Wikidata is still legitimate when the organisation or person genuinely meets Wikidata’s notability policy and you add verifiable statements with references, openly. It becomes risky when it is treated as a publishing channel: items created for things with no public references, promotional descriptions, undisclosed paid editing, or edits that fight other editors. The strategic value is also smaller than it is sometimes sold as. Wikidata is one public source among many that search engines and AI systems can draw on, and a correct item makes your entity data easier to reconcile. It does not guarantee a knowledge panel or better rankings.

    What the rules actually require

    Wikidata’s notability policy is broader than Wikipedia’s. An item can qualify if it has a link to a Wikimedia page (such as a Wikipedia article), if it refers to a clearly identifiable entity that can be described using serious and publicly available references, or if it is needed to make statements on other items. A real company with a registered entity, press coverage or official records often clears the second test. A product launched last week with only its own press release usually does not.

    Two further rules matter for anyone editing on behalf of a business:

    • Paid editing must be disclosed. The Wikimedia Terms of Use require anyone paid to contribute to disclose their employer, client and affiliation. That applies on Wikidata as well as Wikipedia. An agency editing a client’s item without disclosure is breaking the terms, whatever the quality of the edit.
    • Statements need references. Unreferenced claims about living people or companies are the first to be questioned or removed. Basic facts can often be referenced to official sources (a company registry, the official website for the website URL, an annual report), while claims that sound promotional need independent sources.

    Wikidata does not operate with Wikipedia’s article-level editorial debate, but the community does patrol recent changes, and items that look promotional get flagged, merged or nominated for deletion. Treat every edit as something a volunteer may review within days.

    Where it helps and where it does not

    Use Value Risk
    Correcting wrong facts on an existing item (founding date, headquarters, official website) High, because bad data spreads to other systems that reuse Wikidata Low when referenced and disclosed
    Adding identifiers (company registry, ISNI, LEI, social profile IDs) Useful for reconciliation: they connect your entity across databases Low
    Creating an item for a notable organisation that lacks one Moderate, gives other systems a stable identifier to reference Moderate if notability is borderline
    Items for individual products, executives or minor sub-brands Low High: often fails notability and draws attention to the rest
    Descriptions written as marketing copy None High: reverted and noticed

    The value is mostly in consistency. When your Organization markup uses sameAs to point at your Wikidata item, and that item points back to your official website and the same profiles, you have given machines a clean chain of identifiers. Whether any particular system uses it, and how much weight it gives it, is not documented. Google says its Knowledge Graph draws facts from many sources, and knowledge panels often cite Wikipedia rather than Wikidata. I would describe the Wikidata item as supporting infrastructure, not a lever.

    A safe way to do it

    1. Check notability honestly first. If you cannot list two or three serious public references about the entity that you did not write, stop. Build the public record first.
    2. Edit from a named account with disclosure. State the affiliation on the user page. For agencies, name the client.
    3. Start with corrections and identifiers, each with a reference. Leave descriptions short and neutral, in the style of other items in the same class.
    4. Do not remove unflattering but referenced statements. If something is wrong, add a better-referenced statement and explain on the talk page.
    5. Link it from your own markup with sameAs, and make sure the facts on your About page match the item.
    6. Watch the item. Add it to your watchlist so you see edits by others, including vandalism, and respond on the talk page rather than by reverting repeatedly.

    Watch for this:

    Creating a Wikidata item to “prepare” for a Wikipedia article that does not exist yet is a common agency move and a common reason items get deleted. If the only reference is the company’s own site, the item fails the test that lets it exist without a Wikimedia link.

    Why accuracy matters more than presence

    The best argument for paying attention to Wikidata is defensive. Wikidata is openly licensed and widely reused: other databases, apps and data products pull from it, and large language models are trained on corpora that include Wikimedia content. A wrong founding year, an old headquarters or a merged-up item that confuses your company with a similarly named one can travel further than a typo on your own site, and it is harder to trace once it has been copied. Correcting a wrong item is often more valuable than creating a new one.

    A related case is the item that describes the wrong entity. Companies with common names regularly find their logo, website or leadership attached to a different organisation’s item, or two items that should be one. The fix is a referenced correction and, where two items describe the same entity, a merge request following Wikidata’s merge process. Leave a note on the talk page explaining the change, so the next editor understands why the statements moved.

    People items need extra care

    Founders and executives are living people, and Wikidata’s guidance on living people asks editors to be careful with personal information and to reference claims well. Adding a birth date sourced only to a LinkedIn profile, or a home location, is the kind of edit that gets removed and can create a privacy problem for the person. For executives, I would limit items to people who are independently notable, and limit statements to their role, employer, official profiles and public identifiers. If an executive does not have public coverage, their presence on your own About page is enough.

    Who should do the editing

    For a single company, someone in-house who reads the policies and edits transparently is usually better than an agency, because the affiliation is simple to disclose and the knowledge of the facts is first-hand. For agencies handling many clients, the risk is pattern behaviour: the same account creating dozens of thin company items looks like promotion even when every edit is disclosed. If you cannot answer “would a volunteer with no link to this company have created this item?” with a clear yes, it is probably not worth creating.

    How to judge whether it worked

    Do not measure Wikidata work in rankings. Measure it in entity accuracy: whether the knowledge panel (if one exists) shows the right founding date, logo, website and leadership; whether Google’s Knowledge Graph Search API returns an entity for the brand; whether AI assistants describe the company with correct basic facts; and whether the item survives without deletion notices. If those improve, the work paid off. If a knowledge panel does not appear, the more common missing ingredient is independent coverage, not another Wikidata property.

    Do it for organisations that clearly qualify, do it transparently, keep it factual, and treat it as hygiene for your entity data rather than a strategy on its own. If the entity does not qualify yet, the right work is earning public references, and Wikidata can come later.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.