Recently Updated: 17 min read

News Site SEO Checklist: Technical, Editorial, Trust

News Site SEO Checklist: Technical, Editorial, Trust

Short answer: news site SEO rests on three layers. The first is a technical base that Google can reach, with crawlable links and an orderly structure. The second is clarity on every article: an honest headline, a visible date and byline, and fitting markup. The third is trust: who publishes, how the work is produced, why it exists and how readers can get in touch. Google's documents tie none of these to a ranking guarantee, but each helps a site describe itself accurately to readers and to search.

This checklist is for publishers, owners and editors. Joining Google News is not a prerequisite. The Google News policies apply to news surfaces only, while the steps here make sense for ordinary Google Search too. For News-specific rules, see our Google News SEO guide for publishers. This page covers the general technical and editorial health of a news site.

What news readers are really asking

A news query comes from a different need than a how-to query. The reader wants to know what happened, when, and on whose word. Google's documents do not define "news intent" as a separate concept, so the framing in this section is a practical reading of principles found in them, and it should be read that way.

The reader's quick questions

  1. What happened, and when? Dates and update notes decide this one.
  2. Who says so, and on what basis? Author, sources and publisher information answer it.
  3. What happens next? For developing stories, the current status and links to related coverage.

A story page that cannot answer these three questions leaves the reader short, however good the headline is.

Cautions from Google that publishers should hear

Google's creating helpful, reliable, people-first content (Opens in a new tab) page contains two cautions that touch news directly. First, avoid writing about topics simply because they seem trending rather than because they fit your existing audience. Second, avoid promising answers that do not exist; the page's example is suggesting there is a release date for a product, movie or TV show when none is confirmed. For a newsroom this means not presenting an unconfirmed claim in a headline as if it were settled.

The page also lists changing page dates to seem fresh when the content has not substantially changed as a warning sign. If you have not made a meaningful update, leave the date alone.

Story formats and what each reader wants

The table below is a working interpretation, not a classification from the documents.

Content typeWhat the reader needsWhat stands out on the page
Breaking reportWhat happened, current statusHeadline, date, short summary, sourcing
Analysis and opinionWhy it happened, what it meansWriter's expertise, reasoned argument
ExplainerHow something worksSteps, definitions, a current date
InterviewWho said whatThe speaker's identity, context
Local reportWhat is happening nearbyPlace, date, official source

Deciding your beat

No newsroom can cover everything. In line with Google's caution, give priority to subjects that fit your audience and your expertise. For a regional outlet that means local decisions, schools, transport and public services. On large national stories, publish only when you can add something original.

Making the site reachable and orderly

Google Search Essentials has three parts: technical requirements, spam policies and key best practices. The detailed technical requirements live on their own page. For current wording, read the Search Essentials (Opens in a new tab) pages directly. The overview lists key best practices that include creating helpful, reliable, people-first content, using words people would search for (especially in the title and main heading), making links crawlable, following best practices for images, videos, structured data and JavaScript, and using the appropriate method to keep content out of results.

Five access questions

Practical suggestion: run these checks on a regular schedule.

  1. Are the home page, section pages and story pages blocked by robots.txt?
  2. Are story links real links (an anchor with an href) or do they only open through script?
  3. How many clicks does it take to reach a story from the home page?
  4. Do pagination, archive and tag pages produce needless duplicates?
  5. How is content behind a login or subscription wall handled?

These belong to a general technical audit. For ordering and prioritising them, see the technical SEO audit checklist and prioritization.

Index or keep out

The Search Essentials overview names choosing the right method to keep content out of results as a best practice. Which method fits which case is explained in the relevant Google pages. Typical candidates on a news site are internal search results, duplicate archive pages, print-friendly copies and test content. Decide with an editorial list: stories, section pages, author pages and organisation pages belong; duplicates and empty pages do not.

How the site is layered

LayerContentsPurpose
Home pageTop stories, links to sectionsCarry readers and crawlers to sections
Section pagesNews, local, business, sportCoherent topic groups
Story pageOne story, related coverageUnderstood as a standalone document
Author pageBiography and recent workShow who writes
Organisation pagesMasthead, contact, policiesTrust signals

The structure is a suggestion. The number of sections depends on your coverage. What matters is that every story belongs to at least one section and links to related coverage.

Helping new stories get found

A current sitemap helps new stories get discovered. For auditing it, see XML sitemap audit and error fixes. These Google pages set no frequency or format rule specific to news sites, so do not invent one.

