How to Do SEO for News Websites

Published Read 7 min read

On this page

News surfacing in Google is now fully automated, and the single most valuable thing to know in 2026 is that there is nothing to submit. Publisher Center no longer accepts manual publication setup, RSS feeds, or web-location submissions; publication pages are generated automatically, and content that meets Google’s policies is automatically considered for Top Stories and the News tab. Technical eligibility is therefore earned by correct NewsArticle or Article markup, a compliant news sitemap, crawl freshness, and disciplined scale management, not by any submission action. Teams still working a Publisher Center submission queue are maintaining a retired workflow.

The automation shift: stop submitting

In late March 2025 Google completed its transition to automatically generated publication pages in Google News. The concrete effects: Google News no longer uses RSS feeds or web-location entries submitted in Publisher Center, manually created publication pages no longer appear to users, and the Google News tile was removed from Publisher Center. Publication pages are auto-generated, with Google using the site favicon for the logo and the site name for the title. Content from any publisher that adheres to the content policies is automatically eligible for consideration in Google News and other news surfaces, ranked on factors like relevance, prominence, authoritativeness, freshness, location, and language.

This kills the old advice directly. “Submit your articles to Publisher Center,” “set up an RSS feed for Google News,” and “add your web locations” are all obsolete instructions. There is no manual submission step left in the news pipeline. The correction is the headline action: delete that work from your runbook and redirect the effort to markup, sitemap, and crawl health, which are the only inputs you still control.

NewsArticle versus Article schema

Mark up news content with structured data so Google can interpret it precisely. The decision between NewsArticle and Article is straightforward: NewsArticle is the more specific type for news reporting and is appropriate for journalistic content; Article is the general parent and is fine for non-news editorial. NewsArticle is a subtype of Article, so the required and recommended fields overlap heavily. Use NewsArticle for actual news pieces because the more specific type communicates the content’s nature accurately.

The fields that matter are headline, image, datePublished, author, and publisher (with its logo). For any piece you update after publishing, set dateModified as well, because the publish-then-update pattern depends on Google seeing a fresh modification timestamp. Keep the headline in the markup consistent with the visible headline, and supply a real image. Validate the markup with the Rich Results Test or the schema validator, and treat Search Central as the authority for the current required-versus-recommended field list rather than memorizing a stale set.

News sitemap specifics

A news sitemap is a distinct artifact from your regular sitemap, with strict rules.

Requirement Rule
Recency window Only include URLs for articles published in the last two days; remove the news metadata once an article ages past 48 hours
Namespace Use the news namespace, http://www.google.com/schemas/sitemap-news/0.9
Required tags news:publication, news:name, news:language, news:publication_date, news:title
Size Fewer than 1,000 article URLs per sitemap
Maintenance Update the same sitemap as articles publish; do not generate a brand-new file each time

The 48-hour window is the defining constraint: the news sitemap is a feed of what is current, not an archive. Once an article is older than two days, drop the URL or strip its news:news block. Regenerate the sitemap frequently as new articles go out, keep it under the per-file URL limit, and submit it in Search Console. The sitemap helps Google discover fresh articles quickly; it does not by itself guarantee inclusion, which still depends on policy compliance and the ranking systems.

The field set has also been trimmed over time, which is a reason to validate against the current spec rather than against an old tutorial. The optional news:keywords and news:genres tags that older guides treated as important metadata are no longer required, and the only element Google strictly requires inside the news:publication block is the publication itself with its name and language.

The risk lands on legacy tooling. If you are carrying forward a sitemap generator or CMS plugin configured years ago, it may still be emitting deprecated tags or, worse, omitting a tag the current spec expects. Re-read Search Central’s news sitemap documentation, confirm the required-versus-optional list as it stands now, and have your generator match it. A sitemap that validates cleanly against the live namespace schema is doing its discovery job; one stuffed with retired tags is just noise the parser ignores.

Crawl freshness and the publish-then-update pattern

For news, speed of discovery is a ranking input in a way it is not for evergreen content. Google has to find and crawl a breaking story fast for it to compete in Top Stories while the story is hot, so crawl freshness and publication speed matter directly. Two technical habits support this. First, keep the news sitemap current and the site fast to crawl and render, so new URLs are discovered with minimal delay. Second, use the publish-then-update pattern correctly: when you update a developing story, change the visible content and the dateModified in the markup so Google registers the revision, rather than silently editing the body and leaving the timestamp stale.

Render speed feeds this too. A page that is slow to render or buries the article body behind heavy client-side JavaScript delays the point at which Google has the full content, which is the opposite of what a freshness-sensitive surface rewards.

AMP is not required for Top Stories

Top Stories was decoupled from AMP in 2021. AMP still exists and is still supported, but it is not a requirement for Top Stories eligibility and it carries no ranking advantage for it. Do not adopt or keep AMP for the sake of Top Stories. Build fast, standards-based pages instead; the freshness and crawl benefits come from genuine speed and clean rendering, not from the AMP format.

What replaced the AMP shortcut is the same page-experience discipline that applies to the rest of the site: genuinely fast pages measured by real performance rather than a format badge. For a news template that means keeping the article body in the initial HTML response, deferring non-critical scripts, sizing and lazy-loading images below the fold, and not blocking render on heavyweight ad or analytics stacks. A news team that dropped AMP and then let its standard templates bloat with client-side rendering has traded one problem for another, because the freshness-sensitive surfaces still reward the page that delivers content quickly.

