Editorial Calendar URL Inventory avatar

Editorial Calendar URL Inventory

Pricing

from $6.50 / 1,000 url record profileds

Go to Apify Store
Editorial Calendar URL Inventory

Editorial Calendar URL Inventory

Create an editorial inventory from public URLs with publish and update dates, authors, content types, categories, status clues, seasonal hooks, and refresh cadence recommendations.

Pricing

from $6.50 / 1,000 url record profileds

Rating

0.0

(0)

Developer

junipr

junipr

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

17 days ago

Last modified

Share

Turn accepted content pages and archive pages into calendar-ready, source-linked editorial inventory rows. The Actor extracts content URL, title, content type, author, publication and update dates, categories or tags, and explicit scheduling rules. Missing fields remain visible in inventoryStatus so content operations teams can review incomplete records before import.

Use it for editorial inventories, refresh calendars, author or category exports, seasonal review planning, and content-operations worksheets. The Actor reports what is present in accepted HTML or Article JSON-LD. It does not infer unpublished dates, hidden authors, or editorial ownership.

Supported sources

The Actor recognizes:

  • repeated <article> cards with links, headings, authors, dates, categories, or tags;
  • Article, BlogPosting, and NewsArticle JSON-LD records;
  • direct content pages when no archive card or supported structured record is present.

Seasonality and cadence are applied only through your supplied rules. A seasonality rule may contain name, one or more regular-expression patterns, and reviewMonth or month. A cadence rule may contain patterns plus cadence, refreshCadence, or cadenceMonths. Invalid optional patterns are ignored without creating a scheduling claim.

Input

FieldPurposeDefault / cap
contentUrlsIndividual content pages to retrieveempty
archiveUrlsArchive or listing pages to retrieveempty
extractAuthorsExtract visible or structured author namestrue
extractCategoriesExtract visible or structured categories and tagstrue
seasonalityRulesExplicit pattern-to-season or review-month mappingsempty
cadenceRulesExplicit pattern-to-refresh-cadence mappingsempty
maxUrlsMaximum accepted URL sources25 maximum
maxRecordsMaximum inventory rows100 default, 500 maximum
htmlInputsCaptured content or archive recordsempty
allowedDomainsOptional hostname allowlist for retrievalempty
maxPagesMaximum pages retrieved1 default, 25 maximum
includeEvidencePreserve evidence excerpts in rowstrue
includeRawSnapshotsStore accepted raw source HTMLfalse
maxChargeUsdStop before the next event exceeds this amount10 USD maximum

Example:

{
"archiveUrls": [
"https://publisher.example/archive"
],
"extractAuthors": true,
"extractCategories": true,
"seasonalityRules": [
{
"name": "Tax season",
"patterns": ["tax checklist", "filing deadline"],
"reviewMonth": "January"
}
],
"cadenceRules": [
{
"patterns": ["operations", "reliability"],
"cadence": "6 months"
}
],
"maxRecords": 100,
"allowedDomains": ["publisher.example"],
"maxChargeUsd": 3
}

Disable author or category extraction when those fields are not part of the intended inventory contract; disabled fields become null or empty and are not counted as missing. The Store default has no source and returns a nonempty source_required diagnostic.

Dataset output

Every row includes common provenance plus:

  • contentUrl and contentTitle for the inventory record;
  • contentType from archive context or structured metadata;
  • authorName, publishedDate, and updatedDate when observed;
  • categories as a deduplicated string array;
  • seasonalHook and recommendedReviewMonth only when a supplied seasonality rule matches;
  • refreshCadence only when a supplied cadence rule matches;
  • inventoryStatus as complete or a precise missing_... value;
  • issueCode, evidenceSnippet, recommendation, httpStatus, and scannedAt for QA.

The inventory status is a field-completeness check, not a content-quality grade. A complete row may still need owner validation, publication-state review, or taxonomy normalization before entering an editorial system.

Reports

When includeReport is enabled, key-value storage receives a Markdown summary, full CSV, issue rows in JSON, bounded evidence excerpts, and run metadata. Raw accepted HTML is stored only when includeRawSnapshots is explicitly enabled.

Pay-per-event pricing

EventPrice (USD)When charged
actor-start0.0100after successful startup
url-record-profiled0.0065once for each accepted URL record source
editorial-field-validated0.0065before a paid complete inventory row
inventory-issue-detected0.00295before a paid incomplete or diagnostic row
qa-report-generated0.0800before QA report artifacts are stored

Apify platform usage pass-through is off. Higher-tier Store discounts are reserved in the pricing policy. maxChargeUsd is evaluated before each event; rejected, partial, or over-budget charges stop the related output write.

Safety and interpretation

Only HTTP and HTTPS sources are retrieved. Loopback and private IPv4 destinations are rejected, optional hostname allowlists narrow accepted hosts, and URL counts, row counts, response size, and timeouts remain bounded. Links found inside accepted archive cards are recorded but not crawled. Access-denied and human-verification pages return diagnostics.

Archive markup varies across publishers, and structured metadata can be incomplete. Review missing-field rows, normalize taxonomies and author identities, and confirm publication state before importing records into a calendar or assigning editorial work.