Shopify Blog Tracker — Articles, Dates & Publishing Activity

What is this brand actually publishing?

Every article a Shopify store lists, newest first, with the full text on the recent ones. Point it at a list of competitors and read a season of their content strategy in one sheet.

No API key. No login. No Shopify partner account. No proxies.

Try it in one click. The input form opens already filled in: deathwishcoffee.com, newest 50 articles. That run returns 50 articles in about 5 seconds, for $0.26.

---

The number other tools cannot give you

Shopify serves blog posts through an Atom feed. That feed stops at 30 posts per blog, and paging parameters are ignored — ?page=2 and ?page=3 return byte-identical responses with the same 30 articles. Measured 2 September 2026.

So a tool built on the feed alone tells you a store has 30 posts. Here is what these stores actually publish:

Store	Articles published	What the feed alone returns
deathwishcoffee.com	368 across 8 blogs	122
rothys.com	3,852	~30 per blog
allbirds.com	80	80

This actor reads the store's own sitemap as well, so blogArticlesTotal is the real count and you can see at a glance whether a brand publishes weekly or has posted twice since 2023.

---

What you get

One row per article:

Which blog — blogHandle, blogTitle, blogArticlesTotal

The article — articleTitle, articleUrl, imageUrl, summary, author, tags

When — publishedAt, daysSincePublished, lastModified, daysSinceModified

How complete — hasFullText, and the body itself when you ask for it

---

Two modes

Default — recent articles, complete. Everything the Atom feed covers: full text, author, tags, real publish dates. This is the mode for tracking activity.

Archive on — everything the store lists. Adds every older article from the sitemap: title, URL, image and modification date. hasFullText is false on those rows and publishedAt is left empty, because a modification date is not a publish date and this actor does not pretend otherwise.

Run it on deathwishcoffee.com and the default gives 122 articles; archive on gives all 368.

---

Example output

One row per article — the newest post on deathwishcoffee.com from the prefilled run:

{
  "storeDomain": "deathwishcoffee.com",
  "blogHandle": "recipes",
  "blogTitle": "Death Wish Coffee - Recipes",
  "articleTitle": "How to make an affogato with our Vanilla Coffee",
  "articleUrl": "https://www.deathwishcoffee.com/blogs/recipes/how-to-make-our-vanilla-affogato",
  "publishedAt": "2026-09-28T09:31:00-04:00",
  "lastModified": "2026-09-28T14:35:36-04:00",
  "daysSincePublished": 5,
  "daysSinceModified": 5,
  "author": "Austin Trainor",
  "tags": "",
  "summary": "",
  "imageUrl": "https://cdn.shopify.com/s/files/1/0271/7209/articles/Almond-Afterlife-Affogato_f11edb25-1b05-4b2b…",
  "hasFullText": true,
  "blogArticlesTotal": 94
}

Real rows from runs on 4 October 2026; long text and long lists are shortened here, the dataset has them in full.

---

Typical uses

• Compare content cadence across a category. Twenty brands, sorted by blogArticlesTotal and last publish date. Who is investing in content and who quietly stopped.
• Watch a competitor week by week. Set the day filter to 7 and schedule it.
• Find the topics a brand keeps returning to. Tags and titles across the whole archive.
• Feed a content brief. Recent articles come with the body text.

---

Input

Field	What it does
storeUrls	The stores to read. Normal website addresses.
daysBack	0 for everything, or a window — 7 for a weekly check.
includeArchive	Add every older article the sitemap lists, without body text.
includeBody	Add the article text. Only recent articles have one.
maxArticlesPerStore	Upper limit per store. Large brands publish thousands.

---

What it costs

$5.00 per 1,000 articles, plus $0.005 per run. Apify's Starter, Scale and Business plans get 10%, 20% and 30% off.

Your run	You pay
The newest 50 articles from one store	$0.26
One store's full 368-article archive	$1.85
10 stores, about 10 new articles each	$0.51

Billed per article delivered. A store with no blog returns nothing and costs nothing beyond the run start — and plenty of stores have blogs with nothing in them. Platform usage is included. No proxies are needed, so there are no proxy costs.

---

How it works

Two public sources, combined:

1. sitemap.xml → sitemap_blogs_N.xml — every blog, every article, with titles and modification dates. This is where the real count comes from.
2. /blogs/<handle>.atom — the 30 most recent posts per blog, with full text, author, tags and publish dates.

Headless storefronts are followed to their real shop. Brands running a custom front end are resolved to the Shopify shop named in their own markup — mejuri.com resolves this way.

Both sources are XML the store publishes for search engines. No HTML parsing means a theme change cannot break it.

---

Honest limits

• Only the 30 most recent posts per blog carry body text, an author and a publish date. This is Shopify's limit, not a design choice — see the measurement above. Older rows are marked hasFullText: false.
• lastModified is a modification date, not a publish date. A 2019 article edited last month shows last month. It is reported under its own name and never copied into publishedAt.
• Blogs with no articles are common. gymshark.com publishes 10 blogs and 0 articles. The run reports that rather than failing, and bills nothing.
• Stores with no blog sitemap have no blog, and are reported per store.
• Article counts come from what the store publishes to search engines. Unpublished drafts and hidden posts are not there — which is correct, but it is not the store's admin view.

---

Scheduling

Content programmes run in quarters. Schedule this monthly against a competitor list and the archive count plus last publish date tells you who is still investing — usually before it shows up anywhere else.

Pair it with tidyfeed/shopify-new-arrivals for product launches and tidyfeed/shopify-store-report for the commercial picture.

---

Legal

This actor reads only data a Shopify store publishes publicly, at addresses the store itself serves to search engines. It collects no personal data, requires no login, and bypasses no access control. You remain responsible for how you use the exported data.

---

Questions, or a store that behaves oddly? Open an issue on the actor — issues are read and answered.