Content Optimizer
Scan existing URLs, raise SEO+GEO scores, apply 15–25 optimization suggestions per analysis.
The Content Optimizer takes an existing URL — whether created in Rankion or published externally — scrapes the live HTML, scores SEO and GEO, and returns a prioritized list of 15–25 concrete optimization suggestions. Each suggestion is atomic, has a score impact, and can be accepted or rejected individually. When you apply, the optimizer writes the new variant back (for Rankion articles) or returns a ready-to-paste patch diff (for external URLs). That lifts existing content into top rankings step by step, without rewriting from scratch.
What it can do
- URL scan — scrape any live URL and analyze the current content state.
- SEO + GEO side by side — classic on-page signals plus generative-engine optimization (structures, citations, fact density) in one score.
- 15–25 suggestions per analysis — atomic, with rationale, score delta, and example snippet.
- Selective adoption — pick which suggestions to apply via
suggestion_ids[]; the rest stay as-is. - Async pipeline — analyze and apply run as queue jobs, the UI polls status.
- Versioning — every apply run creates a new article version (see AI Content Editor); rollback at any time.
- Diff view — before / after side by side before you commit.
When to use
- You have articles at position 8–15 that small tweaks could push to top 3.
- You want to lift older content to current GEO standards (citability, fact structure).
- You have an external blog post and want to quantify its optimization potential.
- You want to act on a refresh hint from Content Freshness.
Workflow
- Submit URL —
POST /content-optimizer/analyzewith the URL, returns202+id. - Poll status —
GET /content-optimizer/{id}untilstatus=completed. - Review suggestions — the response contains prioritized suggestions with score impact.
- Make a selection — pick which suggestions to apply.
- Apply —
POST /content-optimizer/{id}/applywith{suggestion_ids: [...]}. - Re-score — a new SEO/GEO score is calculated, the diff becomes visible.
Detailed walkthrough in Optimize content for Google + AI.
API
| Method | Endpoint | Notes | Credits |
|---|---|---|---|
| GET | /v1/content-optimizer |
List of your optimization runs | — |
| GET | /v1/content-optimizer/{id} |
Status + suggestions | — |
| POST | /v1/content-optimizer/analyze |
Body {url}, async 202 |
5 |
| POST | /v1/content-optimizer/{id}/apply |
Body {suggestion_ids[]}, async 202 |
5 |
Body example POST /content-optimizer/analyze:
{
"url": "https://meinedomain.de/blog/stossdaempfer-wechseln"
}
Body example POST /content-optimizer/{id}/apply:
{
"suggestion_ids": [12, 14, 15, 17, 22]
}
Credits & Limits
- Analyze: 5 credits per run.
- Apply: 5 credits per run, regardless of how many suggestions are accepted.
- Async model: both endpoints return
202, result via polling. - External URLs are loaded via a scraper service; protected content (login wall, bot block) results in
failed.
Related modules
- AI Content Editor — create new articles instead of optimizing existing ones.
- Content Freshness — detects stale articles and triggers optimizer runs.
- Content Audit — site-wide analysis instead of single URL.
- Guide: Optimize Content — step by step.