Access and structure checklist

  • Are important pages free from robots.txt blocks?
  • Are links crawlable?
  • Can stories be reached from the home page and sections?
  • Are duplicate archive and tag pages under control?
  • Is the sitemap current and accurate?
  • Do images and video follow best practices?

Marking up stories and their dates

Google's Article structured data (Opens in a new tab) page accepts the types Article, NewsArticle and BlogPosting. NewsArticle is one of the listed types. The page gives no extra rule on which type a given site should prefer, so the choice follows your structure.

Property reference

PropertyWhat the page says
headlineThe title of the article. Keep it concise; long titles may be truncated
authorThe author of the article, a Person or an Organization
author.nameThe author's name only
author.urlA link to a page that uniquely identifies the author. sameAs can be used instead
datePublishedWhen the article was first published, in ISO 8601 format
dateModifiedWhen the article was most recently modified, in ISO 8601 format
imageImages that represent the article, not logos or captions

Handling publication and update dates

Providing timezone information is recommended; otherwise Google uses Googlebot's timezone. Add datePublished and dateModified only if they give Google more accurate date information. The Rich Results Test does not warn about them. On a news site the two fields separate first publication from the latest meaningful update. If nothing meaningful changed, do not refresh dateModified. The helpful content page treats date changes without substantial updates as a warning sign.

Marking up the writers

The author guidelines are specific: include every author shown on the page, list each in a separate author entry, give valid url or sameAs values, put only the name in author.name (use jobTitle, honorificPrefix or publisher for other details), and use Person for people and Organization for organisations. A story signed by "Newsroom" is an organisation and can be marked up as one, though readers still need a place where editorial responsibility is explained.

Story images

Image URLs must be crawlable and indexable. The page recommends several high-resolution images in 16x9, 4x3 and 1x1 aspect ratios, each at least 50K pixels (width times height). Limits can change, so check the current page before you rely on a figure.

Before-you-ship markup checklist

  • Does every story page carry Article, NewsArticle or BlogPosting?
  • Is the headline concise and consistent with the visible title?
  • Are datePublished and dateModified in ISO 8601 with a timezone?
  • Is every visible author listed as an author?
  • Does author.name hold only a name, and is there a url or sameAs?
  • Can image URLs be crawled?
  • Does the markup match what the page shows?

For setup detail, see the JSON-LD structured data guide.

Editorial standards and openness

Trust signals are not a single page. They are a promise the whole site makes to readers. Google's helpful content page frames this as Who, How and Why.

The Who, How and Why test

  • Who: It should be clear to readers who created the content. Bylines belong where readers expect them and should lead to background about the author. The page treats made-up creator profiles, such as invented names, false credentials or AI-generated headshots, as deception.
  • How: Explaining how content was produced helps where readers might wonder about it. The page names automation or AI involvement as a case where disclosure is useful.
  • Why: The page calls it perhaps the most important question. Content should exist primarily to help people, not to attract visits from search engines.

Reading E-E-A-T sensibly

The page says E-E-A-T stands for experience, expertise, authoritativeness and trust, and that trust is the most important. It also says E-E-A-T itself is not a specific ranking factor, while a mix of factors that can identify content with good E-E-A-T is useful. Use it as a set of questions, not as a score.

What the News policies ask for

The Google News policies (Opens in a new tab) expect sources on news surfaces to provide clear dates and bylines, information about authors, the publication and the publisher, information about the company or network behind the content, and contact information. These policies apply only to news surfaces. Violations can lead to removal from news surfaces, and ineligible content may still appear elsewhere in Search if it complies with other policies. Even if your site is not in News, the list is a sound transparency yardstick. To check your masthead and contact details, read news site masthead and contact details check.

The same policy page says paid promotional material should not exceed your content. Content that hides or misstates sponsorship as independent editorial is not allowed, and relationships such as ownership, affiliate interest or payment should be disclosed to readers. Publishers also must not use preview content that misleads users by promising details the underlying content does not contain. Checking headlines against story text regularly is a practical safeguard.

Standing pages publishers need

Page or elementWhat it should hold
AboutThe publisher, the team, the purpose
MastheadOwner, responsible editor, address
ContactA reachable email or form
Author pageShort bio, expertise, recent work
Editorial standardsVerification, corrections, sponsorship disclosure
Corrections policyHow errors are reported and fixed

