Before you pitch a client's story, see what MAP can observe about the page.

You're already vetting sources under deadline pressure. MAP Verified documents what can be observed about an article URL at the moment MAP sees it — where it appears to originate, who's cited, how it's framed and, if MAP has observed the same URL more than once, what differed between observations — so you can check before you pitch, not after a client asks why. MAP does not verify, score or rate content, and it does not assess an outlet's past reporting.

What Publisher Certification actually is

A real application, reviewed by MAP's founder — not an automated score, not something you can buy your way into. No publisher has been certified yet. MAP does not rate credibility or trustworthiness anywhere on the platform, including here. Certification is designed to confirm a set of documented facts about a publisher's practices: ownership disclosure, editorial policy, correction visibility, author transparency — presented as a record, not a verdict.

What you can and can't show a client who asks "how do you know?"

MAP writes its records to a SHA-256 hash-chained, append-oriented ledger that MAP operates. Records carry their own hash and the hash of the record before them, which MAP publishes for reference (some older rows predate hashing), and MAP runs a daily continuity check and reports the result. Readers cannot yet recompute the hashes or check the chain themselves, so today a MAP record is MAP's own documented observation. Records are point-in-time snapshots; a later observation of the same URL creates a new record.

Real application, reviewed by MAP's founder. Not a form that auto-approves. No publisher has been certified yet.