get_next_actionable_page workflow
Get the highest-priority page with unresolved issues
Overview
After comparisons complete, this tool returns the most important page that still has unresolved issues — ordered by backlink rank. Use it to iteratively fix pages in priority order: get next page → fix issues → log attempts → re-compare → repeat.
How It Works
- Queries compared pages in the job with open issues, sorted by backlink importance.
- Returns the highest-priority page with all its open issues, sorted by severity.
- Includes AI-generated fix prompts, attempt history, and code suggestions.
- Supports skip_page_ids to move through pages you've already addressed.
- Returns a complete workflow guide for fixing, logging, and verifying.
Input Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id |
string |
required | Cloning job ID |
skip_page_ids |
string[] |
optional | Page IDs to skip (pages already fixed in this session) |
What You Get Back
- Page details (URL, type, match scores, backlink rank)
- All open issues sorted by severity with before/after values
- AI text and SEO fix prompt for the page
- Attempt history per issue
- Workflow instructions for fixing, logging, and verifying
Example Use Case
After run_full_comparison finishes, call get_next_actionable_page to get the most important page needing fixes. Fix the critical issues, call log_fix_attempt, then call compare_page_pair to re-verify. Repeat with the next page.
Tips
Start with the first page returned — it's the highest priority based on backlink importance.
Use skip_page_ids to track pages you've already handled in the current session.
Focus on critical and high severity issues first within each page.
If stuck on an issue after 3+ attempts, use diagnose_fix for AI-powered root cause analysis.