Sign in Start free

Prioritize by Effort Against Realistic Win

Most prioritisation scores multiply volume by an invented difficulty number and produce a ranking nobody trusts. The problem is that difficulty scores are site-agnostic - they tell you how hard a term is for an average site, not for yours. What you need is an honest estimate of whether this specific domain can reach page one within the horizon you are planning for.

CATEGORY
Content strategy
FORMAT
effort-vs-realistic-win.md
STEPS
6
PRICE
Free - no account
WHEN TO REACH FOR THIS

Use when your content backlog is longer than your capacity and you need to decide what gets built this month rather than eventually.

The skill file

effort-vs-realistic-win.md 
---
name: effort-vs-realistic-win
description: Use when your content backlog is longer than your capacity and you need to decide what gets built this month rather than eventually.
---

# Prioritize by Effort Against Realistic Win

Most prioritisation scores multiply volume by an invented difficulty number and produce a ranking nobody trusts. The problem is that difficulty scores are site-agnostic - they tell you how hard a term is for an average site, not for yours. What you need is an honest estimate of whether this specific domain can reach page one within the horizon you are planning for.

## What you need first

- current positions for every target query
- a list of the 3 sites that actually occupy positions 1-5 for your core clusters
- an honest count of your weekly production capacity in finished pages

## Method

1. Split the backlog into three bands by your current position: 8-20, 21-40, and unranked or 40+. Positions 8-20 are already judged relevant by Google and usually move with on-page work alone.
2. For anything in the 21-40 band, check whether the pages above you are on domains materially stronger than yours. If four or more of the top 10 are, the term needs links and belongs in a different budget line, not the content plan.
3. Estimate effort in production hours, not word count. A 900-word page needing original data costs more than a 2,500-word explainer you can write from knowledge.
4. Multiply realistic monthly clicks at your achievable position - not position 1 - by the value per click you can defend from analytics. Use position 5 as the ceiling for competitive clusters.
5. Rank by value divided by hours, then override the ranking once: pull forward anything that unblocks a later cluster, even if it scores badly on its own.
6. Commit only to what fits capacity with 25 percent slack, because refreshes and unplanned work always eat the rest.

## What this produces

A committed monthly build list with expected clicks and hours per item, and an explicit deferred pile.

## Where this goes wrong

- modeling revenue at position 1 when your realistic ceiling for that cluster is position 6
- using a generic keyword difficulty score as if it accounted for your own domain strength
- filling 100 percent of capacity so the first refresh emergency wrecks the schedule

---

From the QuQi skill library - https://www.quqi.io/skills/effort-vs-realistic-win
Free to download · no account, no email

What you need first

  • current positions for every target query
  • a list of the 3 sites that actually occupy positions 1-5 for your core clusters
  • an honest count of your weekly production capacity in finished pages

Method

  1. 01 Split the backlog into three bands by your current position: 8-20, 21-40, and unranked or 40+. Positions 8-20 are already judged relevant by Google and usually move with on-page work alone.
  2. 02 For anything in the 21-40 band, check whether the pages above you are on domains materially stronger than yours. If four or more of the top 10 are, the term needs links and belongs in a different budget line, not the content plan.
  3. 03 Estimate effort in production hours, not word count. A 900-word page needing original data costs more than a 2,500-word explainer you can write from knowledge.
  4. 04 Multiply realistic monthly clicks at your achievable position - not position 1 - by the value per click you can defend from analytics. Use position 5 as the ceiling for competitive clusters.
  5. 05 Rank by value divided by hours, then override the ranking once: pull forward anything that unblocks a later cluster, even if it scores badly on its own.
  6. 06 Commit only to what fits capacity with 25 percent slack, because refreshes and unplanned work always eat the rest.

What this produces

A committed monthly build list with expected clicks and hours per item, and an explicit deferred pile.

Where this goes wrong

  • modeling revenue at position 1 when your realistic ceiling for that cluster is position 6
  • using a generic keyword difficulty score as if it accounted for your own domain strength
  • filling 100 percent of capacity so the first refresh emergency wrecks the schedule

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Claude Code Save it as ~/.claude/skills/effort-vs-realistic-win/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.

Questions about this skill

When do I need this rather than a volume times difficulty score?

When the backlog is longer than capacity and someone will ask why a high volume term is not on the list. Difficulty scores are site-agnostic: they describe how hard a term is for an average domain, not for yours. This substitutes an honest read of whether your specific site can reach page one inside the horizon you are planning for.

What do I need in hand before starting?

Current positions for every target query, the three domains actually holding positions one to five in your core clusters, and honest weekly throughput in finished pages. Without current positions you cannot band the backlog into 8 to 20, 21 to 40 and unranked, and that banding is the whole method. Without a real capacity number you commit to a list nobody can build.

What do I end up with, and which part of it gets used?

A committed monthly build list with expected clicks and hours per item, plus an explicit deferred pile. The deferred pile gets used most, because it is the answer when someone asks where their topic went. Treat the click figures as a ranking device rather than a forecast: they are modelled at your achievable position, with position five as the ceiling on competitive clusters.

What ruins this most often?

Modelling revenue at position one when your realistic ceiling for that cluster is position six. Click curves fall steeply, so the estimate can overstate the return several times over and the ranking reorders around terms you will never reach. The cost is a quarter spent on the wrong half of the backlog while the winnable 8 to 20 band sits untouched.

More in Content strategy

Build a Topical Map From Real Demand

Use when you have a subject area but no defensible list of what to publish, and keyword exports...

Decide Build New or Refresh Existing

Use when a target query is one you already have a page for and you are unsure whether to rewrite...

Competitor Gap Analysis Without Fooling Yourself

Use when you want to learn from competitors' content but keep producing a list of topics you hav...

Set a Cadence You Can Actually Sustain

Use when you are planning publishing volume and tempted to commit to a number that assumes nothi...