Press Releases and AI: Worth It?

Press releases rarely improve AI visibility by themselves. Google's spam policies name "links with optimized anchor text in articles, guest posts, or press releases distributed on other sites" as link spam ([Google](https://developers.google.com/search/docs/essentials/spam-policies)). Our view: a release earns its keep when it announces real news that others cover, or when it's the clearest, dated record of a fact engines need.

Facts are from Google Search Central, accessed 30 Oct 2026. Points marked "Our view" are interpretation; examples are illustrative.

On this page

• What does Google's policy say about press releases?
• Why do releases rarely move AI answers?
• When is a release worth it?
• How do you write a release worth citing?
• Should you use a wire service?
• What should a newsroom page include?
• What should you avoid?
• How do you measure whether it worked?
• How do releases fit into a wider plan?
• What does a good release look like in practice?
• How do you decide whether to issue one at all?
• Exercise
• Checklist
• From MentionX data: which pages engines cite
• Worked example: Ledgerline decides whether to send a release
• What makes a release factual enough to quote?
• How should the newsroom be structured?
• How do releases support other channels?
• When is a wire service worth paying for?
• How do you handle corrections?
• How do you track whether a release reached AI answers?
• What should a release checklist include?
• Common questions
• Related
• Sources

Checked on 31 October 2026. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.

What does Google's policy say about press releases?

Two points are documented. First, the link spam section lists optimised-anchor-text links in press releases distributed on other sites as an example of link spam (Google). Second, the site reputation abuse section says wire services and press release sites are not considered inconsistent with that policy (Google). So distributing a release isn't a problem; trying to use it to build ranking links is.

For any link you place in content that's paid for, Google asks you to use rel="sponsored" or nofollow (Google).

Why do releases rarely move AI answers?

Our view: wire distribution copies the same text to many low-traffic pages. Engines looking for helpful, original content have little reason to prefer one copy, and Google's guidance for its AI features stresses unique, non-commodity content (Google). A release announcing a minor feature update is commodity content by that definition. What gets cited is the coverage, analysis or data that follows.

When is a release worth it?

How do you write a release worth citing?

