Kokil Thapa - Professional Web Developer in Nepal
Freelancer Web Developer in Nepal with 15+ Years of Experience

Kokil Thapa is an experienced full-stack web developer focused on building fast, secure, and scalable web applications. He helps businesses and individuals create SEO-friendly, user-focused digital platforms designed for long-term growth.

SEO for News Sites Google News Best Practices

By Kokil Thapa | Last reviewed: September 2026

Breaking stories lose value in minutes, not days. SEO for News Sites Google News Best Practices decides whether Google News, Discover, and standard search surface your headline while it still matters. The work starts in your CMS fields, URL patterns, and server response times — not in a keyword spreadsheet you fill after launch. On content-heavy Laravel builds and legal-information portals I've maintained, the same crawl and schema habits separate stories that rank within hours from pages that never get picked up. Start with our on-page SEO checklist for Nepal sites if you need a baseline, then apply the news-specific rules below.

What is SEO for News Sites and How Does Google News Index Articles?

News SEO is technical indexation under time pressure. Standard SEO chases evergreen rankings over weeks. News SEO chases crawl discovery in minutes. Google News pulls from your site through normal crawling plus optional Publisher Center signals. It does not replace organic search — it adds a topical, time-sensitive layer on top.

Google retired the old manual Google News inclusion application. Today, eligibility flows through Google Publisher Center plus healthy site-wide SEO. Your articles must look like news to humans and to parsers: datelines, named authors, topical headlines, and publication timestamps that match the visible page.

News Indexation FlowCMS Publishtitle, date, authorNews Sitemaplast 48 hoursGoogle CrawlHTTPS, fast TTFBIndex + RankNews, DiscoverRequired On-Page SignalsNewsArticle JSON-LD with datePublishedNamed author + publisher logoSingle canonical URL per storyVisible publication timestamp
SEO for News Sites Google News Best Practices: publish → news sitemap → crawl → indexation pipeline

How Google discovers news URLs

Google finds news through three main paths. First, it crawls links on your homepage and section pages. Second, it reads your news XML sitemap. Third, Publisher Center maps your sections to Google News surfaces. Weak internal linking from section hubs is a common reason fresh URLs sit uncrawled for hours.

For Nepali publishers covering politics, business, or court updates, bilingual URL strategy matters too. Pair English and Nepali editions with correct hreflang if you run both — our hreflang guide for multi-language sites covers the markup patterns.

Publisher Center setup checklist

  1. Verify domain ownership in Search Console and link it inside Publisher Center.
  2. Add publication name, primary language, and category labels that match your site sections.
  3. Upload a square logo at least 512×512 px — Google uses it in News cards.
  4. Map each site section (Politics, Sports, Business) to a live URL path.
  5. Submit your news sitemap URL and confirm it validates without errors.
  6. Review the content policies page on Google News Publisher Center help before going live.

If you are planning the CMS itself, not just tuning an existing one, read the Nepal news website development guide first. Architecture choices — permalink structure, author taxonomies, AMP vs responsive — are cheaper to fix before launch.

How Do You Build a Google News Sitemap That Gets Crawled Fast?

A news sitemap is not your regular sitemap with a different filename. It is a time-windowed feed of recent URLs. Google expects only articles published in roughly the last 48 hours. Older URLs belong in your standard sitemap, not the news one.

I've seen publishers dump 10,000 URLs into a news sitemap and wonder why Google ignores it. Keep the file small, fresh, and valid. Regenerate it on every publish event — not once nightly via cron if your site breaks news hourly.

News sitemap XML structure

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:news="http://www.google.com/schemas/sitemap-news/0.9">
  <url>
    <loc>https://example.com/politics/coalition-talks-sept-2026</loc>
    <news:news>
      <news:publication>
        <news:name>Example Daily</news:name>
        <news:language>en</news:language>
      </news:publication>
      <news:publication_date>2026-09-08T06:30:00+05:45</news:publication_date>
      <news:title>Coalition Talks Resume in Kathmandu</news:title>
    </news:news>
  </url>
