# Blog Archive Taxonomy Extractor (`junipr/blog-archive-taxonomy-extractor`) Actor

Extract blog/archive taxonomy, categories, tags, authors, dates, pagination, article URLs, and archive health from public blog index pages

- **URL**: https://apify.com/junipr/blog-archive-taxonomy-extractor.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** SEO 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 archive page scanneds

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

## Blog Archive Taxonomy Extractor

Extract an article inventory from public blog index, category, tag, author, and archive pages. The Actor links visible cards to article URLs and captures titles, authors, publish and update dates, categories, tags, pagination position, duplicate URLs, and missing archive evidence.

This is designed for editorial migrations, archive quality audits, taxonomy cleanup, and content operations. It works from visible `<article>` cards first and can fall back to parseable `Article` or `BlogPosting` JSON-LD when a page does not expose article cards.

### What is extracted

- absolute article URLs resolved against the archive page;
- visible article titles from headings or card links;
- author names from author-labelled elements;
- `datetime`, `data-published`, and `data-updated` values;
- category and tag labels from common class and `rel=tag` patterns;
- `Article` and `BlogPosting` headline, URL, author, dates, article section, and comma-separated keywords;
- pagination page number for each archive source;
- repeated article URLs across supplied archive pages;
- missing URL, title, author, and publish-date evidence.

The Actor never fills missing authors or dates from guesses. A record with incomplete evidence is preserved and marked with an archive issue so the inventory remains useful.

### Input

Use `archiveUrls` for public archive pages, `sitemapUrls` for a bounded set from XML sitemaps, or `htmlInputs` for captured archive HTML.

| Field | Purpose | Default / cap |
| --- | --- | --- |
| `archiveUrls` | Public archive, category, tag, or author-index URLs | empty |
| `startUrls` | Additional public archive URLs | empty |
| `sitemapUrls` | Public XML sitemaps | empty |
| `htmlInputs` | Captured records with `sourceUrl` and HTML | empty |
| `followPagination` | Follow a same-domain `rel=next` link | `false` |
| `maxDepth` | Maximum `rel=next` depth | 0 by default, maximum 1 |
| `maxArchivePages` | Maximum accepted archive pages | 1 by default, maximum 25 |
| `maxArticles` | Maximum article records per archive page | 100, maximum 1,000 |
| `extractAuthors` | Extract visible or structured author names | `true` |
| `extractTags` | Extract categories and tags | `true` |
| `extractDates` | Extract publication and update dates | `true` |
| `allowedDomains` | Optional hostname allowlist | empty |
| `includeEvidence` | Keep evidence excerpts in rows | `true` |
| `includeRawSnapshots` | Store raw accepted archive HTML | `false` |
| `maxChargeUsd` | Stop before the next event exceeds this amount | 15 USD maximum |

Example:

```json
{
  "archiveUrls": ["https://blog.example/archive"],
  "followPagination": true,
  "maxDepth": 1,
  "maxArchivePages": 2,
  "maxArticles": 100,
  "extractAuthors": true,
  "extractTags": true,
  "extractDates": true,
  "allowedDomains": ["blog.example"],
  "maxChargeUsd": 3
}
```

When pagination is enabled, only the first same-domain `rel=next` URL on an accepted page can enter the bounded queue. Other discovered links are not crawled. The Store default has no archive source and returns a nonempty `source_required` diagnostic.

### Dataset output

Each dataset item has stable provenance plus archive fields:

- `archiveUrl` identifies the page where the article record appeared;
- `articleUrl` and `articleTitle` identify the linked content;
- `authorName`, `publishedDate`, and `updatedDate` preserve visible or structured values;
- `categories` and `tags` are arrays suitable for spreadsheet or database import;
- `paginationPage` is an integer beginning at 1;
- `duplicateArticleUrl` is set when the same resolved URL appeared previously;
- `archiveHealthIssue` records missing evidence, duplicates, blocked sources, or source diagnostics;
- `issueCode`, `severity`, `evidenceSnippet`, and `recommendation` explain what needs attention;
- `sourceUrl`, `canonicalUrl`, `httpStatus`, and `scannedAt` preserve source context.

Turning an extraction toggle off returns the affected fields as null or empty arrays and prevents those omissions from being flagged. `maxArticles` is applied before dataset rows are produced.

### Reports

With reports enabled, key-value storage receives:

- a Markdown run summary;
- a CSV with every article and diagnostic row;
- a JSON issue list;
- bounded evidence excerpts;
- metadata with page counts, row counts, issue codes, pricing mode, and consumed input fields.

Raw archive HTML is opt-in and stored separately from ordinary reports.

### Pay-per-event pricing

| Event | Price (USD) | When charged |
| --- | ---: | --- |
| `actor-start` | 0.0100 | after successful startup |
| `archive-page-scanned` | 0.0065 | once for each accepted archive source unit |
| `taxonomy-record-extracted` | 0.00295 | before a paid article/taxonomy row |
| `archive-issue-emitted` | 0.00295 | before a paid archive diagnostic or duplicate row |
| `audit-report-generated` | 0.0800 | before report artifacts are stored |

Apify platform usage pass-through is off. Before an output row or report is written, the Actor verifies the next event fits within `maxChargeUsd` and that the charge was fully accepted.

### Safety and limits

The fetcher accepts only public HTTP and HTTPS URLs. Loopback and private IPv4 targets are rejected. Domain allowlists, page caps, request timeouts, and bounded delays are applied before fetching. It does not bypass access controls or human-verification challenges; those sources produce diagnostics.

Archive markup varies. Client-rendered cards may require captured HTML from an authorized browser workflow. A missing field means it was not observed in the accepted source, not that the underlying article lacks it. Validate dates, author identity, canonical URLs, and taxonomy policy before a migration or bulk editorial change.

# Actor input Schema

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

Public blog archive, category, or author-index URLs.

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

Optional public archive URLs; archiveUrls is preferred for role clarity.

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

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

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

Optional records with sourceUrl and html or currentHtml for deterministic extraction.

## `followPagination` (type: `boolean`):

Follow only same-domain rel=next links, bounded by maxDepth and maxArchivePages.

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

Extract visible author names when present in archive entries.

## `extractTags` (type: `boolean`):

Extract visible category and tag labels when present.

## `extractDates` (type: `boolean`):

Extract visible publish or update dates when present.

## `maxArchivePages` (type: `integer`):

Maximum archive pagination pages to inspect.

## `maxArticles` (type: `integer`):

Maximum article links to extract from archive pages.

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

Optional hostname allowlist for fetched pages.

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

Maximum pages to fetch in one run.

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

Maximum same-domain pagination depth to follow from the start URL.

## `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
{
  "archiveUrls": [],
  "startUrls": [],
  "sitemapUrls": [],
  "htmlInputs": [],
  "followPagination": false,
  "extractAuthors": true,
  "extractTags": true,
  "extractDates": true,
  "maxArchivePages": 1,
  "maxArticles": 100,
  "allowedDomains": [],
  "maxPages": 1,
  "maxDepth": 0,
  "includeEvidence": true,
  "includeRawSnapshots": false,
  "requestDelayMs": 250,
  "timeoutMs": 15000,
  "userAgentMode": "standard",
  "maxChargeUsd": 15,
  "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/blog-archive-taxonomy-extractor").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/blog-archive-taxonomy-extractor").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/blog-archive-taxonomy-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/blog-archive-taxonomy-extractor"
        }
    }
}

```

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/HoXhL1QJ3Tuy1wbhG/builds/drxmcxxphlp3g7Zs9/openapi.json