The asset is original and the pitch is a product sheet
You have data, a method, or a timely finding. The email still reads like a launch. We rewrite the hook until a stranger could file it. We do not add adjectives.
Digital PR
Digital PR to Fit One Asset to One Editorial Desk
Digital PR from senior consultants who turn search demand into rankings, traffic and revenue for your business. We start with a free audit and a 90-day plan built around your goals.
- Hook
- Beat
- Pitch
Our process
How the work runs
- 01
Hook
We write the one sentence a journalist could report, built on a real finding, timing or method.
- 02
Beat
We list reporters and sections that already cover your subject, and pass non-editorial blogs to outreach.
- 03
Pitch
Pitches are short and personal, covering the hook, proof and why it suits that desk, never a mass email.
- 04
Mention
We log every story with the outlet, date and link status, plus any declines, and update it when coverage changes.
Position
The desk has a hole to fill. The asset has to fill it.
Digital PR here is not a link shopping list. It is a newsworthy asset plus a journalist whose beat already includes that kind of story. Search intent on the public asset page has to match the claim you want them to report. If the page is a product brochure, the desk has nothing to run. If the page is original data, a method, or a finding they can verify, you have a hook.
Link building owns the editorial href as the object. Guest post services own one contributed article. Blogger outreach owns the CRM. Content marketing owns a calendar for your own live pages. Knowledge Graph work owns panel facts. It starts from whether a human editor would file the story without being paid to host your paragraph.
We will not promise a coverage SLA. We will not run a guest article factory from a PR ticket. We will not blast a blogger list and call it a newsroom. We will not edit Wikipedia as a ranking product. If the honest next step is a cite on a money URL with no story, open link building. If the honest next step is a full draft they commissioned, open guest post services. If the honest next step is moving a keeper you already published, open content marketing. This page is a mention you can show.
Keyword targeting is not the hook. The hook is the finding, the timing, or the method. Topical relevance is the beat test: did this reporter run a cousin story in the last year? Keyword density in old clips is not a reason to pitch. Semantic keywords belong in the asset if they are still the finding, not as stuffing in the pitch subject line.
Entity optimization as a newsroom input means the pitch and the asset use the same organization and product names. Panel correction still lives on Knowledge Graph work. LLM visibility measurement stays off this page. A shopping assistant is not a reason to buy advertorials.
Compare packages if a published retainer already fits. Use Link building when a related service is the real job. If this page is still a guess, start with a free AI + SEO audit.
When this fits
When you have a finding and nobody has a beat list
This page fits when you can name an asset a journalist could file, and you cannot name the desks that already cover it. If you needed a link log, a guest draft, or a panel correction, start there instead.
Outlets are a wish list with no beat
Someone wants the Times because the Times is famous. We ask who on that desk already covers this subject. If nobody does, the outlet leaves the list.
Last campaign promised ten clippings
The SLA trained the team to buy mentions. We replace the SLA with a mention log. Passes stay visible. Purchased advertorials go on a refusal note.
Someone wants Wikipedia as the win
We will say no on this page. A biography campaign is not a journalist beat. Panel facts belong on Knowledge Graph work when that is the real ticket.
Process
Write the hook. Name the beat. Pitch once. Log the mention.
Four newsroom jobs, in that order. Each job ends with a note the newsroom owner can keep. We do not open a link marketplace in the last step. The point is a mention a desk chose, not a clipping count finance prepaid.
-
Hook
Outcome A hook line plus the asset URL that proves it, or a stop.
-
Beat
Outcome A beat list with names, sections, and recent cousin stories.
-
Pitch
Outcome A dated pitch record per desk, including who was not contacted.
-
Mention
Outcome A mention log you can show without hiding passes.
Deliverables
What a newsroom owner can keep after we leave
You leave with a hook line, a beat list, a pitch record, and a mention log. You do not leave with a coverage SLA, a Wikipedia page, or a link quota.
Hook line and proof URL
The sentence a desk can file, plus the page that shows the method or data. Dated. Last year's survey is not this hook unless we say it still holds.
Beat list
Named people and sections, with cousin stories. Famous outlets with no beat are removed on purpose.
Pitch record
Who got the note, when, and what we sent. A BCC blast is not a record we will keep.
Mention log
Live stories, passes, href if any, corrections. Hidden passes are not a log.
Handoff note
Which asks became a guest article, a resource link, or a graph ticket. Two teams must not pitch the same person twice.
Benefits
What a clipping quota cannot teach a desk
The hook is checkable
A reporter can verify the claim without a sales call. That is the whole point of the asset.
The beat has names
You stop emailing a masthead. You email a person who already covers the subject.
Passes stay in the log
Leadership sees the real hit rate.
Hrefs are optional wins
A mention still counts here. Link building can pick up a resource ask if one appears.
Methodology
Who can approve the claim in the hook
This works when someone owns the finding and someone can talk to a reporter the same day. If both are missing, we are decorating a PDF. We are not pitching a desk.
We start with the public asset, the claim, and the person who can defend the method. If any of those is missing, we name it first.
We fetch the asset URL. We do not trust a slide. Would a stranger file this without calling sales? Does a cousin story already exist on the beat we named?
You may rename the roles below. You may not leave the claim implied. An implied percentage is how a desk writes a correction with your name on it.
- Digital PR lead SEOConsultants.ai writes the hook, the beat list, the pitch, and the mention log. We do not become your in-house newsroom because one story ran.
- Claim owner Stands behind the data or the method.
- Whoever can answer the desk Same-day replies, extra charts, a quote that is not marketing paste. Silence after a yes burns the beat.
- Legal Approves what may be claimed and which outlets are off limits. A late veto after a send is a process failure.
- Leadership Accepts that a pass is a real outcome. An honest empty week is not a failure of this page. A purchased SLA would be.
First working session
Start with the hook sentence, not the outlet wish list
The first hour is one claim a desk could file, plus the URL that proves it. It is not a tour of journalist databases.
We write the hook on a whiteboard or a doc. We open the asset URL. If the URL does not prove the hook, that is the job. If the real question is an href on a money page, that is link building. If the real question is a contributed draft, that is guest post services. If the real question is a CRM, that is blogger outreach. If the real question is a panel fact, that is Knowledge Graph work.
Then we name three desks and look for cousin stories. If none exist, the beat is a wish. A media list CSV with no URLs is not evidence.
We leave with a first hook or a stop. A hook names the claim, the proof URL, and who answers the reporter. A stop names what is missing: a public asset, a claim owner, or a program that is actually a link quota. Both are outcomes.
AI search
A mention is not an AI Overview
A real story can help later extraction. This page cannot sell AI Overviews, a chat mention, or LLM visibility as a score.
People ask whether Digital PR will land the brand in Google AI Overviews (AIO). If the only clips are advertorials, generative search has paid copy to lift. That is ours to refuse. A program across search UIs is AI SEO.
The asset has to print in the first HTML
AI search needs a page it can fetch. A gated webinar replay is not a hook a model can check. Nobody can guarantee a spot in AI Overviews, but clear pages improve your chances.
Names in the story should match the thing you are
We check whether the pitch and the asset use the same organization and product names. That is entity optimization as a newsroom input. Panel correction still lives on Knowledge Graph work.
Measuring model answers is another URL
LLM visibility needs a sentence a model can quote, then measurement on LLM SEO. A mention log can show a live story. Semantic keywords belong in the asset if they are still the finding, not as stuffing in the pitch subject line.
Schema
News markup does not make a desk file the story.
JSON-LD on the asset can describe a Dataset or an Article the page already is. This work does not add fake NewsArticle types on a brochure. Schema supports the work; it is not the whole job.
Mark up what the asset actually is
A survey page is not a NewsArticle because you hope a reporter will come. Valid types still need facts that match the HTML.
Quotes in schema must appear on the page
If a reporter uses a quote, it should already be public or given on the record.
Extra fields do not buy a clipping
Markup will not force generative search to cite the campaign. Good markup makes you eligible; it cannot buy a mention.
Who we work with
The person who can talk to a reporter today
Someone has to answer the desk. We work with that person. We do not replace them with a second PR retainer that sells clipping counts.
Claim owner
Owns the method and the numbers. Holds the hook when marketing wants a bigger percentage.
Desk contact
Replies the same day. Sends charts. Does not add a sales deck to the thread.
Whoever already runs PR
Can keep relationships once beats are named. If they try to run this as a guest-article mill or a link quota, two jobs collide. Split the ticket.
FAQ
Digital PR FAQs
Is this the same job as link building?
No. Link building owns a relevant editorial href on a money URL, with a refusal list and a placement log. This page owns a newsworthy asset and a journalist beat. The object here is a mention. A link is a byproduct if the desk runs the story. A cite with no story is that job. A story with no href can still be this one.
Is this the same job as guest post services?
No. A guest contributed article is one named draft on one named site that already agreed to host it. Digital PR is a pitch to a desk that did not commission you to write their section. If they want a full byline package, that ticket leaves. If they want a hook they can report, this is the page.
Will you guarantee coverage this month?
No. We will not sell a coverage SLA. Hook, beat, pitch, mention is the work. A desk can pass. That pass goes in the mention log as a pass. A promised clipping count is not a deliverable.
Do you build Wikipedia pages as the product?
No. Wikipedia is not a newsroom we operate from this ticket. Knowledge Graph work owns panel facts and sources you already control. We will not invent a biography to force a node, and we will not treat an unpaid editor as a journalist beat.
Does a Digital PR campaign put us in AI Overviews?
No. Honest mentions can help later extraction. This work does not buy a place in Google AI Overviews (AIO), a generative search mention, or an LLM visibility score.
An asset a desk can file
Is the story a spreadsheet nobody asked for?
Bring the pitch asset URL, the claim you want a desk to run, and three outlets you think already cover this beat. We will say if Digital PR fits, or whether link building, a guest article, or Knowledge Graph work should go first. Then we name the hook or we stop.