Most niche sites that add a news section do it for one of three reasons. They want fresh content, they want to catch spikes in demand, or they want to look active. Whether the section helps the rest of the site depends on something else: whether each post gives a reader and a search engine a reason to treat it as worth keeping. This article separates what Google has said on the question, what the 2024 documentation leak does and does not show, and what you can check in your own data. It ends with a checklist for publishing news that earns trust.
One note on evidence first. This piece does not publish invented percentages. Where a claim about how news URLs behave on a site can only be settled with your own Search Console data, the article tells you how to read that data instead of quoting figures nobody can verify. That is slower, but the result is more useful to you than a table of numbers you could not check.
- The short answer
- What Google has actually said
- Why news is a different kind of page on a niche site
- What network-level data can and cannot tell you
- What the 2024 leak does and does not prove
- Google News versus Google Search: not the same thing
- Content pruning for news archives
- A 10-point checklist for publishing news that earns trust
- Setting a sensible publishing rhythm
- Deciding whether your site should run news at all
- Frequently asked questions
- Summing up
The short answer
News posts can help a niche site, and they can also drag it down. The format does not decide which. Four things do:
- Fit. The post belongs to the topic the site is already known for.
- Contribution. It adds something the reader cannot get from the source it summarises.
- Lifespan. The site plans for what happens to the post once the story is over.
- Proportion. News does not crowd out the pages that carry the site's long-term value.
A site that publishes five original, sourced news items a month in its own subject is in a different position from a site that rewrites forty press releases a week to feed a "latest" page. Search engines can tell these two apart through ordinary quality evaluation, and Google's public guidance describes the difference clearly enough.
What Google has actually said
Google's guidance on this is spread across the helpful content documentation, the core update documentation and the spam policies. Read them directly, because the wording is revised over time. The official pages are the source of truth, and what follows is a summary, not a replacement.
Scaled content
The spam policies name scaled content abuse: producing many pages mainly to manipulate rankings and not to help users. The policy says the method of production is not the point. Automation, human writers or a mix can all fall under it. The point is the purpose and the value of the output.
For a news section, that matters because news is the easiest format to scale. A feed, a template and a rewrite step can produce dozens of pages a day. If each page is a thin restatement of another page, the section looks like the thing the policy describes, however the pages were made.
The helpful content guidance asks questions that fit this situation well. Is the content original information, reporting or analysis? Does it add substantial value compared with other pages in results? Does the site produce lots of content on many different topics in the hope that some of it performs? Those questions are written for self-assessment. A news section that fails most of them is a risk to the whole site, not only to itself.
Deleting content
Google's public line, repeated by its search liaison and in documentation, is that you do not need to remove content simply because it is old, and that age alone is not a reason to delete. The core update guidance also says that if a site was hit, the answer is not a mechanical deletion exercise. It is an honest look at whether the content is helpful and reliable.
That is not the same as saying removal is never right. The helpful content guidance has also described removing unhelpful content as something that may help the rest of the site, in the sense that a large amount of low-value material can weigh on how a site is perceived. Both statements can be true. Old but useful content should stay. Content that is thin, duplicated and has no reader should be improved, merged or removed. We return to this under content pruning below.
Dates
The helpful content questions include a warning about changing dates to make pages seem fresh when the content has not substantially changed. For news this has two consequences:
- A visible date on a news post is a claim. If you update the post, say what changed. If you did not change anything meaningful, do not move the date.
- Dates in structured data and on the page should agree with each other. Google's documentation on date handling says it uses several signals and prefers consistent ones. Check the current wording on the official page.
News gets its value from being dated honestly. A post from last March that still reads correctly is an asset. The same post with a refreshed date and unchanged text is a small signal of the wrong kind.
Why news is a different kind of page on a niche site
A niche site usually has two kinds of page.
Evergreen pages answer a question that stays asked: how something works, what to compare, how to do a task. Their value builds over time and they are updated, not replaced.
News pages answer a question that is asked for a short window: what just happened. Their value peaks early and then falls, unless the post becomes the reference for a story that keeps developing.
These two kinds have different life cycles, different link patterns and different risks. Evergreen pages invite scrutiny on depth and accuracy. News pages invite scrutiny on sourcing, originality and speed. A site that mixes the two without a plan tends to end up with a large archive of pages whose purpose expired the week after publication.
There is also the question of competition. For most newsworthy events in a niche, the primary source (a regulator, a company, a court, a researcher) and several large publishers already have pages. A small site that adds a fourth paraphrase has no particular reason to be shown. A small site that adds something the others lack, such as a comparison table, context from its own subject expertise or a direct reading of the primary document, does.
What network-level data can and cannot tell you
The commissioning idea for this article was to compare how news URLs and evergreen URLs behave across a group of sites: how many get indexed, how impressions look after 30 and 90 days, and what happens to news that lacks a primary source or an original table.
This article does not report figures for that comparison, because none are supplied with it that can be cited and checked. Quoting numbers without a source would be the kind of false precision that makes SEO writing unreliable. What can be said honestly is what such a comparison would show, how to run it on your own property and how to read the result.
The three comparisons worth making
1. Share of URLs indexed, by type. In Search Console, the page indexing report lists URLs that are indexed and URLs that are not, with reasons. Export the list, tag each URL as news or evergreen (a URL folder, a category or a template flag is enough) and compare the shares. Many sites find the "discovered, currently not indexed" and "crawled, currently not indexed" statuses concentrate in whichever section is thinnest or most repetitive. If news is where they concentrate on your site, that tells you something about how the section is being assessed. Treat it as a pattern to investigate, not a verdict.
2. Search performance at fixed ages. For each news URL, compare search impressions in the first 30 days after publication with the next 60 days (days 31 to 90). News posts typically show a spike and a decline. The useful questions are whether the posts have any tail at all and whether the tail belongs to specific kinds of posts. Evergreen pages usually look different: slow start, longer plateau. Use the Search Console performance report filtered by page, and be careful with sampling and date ranges when you export.
3. Outcome by post features. Split the news posts into groups by features you can verify by reading them:
- cites and links a primary source
- contains an original table, chart or comparison
- adds named analysis or context from the site's own expertise
- is a plain rewrite with none of the above
Then compare indexing status and impressions across the groups. The expectation, in line with Google's own helpful content questions, is that posts with a primary source and original material hold their place longer than pure rewrites, and that pure rewrites are the group most likely to sit unindexed or fade fast. That is an expectation based on published guidance. Your data may confirm it, partly confirm it or contradict it, and only your data can say.
Reading the result without fooling yourself
- Small groups mislead. Ten posts in a group do not support a conclusion. Look for consistent direction across a larger set.
- Topics differ. A post on a breaking regulatory change and a post on a minor product update live in different demand conditions. Compare like with like.
- Links change outcomes. A news post that earns links from other sites behaves differently regardless of its format. Note which posts got links.
- Timing interacts with updates. If a core update fell inside your 90-day window, you cannot attribute a change purely to post quality. The Google algorithm update history is a useful reference for lining up your dates against known rollouts.
What the 2024 leak does and does not prove
In 2024, documentation describing a large number of internal Google Search API attributes became public and was analysed by many SEO practitioners. It is a list of fields and descriptions, without the code that uses them, and without any weights. Two attribute names come up often in discussions of content quality and news-style publishing.
contentEffort
contentEffort appears in the documentation as an attribute linked to an estimate of the effort behind a page's content. Analysts have read it as a model-derived signal that tries to capture how much work went into producing the page, such as whether it looks original and costly to make or easy to copy.
What it suggests: Google has, at least in the version that was documented, a concept that resembles "effort" at the page level. That is consistent with the public guidance about original information and added value.
What it does not prove: that this attribute is used in ranking at any given time, how much it counts, what inputs feed it or how it applies to news. A field existing in documentation is not evidence of a live ranking factor with a particular effect.
siteFocusScore
siteFocusScore appears alongside a related attribute, siteRadius, in the documentation on site-level topical measures. The common reading is that Google can compute how concentrated a site's content is on a topic, and how far an individual page sits from the site's central theme.
What it suggests: topical focus may be measured at site level. That is consistent with the guidance against producing lots of content on many unrelated topics. For a niche site, it supports the idea that news posts far from the core subject are a cost.
What it does not prove: that a low score causes a particular ranking loss, that there is a threshold or that adding off-topic news pages lowers your score by a known amount. It also does not tell you whether the attribute is still in use.
How to use leak material responsibly
Treat the leak as a source of hypotheses, not as a rulebook. Where a field name matches Google's public guidance, it can strengthen your confidence that the guidance is meant seriously. Where it matches nothing public, do not build a content plan on it. Google has said publicly that documentation of this kind can be out of date or lack context. For a broader view of how rank signals are usually discussed, see the overview of Google ranking factors and how to improve your website's position.
Google News versus Google Search: not the same thing
When people search for advice on news SEO, they often mix two different surfaces.
- Google Search, including the Top stories feature, which can show recent articles for newsworthy queries.
- Google News, the product and app, with its own content policies and its own inclusion process.
Some of the work overlaps: clear article structure, accurate dates, named authors, transparent ownership and original reporting help in both. But the policies and eligibility rules are separate, and they change. If you want to be considered for Google News, read the current content policies and Publisher Center documentation on the official Google pages instead of relying on a secondhand summary, including this one. The same applies to news sitemaps and any structured data requirements: check the current developer documentation.
For a niche site that is not a news publisher, the realistic aim is usually not to become a news outlet. It is to publish occasional timely pieces that suit the topic, hold up on their own and do not dilute the site.
Content pruning for news archives
Content pruning in SEO means removing, merging or improving pages that no longer serve a purpose. For news archives it is a sensible exercise, provided it is done with care and not as a reaction to a ranking drop.
A workable approach looks like this:
- List every news URL with its publication date, indexing status, search impressions and clicks over a long enough period, and any links pointing to it.
- Mark each post as one of four types: still useful as written; useful but out of date; superseded by a newer or more complete page; no longer useful.
- Decide per type.
– Still useful: leave it, and make sure it links to the current related pages. – Out of date but useful: update it with real changes and note what changed. – Superseded: redirect it to the page that replaces it, if the topic matches closely. – No longer useful, with no links and no traffic: remove it, so it returns a not-found or gone response, or exclude it from search if it must remain for readers. The noindex tag article explains when that option makes sense and when it does not.
- Do it in batches and watch indexing and crawl behaviour before the next batch.
Two cautions. First, do not delete pages with links or steady readers just because they are old, since this runs against Google's public position. Second, do not use noindex as a way to hide a quality problem you intend to leave. If a page is not worth indexing, ask whether it is worth keeping.
A 10-point checklist for publishing news that earns trust
Use this before publishing any news post on a niche site. It is built from Google's public helpful content questions and from general editorial practice, not from any leaked field.
- Name the primary source and link to it. A regulator's notice, a company statement, a filing, a paper. If you cannot identify one, say that the story rests on secondary reports, and treat it with caution.
- State what is new, in the first paragraph. The reader should know what happened, when and why it matters to your audience.
- Add something the source does not. A comparison table, a timeline, an explanation of consequences for your readers, or a plain-language reading of the document. If you add nothing, reconsider publishing.
- Keep it inside your subject. If you would not publish a guide on the topic, think twice before publishing news on it. Off-topic posts spread the site thin.
- Show who wrote it and who checked it. A real author with a visible profile and relevant background, and an editorial note on corrections where it applies.
- Date it honestly. Show the publication date, and show an update date only when the content changed in a way a reader would care about. Describe the change.
- Separate fact from opinion. Label analysis as analysis. Do not present speculation as reporting.
- Link to your evergreen pages. The news post should point readers to the lasting explainer on the subject, and the explainer should be updated where the news changes it. This also supports the site's topical structure. The piece on semantic connectivity and outbound links covers how those connections work.
- Plan the afterlife. Decide at publication whether the post will be updated, merged into a guide, left as a dated record or retired. Put a review date in your calendar.
- Check technical basics before release. Indexable status, correct canonical, working structured data where you use it, consistent dates in page and markup, and no accidental
noindex. Verify in the live page and in Search Console after publication.
If a post fails the first three points, it is likely to be a rewrite that offers no reason to be shown. That is the kind of page to skip.
Setting a sensible publishing rhythm
A rhythm should follow what you can do well, not a target number. Some practical guidance:
- Fewer, better posts. A site with a small team is better off covering the handful of developments that matter to its readers than chasing everything.
- Speed is not the only edge. Large publishers will be faster. A niche site can be more useful, by being more specific, more careful or more complete.
- Use news as a trigger to update evergreen pages. Often the better outcome of a development is a revised guide, not a new post.
- Avoid automation without editing. Automation can help with monitoring sources, tracking changes and preparing drafts of tables. Publishing unedited output at volume is exactly where scaled content concerns arise. The article on SEO automation discusses where automation helps and where it needs a person.
It is also worth thinking about where search is heading. As answer-style results grow, pages that merely restate facts have less to offer than pages that add analysis or original material. The guide on the age of answers looks at that shift for site owners.
Deciding whether your site should run news at all
A short test helps.
- Does your audience ask for it? If readers regularly want to know what changed in your subject, news has a purpose.
- Can you add original value on most posts? If the honest answer is "rarely", a news section will mostly produce pages like the ones Google's guidance warns about.
- Do you have capacity to maintain it? News needs ongoing editing, review and pruning. An abandoned news section is a liability.
- Would the evergreen part of the site gain? If news pushes readers toward your lasting pages and earns links to them, it supports the whole. If it competes with them or distracts from them, it does not.
If most answers are no, a "what changed" page or a periodically updated guide can serve the same readers with less risk. If most are yes, start small, measure with the three comparisons above and expand only if the data supports it.
Frequently asked questions
Does publishing news help the rest of my site rank? There is no public statement from Google that publishing news raises rankings elsewhere on a site. News can support a site by earning links, attracting readers who then use other pages and showing active editorial work. It can also weigh on a site if it adds many thin or off-topic pages. The effect depends on quality and fit.
Are news posts harder to get indexed than evergreen pages? Not by definition. Indexing depends on discovery, perceived value and technical setup. Thin, repetitive pages in any section are more likely to remain unindexed. Compare the indexing status of your own news and evergreen URLs in Search Console to see what applies to your site.
Should I delete old news posts? Not simply because they are old. Google's public position is that age alone is not a reason to remove content. Review each post: keep what is still useful, update what can be improved, redirect what has been replaced and remove only what serves no one and has no links. Do this in batches and watch the results.
Does changing the date on an updated news post help? Changing a date without a substantial change to the content is the practice Google's helpful content guidance warns against. Update the date only when the post has really changed, and describe the change for readers.
Do contentEffort and siteFocusScore mean I must stay strictly on topic? The leaked documentation shows that these attributes exist and suggests what they are meant to capture. It does not show their weight or whether they are active. The sensible conclusion is the one Google's public guidance already supports: keep the site coherent and make each page worth its place.
Is Google News SEO the same as SEO for news articles in regular search? They overlap in practice but are separate. Google News has its own policies and inclusion process, while news articles in Search can appear in places such as Top stories. Check the current official documentation for each before making plans.
What is the minimum a news post should include? A named primary source, a clear statement of what is new, and something of your own: analysis, a table, a timeline or context that a reader cannot get from the source alone. Without that, the post is a rewrite.
Can I use noindex on news posts I do not want in search? Yes, noindex is a legitimate tool for pages that should exist for readers but not appear in search. It is not a substitute for deciding whether a page deserves to exist. Review the noindex tag guide for the rules and the common mistakes.
Summing up
News on a niche site is neither a ranking trick nor a risk in itself. Google's public guidance asks the same questions of every page: does it offer original value, does it fit the site, is it honest about its dates and sources, and was it made for readers? The 2024 leak adds two field names, contentEffort and siteFocusScore, which are consistent with that guidance but cannot be used to claim specific effects. The reliable way to find out what news does for your site is to compare indexing and impressions at fixed ages in your own data, split by whether posts have a primary source and original material, and to prune with care. Publish fewer posts, make each one earn its place, and plan what happens to it after the story moves on.