How to Submit a Press Release to Google News? (Step by Step Process)

Google News stopped accepting manual applications years ago. What replaced it is a mix of crawl signals, structured data, and Publisher Center configuration, and most teams still approach submission like it's 2015.

This guide follows the actual sequence that gets a release crawled, indexed, and surfaced: eligibility, configuration, content engineering, technical publishing, distribution, verification, and troubleshooting.

Pre Submission Eligibility Audit: Confirming Google News Readiness

Before touching the Publisher Center, confirm the domain and the release itself meet baseline requirements. Google News inclusion today runs on algorithmic inclusion, not a queue of human reviewers approving submissions one by one. Skipping this audit is the single biggest reason releases get crawled but never surfaced.

There are two separate systems at play. Organic crawling can pick up news content from any indexable domain with no configuration at all. Publisher Center exists to control presentation, things like sections, topic tags, and how a publication name displays, not to unlock indexing by itself.

Verifying Domain Level Eligibility (Publisher Center vs. Organic Crawling)

Check whether Google is already crawling the domain for news before configuring anything. Search the exact domain inside the Google News app, and separately check the "News" filter under Search Console's search results report.

A domain with no prior news history faces a harder path. Treat a first submission as trust building rather than a guaranteed placement, and lean on a team handling ongoing public relations output to keep a steady cadence of qualifying content rather than a single one-off release.

Auditing Content Policy Compliance Before Submission

Run the release against Google's content policies before it goes anywhere near a sitemap. The most common rejection causes are undisclosed sponsorship, misleading headlines, and missing authorship, all fixable in five minutes if caught early.

Pre-submission checklist:

• Byline present and attributed to a real person or organization

• Dateline present with city and publication date

• Company or source clearly disclosed, not hidden behind vague phrasing

• Headline matches the actual content, no bait

• No paid promotion disguised as editorial content

A surprising number of rejections trace back to basic errors made while drafting press release copy, like duplicated boilerplate paragraphs pulled straight from an old template. Relying on generic off the shelf press release templates without customizing the core paragraph is one of the most common culprits, since the duplicate structure reads as thin content no matter how clean the schema is.

Step 1: Configuring Google Publisher Center for Press Release Distribution

Set up Publisher Center to control how the release is categorized, not to trigger indexing. This is the most misunderstood step in the entire process. Adding a publication here doesn't guarantee inclusion; it shapes how an already crawlable domain gets presented once it's in the system.

Creating and Verifying Your Publication

Sign in to Publisher Center, add the publication, and verify ownership through an existing Search Console property. Confirm the logo, publication name, and language settings match what's live on the site.

Unverified domains sync silently in the background and fail without any visible error. Check verification status again a day later if the publication doesn't appear active.

Setting Up Sections, RSS/Sitemap Feeds, and Metadata

Map a dedicated "Newsroom" or "Press Releases" section to its own sitemap or RSS feed URL. Keep this content on a distinct URL path like /newsroom/ instead of folding it into a general blog taxonomy.

A clean, separated path gives Google a clearer crawl signal at the section level, which matters more than most teams assume when it comes to improving how a release performs in search. It also makes it far easier to spot a crawl error later, since the section stands apart from unrelated blog content.

Assigning Topics and Geographic Targeting

Select industry topics that genuinely match the content, and set geographic targeting if the release has clear regional relevance. Over tagging unrelated topics to chase extra visibility violates policy and tends to backfire through reduced trust signals over time.

Step 2: Engineering the Press Release for Algorithmic Inclusion

This is where most technical rejections actually originate. Google News crawlers weigh structured data and editorial transparency heavily, and a release that reads fine to a human can still fail machine parsing. Getting the fundamentals right when a team sits down to draft a press release from scratch prevents half of these failures before schema even enters the picture.

Structuring NewsArticle Schema Markup

Implement NewsArticle JSON-LD with the required properties before publishing, not as an afterthought.

Run the live URL through Google's Rich Results Test before publishing, not after. Catching a missing dateModified field pre-launch saves a full crawl cycle.

The headline field needs to match what's on the page exactly. How the wording of a press release headline affects rich result eligibility just as much as it affects click through, so keep it factual and specific instead of reaching for clickbait framing.

Establishing Editorial Transparency (Bylines, Datelines, Author Markup)

Pair visible authorship with structured markup, both matter independently. A named byline and a location-plus-date line need to appear on the page itself, and the author object in schema should mirror that same name exactly.

Correct formatting of location and date lines within a release is one of the most frequently skipped steps, and it's a silent rejection cause more often than a broken schema tag. Link author names to a sameAs profile where one exists.

Originality Safeguards and Duplicate Content Mitigation

Add at least one genuinely unique paragraph or quote per release before it goes anywhere near syndication. Boilerplate only releases get filtered as low value duplicate content even when the schema is technically flawless.

Set the canonical tag to point at the owned-domain original ahead of any wire copy. This single tag decides which version Google treats as the authoritative source.

How long a press release should actually run matters here too. A release padded past 600 to 800 words with recycled boilerplate reads as thin duplicate content just as easily as a 150 word stub does, so aim for enough original substance to justify the length, not the other way around.

Step 3: Technical Publishing Requirements (Sitemaps & Crawlability)

Confirm the release is physically reachable by crawlers before worrying about anything downstream. Everything built in the previous section is wasted if a crawl blocker sits in the way.

Building/Updating the XML News Sitemap

News sitemaps run on different rules than standard XML sitemaps. Entries need to reflect the publish window within roughly 48 hours, and each sitemap file caps out at 1,000 URLs.

