Competitor Content Tracker: Everything They Publish, In One Feed

Watch what every competitor publishes without visiting a single blog.

Content teams find out what the competition shipped when a colleague forwards a link, usually a fortnight late. The information was public the whole time. It just was not collected anywhere.

Give this a list of sites and get every post they published, newest first, with the title, link, date, author, summary and topic tags. The Actor works out where each site publishes on its own, so you never have to hunt for a feed URL.

Built for content marketers tracking a category, SEO teams watching what a rival ranks for next, product marketers on competitive intelligence, and anyone who has to write a weekly "what changed" update.

How it works

flowchart TB
    A[Site list] --> B[Read the home page]
    B --> C{Feed declared<br/>in the head?}
    C -->|yes| F[Parse the feed]
    C -->|no| D{Feed at a<br/>common path?}
    D -->|yes| F
    D -->|no| E{Sitemap?}
    E -->|yes| G[Read sitemap,<br/>keep article URLs]
    E -->|no| H[Reported as<br/>nothing found]
    F --> I[Filter by date<br/>and keywords]
    G --> I
    I --> J[(Your content feed)]

Discovery runs in that order because it moves from most reliable to least. A feed the site advertises is authoritative, a feed at a conventional path is nearly always right, and a sitemap is a last resort that still beats nothing. Whatever it used, the row tells you.

What you get

One row per post. A real row from a live run:

{
  "site": "github.blog",
  "title": "How we make AI coding more cost efficient without sacrificing task quality",
  "url": "https://github.blog/ai-and-ml/github-copilot/how-we-make-ai-coding-more-cost-efficient/",
  "publishedAt": "2026-09-02T18:00:00.000Z",
  "dateMeaning": "published",
  "author": "Erik Kristensen",
  "summary": "Why shorter outputs can cost more, and how GitHub Copilot reduces wasted work across the complete coding task.",
  "categories": ["AI & ML", "Engineering", "GitHub Copilot", "LLMs"],
  "sourceType": "feed",
  "sourceUrl": "https://github.blog/feed/"
}

Dates mean what they say

A feed publishes a real publish date. A sitemap publishes lastmod, which is when the page last changed, and a page can change years after it was written. Both land in publishedAt, and dateMeaning says which one you are looking at, so a refreshed old page is never mistaken for something new.

Watching a topic instead of a whole blog

Add keywords and only posts mentioning those terms in the title, summary or tags come through. This is the difference between tracking a competitor and tracking a competitor's pricing announcements.

{
  "sites": ["competitor.com", "otherrival.com"],
  "days": 7,
  "keywords": ["pricing", "acquisition", "funding", "launch"],
  "onlyNewPosts": true
}

Put that on a weekly schedule with onlyNewPosts on and the dataset becomes a digest that only ever contains things you have not seen.

Run it from the command line

curl -X POST "https://api.apify.com/v2/acts/arched_friend~competitor-content-tracker/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "sites": ["blog.cloudflare.com", "github.blog"],
    "days": 30,
    "maxPostsPerSite": 20
  }'

Pricing

$0.003 per post returned. A site that published nothing in the window costs nothing.

	This Actor	Content monitoring SaaS	RSS reader
20 sites, weekly	about $1 a month	$50 to $300 a month	Free, but no data out
Finds the feed for you	Yes	Sometimes	You paste each one
Works without a feed	Sitemap fallback	Rarely	No
Keyword filtering	Yes	Yes	Limited
Data you own	Dataset, API, webhook	Their dashboard	In the reader

Notes and limits

• Some sites publish neither a feed nor a usable sitemap. Those are reported in the run summary under sitesWithNothing with the reason, rather than failing the run.
• Sitemap rows have no title, because a sitemap lists URLs and nothing else. The URL and the date are still there.
• Feeds usually carry the ten to fifty most recent posts, so a very long lookback returns whatever the feed still holds rather than the full archive.
• Very large feeds are read up to a size cap so one enormous file cannot dominate a run.

Related products

• Brand Mention Monitor for when your competitors are written about elsewhere.
• Hacker News Brand Monitor for the same watch on Hacker News.
• Tech Stack Checker for what those same competitors are running under the hood.