# Editorial Calendar URL Inventory (`junipr/editorial-calendar-url-inventory`) Actor

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

- **URL**: https://apify.com/junipr/editorial-calendar-url-inventory.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** SEO tools, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.50 / 1,000 url record profileds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Editorial Calendar Url Inventory

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

| Field | Purpose | Default / cap |
| --- | --- | --- |
| `contentUrls` | Individual content pages to retrieve | empty |
| `archiveUrls` | Archive or listing pages to retrieve | empty |
| `extractAuthors` | Extract visible or structured author names | `true` |
| `extractCategories` | Extract visible or structured categories and tags | `true` |
| `seasonalityRules` | Explicit pattern-to-season or review-month mappings | empty |
| `cadenceRules` | Explicit pattern-to-refresh-cadence mappings | empty |
| `maxUrls` | Maximum accepted URL sources | 25 maximum |
| `maxRecords` | Maximum inventory rows | 100 default, 500 maximum |
| `htmlInputs` | Captured content or archive records | empty |
| `allowedDomains` | Optional hostname allowlist for retrieval | empty |
| `maxPages` | Maximum pages retrieved | 1 default, 25 maximum |
| `includeEvidence` | Preserve evidence excerpts in rows | `true` |
| `includeRawSnapshots` | Store accepted raw source HTML | `false` |
| `maxChargeUsd` | Stop before the next event exceeds this amount | 10 USD maximum |

Example:

```json
{
  "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

| Event | Price (USD) | When charged |
| --- | ---: | --- |
| `actor-start` | 0.0100 | after successful startup |
| `url-record-profiled` | 0.0065 | once for each accepted URL record source |
| `editorial-field-validated` | 0.0065 | before a paid complete inventory row |
| `inventory-issue-detected` | 0.00295 | before a paid incomplete or diagnostic row |
| `qa-report-generated` | 0.0800 | before 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.

# Actor input Schema

## `contentUrls` (type: `array`):

Public content URLs to inventory for editorial planning.

## `archiveUrls` (type: `array`):

Public archive, category, or listing URLs to extract content URLs from.

## `extractAuthors` (type: `boolean`):

Extract visible author names when present.

## `extractCategories` (type: `boolean`):

Extract visible category labels when present.

## `seasonalityRules` (type: `array`):

Rules with name, pattern or patterns, and reviewMonth.

## `cadenceRules` (type: `array`):

Rules with name, pattern or patterns, and cadence or cadenceMonths.

## `maxUrls` (type: `integer`):

Maximum URLs to inspect in one run.

## `maxRecords` (type: `integer`):

Maximum editorial inventory records to emit.

## `startUrls` (type: `array`):

Optional public page URLs to analyze when actor-specific URL fields are not used.

## `sitemapUrls` (type: `array`):

Optional public XML sitemap URLs. Accepted pages remain bounded by maxPages.

## `htmlInputs` (type: `array`):

Optional captured HTML records with sourceUrl and html or currentHtml for deterministic analysis.

## `allowedDomains` (type: `array`):

Optional hostname allowlist for fetched pages.

## `maxPages` (type: `integer`):

Maximum pages to fetch in one run.

## `maxDepth` (type: `integer`):

General link discovery is disabled.

## `includeEvidence` (type: `boolean`):

Include short source evidence snippets in output rows.

## `includeRawSnapshots` (type: `boolean`):

Opt in to raw HTML artifacts in key-value storage.

## `requestDelayMs` (type: `integer`):

Delay in milliseconds between outbound page requests.

## `timeoutMs` (type: `integer`):

Maximum time in milliseconds to wait for a page request.

## `userAgentMode` (type: `string`):

User agent profile to use for public page requests.

## `maxChargeUsd` (type: `number`):

Maximum estimated PPE spend before the actor exits gracefully.

## `includeReport` (type: `boolean`):

Write the markdown summary report to the run key-value store.

## Actor input object example

```json
{
  "contentUrls": [],
  "archiveUrls": [],
  "extractAuthors": true,
  "extractCategories": true,
  "seasonalityRules": [],
  "cadenceRules": [],
  "maxUrls": 25,
  "maxRecords": 100,
  "startUrls": [],
  "sitemapUrls": [],
  "htmlInputs": [],
  "allowedDomains": [],
  "maxPages": 1,
  "maxDepth": 0,
  "includeEvidence": true,
  "includeRawSnapshots": false,
  "requestDelayMs": 250,
  "timeoutMs": 15000,
  "userAgentMode": "standard",
  "maxChargeUsd": 10,
  "includeReport": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `report` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/editorial-calendar-url-inventory").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/editorial-calendar-url-inventory").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call junipr/editorial-calendar-url-inventory --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/editorial-calendar-url-inventory"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/hg85ROcNzFhHR4b7R/builds/g5pLOvDUmk452copD/openapi.json