Required tags include <news:publication>, <news:publication_date>, and <news:title>. Missing the publication name tag is a common reason a technically valid sitemap still fails to register.

Crawler Accessibility Checks

Run through this list before hitting publish:

• robots.txt isn't blocking the /newsroom/ path

• No accidental noindex meta tag on the page

• Canonical tag self references correctly

• Mobile rendering confirmed clean in Search Console's usability report

Timing the Submission Within the Indexing Window

Publish during business hours in the target market's timezone and ping the sitemap immediately, not in a batch at the end of the day. News content loses relevance fast, and crawl frequency tends to favor content that lines up with normal publishing hours.

Step 4: Choosing a Distribution Pathway

Two paths exist here, and neither replaces the technical work already covered. This is a decision about reach, not a substitute for schema or sitemap setup.

Once schema and sitemaps are solid, the remaining question is how to get the release out to the channels that actually matter. Finding the strongest available option for spreading a release wide means weighing wire reach against cost, not defaulting to whichever provider a past campaign happened to use.

Direct/Manual Submission via Owned Domain

Relying solely on the owned domain works only once that domain already carries established trust with Google News, per the audit in step one. A brand-new domain publishing its first release through this path alone will likely see slow or no pickup.

Leveraging Premium Wire Networks for Syndication Footprint

Wire distribution extends reach into aggregator surfaces an owned domain may never reach independently.

Vet the provider first

Understanding the mechanics behind newswire syndication matters before picking anyone, since not every service marketed for SEO actually holds genuine Google News publisher status. Run side by side newswire provider evaluations against three checks:

• Confirmed publisher status

• Actual placement history

• Transparent reporting

Free vs paid tiers

Publicly available distribution options with no paid tier exist too. They're worth testing for lower stakes announcements, though reach and placement consistency tend to trail paid tiers.

Match the provider to the vertical

Vertical fit matters as much as reach. A launch stage company putting out its first release needs a different provider mix than an established enterprise, and different industries carry different aggregator relationships and audience overlap:

• Blockchain native announcement distribution

• Software subscription focused distribution networks

• Online retail focused distribution options

• Utility and chemical sector distribution channels

• Property and housing market distribution services

• Banking and payments focused distribution networks

A token launch specific release strategy in particular needs a provider that won't flag the content under financial promotion policies. For subscription software companies, a dedicated walkthrough built specifically for SaaS announcement strategy pairs well with the vertical options above, since product-launch releases in that category hinge on different proof points than a funding announcement does.

Pricing considerations

Cost varies wildly across this landscape. What a typical release actually costs depends on wire tier, word count, and add ons like multimedia embeds. How those pricing tiers break down is worth mapping out before committing to an annual contract instead of pay-per-release.

Managing Duplicate/Syndicated Content Signals

Publish on the owned domain first, then syndicate outward with correct attribution and canonical links pointing back to the source. Reversing this order confuses canonicalization and can hand ranking credit to the wire copy instead of the original.

Step 5: Verifying Indexation and Google News Appearance

Confirm the release actually indexed instead of assuming it did. This verification pass is where most teams stop too early and miss a fixable problem.

Using Search Console to Confirm Indexing Status

Run the live URL through the URL Inspection tool and check the News specific reporting tab. A healthy status shows the URL indexed with no coverage warnings attached.

Validating Rich Results / NewsArticle Structured Data

Test the live URL through Google's Rich Results Test and Schema Markup Validator. The three most common warnings are missing image dimensions, an incorrectly typed author field, and a malformed date format.

Checking Appearance in News Aggregation Surfaces

Search the exact headline inside the Google News app and through the News tab in regular search. Technical indexing and actual surface placement in Top Stories are two different outcomes, and confirming one doesn't confirm the other.

Troubleshooting Common Indexing Failures

Diagnosing "Crawled, Currently Not Indexed" Errors

This status usually reflects a quality threshold rather than a technical block. Strengthen originality, add clearer author entity signals, and confirm the content goes beyond boilerplate before resubmitting.

Fixing Schema/Markup Errors Blocking Inclusion

Pull the exact warning from the Rich Results Test output and match it against the CMS template field it maps to. A missing datePublished almost always traces back to a template that never set an ISO 8601 timestamp field in the first place.

Resolving Policy Violations and Manual Actions

Check the Manual Actions report inside Search Console for any flag tied to the domain. File a reconsideration request only after the underlying issue, whether that's misleading content or undisclosed promotion, has actually been corrected.

Addressing Duplicate Content / Canonicalization Conflicts

Audit canonical tags across every syndicated copy and confirm the owned domain carries the canonical designation. A wire copy without a proper attribution link back to the source is the most common cause of this conflict.

Post Publication Maintenance and Long Term Optimization

Single submission success doesn't carry forward automatically. Google News trust builds through consistency across many releases, not a one time technical fix.

Monitoring Performance in Publisher Center & GSC

Check News performance reports and crawl stats on a recurring basis, weekly if volume allows, monthly at minimum. Catching a regression a week after it starts is far cheaper than catching it a quarter later.

Maintaining Ongoing EEAT Signals Across the Newsroom

Keep author bylines consistent across every release rather than only on flagship announcements. An About page and a visible editorial policy page reinforce the same transparency signals schema markup is trying to communicate.

Scaling Future Submissions

Turn every section above into a reusable internal checklist rather than relearning it release by release. A well run internal communications function that treats this as a repeatable workflow, not a one off scramble, is what separates domains that build lasting News trust from ones that get one lucky placement and then disappear from the surface entirely.