The SEO Compare Post vs URL Agent compares a selected WordPress post or page with an external URL
and generates detailed SEO improvement recommendations for your content.
It helps you benchmark your content against competitors or reference pages and identify structural, semantic,
and optimization gaps.
What This Agent Does
- Selects a WordPress post or page
- Fetches content from an external URL
- Compares headings, structure, keyword usage, length, and content depth
- Generates actionable SEO recommendations for improving your post
- Supports customizable prompt instructions
- Allows model selection and timeout control
- Can run instantly or via WP-Cron queue
Required Fields
Before starting the task, the following must be configured:
- Post/Page selection
- External URL
- Model
Note: If any required field is missing or invalid, the task will not start.
Prompt Customization
The agent uses a single editable prompt field. By default, it uses the following prompt:
Given url {{external_url}} and post id={{post_id}}
Compare their SEO and give recommendations how to improve SEO of post.Supported placeholders:
{{external_url}}{{post_id}}
Placeholders are automatically replaced before sending the request to the AI model.
You may edit the prompt freely. Click “Switch to default” to restore the original template.
How It Works
Workflow steps:
- Fetch external URL content
- Extract WordPress post content
- Compare SEO and generate recommendations
The final AI prompt includes:
- Your configured instructions (after placeholder replacement)
- Extracted external page content
- Extracted post content
Note: If the total content exceeds the selected model’s safe limit, the task will stop. So reduce content length or choose a different model.
Typical Use Cases
- Compare your article with a competitor page
- Improve blog post ranking potential
- Identify missing headings or keyword gaps
- Optimize content structure
Notes
- Only textual content is analyzed.
- Very large pages may exceed model limits depending on model selection.
- Dynamic JavaScript content may not always be fully captured.