Openness checklist

  • Does each story show a date and a byline?
  • Does the byline link to an author page?
  • Are publisher and contact details easy to find?
  • Is sponsored content clearly marked?
  • Does any headline or preview promise something the story lacks?
  • Are corrections shown openly?

A rhythm for audits

A news site changes daily, so the audit has to be a habit. The calendar below is a suggestion; Google's documents do not set an audit period.

Each week

  1. Spot-check new stories for headline, date, byline and markup.
  2. Look for broken links on top stories.
  3. Read crawl and indexing warnings in Search Console.

Each month

WeekFocusOutput
1Technical: robots.txt, sitemap, crawlabilityIssue list
2Stories: markup, date and author fieldsSample report
3Trust: masthead, contact, author pages, policiesUpdated pages
4Performance: images, speed, old content cleanupPrioritised to-do list

Each quarter

  • Review older stories: still accurate, or in need of a correction?
  • Refresh author pages.
  • Check whether Search Essentials or the News policies have changed. Limits and rules in Google documents can change; look at the current page before you act.

Why a log pays off

Record each audit with the finding, the owner and the date. Knowing what changed and when tells you next month what worked. Without a log, the same problem is rediscovered at every audit.

Where a small local newsroom should start

The decision question is this: for a small local newsroom, which three things come first? A team with little time cannot do everything at once. The order below is a suggestion, and Google's documents set no priority order.

The ordering rule

  1. Access and crawlability first. If pages are closed to Google, nothing else matters. Check robots.txt, noindex and link structure.
  2. Story page completeness second. Give every story a clear headline, visible date, byline and matching markup. It raises the value of each story separately.
  3. Transparency pages third. About, masthead, contact and author pages. It is a low-cost, lasting trust investment.

Dependency drives the order: markup on a page nobody can reach is wasted, and a story without a byline has nothing to link to an author page.

The local advantage

A local outlet's strength is knowledge nobody else holds. Original reporting, announcements checked against official sources and local interviews answer the question Google's page asks: does the content provide original information, reporting, research or analysis? Republishing agency copy unchanged gives that advantage away.

Ranked table

RankAreaMain jobExpected effect
1Crawlabilityrobots.txt, links, sitemapPages can be discovered
2Story pageDate, byline, markupClarity at page level
3TransparencyMasthead, contact, author pagesReader trust
4ContentOriginal local reporting, corrections flowDifferentiation
5PerformanceImages, speed, mobileEase of use

The effect column is not a ranking promise. It shows the direction in which the site explains itself better to readers and to search.

Building one story page

Site checks matter, but so does how one story page is built. The table gathers the requirements above into one template. Each row names its source, and rows marked as a practical suggestion are not drawn from the documents.

FieldWhat it should beSource
HeadlineAccurate, not misleading, conciseArticle headline, News policies
Main headingConsistent with the headline, one per pageSearch Essentials: searched words in the main heading
BylineVisible author with a link to an author pageHelpful content page, Article author
Publication dateVisible and equal to the markupNews policies, datePublished
Update dateOnly for meaningful changesHelpful content page, dateModified
ImageRepresents the story, crawlable URLArticle image
SourcingWhere the information came fromPractical suggestion
Related storiesInternal links on the same subjectPractical suggestion

Writing the first paragraph

The first paragraph should tell readers what happened, where and when. Whatever the headline promises must be delivered there, because the News policies do not allow misleading preview content that promises details the underlying content lacks. If something is not yet confirmed, say so inside the sentence rather than presenting it as settled.

Stories that keep developing

When you update a developing story, refresh dateModified and let readers see what changed. Practical suggestion: add a short update note at the top or bottom ("Update: statement added after the meeting"). That ties the new date to a real change and stops readers mistaking old information for new.

Handling corrections

When a story is corrected, mark the correction visibly. Silent edits damage trust. Publishing a corrections policy fits the News policies' wish for information about the publication and a way to contact it. The Google pages do not require a corrections page, so this is a suggestion.

Example scenario: a new business news site before launch

Example scenario: a team prepares a digital-only business news site with a handful of sections. They want the basics right before the first story goes live, so they build a short pre-launch review instead of fixing problems afterwards.

  1. Reachability. They confirm the staging rules do not carry over to the live site. Robots.txt must not block section pages, and no site-wide noindex should remain from the build phase.
  2. Story template. They fix the fields every story carries: headline, byline linked to an author page, visible publication date, optional update note and a representative image. The template then writes matching Article markup from the same fields.
  3. Standing pages. They publish an about page, a masthead with an editorial contact, a corrections policy and a sponsorship disclosure rule before the first story appears.
  4. Review habit. An editor owns a short monthly sample check of markup and bylines.

