If you research outreach contacts, you need a route appropriate to the request you intend to make. Published contact information and verified person-level contact data are different things bought from different tools. Knowing which you have prevents both wasted outreach and wasted subscriptions.
Two types of contact data
What a site publishes about itself. Contact pages, submissions forms, editorial addresses, general enquiries lines, social profiles. Collected from the site, broad in coverage, and describing a route rather than a person.
A verified address for a named individual. Found by a service that also tests whether the address accepts mail. Narrow, specific, and answering a different question.
OppAlerts Site Info searches records for around 40 million sites and returns the first. It does not verify deliverability, promise a fixed refresh interval or provide a separate correction channel, and it is not a journalist database with reporter profiles and beats.
Which one your task needs
The instinct is that a named person is always better. For the placements link and PR research produces, that is frequently wrong.
Sites that accept contributions, listings, submissions or corrections usually state how they want to be approached. Following that route reaches whoever handles it, which on a small publication may be one person and on a larger one may be a rotating desk. It also demonstrates that you read the page.
Reaching past a stated process to an individual can be slower and, on a site with clear instructions, reads as having ignored them.
So the order is: read what the site publishes, use the stated route if there is one, and look for an individual only when there is not or when the placement justifies the effort.
Reading a thin record
Some sites return few details or none. That means no contact route was found when the site was collected, not that none exists.
Common causes are a form-only contact page with no address in the markup, details rendered by script, contact information published as an image, and a site that has changed since it was collected.
Where the prospect is worth pursuing, spend the minute on the site itself. Discarding a good fit because a stored record is empty is the expensive version of this mistake.
What stored data cannot tell you
Three things, each of which causes a predictable failure.
Whether the address still works. Nothing is tested. If bounce rates are your problem, an email verification service solves it and this does not.
Whether the person is still there. Staff change more often than websites do. An address that reaches a departed employee's mailbox is worse than no address, because it looks delivered.
Whether it is the right route for your request. A general enquiries address at a publication with a separate submissions process will route your pitch to somebody who cannot act on it.
A sequence that wastes less
- Qualify the prospect first. Contact details for a site you should not be contacting are worthless. Relevance, whether it accepts anything, and its requirements all come before this step.
- Read the site's published route. Frequently the answer is right there, with the requirements attached.
- Match the route to the request. A submissions form for a submission; an editorial address for a correction; a general address only as a last resort.
- Verify only when you need an individual. Verification costs money per lookup, so spend it on prospects that already passed the earlier checks.
- Confirm the contact details on the current site before sending.
This order reserves paid verification credits for the prospects you have assessed and intend to contact.
Using contact data responsibly
These are routes a business published so people could reach it. That is not consent to receive bulk messages, and the obligations on your outreach come from the law where you and the recipient are, not from the data.
The practical version: contact people about things relevant to what they publish, use the route they asked for, keep it short, and stop when asked. That is also what produces replies.
After qualifying a publication, check its current instructions for your request. Use the contact record to help find that route before preparing an approach.
See Site Info, where the details come from, or finding contact details.