The practical test is simple: when Googlebot fetches a breaking story, is the headline and the lede in the markup immediately, or does the meaningful content arrive only after a round of JavaScript execution? The first case competes in Top Stories while the story is hot; the second concedes the early window that matters most for news.

Scale and paywall management

News sites operate at archive scale, which creates two technical problems. The first is crawl management across a large, fast-growing archive: ensure NewsArticle markup is applied consistently at volume through your CMS rather than by hand, keep the news sitemap scoped to the 48-hour window so it stays small and current, and let your regular sitemap and internal linking handle the deep archive.

The second is paywalls. To rank paywalled news, let Googlebot access the full content while users see the paywall, and declare it transparently with the isAccessibleForFree property and hasPart pointing to the gated sections. That declaration is flexible sampling, an explicitly sanctioned approach, and it is not cloaking precisely because you are disclosing the paywall status rather than hiding it. Serving Googlebot different content while concealing the paywall would be cloaking; declaring it with the schema is the sanctioned alternative. Confirm the current flexible-sampling and paywalled-content guidance in Search Central before implementing.

Frequently Asked Questions

Do I still need to submit my site to Google News Publisher Center?

No. Since the March 2025 transition, Publisher Center no longer takes manual publication setup, RSS feeds, or web-location submissions, and publication pages are generated automatically. Policy-compliant content is automatically considered for Top Stories and the News tab. The work is now markup, sitemap, and crawl health, not submission.

Does my news site need AMP to appear in Top Stories?

No. Top Stories was decoupled from AMP in 2021. AMP still works but is not required and gives no ranking advantage for Top Stories. Build genuinely fast, standards-based pages instead.

How long should articles stay in my news sitemap?

Only while they are within the last 48 hours. Once an article is older than two days, remove its URL from the news sitemap or strip the news metadata, keep the file under 1,000 URLs, and update the same sitemap as new articles publish rather than creating a new file each time.

Sources

Google News, transition to automatically generated publication pages: https://support.google.com/news/publisher-center/answer/15898024?hl=en

Google Search Central, create a news sitemap: https://developers.google.com/search/docs/crawling-indexing/sitemaps/news-sitemap

Google Search Central, paywalled content and flexible sampling: https://developers.google.com/search/docs/appearance/structured-data/paywalled-content

Related posts:

  1. How to Handle Duplicate Content Issues Duplicate content is a technical canonicalization problem, not a penalty and not a "rewrite everything" problem. Outside of deliberately deceptive scraping, Google does not penalize a site for having duplicate......
  2. How to Optimize for Zero-Click Searches Most Google searches now end without a click. AI Overviews, AI Mode, featured snippets, and other SERP features answer the query in place, so the searcher gets what they came......
  3. Neighborhood-Level SEO: Why “Local” Isn’t Local Enough Anymore TL;DR Local SEO strategies treating entire metro areas as single markets are leaving rankings on the table. Search behavior varies dramatically between neighborhoods within the same…...
  4. Informational SEO is Dead. Here’s What’s Left. Publishing top-of-funnel informational content primarily to capture search clicks has lost its economics. AI Overviews now answer "what is" and "how to" queries directly inside the results page, so the......
  5. Google Is Indexing Parameters You Blocked in Robots.txt Robots.txt controls crawling, not indexing, and that single distinction explains the whole paradox. Google can index a URL it has never crawled, purely from external link signals, which is exactly......
  6. SEO Quarterly Business Reviews: Executive Reporting and Strategic Alignment A quarterly business review exists to keep SEO funded and strategically aligned, and it does that by reporting outcomes instead of activity. Executives do not allocate budget based on how......
  7. SEO Team Capacity Planning: Workload Modeling and Resource Allocation Capacity planning is the constraint that forces real prioritization. SEO work is effectively unbounded; there is always another page to optimize, another competitor to analyze, another technical issue to chase,......
  8. Magento SEO at Enterprise Scale Without Losing Sanity Enterprise Magento (now Adobe Commerce) SEO is an architecture-constraint problem, not a configuration problem. The platform's defaults generate crawlable URLs faster than you can tune settings: layered navigation multiplies filter......
  9. SEO vs GEO: A Misframed Debate and the Real Answer "Should I do SEO or GEO" is a false choice. Visibility has fragmented across traditional search engines and AI engines that retrieve and cite sources differently and that share surprisingly......
  10. Why Google Won’t Index Your Catering Website Page: Mechanisms, Diagnosis, and Solutions When a catering page will not index, the diagnosis is not a guess: you read it straight off the GSC URL Inspection status, and that status dictates the fix. Run......
  11. Your Domain Authority Is High But Traffic Is Dying A high Domain Authority alongside falling traffic is not a paradox. It is a diagnosis. Domain Authority is a third-party Moz score that Google does not use for crawling, indexing,......
  12. Managing Freelance SEO Writers: Quality Control at Scale Freelance content scales only when quality control becomes a system rather than a series of individual judgment calls. The reason is structural: freelancers do not absorb the organizational context that......
  13. Google Keeps Crawling URLs You Deleted Years Ago Deleting a page does not remove its URL from Google's memory. Google maintains a persistent per-domain database of URLs it has ever discovered, fed by your sitemaps, your internal links,......
  14. Marketplace Seller SEO When the Platform Outranks You You will not beat Amazon, Etsy, or eBay on transactional head terms from your own store, and chasing them is the wrong fight. The marketplace has two decades of behavioral......
  15. Why Your CDN Is Serving Different Content to Googlebot If Googlebot is indexing a version of your pages that no longer exists for users, your CDN is almost certainly serving the crawler a stale or differently-processed response. This usually......