Content Optimizer
Scores a live page against a target keyword and the current top-10, then returns the specific edits to make, ranked by impact.
Last updated 2026-08-06
Summary#
Content Optimizer takes a live URL and a target keyword, scores the page out of 100 against the pages currently ranking for that keyword, and returns a prioritized list of edits. Its internal tool id is content_optimizer and it costs 1 credit.
Purpose#
You have already written the page. It is published, indexed and not ranking. The useful question is not "is this good content?" but "what do the pages beating me have that this one does not?"
This tool answers that in numbers. The decision it supports is what to change first on a page that already exists — and whether the gap is worth closing at all.
Overview#
You supply a page URL and the keyword you want it to rank for, separated by a vertical bar. Metric Vault then:
- reads the live Google results for that keyword to a depth of 30 and keeps the real top ten, with their titles and descriptions,
- pulls related keyword suggestions with their volume and competition,
- measures the keyword's real difficulty,
- and fetches your page itself for its word count and heading structure.
Your page is then scored against that benchmark across ten factors, and the gaps are turned into specific, ordered edits.
The vertical bar matters. With example.com/post | seo tips the tool knows which part is the page and which is the keyword. Given only a URL, it derives a keyword from the domain name, which is rarely what you meant.
Benefits#
- The benchmark is the live top ten for your keyword, not a generic checklist.
- Ten subscores tell you which dimension is weak, so the fix is specific.
Current vs Recommendedstates the gap as a number you can close.- Title and meta description suggestions come with the report.
- 1 credit per run keeps it below the monthly premium threshold.
Use Cases#
Reviving a page that stalled. It ranked on page two and stopped. The subscores usually show which single dimension is dragging.
Checking a draft before publishing. Publish, run the optimizer, fix, and you start from a stronger position than a blind launch.
Settling an editorial argument. "It needs to be longer" becomes a measured word-count gap or it goes away.
Auditing a competitor's page. Any public URL works, so you can score theirs against the same keyword and see why it wins.
Closing out a content project. Score every page produced by AI Article Generator against its brief's keyword.
Requirements#
- A signed-in account.
- A paid plan — 1 credit per run, and any cost above zero is blocked on Free.
- A page that is publicly reachable. Pages behind a login or a firewall cannot be fetched.
- A target keyword. Without one the score has no benchmark.
Permissions#
Any workspace member on a paid plan can run it. Free accounts are refused with This tool needs a paid plan. Free includes the 10 technical SEO tools; upgrade to Pro to unlock the rest. Signed-out visitors see Please sign in to run this tool. The recommendations panel below the result needs Pro or above.
Cost#
1 credit per run. Below the premium threshold of 3, so the monthly quota never blocks it — only the hourly fair-use cap of 100 light-tool calls per hour.
This tool has the shortest shared cache in the product: 12 hours, because the page being scored is usually your own and changes often. A cache hit inside that window still charges the credit. If you have scored the same URL and keyword before, the You already ran this dialog offers Open saved result, which is free. See How credits work and Result caching and freshness.
Navigation Path#
Dashboard → Write & Optimize → Content Optimizer
Inputs#
| Field | Accepts | Required | Default | Validation | Notes | |
|---|---|---|---|---|---|---|
| `e.g. your-url.com \ | target keyword` | A page URL, a vertical bar, then the target keyword | Yes | Empty | Empty shows Enter a value first. | The bar is what separates page from keyword. https:// is optional |
| The URL half | A full URL or a bare domain | Yes for a real score | — | Must be publicly reachable | Score a specific page, not the homepage, unless the homepage is the target | |
| The keyword half | A search phrase | Strongly recommended | Derived from the domain name if omitted | — | Without it the benchmark is meaningless | |
| Country picker (topbar) | Country list | No | United States | — | Recorded with the run, but the SERP and keyword data always come from the United States, English-language index | |
| Date range (topbar) | — | — | — | — | Hidden on this view; the score always reflects the current SERP |
Step-by-Step Guide#
- Open
Write & Optimizeand choose Content Optimizer. - Read the three steps on the card: paste URL and target keyword, compare against the real top-10, get fixes ranked by impact.
- Type your page and keyword into the field, separated by a bar — for example
example.com/blog/seo-basics | seo basics. - Click Optimize Page · 1 report, or press Enter.
- Wait for
Analyzing… this can take a few seconds for live data.to clear. - Read
Overall Score, then go straight toPrioritized Fixes. - Make the edits, wait for the page to be re-crawled, and re-run to confirm the score moved.
Reading the Results#
The header. Your URL, a Content Optimizer verified badge, the target keyword under Target:, and Scored just now.
The KPI tiles. Up to four, drawn from what the page actually returned.
| Tile | Sub-label | Reads | Good | Bad | Action |
|---|---|---|---|---|---|
Overall Score | content optimization | The page out of 100 against the top ten | 80+ | Under 60 | Under 60 the page needs restructuring, not tweaking |
Word Count | target N | Words on the page against the recommended figure | Within about 10% of target | Less than half the target | A large shortfall is usually the single biggest lever |
Keyword Uses | target N | How often the target keyword appears | At or near target | Zero, or far above | Zero means the page is not about the keyword; far above reads as stuffing |
Flesch Score | reading ease | Reading ease of the page | 50-70 for most business content | Under 30 | Under 30 means dense sentences — split them |
Headings | target N | Heading count, shown when no reading score was returned | Close to target | 0-1 | Structure is one of the cheapest subscores to fix |
The rank-prediction banner. A single sentence estimating how the page is likely to place if nothing changes. It is colored by your overall score: green at 80 or above, amber from 60, red below. Treat it as a summary of the score, not as a forecast.
Optimization Subscores — N factors. The most diagnostic block on the page. Each factor is a 0-100 meter, green at 80 or above, amber from 60, red below:
| Subscore | What it measures | What a low score means |
|---|---|---|
Word Count | Depth against the ranking pages | The page is thin for this query |
Keyword Coverage | Presence of the target term where it matters | The page does not clearly claim the keyword |
Semantic Breadth | How much of the topic vocabulary is present | You cover the keyword but not the subject |
Readability | Sentence and paragraph difficulty | Dense writing; split sentences and add subheads |
Structure | Heading hierarchy and section flow | Missing or badly ordered H2s |
Media Richness | Images and other media | A wall of text competing against illustrated pages |
Internal Links | Links out to your own related pages | The page is an orphan in your own site |
External Links | Citations to sources | No evidence of research |
Schema | Structured data on the page | No machine-readable markup |
E-E-A-T | Experience, expertise, authority and trust signals | No author, no credentials, no first-hand detail |
Work on the two lowest meters. Moving one factor from 30 to 80 shifts the overall score more than polishing three that are already green.
Current vs Recommended — close the gap. A four-column table — Metric, Current, Recommended, Gap — covering word count, keyword occurrences, headings, images, internal links, external links and schema blocks. The gap cell shows on target when the two match, a green negative when you are above the recommendation, and an amber +N when you are short. This is the checklist to hand to whoever edits the page.
Top-10 Benchmark. What the ranking pages actually do — the averages your recommendations were derived from. Use it to sanity-check a recommendation that looks extreme.
Prioritized Fixes. The action list, each with an Impact: line and a priority. High priority renders red, medium amber, low green — the color marks urgency, not quality. Work top down; the order already accounts for effort.
Missing Semantic Keywords. Terms the ranking pages use that your page does not. Cover them as concepts inside real sentences. Pasting them in as a list will not move the semantic-breadth score in a way that survives review.
Recommended Headings. The H2 structure suggested for this keyword. Compare with what you have; the difference is usually where the structure subscore went.
Title Tag Suggestions and Meta Description Suggestions. Rewrites for the two elements that decide clicks. For a full set of scored variants with a SERP preview, use Meta Generator.
Readability Issues. Specific passages or patterns causing the readability score, each with a severity.
Schema Recommendations. The structured-data types this page should carry. Validate whatever you add with Schema Tool.
Internal Link Suggestions. Where to link from and to inside your own site.
What to do with it. Take the top three Prioritized Fixes, apply the Current vs Recommended numbers, add the missing semantic keywords in real prose, and re-run after the page has been re-crawled. Anything below 60 usually needs a rewrite rather than an edit.
Examples#
Example: You run example.com/blog/email-deliverability | email deliverability. Overall Score is 61 with an amber rank-prediction banner. The tiles show 780 words against a target of 1,900 and 4 keyword uses against a target of 12. In Optimization Subscores, Word Count sits at 34 and Semantic Breadth at 41, while Readability and Structure are both above
Current vs Recommendedshows+1,120words and+3headings. The top
prioritized fix is to expand the page with the six missing semantic terms listed below. You expand the piece to 1,900 words around those terms, add three H2s, and the re-run comes back at 84.
Screenshots#
Tips#
- Always include the bar and the keyword. It is the single biggest difference between a useful score and a meaningless one.
- Score the exact page, not the section index. A category URL will be benchmarked against article pages and always score badly.
- Fix the lowest two subscores first, not the longest fix list.
- Re-run only after the page has been re-crawled. Scoring an hour after an edit usually returns the same numbers.
- Score a competitor's URL against the same keyword to see what a high score looks like in your niche.
Best Practices#
- Brief with Content Brief & Template before writing, score with this tool after publishing. The two use the same benchmark.
- Rewrite for the semantic terms rather than inserting them; the score follows coverage, not repetition.
- Keep a record of the score before and after each edit — Saved Work holds every run.
- Pair with On-Page SEO Checker for the technical side of the same page; this tool grades content, that one grades markup.
- Re-score important pages quarterly, and use Content Decay Detector to find which pages need it.
Common Mistakes#
- Entering a URL with no keyword. The tool then derives a keyword from the domain name and benchmarks you against the wrong SERP.
- Reading the overall score as a ranking prediction. It measures the content gap; links, authority and intent also decide position.
- Chasing word count alone. Length with no semantic breadth moves one meter and nothing else.
- Scoring a page behind a login. The fetch fails and the report has nothing to compare.
- Re-running inside twelve hours and paying a credit for a cached answer.
Limitations#
- The SERP, keyword suggestions and difficulty all come from Google's United States, English-language index. The country picker does not change the market.
- The live results are read to a depth of 30 and the top ten are used as the benchmark.
- The page fetch reads the served HTML, so content that only appears after JavaScript runs may not be counted.
- Related keywords are capped at 30, so the semantic list is a strong sample rather than the entire topic vocabulary.
- The score covers content. It does not weigh backlinks, domain authority, page speed or index status — use Domain Overview and PageSpeed & Vitals for those.
- Only one page is scored per run. There is no bulk mode for this tool.
- Recommendations are model-written on top of measured data; the numbers are real, the prose is guidance.
Troubleshooting#
| Symptom | Likely cause | Fix | |
|---|---|---|---|
Enter a value first. | Empty field | Type a URL and keyword | |
Please sign in to run this tool. | Signed out | Sign in and run again | |
This tool needs a paid plan… | Free plan | Upgrade — see Plans and pricing | |
| `No optimization data found for … Provide a page URL and target keyword (e.g. example.com/post \ | seo tips) to score the content.` | The input had no usable URL or keyword, or the page could not be read | Add the bar and the keyword; check the page is public |
| Word count reads far lower than the page looks | The content is rendered by JavaScript after load | Compare with the server-rendered HTML; consider server-side rendering | |
| Score barely moves after edits | The page has not been re-crawled, or a cached result was served within twelve hours | Wait and re-run | |
Flesch Score tile missing | No reading score was returned; the Headings tile takes its place | Expected | |
| Recommendations look extreme | The top ten for that keyword are unusually long or deep | Check Top-10 Benchmark before acting | |
Monthly limit reached — upgrade to continue. | Out of credits | See I ran out of credits |
FAQs#
What does the overall score actually measure? How closely your page matches what the pages currently ranking for your keyword do, across ten content factors. It is a content-gap score, not a ranking forecast.
Why do I need the vertical bar? It tells the tool which part of your input is the page and which is the keyword. Without it, the keyword is guessed from the domain name and the benchmark will be wrong.
Can I score a page that is not mine? Yes, as long as it is publicly reachable. Scoring a competitor against your target keyword is one of the fastest ways to see what a winning page looks like.
Why is this only 1 credit when Gap Finder is 3? Credits track backend cost. This tool makes fewer and cheaper provider calls than a two-domain keyword comparison. See How credits work.
How soon can I re-run after making changes? Wait until the page has been re-crawled and at least twelve hours have passed — inside that window the shared cache may return the same result while still charging a credit.
Does it rewrite the page for me? No. It returns scores, gaps, suggested headings, title and meta options and an ordered fix list. To produce new copy, use AI Article Generator.
See also
Was this article helpful?
Thanks — feedback noted for the docs team.