</urlset>

Use ISO 8601 timestamps with your real timezone offset. Nepal runs UTC+5:45 — do not store everything as UTC while displaying Nepali local time. Mismatched dates between HTML, schema, and sitemap are a trust hit. See the official Google news sitemap documentation for field rules.

Laravel news sitemap generation pattern

On Laravel 12 or 13 builds, generate the news sitemap from a queued job triggered on publish. Query only articles from the last two days with a `published_at` index:

Article::query()
    ->where('status', 'published')
    ->where('published_at', '>=', now()->subHours(48))
    ->orderByDesc('published_at')
    ->limit(1000)
    ->get();

Cache the rendered XML for one to five minutes on high-traffic desks. Purge CDN cache for `/news-sitemap.xml` when a major story drops. Deeper sitemap architecture is covered in our Laravel sitemap generator SEO guide and the broader XML sitemap best practices for 2026 article.

Standard vs News SitemapStandard SitemapAll indexable URLsNo date required50k URL limit per fileEvergreen + news mixWeekly refresh OK/sitemap.xmlNews SitemapLast 48 hours onlynews:publication_datenews:title requiredNews articles onlyRefresh on publish/news-sitemap.xml
Google News sitemaps require publication dates and titles; standard sitemaps cover your full crawlable archive

What Structured Data and On-Page Markup Do News Articles Need?

Every article page needs machine-readable metadata that matches what visitors see. NewsArticle JSON-LD is the baseline. Pair it with visible bylines, a clear dateline, and a publisher logo in the footer or header.

NewsArticle schema example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "headline": "Supreme Court Issues New Directive",
  "datePublished": "2026-09-08T09:15:00+05:45",
  "dateModified": "2026-09-08T10:02:00+05:45",
  "author": {
    "@type": "Person",
    "name": "Sita Sharma",
    "url": "https://example.com/authors/sita-sharma"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Daily",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/static/logo-512.png"
    }
  },
  "image": ["https://example.com/media/court-2026.jpg"],
  "mainEntityOfPage": "https://example.com/national/court-directive-sept-2026"
}
</script>

Validate with Rich Results Test before shipping. The Schema.org NewsArticle specification lists recommended and required properties. Do not mark opinion columns or sponsored posts as straight NewsArticle unless the content truly is news reporting — use OpinionNewsArticle or add clear labels.

URL and canonical rules for news desks

Permalinks must be stable after publish. Changing slugs after a story trends breaks shares and splits ranking signals. If you must fix a typo, 301 the old URL and update canonical tags immediately. Our canonical tags guide explains duplicate scenarios common on tag and category archives.

Avoid these URL patterns on news sites:

  • Session IDs or tracking parameters in canonical URLs — strip them at the server.
  • Pagination chains where page 2 competes with page 1 for the same headline.
  • Print-friendly duplicate paths (`/print/`, `?output=amp`) without canonicals.
  • Identical wire copy published under multiple section paths without a chosen primary URL.

E-E-A-T signals matter more for Your Money Your Life adjacent topics — health, finance, legal updates. Build author pages with bios and link them from every byline. The E-E-A-T authority signals guide maps directly to newsroom credibility. On legal-information portals I've worked on, named editors and sourced citations reduced indexation delays noticeably.

How Does Technical Performance Affect Google News Rankings?

Speed is not a tie-breaker for news — it is the entry fee. Slow TTFB means Googlebot may defer your URL while competitors get crawled first. Core Web Vitals still apply, but server response and cache strategy usually move the needle more than micro-optimising hero images on deadline day.