The scenario describes an order of work. It sets no timeline and promises no outcome.

Why launch is the cheapest moment

Changing a template before hundreds of pages exist costs far less than repairing hundreds of pages later. A launch checklist also makes the standards visible to every new writer from the first day.

Splitting the review findings

A team can sort what it finds into three piles. Blockers stop discovery and must go first. Template work covers fields and markup that repeat on every story. Habits are the recurring checks that stop the same mistakes coming back. Sorting this way keeps urgent work from crowding out durable fixes.

Notes on media, phones and speed

The Search Essentials overview lists following best practices for images, videos, structured data and JavaScript among its key practices. News pages are heavy on images and video, so a few notes help.

  • Images that represent the story. The Article page asks for images that represent the article, not logos or captions.
  • Crawlable image URLs. An image behind a CDN rule or login does nothing for markup.
  • Ads and embeds. Promotional material that outweighs content conflicts with the News policy on paid material.
  • Mobile reading. Headline, date and byline should be visible on a phone. This is a suggestion; the Google pages here set no separate mobile rule for news sites.

Detailed speed and performance rules are outside this checklist. For measurement steps, use the performance items in the technical SEO audit checklist mentioned above.

Slips newsrooms repeat

  • Refreshing dates all the time. Without a meaningful update, a changed date is a warning sign.
  • Chasing every trending topic. Covering subjects that do not fit your audience is the behaviour Google cautions against.
  • Unsigned stories. The question of who wrote it stays unanswered.
  • Misleading headlines. Misleading previews that promise details the story lacks are not allowed under the News policies and cost reader trust anyway.
  • Markup that disagrees with the page. If the marked-up author differs from the visible one, trust suffers.
  • Hidden sponsorship. Sponsorship relationships should be disclosed.
  • An unattended archive. Old errors remain uncorrected.

A pre-publication card

Use a short pre-publication card: does the headline match the story, are date and byline present, are sources named, is sponsorship marked. An editor should finish it in two minutes. Cards that grow long get skipped.

Related guides: Article Markup for News Sites: Date and Author Fields, How to Write a Corrections and Updates Policy for a News Site.

Conclusion

News site SEO combines a technical base, clear story pages and visible trust. Google Search Essentials lists technical requirements, spam policies and key practices. The Article page gives concrete rules for headline, author and ISO 8601 dates. The News policies and the helpful content page ask for clear dates, bylines, publisher information and contact details. For a small local site the order is crawlability, then story page completeness, then transparency pages. No item guarantees rankings or admission to Google News; the aim is to present the site accurately and credibly to readers and to search.

If you want to explore advertising and promotion options that support a news site's reach, take a look at the ad spaces. Scope and terms are described on the product page.

Frequently Asked Questions

Do I need to be in Google News to use this checklist?

No. The Google News policies apply to news surfaces only, and content that is not eligible there can still appear elsewhere in Search if it complies with other policies. This checklist is useful for general Google Search and sets no News enrolment requirement.

Which markup type should news stories use?

Google's Article page accepts Article, NewsArticle and BlogPosting. It gives no extra rule about which type a particular site should choose. The headline, author, datePublished, dateModified and image properties are explained on that page.

When should I update dateModified?

Per the Article page it is the date the article was most recently modified, and it should be added if it gives Google more accurate date information. The helpful content page treats changing dates without substantial updates as a warning sign, so refresh it only for meaningful changes.

Why does author information matter?

Google's helpful content page says readers should be able to tell who created the content, and bylines should lead to information about the author. Made-up author profiles count as deception. The Article markup also asks that every visible author be listed in a separate author entry.

Where should a small local news site begin?

As a practical suggestion: crawlability first, then story page completeness (date, byline, markup), then transparency pages (about, masthead, contact, authors). This order is not taken from Google's documents.

What do Google's pages say about sponsored content?

The Google News policies say paid promotional material should not exceed your content, sponsorship must not be hidden or presented as independent editorial, and relationships such as ownership, affiliate interest or payment should be disclosed to readers. These policies apply to news surfaces.

Will following this checklist raise my traffic?

There is no guarantee. Google's documents do not promise rankings. The steps make a site reachable, understandable and trustworthy; results depend on competition, content quality and reader behavior.

0 Comments

No comments yet for this article.

Post a comment

Please log in to leave a comment. Login