Every audit produces the same awkward moment. You’ve scored dozens of checks, found a respectable number of problems, and now you’re staring at a list that looks less like a plan and more like a confession. Schema is incomplete. The About page is vague. Two assistants think you’re in a different city. Somebody’s security plugin is blocking a crawler you wanted. The FAQ page was last updated during a previous presidential administration.
Where do you start?
Most teams start with whatever is most embarrassing, or whatever the loudest stakeholder noticed, or whatever is easiest to explain in a meeting. None of those is a prioritization method. They’re moods.
This article is a teardown of a better method: a two-input priority formula, Impact × (4 − Effort), used in the fix plan of the AI-Visibility (AEO) Audit. It’s deliberately simple. The simplicity is the point.
Why do audits so often fail to produce change?
Because diagnosis and decision are different jobs. An audit is excellent at finding problems. It says nothing, by itself, about which problems deserve your next Tuesday afternoon. Without a decision layer, three things happen:
- Everything is urgent, so nothing is.
- Hard problems block easy ones, because the team feels it should tackle the big stuff first.
- The list ages. By the time anyone returns to it, half the findings are stale and the other half are forgotten.
A fix plan solves this by forcing every finding through the same two questions and producing a single number you can sort by. Sorting is underrated. A sorted list is a plan. An unsorted list is a mood board.
What do Impact and Effort mean in an AEO fix plan?
In the Audit workbook, every check you score 0 or 1 moves to the Fix Plan tab. There you rate two things on a scale of 1 to 3:
- Impact: how much fixing this would improve how machines understand, reach or describe your business. A 3 is foundational, like a wrong business name in your schema. A 1 is polish.
- Effort: how much work the fix requires. A 1 is an afternoon with access you already have. A 3 involves a developer, a vendor, a stakeholder approval or all three.
The workbook then calculates Priority = Impact × (4 − Effort). The “4 − Effort” flips the effort scale so that easier work scores higher. High impact and low effort rise to the top automatically.
What does the full grid look like?
Because both inputs run from 1 to 3, there are exactly nine possible combinations, which makes the whole system easy to see at once:
| Impact | Effort | Priority |
|---|---|---|
| 3 | 1 | 9 |
| 3 | 2 | 6 |
| 2 | 1 | 6 |
| 2 | 2 | 4 |
| 3 | 3 | 3 |
| 1 | 1 | 3 |
| 2 | 3 | 2 |
| 1 | 2 | 2 |
| 1 | 3 | 1 |
A few things jump out once you see it laid out.
A 9 is rare and precious. High impact with low effort is the definition of a quick win. If your plan has any 9s, they go first, full stop.
Two different 6s mean two different things. A 3/2 is an important fix that takes some work. A 2/1 is a moderately useful fix that’s nearly free. Both deserve to be near the top, for different reasons.
The 3s are a trap. A big, hard, important fix (3/3) scores the same as a small, easy, minor one (1/1). That’s not a flaw in the math. It’s a signal that those two items need a human decision about sequencing, and that big hard fixes should probably be broken down.
Why multiply instead of add?
Addition would treat Impact and Effort as interchangeable. A 3/3 would score the same as a 1/1 under some additive schemes and differently under others, and the gaps between scores would be evenly spaced. Multiplication makes the extremes matter more. A fix that’s both important and easy pulls far ahead of everything else, which is exactly what you want when time is limited.
Multiplication also means a low rating on either input drags the whole score down. A fix that matters very little stays low no matter how easy it is. That keeps your plan from filling up with satisfying busywork.
What have other fields learned about simple prioritization?
Prioritizing with two variables and a sort order isn’t new. Three older systems make the case for keeping it simple.
Battlefield triage. Dominique Jean Larrey, a surgeon in Napoleon’s armies, is widely credited with organizing the care of wounded soldiers by the severity of their injuries rather than by rank. The insight was not a complicated scoring model. It was a consistent rule applied quickly under pressure.
The Pareto principle. Vilfredo Pareto observed in the 1890s that a large share of land in Italy was held by a small share of the population. Quality pioneer Joseph Juran later generalized the pattern as “the vital few and the trivial many.” The fix plan is a practical way to find your vital few.
The urgent-important matrix. Popularized by Stephen Covey in the late 1980s and often associated with Dwight Eisenhower, the two-by-two grid sorts tasks by urgency and importance. Its staying power comes from the fact that anyone can use it in their head.
Each of these works because it trades precision for speed and consistency. An AEO fix plan should do the same.
How do you rate Impact honestly?
Impact is where most bias creeps in. Three questions keep it grounded:
- Does this affect identity? Anything that could cause a machine to confuse who you are, such as naming, schema or sameAs, starts at a 3.
- Does this affect access? If a crawler you want can’t reach the content, nothing downstream matters. Usually a 3.
- Does this affect a specific, recorded problem? If your AI spot check shows assistants misstating your hours, the fix that addresses that gets a higher rating than a generic best practice.
Everything else, including nice-to-have improvements and theoretical risks, is usually a 1 or a 2. Be stingy with 3s. If everything is a 3, you’re back to a mood board.
How do you rate Effort without kidding yourself?
Effort ratings fail in a predictable direction: people underestimate the work that needs other people. A schema change is a 1 if you can edit the site yourself and a 3 if it requires a ticket to a developer who’s booked through next month. Rate the effort for your situation, not in the abstract.
Useful anchors:
- 1: You can do it today with access you already have.
- 2: It takes a few hours, or one other person’s quick help.
- 3: It needs a vendor, a developer, budget, sign-off or coordination across teams.
When in doubt, rate it higher. An overestimated effort that turns out easy is a pleasant surprise. An underestimated one blocks the plan.
What happens after the numbers?
The numbers sort. People still decide. Once the Fix Plan is sorted, four practical steps turn it into work:
- Pick the top three to five. The Audit’s own checklist includes a check for exactly this: top five fixes prioritized by the formula.
- Assign an owner and a due date to each. A fix without an owner is a wish.
- Break down any 3/3 items into smaller pieces that can be rated separately. Large items often contain a 2/1 hiding inside them.
- Set a re-audit date. The workbook’s Summary tab shows a score percentage for each area, so you can see movement after the next pass.
That last step closes the loop. A fix plan isn’t a one-time ranking. It’s a queue that gets re-sorted every time you learn something.
What does a sorted plan look like in practice?
Imagine a fictional landscaping business with five findings: an About page that never states the service area (Impact 3, Effort 1, Priority 9); Organization schema missing sameAs links (3, 2 → 6); no page answering “how much does lawn aeration cost” (2, 1 → 6); a blocked crawler caused by a plugin only the web host can configure (3, 3 → 3); and an outdated team photo (1, 1 → 3).
Sorted, the plan practically writes itself. Rewrite the About page this week. Fix schema and write the pricing answer page next. Open a ticket with the host for the crawler issue now, because it’ll take time, but don’t let it block the rest. The team photo can wait for a sunny day.
Notice what the formula did: it kept the hard, important crawler fix visible without letting it freeze everything else. That’s most of what a prioritization system is for.
Where does the formula break down?
Every simple model has edges. Three to watch:
- Dependencies. Sometimes a low-priority fix must happen before a high-priority one. Note dependencies in the plan and sequence manually.
- Deadlines. A rebrand launching next month can make a 4 more urgent than a 9. Urgency isn’t in the formula on purpose; add it with judgment.
- Team skills. If nobody on the team can edit schema, the effort rating should say so. The formula only knows what you tell it.
Knowing these edges is what separates using a tool from being used by one.
A plan you can actually finish
The best audit in the world is useless if it ends in a list nobody acts on. The value of Impact × (4 − Effort) isn’t mathematical sophistication. It’s that it turns a pile of findings into a sorted queue in minutes, with reasoning anyone on the team can follow and challenge.
If you want the whole system ready to go, with 60 scored checks across eight audit areas, a 27-page guide and a workbook whose Fix Plan tab calculates priority automatically, get the AI-Visibility (AEO) Audit. Score your site, sort the plan, and take the top three into next week. The rest will still be there, now in the right order.
The Audit, including the Fix Plan tab that does this arithmetic for you, is on Content & SEO Workflows.
Leave a Reply