FactorTarget for News SitesWhy It Matters
Time to First ByteUnder 200 ms at edgeCrawl queue priority on breaking desks
Largest Contentful PaintUnder 2.5 s mobileDiscover card eligibility
HTTPS everywhere100% of article URLsHard requirement since 2015
CDN cache on articlesShort TTL, purge on updateHandles traffic spikes without origin melt
Image deliveryWebP/AVIF, explicit width/heightPrevents CLS on liveblogs
robots.txtNever block CSS/JS or /media/Rendering failures hide paywalled previews

WordPress 7.1 newsrooms often lean on caching plugins plus object cache. Custom Laravel stacks give finer control — edge purge hooks on publish, separate cache keys per section. Either path works if TTFB stays low under load. For WordPress-specific tuning, see WordPress development services. For Laravel origin optimisation, speed optimization services cover CDN and PHP-FPM tuning.

Crawl budget on high-volume desks

Large archives with thin tag pages waste crawl budget. Block low-value faceted URLs in robots.txt, but never block article paths or media assets Google needs to render previews. The robots.txt complete guide and crawl budget optimization article go deeper on faceted search traps common on publisher sites.

Performance Priority Stack1. TTFB + CDN Edge Cache2. News Sitemap Freshness3. Image + LCP Tuning4. Schema Validation5. Font/JS Diet
For news SEO, fix server response and sitemap freshness before chasing minor front-end savings

How Do You Measure and Fix News SEO Problems in Search Console?

You cannot improve what you do not measure hourly on a live desk. Google Search Console plus GA4 give you indexation lag, query spikes, and Discover traffic — if UTM and event tagging are configured correctly.

Metrics worth a daily glance

  • URL Inspection latency: publish a test article, submit the URL, note minutes-to-indexed.
  • News tab visibility: track branded and head-term queries in the Performance report filtered by News.
  • Discover clicks: sudden drops often trace to image ratio changes or clickbait rewrites.
  • Crawl stats: watch for 5xx spikes during election nights or budget speech traffic.
  • Manual actions: check Security & Manual Actions weekly — hacked injects kill trust fast.

Wire GA4 custom events for `article_publish` and `article_update` so editors correlate traffic bumps with desk actions. Our GA4 for SEO data analysis guide walks through the reports that actually matter for publishers.

Common failure patterns I've seen in production

Paywall markup without valid structured data leaves Google guessing about free preview length. Infinite scroll category pages that omit `` links hide new URLs from crawlers. Auto-refresh liveblogs that change the canonical on every socket push create duplicate clusters overnight.

Fix liveblogs by keeping one canonical URL, updating `dateModified` in schema on each major revision, and linking new entries with stable fragment IDs. For image-heavy galleries, follow the image optimization complete guide — oversized hero files are the usual LCP culprit on mobile readers in Kathmandu and abroad.

AI Overviews now cite news sources directly. Clear headings, sourced quotes, and factual ledes improve citation odds. Read the AI Overviews citation guide alongside this page. Nepali-language desks should run headlines through a Nepali word counter to hit readable headline lengths without truncation in SERP cards.

Story Not in Google News?Start: URL InspectionNot indexed?Fix robots, sitemapIndexed, no News?Check schema, datesSubmit news sitemapVerify Publisher CenterAlign datePublishedAdd author + publisherRe-test in 30–90 minutesMonitor Search Console
Diagnose missing Google News visibility by separating indexation failures from News-specific markup gaps

Run a full technical pass quarterly — not just after a traffic cliff. The technical SEO audit guide for Nepal adapts cleanly to publisher stacks. For ongoing editorial SEO planning, pair it with SEO content strategy for new sites even if your brand is established — news sections behave like startups every Monday.

Need proof these patterns ship in production? Our Court Marriage In Nepal portal and Notary Nepal project combine timely legal updates with structured content architecture — the same building blocks news desks need at higher volume.

