methodology / Brand Presence / #21
Wikipedia entity
#21 · Variable · Web Quality · weighted · Brand Presence · weight 0.7% · impl implemented · method v1.2.0
Web Quality factor
This factor is part of Web Quality — the weighted 0..100 score that sits above Web Standards. Its weight depends on what kind of site is being measured. Web Standards items take priority; this factor only enters the score once Web Standards passes.
- Base weight
- 0.2 applied to every site type unless overridden below
- Why this weight
- Wikipedia entity — notability correlates with size more than quality, so held under news mentions. Corporate bumped 0.5 → 0.7 because in practice an established corporate having a Wikipedia entry is a real legitimacy signal that legacy scoring captured and the matrix shouldn't fully neutralise.
Per-site-type overrides
| Site type | Weight | Δ vs base |
|---|---|---|
| Blog | 0.0 | -0.2 |
| Corporate / B2B | 0.7 | +0.5 |
| News / Publisher | 0.7 | +0.5 |
| Personal site | 0.0 | -0.2 |
| Education | 0.6 | +0.4 |
| Government | 0.6 | +0.4 |
| Nonprofit | 0.4 | +0.2 |
| Media / Streaming | 0.7 | +0.5 |
Site types not listed inherit the base weight.
What this means for your business
A Wikipedia page is one of the strongest signals to Google and AI assistants that you're a real, notable business. Most small businesses don't have one — but if you're big enough, missing it is a wasted credibility win.
Plain title: Whether you have a Wikipedia entry
What we measure
A Wikipedia entry is a high-trust signal recognized by Google's Knowledge Graph. Most small businesses don't have one — those that do get a major credibility boost.
How to improve your score
Wikipedia entries can't be created by request — they have to meet notability standards. Keep building public press coverage and citations until eligibility is natural.
Implementation
stale · v1 · seeded — no connector publish yet · source: freshcoat-discovery/src/connectors/legacy-audit.ts:scoreWikipedia + wikipediaLookup fallback
Detection method
Reads wikipedia_entity_found from the audit endpoint's resolver. When the upstream says 'not found,' the post-score wikipediaLookup fallback queries en.wikipedia.org/api/rest_v1/page/summary/<title> with candidate titles derived from the domain (capitalised primary label + hyphen-split variants). Confirmed presence wins; confirmed absence does not override.
Detection sources
- Audit endpoint entity resolver (primary)
- Wikipedia REST API page-summary fallback (only on upstream miss)
Scoring bands · soft ladder
| Score | Condition |
|---|---|
| 100 | Wikipedia article exists (audit-confirmed or REST-API-confirmed) |
| 70 | no Wikipedia article (notability proxy — held above WARN_SOFT to keep some signal) |
Evidence-key dictionary
What every notes string the connector emits means.
Surfaces in the per-domain dossier evidence column.
wikipedia_entity_present- Audit endpoint confirmed an article.
wikipedia_entity_present_via_rest_api- Audit said 'not found' but the REST API fallback confirmed an article.
no_wikipedia_entity- Both upstream and fallback found no article.
Applicability
Variable tier. Wikipedia notability correlates with size more than quality, so weighted low (0.2 base, 0.7 corporate). Fallback added Apr 29 after Vercel was wrongly scored 70 despite having a Wikipedia article.
Changelog
- 2026-04-29 · seed Initial seed from MethodologyRegistry bootstrap.
Facts
Scoring
Scoring formulas are versioned with the methodology. The current method (v1.2.0) maps raw measurements to pass, warn, fail. Factor weights determine how much each contributes to the composite — see the methodology index for the full table.
Version history
| Version | Change | Date |
|---|---|---|
| v1.2.0 | Factor introduced. Status: live. Scoring impl: implemented. | 2026-04-25 |