What does a site's publishing pace tell a media buyer?
Part of MFA avoidance
The short answer
A site's publishing pace shows up in public files: XML sitemaps, news sitemaps and RSS feeds carry dates for recent articles. A sudden jump in volume, clockwork posting intervals or a burst on new topics can point to a content farm. Real newsrooms also surge around events, so pace is a lead to investigate, never a verdict.
Key takeaways
- Sitemaps, news sitemaps and feeds each show a different slice of a site's output, so a buyer reads all three before counting.
- Google defines sitemap lastmod as the last significant update, not the first publication, so it measures revisions as well as new articles.
- No source cited here sets a posts per day limit; Google's scaled content abuse policy judges unoriginal volume with little to no value, however it was made.
- Coverage of sudden events can surge and then decline toward a baseline, as a 2026 study of 126,602 news articles describes.
- Pace earns weight only when it agrees with content evidence from the articles themselves.
How can a buyer see how often a site publishes?
Publishers expose their output in machine readable files so search engines can find new pages. Those same files let a buyer count articles by date without access to the site's analytics. Each file has rules that limit what it shows, and reading one without knowing those rules produces a wrong count.
| Source | What it shows | What it leaves out |
|---|---|---|
| XML sitemap | Page URLs, with an optional lastmod that Google defines as the last significant update | First publication date; lastmod changes when an old page is revised |
| News sitemap | Articles created in the last two days, each with its original publication date | Anything older than two days; Google allows up to 1,000 news entries per sitemap |
| RSS or Atom feed | Recent items, each with an optional pubDate for when it was published | Older items; Google notes a feed only provides information on recent URLs |
| Article page | A visible date and byline, and datePublished or dateModified in structured data | Nothing beyond that page, so it confirms a date rather than counting volume |
Count a site's recent output in five steps
- Find the files. Look for a sitemap line in the site's robots.txt, then for a sitemap index, a news sitemap and a feed link in the page source.
- Separate articles from other pages. Drop tag, category, author and product URLs, which inflate counts without being new writing.
- Count by publication date where one exists. Use pubDate from the feed and the news sitemap's publication date; treat lastmod as revision activity.
- Repeat the snapshot. A news sitemap and a feed each hold only recent items, so saving them a few days apart builds a longer record.
- Spot check five articles. Open them and compare the visible date and byline with the dates in the files.
What do sitemaps reveal about a site?
Google's sitemap guide (opens in a new tab), updated July 8, 2026, caps one sitemap at 50MB uncompressed or 50,000 URLs and lets larger sites group files under a sitemap index. The structure of that index is itself a clue. A site whose index splits posts by month shows its history at a glance: the number of files per month and the URLs in each trace how output grew.
The same guide says lastmod should reflect the date and time of the last significant update to the page, and that Google ignores priority and changefreq values. That makes changefreq useless as evidence and lastmod a measure of editing, not of writing. A site where thousands of pages share one lastmod value has likely regenerated its pages in one pass, which says more about its publishing system than its newsroom.
Sitemaps also show proportion. When a site lists a few hundred articles and tens of thousands of tag or city pages, the index tells the buyer what the site is built to produce. The templated content guide explains how to judge those generated pages.
What publishing pace suggests a content farm?
None of the sources cited here sets a posts per day threshold, and a buyer should be wary of anyone who offers one. Google's spam policies (opens in a new tab), updated August 28, 2026, define scaled content abuse as many pages generated for the primary purpose of manipulating search rankings and not helping users, with unoriginal content "that provides little to no value to users, no matter how it's created." The test is value, not volume. Pace matters because some patterns are hard to explain any other way.
| Pattern in the files | What it can point to | Innocent reading to check |
|---|---|---|
| Output jumps from a few posts a week to dozens a day in one month | A change of owner or a switch to generated pages | A newsroom launch, a merger of sister sites, or a news event |
| Posts at even intervals around the clock, seven days a week | A scheduler publishing a queue of produced pages | A wire feed or a global newsroom across time zones |
| Hundreds of items share one publication minute | A bulk import or a scrape of another site | A migration that reset dates on the archive |
| A burst on topics the site never covered before | A site chasing high value ad keywords | A new section with its own named editor |
| Feed dates far newer than the dates on the articles | Old pages re-dated to look fresh | A feed that lists updated stories again |
The hard cases sit in the first row. A sudden rise after a domain changed hands is the pattern the expired domains guide describes, and it deserves a look at the archive. A rise driven by generated articles is covered in the AI generated content guide. Pace only tells the buyer which sites to open first.
How do newsroom publishing patterns look?
Definition
- Event surge
- A short rise in a publisher's output around a news event, followed by a decline toward its usual level. It is the normal shape of news coverage, not a sign of automation.
A study by Emily Lugos and Maurício Gruppi, submitted to arXiv (opens in a new tab) on April 15, 2026, tracked coverage of catastrophic and violent events in a corpus of 126,602 news articles from online publishers. Its abstract describes events with rapid surges in coverage that then follow gradual declines toward the baseline. A storm, an election or a trial can lift a local site's output sharply for a week, and the files will show it.
Newsroom output has other tells that a buyer can see in the same files. Bylines vary and recur across months. Weekdays and weekends differ. Dates in the feed match the dates printed on the articles. Google's publication date guidance (opens in a new tab) asks sites to show a user visible date and to label it, for example as published or last updated, and says Google does not depend on a single date factor because all factors can be prone to issues. A buyer can borrow that habit and check more than one date source before drawing a line.
Should publishing pace ever exclude a site alone?
No. A count of dated URLs says how much a site published, not what it published. The same burst can come from a scheduler pushing generated pages or from a local newsroom covering a flood. Exclusion needs content evidence: articles that repeat each other, say nothing specific, or copy other sites. Pace decides the order of review, and the articles decide the outcome.
Before a pace finding goes on a site's record
- The count used publication dates, with lastmod activity recorded apart.
- Tag, category, author and product URLs were removed from the count.
- At least two snapshots of the feed or news sitemap were compared, a few days apart.
- Five articles from the burst were opened and their visible dates matched the files.
- A news event, launch or migration was considered as an explanation and noted.
- The finding names the content evidence that supports it, or says there is none.
What does a publishing pace review look like on a real brief?
Fictional example
A tax preparation brief in Idaho and Montana
A fictional Boise tax preparation firm asks its agency for a display plan in Idaho and Montana from February to April, beside personal finance guides, small business news and local coverage. Twenty sites pass the content review, and the planner reads each one's sitemap index and feed.
A Billings small business blog doubles its output in March. The new posts carry two familiar bylines, cover filing deadlines and local payroll rules, and the same jump appears in the previous March. The planner records a seasonal pattern and keeps the site.
A personal money site shows forty items with one publication minute in its feed, then a steady posting rhythm every twenty minutes, day and night, on topics from mortgages to pet insurance. The planner opens five of them, finds near identical openings, and sends the site to review with the content evidence attached. A Missoula news site with a quiet feed but a recent flood story surge stays on the list.
How does PlacementGraph read sitemaps and feeds on candidate sites?
Frequently asked questions
What if a site has no sitemap or feed?
Then the files cannot show its pace, and that absence is not a finding. A small publisher may never have set up either file. Count from the site's own section pages and archive instead, by opening the newest and oldest pages in a section and reading the visible dates.
Does a news sitemap show a site's full archive?
No. Google's news sitemap rules say to include only articles created in the last two days, with up to 1,000 news entries per sitemap. It is a rolling window. Saving it on several days builds a record of recent output, but the older archive has to come from the regular sitemap or the site itself.
Can publication dates in feeds be wrong?
Yes. The RSS 2.0.11 specification makes pubDate optional, and a migration or a theme setting can reset dates on old posts. Google itself says it does not rely on a single date factor because all can be prone to issues. Compare the feed date, the visible date and the structured data before trusting any one.
Does a slow publishing pace mean a site is weak?
No. A specialist who writes one long, reported piece a week can be a better placement than a site that posts all day. A long silence is worth noting, because an abandoned site can change hands, but a slow steady pace can simply be what original work looks like.
Sources
- Build and submit a sitemap (opens in a new tab)Google Search Central (updated July 8, 2026)
- Create a News sitemap (opens in a new tab)Google Search Central (updated December 10, 2025)
- RSS 2.0 Specification, version 2.0.11 (opens in a new tab)RSS Advisory Board (March 30, 2009)
- Influence your byline dates in Google Search (opens in a new tab)Google Search Central (updated December 10, 2025)
- Spam policies for Google web search (opens in a new tab)Google Search Central (updated August 28, 2026)
- Tracking the Temporal Dynamics of News Coverage of Catastrophic and Violent Events (opens in a new tab)Emily Lugos and Maurício Gruppi, arXiv (April 15, 2026)
Researched and written by PlacementGraph Research. Read how we research, source and update these pages. Corrections: diana@placementgraph.com.