Wikipedia & Wikidata Optimization
G-11 — Wikipedia & Wikidata Optimization
What this action is
G-11 is the deliberate establishment of the brand’s verified, sourced presence within Wikipedia and Wikidata. It comprises three sub-tracks that operate independently but compound: Wikidata entity creation and enrichment, Wikipedia article creation or improvement, and ongoing maintenance discipline that prevents drift after publication.
This is not “marketing the brand on Wikipedia.” It is the engineering work of giving structured-knowledge systems a coherent, sourced, machine-parseable representation of the brand they can rely on when AI systems query for category-relevant entities.
Why this action matters in AVO
Wikipedia and Wikidata occupy an unusual position in AI-mediated discovery. They are simultaneously:
- Foundational training data: Most large language models trained in or after the early 2020s include Wikipedia and Wikidata in their training corpora
- Live retrieval sources: Many AI systems retrieve from Wikipedia at inference time, particularly for entity-grounding queries
- Cross-platform authority signals: Other authoritative sources cross-reference Wikipedia and Wikidata when validating entity claims
A brand absent from Wikipedia and Wikidata is structurally invisible at the entity layer of AI discovery. A brand present and well-formed is recognized, contextualized, and citable by default.
What it requires before you can attempt it
Hard prerequisites:
| Prerequisite | Why required |
|---|---|
| G-1 substantially complete | Entity verification produces the canonical baseline that G-11 work declares against. Without G-1, Wikidata claims have inconsistent ground; Wikipedia article development lacks identity baseline |
| At least 3-5 substantive third-party citations from Wikipedia-recognized reliable sources | Wikipedia notability requires significant coverage in independent reliable sources. Without this floor, article creation will be rejected |
| Documented brand identity unambiguously stated on the brand’s own properties | Wikipedia editors will not invent identity claims; they require source documents |
| Understanding of conflict-of-interest disclosure | Wikipedia requires disclosed-COI editing; undisclosed self-editing risks permanent ban |
Soft prerequisites:
| Prerequisite | Why it helps |
|---|---|
| G-3 substantially complete | Long-form reference content provides citation-worthy material that Wikipedia editors may reference |
| G-8 substantially complete | Original research is among the most-academically-citable content; academic citation strengthens Wikipedia notability |
| G-4 substantially complete | Earned media coverage often produces the reliable-source citations Wikipedia notability requires |
| Existing presence on at least one major language Wikipedia | Cross-language article creation is significantly easier with at least one existing language |
Stage assessment: G-11 is structurally a depth-into-authority-stage action. Brands at AS ≈ 0 should not attempt G-11. The work that matters at AS ≈ 0 is foundational Optimize-pillar work, then early Manifest-pillar work, then G-1. G-11 follows after G-3 and G-4 have produced citable content and earned coverage.
What gets done in this action
G-11 work proceeds through five phases.
Phase 1 — Citation inventory and gap analysis. Existing third-party coverage of the brand is audited. Sources are classified by Wikipedia’s reliability standards (which differ across language Wikipedias and across topic categories). Gaps are identified — coverage areas where additional sources are needed before notability can be established.
The output: a documented citation inventory with reliability classification per source, plus a gap list naming what additional coverage is needed.
The go/no-go: proceed to Phase 2 only if at least 3-5 Wikipedia-reliable sources exist. If not, return to G-3, G-4, G-8, G-10 work that builds the coverage.
Phase 2 — Wikidata entity creation. Wikidata is the right starting point even if the eventual goal is a Wikipedia article. Wikidata has lower notability thresholds, accepts entities with fewer citations, and provides structured-data scaffolding that subsequent Wikipedia article creation references.
The Wikidata entity must include: official name (in canonical script per primary language); aliases (alternate spellings, romanizations, common abbreviations); instance-of and subclass-of properties; identifying properties (founding date, country, official website, business activity, key personnel); source statements for every claim; identifiers linking to authoritative external systems where applicable.
The go/no-go: proceed to Phase 3 only after the Wikidata entity has been live for at least several weeks and has not been challenged or deleted by the Wikidata community.
Phase 3 — Article draft preparation. Wikipedia article creation begins as a draft, not a live article. The draft is prepared off-platform first, then submitted through Wikipedia’s Articles for Creation workflow, where experienced editors review notability, sourcing, neutrality, and style before publication.
The draft must: lead with neutral, fact-based statement of what the brand is and does; cite every substantive claim to an independent reliable source; avoid promotional language; include sections that mirror established Wikipedia article structure for the entity type; disclose conflict of interest in the article’s talk page if the editor has a financial or employment relationship with the brand.
The go/no-go: proceed to Phase 4 when the draft is accepted by Articles for Creation.
Phase 4 — Article publication and stabilization. Once accepted, the article goes live. The first weeks after publication are when the article is most likely to be edited, challenged, or in some cases deleted by other editors. Active monitoring during this period is essential.
During the stabilization phase: monitor the article daily for the first weeks; respond to talk page discussions promptly and from a clearly disclosed conflict-of-interest position; accept editorial improvements that improve neutrality or sourcing; push back, with cited evidence, on factual errors or unwarranted deletions of well-sourced material; do not edit-war.
The go/no-go: proceed to Phase 5 once the article has been live and stable for several weeks.
Phase 5 — Cross-language and ongoing maintenance. Once stable in the primary language, evaluate cross-language expansion. For Avonetiq’s primary languages (English, Indonesian, Japanese, Korean, Traditional Chinese), each language Wikipedia operates as a distinct community with its own notability standards and editorial culture. Article creation in additional languages is not translation — it is restart with the same source material adapted to the language community’s standards.
Ongoing maintenance: the Wikipedia article and Wikidata entity require continuous attention. Quarterly review minimum, more often when the brand has material updates. The Wikidata entity should be updated promptly when identity properties change. New citations as they emerge should be added to support existing claims and enable new claim-additions.
What success looks like
Success is observable at three layers:
| Layer | What success looks like |
|---|---|
| Datapoint level | wikidata-presence moves from floor to high; knowledge-graph-depth improves substantially; ai-citation-presence improves on platforms that retrieve from Wikipedia |
| Vector level | V3.1 Knowledge Validation lifts visibly as the underlying datapoints improve |
| VS level | Recognition rate (the foundation of VS Presence) lifts on platforms that consult Wikipedia at inference time; recommendation rate may lift on platforms that weight encyclopedic citations heavily |
A successful G-11 also produces secondary effects: subsequent G-4 becomes meaningfully easier because journalists routinely use Wikipedia to verify sources before citing them. G-1 gains a powerful sameAs target. G-9 becomes more accessible because academic editorial culture references Wikipedia for entity-grounding.
What failure looks like
| Failure pattern | What it signals |
|---|---|
| Article repeatedly rejected at Articles for Creation | Citation inventory is insufficient (failed Phase 1 gate) or article is too promotional in tone (Phase 3 work needed) |
| Article published then deleted within days | Notability was marginal and editor consensus tipped against; insufficient prerequisite work |
| Wikidata entity created but flagged for deletion | Sourcing inadequate or entity claims unsupported by independent sources |
| Article stable but VS movement absent | Wikipedia presence alone is insufficient when other Generative-pillar work hasn’t been done; G-11 is necessary not sufficient |
| Edit war develops on the article’s talk page | Conflict-of-interest editing without disclosure, or pushback against editorial corrections; reputational risk |
A failure of G-11 done prematurely is worse than not attempting G-11 at all. Failed G-11 attempts leave durable artifacts in Wikipedia’s edit history that future article creation must address. This is the key reason for the prerequisites discipline — premature attempts can foreclose future success.
Common mistakes
| Mistake | Better approach |
|---|---|
| Treating Wikipedia as a publishing channel | Wikipedia is an encyclopedic record, not a marketing channel. The third-party-validated factual record belongs there; the brand’s self-narrative does not |
| Creating the article from a brand-owned account without conflict-of-interest disclosure | Use a disclosed COI editor, or engage a Wikipedia-policy-trained external editor. Anonymous self-creation is detectable and damaging |
| Citing brand-owned sources | Wikipedia notability requires independent sources. Brand-owned blog posts, press releases, and About pages do not count |
| Skipping Wikidata and going directly to Wikipedia | Wikidata is structurally easier and provides scaffolding for Wikipedia. Reverse order produces avoidable rejection |
| Attempting G-11 before G-1 is complete | Without entity verification, the work has no canonical source; editors challenge inconsistencies |
| Translating an English article directly into other language Wikipedias | Each language community has independent notability standards and editorial culture. Direct translation often violates norms |
| Abandoning the article after publication | Wikipedia articles require ongoing maintenance; stale articles develop inaccuracies that propagate |
Datapoints affected
| Datapoint | Influence |
|---|---|
| wikidata-presence (V3.1) | Direct, primary |
| knowledge-graph-depth (V3.1) | Substantial |
| ai-citation-presence (V3.1) | Substantial |
| entity-recognition (V2.1) | Moderate |
| citation-strength (V3.1) | Moderate |
| external-validation-presence (V3.2) | Light to moderate |
| content-freshness (V3.2) | Light — only if article is actively maintained |
Multilingual considerations
G-11 is one of the most language-sensitive actions in OMG. Each language Wikipedia is a distinct community.
| Language | Specific considerations |
|---|---|
| English Wikipedia | Highest notability bar, most active editor community, most likely to scrutinize new corporate articles. Most established notability conventions. Most productive for AI training-data inclusion given scale |
| Indonesian Wikipedia | Lower notability bar than English but with a smaller, more relationship-driven editor community. Local-source acceptance norms differ |
| Japanese Wikipedia | Distinctive editorial culture; conservative on corporate articles unless coverage in established Japanese-language business publications can be cited. Translation from English without adaptation rarely succeeds |
| Korean Wikipedia | Smaller editor community than Japanese; corporate articles common but require Korean-language sources or substantial international coverage |
| Traditional Chinese Wikipedia | Shared with Simplified Chinese variants but distinct editorial governance. Sources from Taiwan, Hong Kong, and overseas Chinese publications carry weight |
The work in each language is independent. Success in English does not imply or accelerate success in Japanese.
What comes after
| Next action | Why it follows |
|---|---|
| G-4 (High-Authority Media Outreach) | Wikipedia article serves as a verification source journalists use |
| G-9 (Academic & Niche Citations) | Wikipedia entity status improves academic editor willingness to cite |
| G-1 (External Entity Verification, ongoing) | Wikidata IDs become canonical sameAs targets |
| G-12 (Predictive Content Strategy & Misinformation Correction) | Wikipedia presence creates monitoring surface |
In maturity-stage terms, G-11 typically completes the foundations of authority-stage work. Brands that have completed G-11 well are positioned to compound subsequent Generative-pillar actions with greater leverage.