Maintaining Wikipedia and Wikidata
Session 5.7 · ~5 min read
Creating a Wikidata item or Wikipedia article is not a one-time task. Both platforms are collaborative and open to editing by anyone. Without ongoing maintenance, your entity data can decay through vandalism, well-meaning but incorrect edits, outdated information, or deletion nominations. This session covers the systems and habits you need to keep your Wikipedia and Wikidata presence accurate and stable.
The Maintenance Workflow
Watchlist Alerts"] --> B{"Changes
detected?"} B -->|Yes| C["Review Each
Change"] C --> D{"Accurate
and sourced?"} D -->|Yes| E["Accept/Ignore"] D -->|No| F{"Vandalism or
factual error?"} F -->|Vandalism| G["Revert Edit
Report if Persistent"] F -->|Error| H["Correct with
Source Citation"] B -->|No| I["No Action
Needed"] E --> J["Monthly: Update
Outdated Facts"] G --> J H --> J I --> J J --> K["Quarterly:
Full Review"] K --> L["Check All
Properties Current"] K --> M["Add New
References"] K --> N["Add New
Identifiers"] K --> O["Verify External
Links Active"] style A fill:#222221,stroke:#c8a882,color:#ede9e3 style G fill:#222221,stroke:#c47a5a,color:#ede9e3 style H fill:#222221,stroke:#c47a5a,color:#ede9e3 style K fill:#222221,stroke:#6b8f71,color:#ede9e3
Watchlists: Your Monitoring System
Both Wikipedia and Wikidata have a built-in watchlist feature. When you add a page to your watchlist, you receive notifications whenever anyone edits it. This is your primary monitoring tool.
What to Watch
| Platform | Pages to Watch | Why |
|---|---|---|
| Wikidata | Your entity's item page | Detect property changes, additions, or removals |
| Wikidata | Your founder/key person item | Person-entity link changes affect your entity |
| Wikidata | Related entity items (parent company, subsidiaries) | Changes to related entities can cascade |
| Wikipedia | Your entity's article | Detect content changes, vandalism, deletion nominations |
| Wikipedia | Your entity article's talk page | Editorial discussions about your article happen here |
| Wikipedia | Articles about your industry or competitors | Context for how your entity is positioned in the encyclopedia |
To add a page to your watchlist, click the star icon at the top of any Wikipedia or Wikidata page while logged in. Configure your email notification preferences in your user settings to receive alerts for watched pages.
Handling Vandalism
Vandalism on Wikipedia ranges from obvious (profanity, blanking content) to subtle (changing dates, altering descriptions, removing references). Wikidata vandalism is typically property changes: swapping values, removing statements, or adding false data.
Response protocol:
- Revert the edit immediately. Wikipedia has a rollback feature for obvious vandalism. On Wikidata, undo the specific change.
- Do not engage with the vandal in edit comments. Keep it factual: "Reverted: unsourced change" or "Reverted: vandalism."
- Report persistent vandalism through Wikipedia's Administrator Intervention Against Vandalism (AIV) board or Wikidata's equivalent.
- Request page protection if vandalism is recurring. Wikipedia administrators can restrict editing to autoconfirmed users.
The Quarterly Review
Beyond reactive monitoring, conduct a structured review of your Wikipedia and Wikidata presence every quarter. This review ensures your entity data stays current as your business evolves.
| Review Item | What to Check | Action if Needed |
|---|---|---|
| Wikidata: Core properties | Are headquarters, employee count, industry, and other facts still accurate? | Update with new sourced values. Add "point in time" qualifiers to historical values. |
| Wikidata: External identifiers | Have you obtained new identifiers (ISNI, VIAF, LEI) since last review? | Add new identifiers with references. |
| Wikidata: References | Are reference URLs still active? Have new sources been published? | Replace dead URLs. Add new references. |
| Wikidata: Labels and descriptions | Are labels in all relevant languages? Is the description current? | Add missing language labels. Update description if business has changed. |
| Wikipedia: Factual accuracy | Is all information in the article still correct? | Suggest corrections on the talk page (COI) or make minor factual corrections with sources. |
| Wikipedia: New developments | Has anything notable happened since the article was last updated? | Add sourced information about new developments. Use talk page if COI applies. |
| Wikipedia: External links | Are all external links in the article still active? | Update or remove dead links. |
| Wikipedia: Source availability | Are cited sources still accessible online? | Use Wayback Machine archives for dead source links. Add archive URLs. |
Updating Wikidata Properties
Some Wikidata properties change over time: employee count, revenue, headquarters location, key personnel. When updating these, do not simply overwrite the old value. Use the preferred/normal/deprecated ranking system:
- Preferred rank: The current, most accurate value.
- Normal rank: Historical values that were true at a specific time.
- Deprecated rank: Values that were incorrect or should not be used.
For example, if your employee count changed from 100 (in 2020) to 150 (in 2026), keep both values. Set the 2026 value to "preferred" rank and the 2020 value to "normal" rank. Add a "point in time" (P585) qualifier to each, specifying the date the count was accurate.
This preserves historical data while ensuring current data is prioritized. Google's Knowledge Graph respects these rankings and will use the preferred-rank value.
Wikipedia and Wikidata are living documents. They require the same maintenance attention as your website or GBP. An unmaintained Wikidata item with outdated facts and dead references gradually loses its value as an entity signal. A quarterly review keeps your entity data clean, current, and credible.
COI-Compliant Maintenance
If you have a conflict of interest (and if you are maintaining your own entity's pages, you do), be transparent about it. For Wikidata, COI editing is generally more accepted because the edits are purely factual and verifiable. For Wikipedia, stick to the talk page for anything beyond minor, uncontroversial factual corrections (like updating a phone number or fixing a dead link).
Document your maintenance activities. Keep a log of what you changed, when, and why. This protects you if an editor questions your edits: you can point to a clear record of sourced, factual updates.
Module Summary
Over this module, you have learned:
- Why Wikipedia and Wikidata are the highest-trust entity signals outside of Google's own systems.
- How Wikidata's item-property-statement structure maps to entity attributes.
- How to create a Wikidata item with minimum viable properties and proper references.
- Which external identifiers to prioritize for Knowledge Graph impact.
- How to honestly assess Wikipedia notability and avoid premature article creation.
- How to write in encyclopedic tone and navigate COI requirements.
- How to maintain your Wikipedia and Wikidata presence over time.
For many entities, the Wikidata item alone provides significant Knowledge Graph value. Wikipedia is the higher bar, but it is not the only path. A well-maintained Wikidata item with rich properties and external identifiers is a powerful entity signal in its own right.
Further Reading
- Wikipedia. "Help: Watchlist." Wikipedia Help.
- Wikipedia. "Wikipedia: Vandalism." Wikipedia Policies.
- Wikidata. "Help: Ranking." Wikidata Help.
- Wayback Machine. "Internet Archive Wayback Machine." For archiving cited sources.
Assignment
- Add your Wikidata item, your Wikipedia article (if it exists), and related pages to your watchlist. Configure email notifications.
- Conduct your first quarterly review using the review table above. Document every item checked and any actions taken.
- If any Wikidata properties have changed since item creation, update them using the preferred/normal ranking system with "point in time" qualifiers.
- Check all reference URLs in your Wikidata item and Wikipedia article. For any dead links, find the Wayback Machine archived version and update the reference.
- Set a recurring quarterly calendar reminder for your next Wikipedia/Wikidata review. Include the review checklist in the calendar event description.