Keyword Cannibalization & SEO Collision Monitor

Compare recurring SERP and ranked-keyword datasets to detect pages competing for the same query, ranking collisions, cannibalization drift and SEO consolidation opportunities.

Why use this Actor

Teams following alt data changes need repeatable evidence and prioritized actions instead of repeatedly inspecting raw rows by hand.

Key features

• Buyer-native inputs aligned to keyword cannibalization monitor.
• Predictable structured output in the default Apify Dataset.
• Pay Per Event pricing tied to measurable result rows or reports.
• Optional MCP connector delivery for downstream automation and AI agents.

Quick start

Start with this working example and replace the target values with your own:

{
  "currentItems": [
    {
      "id": "entity-a",
      "entity": "Alpha",
      "category": "growth",
      "value": 132,
      "date": "2026-09-01",
      "source": "current"
    },
    {
      "id": "entity-b",
      "entity": "Beta",
      "category": "risk",
      "value": 78,
      "date": "2026-09-01",
      "source": "current"
    },
    {
      "id": "entity-c",
      "entity": "Gamma",
      "category": "new",
      "value": 55,
      "date": "2026-09-01",
      "source": "current"
    }
  ],
  "previousItems": [
    {
      "id": "entity-a",
      "entity": "Alpha",
      "category": "growth",
      "value": 100,
      "date": "2026-08-01",
      "source": "previous"
    },
    {
      "id": "entity-b",
      "entity": "Beta",
      "category": "stable",
      "value": 92,
      "date": "2026-08-01",
      "source": "previous"
    }
  ],
  "maxItems": 20000
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

• currentItems — Current records: Current source or normalized rows to analyze.
• currentDatasetId — Current Apify Dataset ID: Optional Apify Dataset ID used when currentItems is not supplied.
• previousDatasetId — Previous Apify Dataset ID: Optional previous Apify Dataset ID used instead of previousItems.
• maxItems — Maximum records: Maximum records loaded from a Dataset input.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

The Dataset exposes predictable machine-readable output. Representative fields include results.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.011500 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

• Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
• Use the Actor from API or schedules for recurring collection, comparison or monitoring.
• Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
• Compare repeat runs when the product supports snapshots or previous-run inputs.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

• Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
• Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
• Analytical outputs depend on the quality and coverage of the supplied or collected source data.
• Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

Detailed documentation

Detailed documentation

Detailed documentation

Why use this Actor

Teams following alt data changes need repeatable evidence and prioritized actions instead of repeatedly inspecting raw rows by hand. This Actor sits above raw extraction: supply a current dataset, optionally add a previous snapshot, and receive an aggregated report built for recurring monitoring and AI-agent workflows.

Key features

• Current-versus-previous snapshot comparison with deterministic deltas.

• Gen2 confidence-scored GO/WARN/BLOCK decision contract.

• Agent-ready recommended actions instead of raw rows.

• Dataset-ID inputs for recurring Apify workflows.

• Reads inline JSON rows or Apify Dataset IDs with limited READ permission.

• Writes one auditable report to the default Dataset and INTELLIGENCE_REPORT.

Example

Use the prefilled example or replace currentItems with rows from an upstream Actor. On recurring runs, provide the prior period in previousItems or previousDatasetId. The Actor normalizes common aliases, compares snapshots, ranks the strongest entity changes and emits agentAction.

Use cases

• alt data monitoring and prioritization.
• zero direct intelligence recurring workflows.
• competitive research and executive briefs.
• AI-agent decision pipelines.

Pricing

One primary pay-per-event outcome: one decision-ready intelligence report. Base price USD 0.011 before Apify tier discounts. The 256 MB data-first architecture is designed for strong unit economics.

Limitations

• Analyzes supplied public or appropriately licensed data and does not bypass restricted sources.
• Scores are decision-support signals, not predictions or guarantees.
• Keep stable identifiers across snapshots for best change detection.
• Zero-direct-competition status is rechecked before publication because the Store changes continuously.

Workflow

upstream dataset -> current snapshot -> optional previous snapshot -> normalization -> entity aggregation -> change scoring -> ranked signals -> agentAction.