run_full_comparison orchestrator
Queue pages for background comparison — full pipeline or manual subset re-run
Overview
Queue pages in a cloning job for comparison. A global background worker processes pages one at a time, ordered by backlink importance (most important first). The queue is database-backed, so it survives server restarts. Pages already queued are deduplicated automatically. Supports three modes: 'new' (default — only uncompared pages, triggers post-scan enrichment cascade), 'all' (reset and rerun every page, also triggers cascade), and 'manual' (re-queue without firing the cascade — useful for refreshing a subset of pages without re-running shared-element / nav / design-system / media extraction).
How It Works
- Marks eligible pages as 'pending' in the database queue.
- A global background worker claims pages one at a time using database locking (FOR UPDATE SKIP LOCKED).
- Pages are processed in order of backlink rank (highest first).
- Each page is compared using Zyte JS rendering + DataForSEO enrichment.
- Failed pages are retried up to 3 times before being marked as errors.
- Issues are synced to the database for stateful tracking.
- Queue state persists across server restarts — stuck pages are automatically recovered.
- Mode 'manual' marks pages with manually_queued=TRUE so the post-scan cascade (deduplication, behaviors, navigation, design system, media extraction, component styles) does NOT re-fire when they finish.
Input Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id |
string |
required | Cloning job ID from discover_all_pages |
mode |
string |
optional | 'new' (default) compares only uncompared pages and triggers the post-scan cascade. 'all' resets and reruns every page (also triggers the cascade). 'manual' re-queues pages without firing any post-scan enrichments. |
min_importance |
number |
optional | Only valid with mode='manual'. Numeric backlink-rank threshold; only pages with backlink_rank > min_importance are re-queued. Omit to re-queue every eligible page in manual mode. |
What You Get Back
- Per-page match scores and status
- Complete fix report sorted by severity
- Pages below threshold highlighted
- Overall cloning readiness score
Example Use Case
After discovering 200 pages and building your React clone, run this to compare every page at once. It finds 47 SEO issues, 12 missing images, and 3 broken WooCommerce features — all in one report with exact fixes for each. After fixing them, use mode 'all' to rerun and verify your fixes landed. Later, to spot-check just the high-importance pages without re-running shared-element / nav / design-system / media extraction, call with mode='manual' and min_importance=50.