Fortune Global 500
5WikiBusines Enterprise
Wikipedia for corporations: one contract, one standard
Wikipedia, Wikidata and AI visibility programs for corporations with many brands, markets and stakeholders. One contract, one editorial standard and one activity log across every language edition.
Since 2010 in the market160+ language editions80+ client countries
Portfolio boardDemo, sample brands
ENDEFRESITARHEZHJAPTUKPLGroup ABrand BBrand CBrand DBrand E
Published 20In review 6Audit 6On watch 1Wikidata only 5
02 Corporate experience
Wikipedia services for Fortune Global 500 groups: experience with leading stock-index companies
Leading indices
11major-index groups
Four regions of the world
7global stock indices
S&P 500DAXCAC 40IBEX 35Nifty 50TA-35Nikkei 225
Selected engagements include subsidiaries and divisions. Groups may fall into more than one category. November 2026.
Rollout in four language editions
Pages published in four Wikipedia language editions across the group's operating markets, each backed by local independent sources.
Deletion defence
An existing page was nominated for deletion. The discussion closed as keep, and the client then moved to annual support.
Project working documents
The source matrix, change log, monitoring alerts and language rollout calendar are available once an NDA is signed.
03 When to choose Enterprise
When a corporation needs Enterprise: managing a Wikipedia presence
A company page solves one task: creating the article. Enterprise is for the point where articles, languages and approvers have multiplied.
- A funding round, IPO or M&A in the next 12 months
- A launch in three or more Wikipedia language editions
- Legal or Communications need a documented approval trail
- Cross-border regulatory disclosure or a compliance context
- A reputation event that needs a coordinated response
CompaniesEnterprise
Scope
One article
A portfolio of brands and languages
Structure
A company record
Group, subsidiaries, brands
Approvals
One contact
Legal, Communications, PR
After launch
Need one page? Wikipedia for Companies90 days or an annual plan
Governance, SLA, reporting
04 One portfolio, many markets
Wikipedia language edition portfolio: a status and an owner for each edition
Each language edition has its own community and its own sourcing bar. We run them in one table. Pick a cell to open that market.
Global portfolioDemo
3 brands4 language editions4 published5 in progress
English Wikipedia
Group A
Published- Source readiness
- Status
- The article is published and under Enterprise Governance.
- Next action
- Update the figures after the annual report.
- Owner
- WikiBusines Editorial
German Wikipedia
Group A
In review- Source readiness
- Status
- The draft is adapted to German sources. The client is checking the facts.
- Next action
- Close two Legal comments.
- Owner
- Legal
Spanish Wikipedia
Group A
Published- Source readiness
- Status
- The article is published on local Spanish sources.
- Next action
- Scheduled update from the calendar.
- Owner
- WikiBusines Editorial
French Wikipedia
Group A
Audit- Source readiness
- Status
- French coverage is being assessed separately from English.
- Next action
- Finish the source matrix.
- Owner
- WikiBusines Editorial
English Wikipedia
Brand B
Audit- Source readiness
- Status
- Independent coverage needs further assessment.
- Next action
- Complete the detailed source review.
- Owner
- WikiBusines Editorial
German Wikipedia
Brand B
Published- Source readiness
- Status
- Strong local coverage, the article is stable.
- Next action
- Monitoring continues unchanged.
- Owner
- WikiBusines Editorial
Spanish Wikipedia
Brand B
Audit- Source readiness
- Status
- Coverage is still narrow, mostly trade mentions.
- Next action
- Decide with Communications whether to build coverage.
- Owner
- Corporate Communications
French Wikipedia
Brand B
Wikidata only- Source readiness
- Status
- The brand lacks notability of its own and is covered in the group article.
- Next action
- Maintain the Wikidata item.
- Owner
- WikiBusines Editorial
English Wikipedia
Brand C
Published- Source readiness
- Status
- The article is published and edits are stable.
- Next action
- Quarterly report.
- Owner
- WikiBusines Editorial
German Wikipedia
Brand C
On watch- Source readiness
- Status
- Edit activity rose after a trade news story.
- Next action
- Closer watch until the end of the quarter.
- Owner
- WikiBusines Editorial
Spanish Wikipedia
Brand C
In review- Source readiness
- Status
- The draft is in review for factual accuracy.
- Next action
- Get Corporate Communications sign-off.
- Owner
- Corporate Communications
French Wikipedia
Brand C
Wikidata only- Source readiness
- Status
- In the French market the brand is represented by a Wikidata item for now.
- Next action
- Reassess after new independent coverage.
- Owner
- WikiBusines Editorial
All statuses and ratings in the demo are illustrative. Notability is only decided after a source audit.
Each language edition is assessed on its own
We publish
Local independent sources hold up against the review of that language community.
We pick another format
For a market without enough coverage we recommend a Wikidata item or Simple English.
We wait for sources
The page goes out once the source base can carry it. Until then we work on coverage.
05 Multi-brand groups
Parent companies and brands on Wikipedia and Wikidata: ownership structure for people and machines
AI routinely confuses parent companies and their brands. A parent-company page and a clean Wikidata structure show who owns what. After a deal or a rebrand we update articles and records together.
Group AGroup articleOutdated name
Subsidiary BWikidata itemDuplicate item
Brand COwn articleNo owner
Subsidiary DWikidata itemShown as independent
Group AGroup articleP355 → B, D
Subsidiary BWikidata itemP749 → A
Brand COwn articleP127 → B
Subsidiary DWikidata itemP749 → A
Question to an AI assistant
Who owns Brand C?
Brand C is probably an independent company. It may also be linked to Subsidiary D.Answer assembled from scattered sources
Brand C belongs to Subsidiary B, which is part of Group A.Source: Wikipedia, Wikidata
- P749
- parent organization
- P355
- has subsidiary
- P127
- owned by
- P1830
- owner of
- P1278
- LEI identifier
A brand with notability of its own
Gets its own article, its own sources and a Wikidata item linked to the group.
A brand without it
Lives as a section of the group article and a Wikidata item. The group stays whole, and no extra articles invite deletion.
06 Engagement models
Corporate engagement models: three models by scale
The cost depends on the number of language editions, brands and the support level. You receive a fixed proposal after the source audit.
For one company or the lead brand
Corporate Foundation
- Source audit
- Wikipedia and Wikidata
- Editorial approvals
- 90 days of monitoring, support and guarantee
International Expansion
- Multilingual rollout on a calendar
- Source matrix by market
- Local editorial requirements
- Portfolio reporting
Continuous Governance
- Continuous monitoring
- Handling of hard cases
- Editorial consulting
- Quarterly reporting and a contractual SLA
Price a typical international package
English is the anchor. The editions groups add most often are Spanish, French and Chinese, together with a Wikidata record for the group. Remove any of them to see the difference.
Detailed packages for large corporations are also described on wikibusines.co.uk.
07 Approvals
Approvals for Wikipedia articles: who approves what before the project starts
Legal and Corporate Communications control facts, risks and commercial decisions. Your team approves the source pack once, before the first line of the draft.
Legal
Contract, legal risk, review of factual claims
Approves
Checks facts
Gets status
Joins on risk
Corporate Communications
Brief, factual data, stakeholder sign-off
Approves
Approves data
Gets status
Gets the report
PR
Publications, spokespeople, context for sources
Provides materials
Comments
Gets status
Coordinates comms
WikiBusines Editorial
Sources, neutral draft, disclosure, editorial actions
Builds the matrix
Writes the article
Submits with disclosure
Monitors and responds
Wikipedia community
Independent review and decisions under Wikipedia's rules
Not involved
Not involved
Decides
Decides
The Wikipedia community decides independently. All paid participation is disclosed under the conflict-of-interest requirements.
08 Contract and procurement
Contract and procurement: from NDA to the first published language edition
Step 1 of 5
NDA and brief
A mutual NDA before kickoff. Brand brief, source list, target language editions, key dates.
Your part
You sign the NDA and name a contact.
Step 2 of 5
Source approval
A written assessment with a go or no-go for each source. Your Legal team signs off in one round.
Your part
You approve the source pack.
Step 3 of 5
Rollout calendar
A coordinated publication schedule across editions. You see every milestone date upfront.
Your part
You align the calendar with internal events.
Step 4 of 5
Phased publication
Language editions go out on the calendar, handled by experienced editors with disclosed status.
Your part
You check each draft for factual accuracy.
Step 5 of 5
Monitoring and reporting
90 days of monitoring, support and guarantee in every project, then an annual plan. A quarterly report for leadership.
Your part
You pick a support level for each page.
SLA-backed delivery
A milestone contract with defined response times for source approvals, draft delivery and monitoring escalations.
Language rollout calendar
Publication is sequenced across editions so that a same-week launch does not draw reviewer attention.
Source approval
Your Legal or Communications team approves the source pack before writing starts. One sign-off, no rolling questions.
One billing contact
One invoice per quarter or milestone. Simpler for procurement, cleaner for accounting.
NDA from day one
A mutual NDA is signed before the kickoff call. We routinely work with teams that need confidentiality from the start.
Fast Lane
Repeat clients get scheduling priority when there is a hard date: an IPO, an M&A close, a regulatory announcement.
09 Hard editorial situations
Disputed edits and deletion of a Wikipedia page: one protocol for every situation
A disputed edit, a deletion nomination, criticism in the press or a deal that changes the group structure. Pick a situation and see it pass through six steps.
Step 1 of 6: Detect
Disputed edit
A sensitive claim with no source has appeared in the group article.
Step 2 of 6: Compare
Disputed edit
We see who changed what, and what the text said before.
Step 3 of 6: Verify
Disputed edit
The claim is not supported. A reliable source describes the event differently.
Step 4 of 6: Assess
Disputed edit
The topic is sensitive, so Legal joins the next step.
Step 5 of 6: Respond
Disputed edit
We propose wording from the source on the talk page, under a disclosed account.
Step 6 of 6: Report
Risk: highDisputed edit
The action, the arguments and the outcome go into the log and the quarterly report.
Group A: difference between revisionsDemo
−The group hid the debts of a subsidiary.
+A regulator opened a review of the subsidiary's reporting.[7]
WikiBusines editor (disclosed): talk page discussion opened
Step 1 of 6: Detect
Deletion nomination
The brand article has been tagged for deletion.
Step 2 of 6: Compare
Deletion nomination
We check which edits came before the nomination and who filed it.
Step 3 of 6: Verify
Deletion nomination
We test the sources against the notability standard of this language edition.
Step 4 of 6: Assess
Deletion nomination
The guarantee applies, and the client gets an alert.
Step 5 of 6: Respond
Deletion nomination
We argue notability in the discussion, under a disclosed account.
Step 6 of 6: Report
Risk: highDeletion nomination
The community's decision and our actions go into the log.
Brand B: difference between revisionsDemo
−{{Article for deletion}}
+Three independent sources added to the notability discussion.
WikiBusines editor (disclosed): nomination contested
Step 1 of 6: Detect
Criticism in the press
A new section based on a recent publication has appeared in the article.
Step 2 of 6: Compare
Criticism in the press
We compare the new text with what the source actually says.
Step 3 of 6: Verify
Criticism in the press
Reliable criticism stays in the article, at the weight the sources give it.
Step 4 of 6: Assess
Criticism in the press
The risk is medium, and Communications gets an alert.
Step 5 of 6: Respond
Criticism in the press
We make the wording neutral and tie it to the source.
Step 6 of 6: Report
Risk: mediumCriticism in the press
The edit and its reasoning go into the log.
Brand C: difference between revisionsDemo
−In 2026 a scandal broke around the product.
+In 2026 the company recalled a batch of the product.[4]
WikiBusines editor (disclosed): neutral wording from the source
Step 1 of 6: Detect
M&A and rebrand
After the deal closes, articles and records still show the old owner.
Step 2 of 6: Compare
M&A and rebrand
We list every page and record the change touches.
Step 3 of 6: Verify
M&A and rebrand
We wait for independent coverage of the deal, because a press release is not enough.
Step 4 of 6: Assess
M&A and rebrand
We schedule the change on the calendar with Corporate Communications.
Step 5 of 6: Respond
M&A and rebrand
We update the language editions and Wikidata in step.
Step 6 of 6: Report
Risk: plannedM&A and rebrand
The log shows every updated page and its date.
Group A: difference between revisionsDemo
−Owner: Group E
+Owner: Group A, after the 2026 deal.[9]
WikiBusines editor (disclosed): updated from the source
10 Enterprise Governance
Enterprise Governance: SLA, reporting, history of editorial actions
Enterprise Governance gives sensitive pages predictable management. Leadership sees risks, decisions and actions in one document.
For Legal, PR and compliance
Enterprise Governance
€3,700 / year- 12-month guarantee
- Priority near real-time monitoring and alerts
- Handling of sensitive edits, disputes and deletion risk
- Risk-based governance
- Quarterly leadership report and activity log
- SLA-defined response
Quarterly leadership reportQ3, Group A
Sample, illustrative data38edits reviewed
6editorial actions
2Legal escalations
0open risks
Edits by week of the quarter
Week 1ReviewedWith our actionWeek 13
| Date | Page | Event | Action | Status |
|---|---|---|---|---|
| 04.08 | Group A, EN | Unsourced edit | Discussion, reverted | Closed |
| 19.08 | Brand B, DE | Sources tag | Two sources added | Closed |
| 02.09 | Group A, ES | New financial report | Figures updated | Closed |
| 17.09 | Brand C, EN | Ownership dispute | Escalated to Legal | Closed |
Showing 4 of 6 actionsEvery action links to its revision in the page history
Which level for which page
The cost of a portfolio depends on the agreed coverage: each page gets the level it needs. Any plan gives a 12-month guarantee.
Annual Support€720 / year
Stable secondary pages
Managed Protection€1,500 / year
Key pages with active monitoring
Enterprise Governance€3,700 / year
Sensitive corporate pages, reporting and SLA
10 pages on Annual Support. Quarterly maintenance with no continuous monitoring.
€7,200 / yearEnglish on Managed Protection, 9 secondary languages on Annual Support.
€7,980 / yearEnglish on Enterprise Governance, 4 key languages on Managed Protection, 5 secondary on Annual Support. Includes a 15% portfolio discount.
€11,300 / year11 Guarantees
Guarantees for corporate Wikipedia pages: separately for each language edition
The standard is 90 days of monitoring, support and guarantee, after which the page is the client's responsibility. Any annual support plan gives a 12-month guarantee.
90 days12 months
Days 0–90: monitoring, support and guarantee are part of the project.After 90 days: the page is the client's responsibility.With a plan: the guarantee runs for 12 months.
We detect
We see the change
An edit, a tag or a deletion nomination.
We defend
We argue notability
We respond on the talk page under a disclosed account.
Up to 3 attempts
We restore the article
We prepare a plan and make up to three reasoned attempts.
Result
The page stands or 80% back
If a language edition cannot be defended, we refund 80% of its cost.
12 Corporate questions
Wikipedia for corporations: frequently asked questions from Legal, procurement and communications
How is Enterprise different from a company page?
A company page creates one article. Enterprise manages a portfolio: several language editions, brands, the Wikidata structure, internal corporate approvals and reporting to leadership.
What is the SLA response time?
Response times are set in the contract, based on coverage and the risk level of the pages. For project stages we define response times for source approvals, draft delivery and monitoring escalations.
Can Legal approve the article text?
Your team checks factual accuracy and approves the sources before submission. The article stays neutral and is written under Wikipedia's rules, and after publication the community can edit it.
Do you guarantee the article will be accepted and not deleted?
The decision belongs to the independent community. We answer for everything that leads up to it: 93% of the pages we take on pass review, and a published page is covered by the guarantee and an 80% refund for any language edition that cannot be restored after 3 attempts.
Does every brand in the group need an article?
No. A brand with its own independent coverage gets an article. The other brands live as a section of the group article and a Wikidata item linked to the parent organization.
How is a portfolio priced?
Creation is priced by language edition, annual support by page. English can sit on Enterprise Governance, key languages on Managed Protection and secondary ones on Annual Support. The proposal after the audit gives the exact amount.
Can you block unwanted edits?
Only Wikipedia administrators can protect an article. We see changes and respond under the protocol, with a disclosed account and within the rules.
How does payment work?
Prices are fixed in euros. For Enterprise we work in milestones: one invoice per quarter or milestone. We accept SWIFT, SEPA, Wise, Payoneer, PayPal, Visa and Mastercard, and USDT (TRC-20).
Order a Wikipedia Enterprise program: planning in 30 minutes
Send a short note on the brand, the target language editions and the event you are preparing for. The call is with the team that would do the work. You get scope, sequencing and a fixed proposal within 5 business days.