Content Velocity Tracker - Blog Publishing Cadence per Site avatar

Content Velocity Tracker - Blog Publishing Cadence per Site

Pricing

Pay per event + usage

Go to Apify Store
Content Velocity Tracker - Blog Publishing Cadence per Site

Content Velocity Tracker - Blog Publishing Cadence per Site

For any list of websites: how often they publish (posts per month over the last 12 months from sitemaps), last publish date, trend, and a status like active, slowing or went quiet. Find companies that stopped blogging, benchmark competitors, schedule weekly.

Pricing

Pay per event + usage

Rating

0.0

(0)

Developer

Musedenny

Musedenny

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Security

Limited permissions

Share

Content Velocity Tracker – Blog Publishing Cadence per Site

For any list of websites: how often they publish. Posts in the last 30, 90 and 365 days, a 12-month series, last publish date, trend (growing, steady, slowing) and a status: active, slowing, went quiet, no dated content, no sitemap or unreachable.

Built for content and SEO agencies (find companies whose blog went quiet: they need help), competitive content benchmarking, and sales teams using "they stopped marketing" as a signal.

How it works

  1. Reads robots.txt and the sitemaps (sitemap indexes followed; blog/news/post sitemaps first; product, tag, author and page sitemaps skipped; up to 25 files).
  2. Keeps content URLs (/blog/, /news/, /insights/, /resources/, /press/… or anything in a post sitemap). Help-center and docs pages are excluded because they get bulk-edited.
  3. Counts <lastmod> / news publication dates by month.
  4. Unreliable dates are detected: if a CMS stamps every URL with one date, or half a big archive was "modified" this month (a bulk re-save), sitemap dates are ignored and the site's RSS/Atom feed is used instead (found from the homepage <link rel="alternate"> or common paths, blog subdomain included). Feeds hold only the latest 10–50 posts, so countsAreLowerBound is set and no trend is claimed.

Scheduled runs also report newContentSinceLastRun: dated content newer than the last run's latest date.

Input

FieldDefaultMeaning
urls–Domains or website URLs
onlyStatus[]e.g. went quiet, slowing
maxSites10000Cap per run

Output

{
"domain": "buffer.com", "status": "slowing", "contentSection": "resources, press, insights", "lastPublished": "2026-10-30",
"daysSinceLast": 2, "posts30d": 41, "posts90d": 79, "posts365d": 471, "avgPerMonth12m": 39.2, "trend": "slowing",
"monthly": {"2025-12": 52, "…": 0, "2026-11": 0}, "dateSource": "sitemap", "sitemapDatesReliable": true, "countsAreLowerBound": false,
"totalUrls": 3443, "contentUrls": 1920, "sitemapsRead": 11, "latestUrls": ["https://buffer.com/resources/…"],
"previousLastPublished": null, "newContentSinceLastRun": null
}

Status rules: went quiet = nothing new for 180+ days; slowing = 90–180 days, or the last 3 months well below the 9 before; active otherwise.

Note: lastmod records when a page changed, which is usually but not always when it was published. Treat counts as publishing activity, not an exact post count.

Pricing (pay per event)

$0.001 per run and $0.002 per site: 500 sites for $1.