Key Takeaways

  • Verify Publisher Center, map sections to live URLs, and keep your logo and language metadata current.
  • Generate a dedicated news sitemap with only the last 48 hours of articles and ISO 8601 dates.
  • Deploy NewsArticle JSON-LD on every story — headline, author, publisher logo, and dates must match visible content.
  • Protect crawl budget: canonical stable URLs, block thin tag pages, never block CSS, JS, or media paths.
  • Prioritise TTFB and CDN purge on publish before micro-optimising fonts on deadline night.
  • Measure indexation lag daily in Search Console and GA4 — treat 90-minute delays as bugs, not normal.

People Also Ask

Do you still need to apply for Google News inclusion?

No separate application exists anymore. Verify your site in Search Console, configure Publisher Center, publish valid news sitemaps, and follow Google News content policies. Eligibility is earned through consistent technical and editorial quality, not a one-time form.

How long should a news article URL stay in the news sitemap?

Google expects articles to drop out roughly 48 hours after publication. Keep older stories in your standard sitemap only. Leaving stale URLs in the news sitemap dilutes freshness signals and can trigger parsing warnings.

Does AMP still matter for Google News SEO in 2026?

AMP is optional on most publisher stacks today. Responsive pages with strong Core Web Vitals, valid NewsArticle schema, and fast TTFB perform equally well when properly configured. Do not rewrite your CMS for AMP unless you have a measured speed gap on low-end mobile networks.

Can a WordPress or Laravel site compete with large news portals?

Yes, on niche and local beats where crawl speed and topical authority beat raw domain age. A focused Laravel or WordPress 7.1 desk with clean sitemaps, named authors, and section-specific internal linking often outranks national portals on long-tail breaking queries within its coverage area.

Ship News SEO That Keeps Pace With Your Desk

SEO for News Sites Google News Best Practices is mostly engineering discipline — stable URLs, fresh sitemaps, honest schema, and servers that respond before your competitor publishes the follow-up. Nail those foundations and editorial quality gets a fair shot in Google News, Discover, and AI-generated summaries. Need Publisher Center setup, a Laravel news desk, or a technical audit on an existing publisher stack? Contact us or explore professional SEO services in Nepal to plan the next sprint.

Frequently Asked Questions

News SEO is technical indexation under time pressure. Standard SEO chases evergreen rankings over weeks; news SEO chases crawl discovery in minutes. Google News pulls from normal crawling plus optional Publisher Center signals—it adds a topical, time-sensitive layer on top of organic search, not a replacement. The work starts in CMS fields, URL patterns, and server response times before any post-launch keyword spreadsheet.

No separate application exists anymore. Verify your site in Search Console, configure Publisher Center, publish valid news sitemaps, and follow Google News content policies. Eligibility is earned through consistent technical and editorial quality, not a one-time form.

Google expects articles to drop out roughly 48 hours after publication. Keep older stories in your standard sitemap only. Leaving stale URLs in the news sitemap dilutes freshness signals and can trigger parsing warnings.

Verify domain ownership in Search Console and link it inside Publisher Center. Add your publication name, primary language, and category labels matching live site sections. Upload a square logo at least 512×512 px for News cards. Map each section—Politics, Sports, Business—to its URL path, submit your news sitemap URL, and confirm it validates without errors. Review Google News content policies before going live.

A news sitemap is a time-windowed feed of recent URLs, not a renamed standard sitemap. Include only articles from roughly the last 48 hours with publication name, language, ISO 8601 publication_date, and title per URL. Regenerate on every publish event—not once nightly if you break news hourly. Keep the file small and valid; dumping thousands of URLs causes Google to ignore it. On Laravel 12 or 13, trigger generation from a queued job on publish and cache XML for one to five minutes.

Every article page needs NewsArticle JSON-LD matching visible content: headline, datePublished, dateModified, named author with URL, publisher organization with logo, and image. Pair schema with visible bylines and datelines. Validate with Rich Results Test before shipping. Do not mark opinion columns or sponsored posts as straight NewsArticle—use OpinionNewsArticle or clear labels instead. Mismatched dates between HTML, schema, and sitemap are a trust hit that slows indexation.

