compare_page_pair

Queue a page pair for background comparison — returns immediately with queue status

Overview

Queues a page pair for comparison by the background worker. The page must already be tracked in a cloning job (via discover_all_pages or add_page_to_job). This tool returns immediately with queue status — it does not wait for the comparison to complete. Use get_migration_status or get_next_actionable_page to see results after the worker finishes.

How It Works

  1. Validates that the source URL is tracked in one of the caller's cloning jobs.
  2. Optionally updates the page's clone_url if it was missing.
  3. Enqueues the page via the database-backed comparison queue (queueSinglePage).
  4. Returns immediately with queue status — the background worker processes the page asynchronously.
  5. If discovery state is incomplete, a non-blocking discovery_warning is included in the response.

Input Parameters

ParameterTypeRequiredDescription
source_url string required URL of the original WordPress page (must be tracked in a cloning job)
clone_url string required URL of the cloned page

What You Get Back

Example Use Case

After fixing the meta description on your clone's product page, call compare_page_pair to re-queue it. The tool returns immediately with comparison_status: 'queued'. Then poll get_migration_status or call get_next_actionable_page to see the updated results once the worker finishes.

Tips

The page must be tracked in a cloning job before calling this — use add_page_to_job if it isn't.
This tool returns immediately — the comparison runs in the background. Don't poll this tool; use get_migration_status to track progress.
Already-queued pages are deduplicated automatically — calling this twice on the same page is safe.
Works with any framework clone — React, Next.js, Vue, Svelte, or static HTML.

Related Tools