What a Wikipedia Notability Consultant Actually Does

Short answer: a Wikipedia notability consultant maps the independent sources that exist for a subject, assesses them against Wikipedia's standard, gives an honest go or no-go, and, when the answer is no, sets out a roadmap for building the coverage that would make a page realistic. The consultant cannot promise approval, because volunteer editors make that decision.

Step one: map the sources that already exist

The work begins with a search, not a draft. The consultant looks for every piece of coverage that mentions the subject and sorts it. The useful question for each item is whether it is independent of the subject, whether it gives significant attention rather than a passing mention, and whether the publication is reliable in Wikipedia's sense.

This mapping is usually the longest part of the engagement, and it is the part most often skipped by sellers who quote a price from a logo and a website. A good map records each source, what it says about the subject, and how it was classified. It also records what was excluded, such as press releases, sponsored content, directory entries, and interviews where the subject is the only voice.

The map also shows the gaps. A subject may have plenty of coverage that is mostly about one product launch, or several mentions that are all a sentence long. Seeing that pattern early saves the client from paying for a draft that the sources cannot carry.

Step two: assess notability against the standard

With the sources mapped, the consultant applies Wikipedia's notability standard. In general, that means significant coverage in independent, reliable sources, enough of it to support a neutral article rather than a list of facts. The Wikipedia notability guidelines explained set out the standard in plain terms.

Different subject types are judged with different emphasis. Authors and musicians, for instance, have their own criteria that lean on particular kinds of coverage, and the notability guide for authors and musicians explains how those differences work. A competent consultant knows which criteria apply to the subject in front of them and says so.

Step three: give an honest go or no-go

The assessment ends in a recommendation. A go means the sources are there to support a neutral article, and the next step is drafting from those sources under a disclosed process. A no-go means the sources are not there yet, and drafting now would produce a page that is likely to be declined or deleted.

A no-go is a useful result, not a failure of the engagement. A page that gets deleted is public and difficult to undo, and it often makes the next attempt harder, since reviewers look at the history. The reasons pages get removed are covered in why Wikipedia pages get deleted.

The consultant should say clearly what the decision rests on. If the answer depends on a judgement call, such as whether a regional outlet counts as reliable, the assessment should say that rather than presenting one answer as settled.

Step four: build a roadmap when the answer is no

A roadmap is what turns a no-go into something useful. It describes the kinds of coverage that would strengthen a future case and how a subject can realistically earn it. That might mean a substantive feature in a reliable outlet, a body of independent reporting tied to a real development, or an academic or industry source that discusses the subject in depth.

The roadmap should be honest about timing. Coverage cannot be bought in a way that counts. Sponsored placements, press releases, and paid profiles do not establish independent significance, and a roadmap that relies on them is not a roadmap for Wikipedia. It is a marketing plan with a Wikipedia label.

A good roadmap also says when to reassess. Once the coverage exists, the sources should be mapped again and the go or no-go decision repeated, because the answer can change.

What a go decision leads to

If the assessment is a go, the work moves to drafting. The consultant or a separate editor writes a neutral article from the mapped sources, avoiding promotional language, and the paid work is disclosed on-wiki as the Terms of Use require. The paid-editing disclosure guide covers what that disclosure has to contain.

Submission and review follow. Volunteers decide whether the draft is accepted, and they may ask for changes or decline it. The consultant's assessment cannot settle that question, which is why the assessment should be honest about the risk rather than optimistic about the outcome. A reviewer may read the same sources differently from the consultant, and a well-prepared draft still gets declined sometimes. The useful question to ask a consultant is not whether they can get the page accepted, but how they will respond if the draft is declined and the reviewer's reasons point to a sourcing gap.

Red flags in a notability consultant

A few patterns should end the conversation. A consultant who says any subject can be made notable with enough money is describing a sale, not an assessment. One who will not show the sources they relied on has not shown their reasoning. A consultant who proposes sponsored articles or press releases as proof of significance is offering material that Wikipedia's standard excludes, and that creates its own problem if it is later noticed.

The honest version of this work is slower and less exciting than the sales version. It produces a clear answer, and sometimes that answer is that the subject should wait.

If you want that assessment for your own subject, the Wikipedia page creation service starts with the same source mapping and go or no-go decision described here.

FAQ