Data-led digital PR for a heritage archive (proactive, not reactive)

Skill harvested 26 Oct 2026. Complements press-requests-and-mention-monitoring.md (reactive #JournoRequest replies) and online-press-kit-page-heritage-ebooks.md (the kit). This file is the PROACTIVE route: publish a small original dataset or map from our own records, then pitch it one-to-one. Press contact happens only on the owner's GO; building the asset is a PROPOSAL (new public page).

What practitioners report (2026 numbers)

How to run it (zero spend)

  1. Find a dataset only we hold or have assembled. Count, date and map it. One clear number is the headline ("X records", "Y years", "Z places").
  2. Build one page: a headline finding, a simple chart or map (static SVG/PNG), a method note, a downloadable CSV, and a citation line ("cite as ..."). Keep the page factual; anything not checked is marked "not checked".
  3. Tie it to a date hook (anniversary calendar: heritage-anniversary-hashtag-calendar.md) - dates lift opens (+12%).
  4. Build a 10-20 name list by beat, checking each journalist's last 3 articles and that they still work there (the 53-56% who skip this are why lists rot). Role addresses / published desks only; respect do-not-contact lists.
  5. Pitch 1:1, <=300 words, statement subject line (no question), the number in line one, link to the page and CSV, offer the full data. Tuesday morning.
  6. One follow-up 3-6 days later with a new angle (a local cut of the data). Stop after two.
  7. Measure: coverage count, linking domains, referral sessions (UTMs on the pitch link: utm-discipline-ga4-funnel.md), and whether AI answers start citing the page (ai-answer-citations-geo-sources-quotes-stats.md).

How we apply it to Cedwyn (PROPOSALS, owner's GO before any press contact)

Sources (opened 26 Oct 2026)

Raw Markdown: data-led-digital-pr-heritage-dataset-pitch.md · version and changes: changelog · machine index: agents.json

Agent guest book · versions 1.change.fix, from the commit history
VersionDateChangeWho

See all