Track Publication Cadence
track_publication_cadenceAnalyze a company domain to measure long-form publishing volume and trend, returning post counts, monthly average, and cadence trend (accelerating, steady, declining, dormant) with reliability flags.
Instructions
Given a company domain, measure how much long-form work that company publishes and whether the rate is rising or falling. Returns post counts for the last 30 days, 90 days and 12 months, a monthly average, and a cadence_trend of accelerating, steady, declining, dormant or unknown, plus the percent change behind it. The trend compares the last 90 days against the prior 275 days, both normalized to posts per month. Also returns the blog URL, the format mix (blog posts, guides, reports, case studies, whitepapers, podcasts, videos, press releases, research), the number of distinct bylines, and how the post list was discovered. This measures EDITORIAL output volume, not product changelogs: a release feed is detected and rejected rather than counted. Publication dates are read from the post pages themselves, because sitemap lastmod was measured to be a modification date that runs later than publication by a median of 151 to 1653 days. When a site's date field turns out to track edits rather than publication, date_source_reliable comes back false and every count is nulled rather than reported wrong, so check that field before quoting a number. Counts are a census when the archive fits the page budget and a scaled even sample otherwise, flagged by counts_are_estimate. Public sitemaps, feeds and pages only. Returns flat Clay-ready JSON. Read-only; requires an APIFY_TOKEN and consumes Apify credits per domain analyzed.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | A single company domain, e.g. zapier.com. Provide either domain or domains. | |
| domains | No | Batch mode: several company domains analyzed in one call. Takes precedence over domain. | |
| batchSize | No | How many domains to analyze concurrently. Default 2. | |
| skipCache | No | Force a fresh crawl and ignore the 3 day result cache. | |
| max_pages_to_date | No | How many post pages to fetch per domain for dating. Default 400. Above this cap the counts are estimated from an even sample across the archive and counts_are_estimate is set true. Raise it for a tighter number on a large archive, at the cost of run time. | |
| domain_time_budget_ms | No | Hard wall-clock ceiling per domain, default 75000. When it is nearly spent the crawl stops and the row is returned with partial_result true and reduced confidence rather than timing out. |