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
A journalist needs a hook they can run this week. They need a beat that already matches. We shape an asset that is actually newsworthy. We name the desks that cover that beat. We pitch once with a fact they can check. We log the mention, including a pass. We do not sell a clipping quota. We do not treat a spreadsheet nobody asked for as a story.
Position
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 ready URLs, prospects, placements, and a log. A href without a story can still be that job. A mention without an href can still be this one. We will not convert a PR pass into a purchased link to hit a count.
Open link buildingGuest post services place one named article on one named site. A pitch that asks a reporter to write their own piece is this job. A pitch that delivers your 1,200 words for their CMS is that job.
Open guest post servicesBlogger outreach owns sequences and inboxes. A desk with a named reporter is this beat list. A hundred blogs with no beat is that CRM. Do not mix the waves.
Open blogger outreachKnowledge Graph optimization evidences public facts and sources you control. We may use an existing article as corroboration later. We will not treat a Wikipedia draft as Digital PR, and we will not sell a panel from this page.
Open Knowledge Graph optimizationLink 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. This page does not reprint those jobs. 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.
When this fits
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.
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.
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.
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.
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
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.
We write the one sentence a reporter could file. It must be checkable. Keyword targeting is not the hook. The hook is the finding, the timing, or the method. If the only sentence is a product name, we stop. The public asset URL must already state the same claim a crawler can fetch.
Outcome A hook line plus the asset URL that proves it, or a stop.
We list reporters and sections that already cover this subject. Topical relevance is the test: did they run a cousin story in the last year? Keyword density in old clips is not a reason to pitch. A lifestyle blog with no editor byline is usually a handoff to outreach, not a beat row here.
Outcome A beat list with names, sections, and recent cousin stories.
We send a short note: hook, proof, why this desk, embargo if real. We do not attach a 40-page PDF as the first line. We do not BCC fifty people. If they ask for a contributed column, that ticket can move to guest post services. If they ask only for a resource link, that can move to link building.
Outcome A dated pitch record per desk, including who was not contacted.
We log the live story, the outlet, the date, whether an href exists, and the pass if they declined. A screenshot of a social share is not a mention unless the desk published. Recheck if they update the piece. A correction is a log row.
Outcome A mention log you can show without hiding passes.
Deliverables
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.
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.
Named people and sections, with cousin stories. Famous outlets with no beat are removed on purpose.
Who got the note, when, and what we sent. A BCC blast is not a record we will keep.
Live stories, passes, href if any, corrections. Hidden passes are not a log.
Which asks became a guest article, a resource link, or a graph ticket. Two teams must not pitch the same person twice.
Benefits
A reporter can verify the claim without a sales call. That is the whole point of the asset.
You stop emailing a masthead. You email a person who already covers the subject.
Leadership sees the real hit rate. Nobody has to invent ten clippings.
A mention still counts here. Link building can pick up a resource ask if one appears.
Methodology
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.
First working session
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. A coverage calendar with invented dates is not.
AI search
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. If the asset already tells the truth and models still invent the finding, that is an AI search audit. A program across search UIs is AI SEO.
AI search needs a page it can fetch. A gated webinar replay is not a hook a model can check. We do not sell Overview presence.
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.
LLM visibility needs a sentence a model can quote, then measurement on LLM SEO. A mention log can show a live story. It does not sample answers. Semantic keywords belong in the asset if they are still the finding, not as stuffing in the pitch subject line.
Schema
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. It is not a schema campaign as the whole job.
A survey page is not a NewsArticle because you hope a reporter will come. Valid types still need facts that match the HTML.
We refuse invented expert quotes in JSON-LD. If a reporter uses a quote, it should already be public or given on the record.
Markup will not force generative search to cite the campaign. Eligibility is not a purchased mention.
Who we work with
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.
Owns the method and the numbers. Holds the hook when marketing wants a bigger percentage.
Replies the same day. Sends charts. Does not add a sales deck to the thread.
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.
Questions
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.
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.
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.
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.
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. If the asset already tells the truth and models still invent the story, that measurement sits on an AI search audit and on LLM SEO.
An asset a desk can file
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.
Hook, beat, pitch, mention. Not a link package.