• Put the news in the first sentence: who, what, when, where.
• Include one specific, checkable fact (a number, date or named customer you're allowed to name).
• Add a short boilerplate with what the company does, in plain words.
• Link to a page on your site with full details, using plain anchor text.
• Name a contact who answers.
• Publish the release on your own newsroom page with a date.

Our view: write the headline the way a buyer would phrase the fact. "Acme Payroll now supports Germany" (fictional) is easier to quote than "Acme Announces Strategic European Expansion".

Should you use a wire service?

Our view: use one when you need reach to journalists or investors, or when disclosure rules require it. Don't use it to build links. For most small companies, a newsroom post plus direct emails to five relevant journalists does more than broad distribution.

What should a newsroom page include?

A dated list of releases, a short company facts block, approved logos and photos, leadership bios and a press contact. Our view: this page often becomes the source engines and writers use for basic facts, so keep it current. See build a brand facts page AI can quote.

What should you avoid?

• Keyword-stuffed anchor links back to your site.
• Announcing things that aren't news.
• Vague claims like "industry-leading" with no evidence.
• Paying for coverage without disclosure.

How do you measure whether it worked?

Track coverage the release produced (articles by journalists, not wire copies), whether those articles are cited in AI answers for your prompts, and whether answers state the announced fact correctly. Our view: if the fact appears accurately in answers within a few months, the release did its job.

How do releases fit into a wider plan?

Our view: treat the release as one step in a sequence. Publish the full story or dataset on your site first, then the release, then direct pitches to journalists and posts in relevant communities. Each step points back to the same canonical page, so the facts stay consistent wherever they're repeated. A release on its own, with nothing to point to, gives writers little reason to cover it.

What does a good release look like in practice?

Fictional example: a payroll software company publishes a study of late salary payments across 2,000 small firms. The full method and data sit on its site. The release leads with the headline finding, gives the sample size and date range, and links to the study with plain anchor text. Two trade journalists write their own articles with fresh quotes. Months later, AI answers about late payroll cite those articles and the study page, not the wire copies. The release was the trigger; the data and coverage were what got cited.

How do you decide whether to issue one at all?

Our view: ask three questions. Would a journalist in your field care? Is there a fact here that people will need to look up later? Do you have a page with the full details ready? If the answer to all three is no, publish a blog post or changelog entry instead and save the budget.

Exercise

Take your last three press releases. For each, list the journalist-written articles it produced and check whether any are cited in AI answers for a related prompt. Rewrite the weakest headline and first sentence so the fact is clear and quotable.

Checklist

• News in the first sentence
• One checkable fact included
• Plain anchor text; paid links qualified
• Published and dated on your newsroom page
• Coverage and AI citations tracked

From MentionX data: which pages engines cite

Method. Read-only aggregate queries over MentionX scans from 22 August to 29 October 2026 (UTC): 2,217 engine runs (2,154 completed) across 18 anonymised projects and six engines.

Press releases are one way to get facts onto the web, but engines cite some page types much more than others. In our sample:

Brand mentions are concentrated in comparison and best-of answers, not news queries:

Our view: a release rarely changes how a brand appears in comparison or best-of answers on its own. What helps is the coverage it triggers on cited publications and a clear, current newsroom page that engines can use for facts.

Limits. A convenience sample of mostly B2B software projects, run through engine APIs, which can behave differently from the consumer apps. Perplexity, Copilot and DeepSeek figures come from a single day (26 October 2026), so treat them as a snapshot, not a trend.

Worked example: Ledgerline decides whether to send a release

Ledgerline is a fictional accounts-payable tool. Figures are illustrative.

Ledgerline is launching approval workflows for multi-entity companies. The team asks three questions: is this news to anyone outside the company, do we have something a journalist can check, and do we need it on record?

The launch is real news for finance trade press, and Ledgerline has customer quotes and clear feature details. It writes a short release with plain facts, one quote and links to the product page, and posts it in its newsroom. It sends it through a wire service for the record, with links marked nofollow, but spends most of its effort on direct pitches to two trade publications its source map shows are cited. One writes a story. Ledgerline later checks the relevant prompts and finds the trade story cited in one engine; the wire copy is not cited anywhere.

What makes a release factual enough to quote?

State who did what, when, where and why in the first paragraph. Use exact names for products and features, and give dates and prices where they're relevant. Avoid adjectives that can't be checked, such as "leading" or "revolutionary". Engines and journalists both prefer sentences that can be lifted as they are.

Include a short company description at the end that matches the description on your About page and other profiles. Consistent wording across the web helps engines describe you the same way every time.

How should the newsroom be structured?

Give each release its own URL with a clear date and headline. Keep an index page listing releases newest first. Add a press kit with logos, leadership bios and a fact sheet: founding year, headquarters, product lines and contact details. Keep the fact sheet current; a stale fact sheet can feed outdated details into answers.

Make the newsroom crawlable. Don't hide releases behind scripts that load only on click, and don't block the section in robots.txt. Link the newsroom from your footer so crawlers find it.

How do releases support other channels?

A release can give sales a link to share, give partners approved wording, and give journalists a single source for facts. It can also anchor a launch page or a blog post with more detail. Our view: treat the release as the factual record and the blog post as the explainer; the blog post usually does more for buyers and engines.

When is a wire service worth paying for?

Wire distribution is useful when you're legally required to disclose news, when you need a timestamped public record, or when trade press in your sector still watch the wire. It's rarely worth it for routine updates. If you use one, mark links as nofollow or sponsored and don't expect syndicated copies to rank or be cited.

How do you handle corrections?

If a release contains an error, correct it on your newsroom page with a dated note, and ask any publication that repeated it to update their story. Don't silently change figures. A visible correction is better for trust, and it gives engines a clear current version.

How do you track whether a release reached AI answers?

List the prompts the release relates to before you send it. Run them before launch and again a few weeks after. Note any new citations, whether to your newsroom, your product page or coverage. Record which publications picked up the story. Over time, this shows which kinds of news earn coverage on cited sources, and which don't.

What should a release checklist include?

Check that the news is real, the facts are verified, the quote says something specific, links point to current pages, links in distributed copies are marked nofollow or sponsored, the newsroom page is live, and the fact sheet matches. Then decide who will pitch which publications directly. The release is the start of the work, not the end of it.

Common questions

Do press release links help SEO? Google's guidance treats optimised anchor links in widely distributed releases as a link scheme risk.

Do AI engines cite wire copies? Rarely, in our experience. Stories written by journalists are cited more often.

How often should we send releases? Only when there's real news. Volume doesn't help.

Related

• Earned media vs owned content
• Earning citations from news sites

Sources

• Google, Spam policies for Google web search; Qualify outbound links; Optimizing for generative AI features

All accessed 30 Oct 2026.