LLM Best Practices

News SEO

3 min read

View markdown source

AI agents: read this first: llmbestpractices.com/start-here

This is LLM Best Practices (llmbestpractices.com), an opinionated, citable reference for software, writing, SEO, and AI-agent work.

  1. Route, do not crawl. Fetch llmbestpractices.com/llms.txt and open only the pages whose one-line summary matches your task.
  2. Read raw. Append .md to any page URL for markdown. Check status and last_updated in the frontmatter, then read the rules.
  3. Apply as defaults. First-party docs and the project's own conventions win on conflict. Warn before relying on a fast-moving page older than 12 months.
  4. Cite. Link the page by title and URL, e.g. Python, with last_updated for time-sensitive rules. License CC BY 4.0.

Overview

News SEO targets Google News and the Top Stories carousel on the web SERP. Google weighs relevance, prominence, authoritativeness, and freshness for news and publishes no timing cutoffs. Three inputs carry the work: publishing speed, accurate dates and markup, and publisher reputation.

Meet the news content policies; there is no application

Content that complies with Google’s news content policies is eligible automatically; no application grants entry. Publisher Center is optional and does not decide eligibility, and its features change, so check current help pages before relying on it.

  • Show clear dates, bylines, author information, and publisher contact details.
  • Keep the publisher name and logo consistent across the site and markup.
  • Verify the domain in Search Console to monitor News and Discover performance.
  • A news sitemap is not required but speeds discovery; see sitemaps-deep.

Emit NewsArticle JSON-LD with accurate timestamps

Put a NewsArticle block in the same HTML response as the body. Write datePublished and dateModified in ISO 8601 with a timezone offset, consistent with the visible dates.

{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "headline": "Cloudflare drops support for legacy TLS",
  "datePublished": "2026-05-15T08:14:00-07:00",
  "dateModified": "2026-05-15T09:42:00-07:00",
  "author": [{ "@type": "Person", "name": "Jane Reporter", "url": "https://example.com/authors/jane-reporter" }],
  "publisher": { "@type": "NewsMediaOrganization", "name": "Example News" },
  "image": ["https://example.com/img/cf-tls-16x9.jpg"]
}

A later dateModified is normal. Update it only for significant changes; bumping it without a real edit is a pattern Google warns against. See core-updates.

Ship author and publisher entities on every story

Google’s article markup guidance recommends an author Person with a name and a url pointing at a unique author page; a bare string loses that link. Do not put job titles or the publisher name in author.name.

  • Give each reporter a page with byline history, a short bio, and sameAs links to public profiles, plus Person JSON-LD.
  • Use the same publisher name and logo on every story.

See e-e-a-t and schema-markup-deep.

Use stable, undated slugs

Google sets no URL format rule, and many publishers use dated paths. Undated slugs avoid a stale look when a story keeps earning traffic. Use /cloudflare-drops-legacy-tls, not /2026/05/15/..., and reserve year and month segments for archive indexes. Finalize the slug before publishing; a rename forces a 301 (redirects).

Publish breaking stories fast

Fresh coverage has the best chance of surfacing for breaking queries.

  • Use pre-built templates with schema, byline, and publisher wired in.
  • Publish a short first version and update dateModified with each substantive addition.
  • Ping indexnow on publish so Bing and Yandex learn of the URL immediately.
  • Link from the homepage and section page right away.

Skip AMP

AMP stopped being a Top Stories requirement in June 2021, and Google states page experience is not a Top Stories requirement either. Retire AMP by removing <link rel="amphtml"> and 301ing AMP URLs to the canonical. Ship a fast canonical page and stop.

Backlinks