Search Result Title Meta Diff Checker

Compare SERP displayed titles/snippets against live page title/meta/canonical data to identify rewrites, stale results, mismatches, and migration issues

Who it is for

Search Result Title Meta Diff Checker helps seo teams, content managers, migration qa teams, agencies compare SERP displayed titles/snippets against live page title/meta/canonical data to identify rewrites, stale results, mismatches, and migration issues. It produces schema-valid dataset rows, evidence-backed KVS reports, safe diagnostics, and capped pay-per-event pricing for predictable Apify Store runs.

Compare captured SERP titles and snippets with matching live-page title, meta description, and canonical evidence. Explicit classifications separate exact matches, minor rewrites, brand additions, truncation, full rewrites, missing values, canonical mismatches, stale captures, and unavailable page sources.

Evidence contract

The actor emits only facts visible in supplied HTML, explicit input records, or a permitted public URL response. It never creates rankings, questions, modules, suggestions, titles, snippets, or page metadata to fill an evidence gap. A missing source produces a schema-valid status row explaining what input is needed.

Network access is conservative. Only HTTP and HTTPS URLs are accepted; localhost, loopback addresses, private IPv4 ranges, and disallowed domains are rejected. The runtime does not follow links discovered in a page. Challenge and access-denied pages are recorded as blocked evidence and are not solved or circumvented.

Input modes

• Pass captured rows in serpResults with query, resultUrl, displayedTitle, and displayedSnippet.
• Pass matching htmlInputs for deterministic page evidence.
• Set fetchLivePages only when public result URLs may be requested; allowedDomains, maxLiveFetches, and timeoutMs bound the operation.
• Captured dates are compared with staleThresholdDays; missing or invalid dates are not treated as stale.

Example input

{
  "serpResults": [
    {
      "query": "junipr seo tools",
      "resultUrl": "https://example.com/tools",
      "displayedTitle": "junipr SEO Tools",
      "displayedSnippet": "Evidence-backed SEO automation.",
      "capturedAt": "2026-07-01T00:00:00.000Z"
    }
  ],
  "htmlInputs": [
    {
      "sourceUrl": "https://example.com/tools",
      "html": "<title>junipr SEO Tools</title><meta name=\"description\" content=\"Evidence-backed SEO automation.\"><link rel=\"canonical\" href=\"https://example.com/tools\">"
    }
  ],
  "fetchLivePages": false,
  "maxSnapshots": 1,
  "maxChargeUsd": 35
}

Dataset output

Each dataset item is one JSON object, which makes the result directly usable in Apify integrations, exports, webhooks, and downstream data pipelines.

• displayed and live titles with a titleDiffType classification
• displayed snippet and live meta description with a snippetDiffType classification
• canonical mismatch and stale-signal booleans
• query, result URL, HTTP status, evidence excerpt, and next action
• a source-unavailable row when no live page evidence exists

Common evidence fields include sourceUrl, sourceType, pageTitle, issueCode, severity, evidenceSnippet, recommendation, httpStatus, and scannedAt. Fields without source evidence are null rather than guessed.

Reports and retained evidence

When includeReport is true, the actor writes a Markdown summary, CSV records, JSON issue rows, evidence excerpts, and run metadata to key-value storage. Set includeRawSnapshots only when retaining capped HTML is appropriate for your workflow; it is off by default.

The report metadata records the actor, timestamp, row count, issue codes, severity totals, consumed input fields, pricing mode, platform-usage setting, and maximum-charge default. This provides a compact audit trail for scheduled comparisons.

Pricing

This actor uses pay per event. Apify platform-usage pass-through is off. Charges are accepted before the corresponding paid dataset row or report is written.

Event	Price
actor-start	$0.03500
query-snapshot-scanned	$0.01150
page-meta-checked	$0.01150
serp-meta-mismatch-detected	$0.01150
executive-report-generated	$0.40000

maxChargeUsd is a strict pre-output budget. A value of zero prevents the first charge and therefore prevents paid output. If Apify rejects a charge, partially accepts it, or reports an event limit, the actor stops before writing the affected output and records billing status.

Higher-tier Store discounts are expected where supported. The event prices above remain the locked base prices.

Limits and predictable runs

• maxPages, maxSnapshots, and actor-specific record caps limit work before analysis.
• maxQueries limits distinct search contexts.
• Public fetches are additionally constrained by allowedDomains, timeoutMs, requestDelayMs, and a fetch cap.
• Reports are optional and raw HTML retention is opt-in.
• Query-only input produces an explicit source-required row instead of an empty or fabricated result.
• Dataset rows and report files follow the declared Actor schemas.

Responsible use

Process only public content or material you are authorized to analyze. Respect website terms, rate limits, privacy obligations, intellectual-property rights, and applicable law. Avoid sending personal or confidential information in HTML or input records unless your workflow is authorized to process it.