AMP is optional on most publisher stacks today. Responsive pages with strong Core Web Vitals, valid NewsArticle schema, and fast TTFB perform equally well when properly configured. Do not rewrite your CMS for AMP unless you have a measured speed gap on low-end mobile networks.

Speed is the entry fee, not a tie-breaker. Slow TTFB means Googlebot may defer your URL while competitors get crawled first. Target under 200 ms TTFB at the edge, under 2.5 s LCP on mobile, HTTPS on all article URLs, short CDN TTL with purge on publish, and WebP/AVIF images with explicit dimensions. Never block CSS, JS, or media paths in robots.txt—rendering failures hide previews. Fix server response and sitemap freshness before micro-optimising fonts on deadline night.

Permalinks must stay stable after publish—changing slugs after a story trends breaks shares and splits ranking signals. If you must fix a typo, 301 the old URL and update canonical tags immediately. Strip session IDs and tracking parameters from canonical URLs. Avoid pagination chains where page 2 competes with page 1, print-friendly duplicate paths without canonicals, and identical wire copy under multiple section paths without a chosen primary URL. For liveblogs, keep one canonical URL and update dateModified on major revisions.

Track URL Inspection latency daily—publish a test article, submit the URL, and note minutes-to-indexed; treat 90-minute delays as bugs. Monitor News tab visibility in Performance reports, Discover clicks for sudden drops, crawl stats for 5xx spikes during traffic surges, and Manual Actions weekly. Wire GA4 custom events for article_publish and article_update so editors correlate traffic bumps with desk actions. Diagnose missing visibility by separating indexation failures from News-specific markup gaps.

Yes, on niche and local beats where crawl speed and topical authority beat raw domain age. A focused Laravel or WordPress 7.1 desk with clean sitemaps, named authors, and section-specific internal linking often outranks national portals on long-tail breaking queries within its coverage area. Weak internal linking from section hubs remains a common reason fresh URLs sit uncrawled for hours—fix that before assuming domain age is the blocker.

Paywall markup without valid structured data leaves Google guessing about free preview length. Infinite scroll category pages omitting pagination links hide new URLs from crawlers. Auto-refresh liveblogs that change the canonical on every update create duplicate clusters overnight. Mismatched publication timestamps between HTML, schema, and sitemap—especially storing UTC while displaying Nepali local time—reduce trust. Oversized hero images hurt LCP on mobile readers. Run a full technical pass quarterly, not only after a traffic cliff.

Use ISO 8601 timestamps with your real timezone offset—Nepal runs UTC+5:45, so do not store everything as UTC while displaying Nepali local time. Mismatched dates between HTML, schema, and sitemap are a trust hit. If you publish English and Nepali editions, pair them with correct hreflang markup. Run Nepali headlines through a word counter to hit readable lengths without truncation in SERP and Discover cards.

E-E-A-T signals matter more for Your Money Your Life adjacent topics—health, finance, legal updates. Build author pages with bios and link them from every byline. Named editors and sourced citations reduce indexation delays on legal-information portals. Clear headings, sourced quotes, and factual ledes also improve odds of citation in AI Overviews, which now pull news sources directly. Opinion and sponsored content need distinct schema types or visible labels—not straight NewsArticle markup.

Large archives with thin tag pages waste crawl budget. Block low-value faceted URLs in robots.txt, but never block article paths or media assets Google needs to render previews. Prioritise strong internal linking from section hub pages so fresh URLs get discovered within hours, not only through sitemap polling. Submit only the last 48 hours of articles to your news sitemap and keep the rest in your standard sitemap. Purge CDN cache for your news sitemap file when a major story drops.

Share this article

0 Comments

Leave a comment

Your email is not published. Comments appear once they have been read. Sign in to have your details filled in.

Quick Contact Options
Choose how you want to connect me: