Prioritise so the work that matters ships first.

Weighing impact against effort means estimating how much a change could improve search performance and how much work it takes, then comparing the two. Google does not publish a prioritisation method, so this section is general explanation. Its sources support the limits on what can be known, which is where most of the difficulty lies.

Impact is an estimate, and the SEO Starter Guide is frank about that. It says there are no secrets that will automatically rank a site first, that not all changes will result in noticeable impact in search results, and that changes can take from a few hours to several months to show. Any impact figure in a plan is therefore a judgement supported by evidence, not a forecast to be guaranteed. Evidence can come from the site's own data: Google's Performance report shows which queries and pages already attract impressions and clicks, and where.

Effort is not only the hours of work. It includes who must do it, what must ship first and how risky the change is, which is why this stage sits next to the foundations guide. A change that looks small can be large if it depends on a rebuild.

Our SEO Strategy page frames the opportunity side as a grid of demand against how hard results are to win. High demand within reach is where to start. High demand that is hard to win is earned over time. Low demand that is within reach gives cheap, specific wins. Low demand that is hard to win is left alone. That grid is an illustrative framework, and real plots come from a site's own data.

Our Insights article on prioritising SEO work: impact, effort and the dependencies people forget goes further into the trade-offs.

Deciding what can wait is the harder half of prioritising, because every item on a list has someone who cares about it. A good plan states what is deferred and gives the reason, so the decision can be revisited when the facts change.

Google's own guidance models this restraint. The SEO Starter Guide says not to drop everything to reorganise a site, because search engines will likely understand pages as they are now. On canonicalisation it says not to worry too much, since search engines can generally work it out on their own most of the time. Its debugging guidance says that small fluctuations in position can happen at any time and recover without action, and recommends avoiding radical changes if a page is already performing well. These are statements about specific situations, not a licence to postpone harmful problems, but they show that not every imperfection deserves to be first.

The traffic-drop guidance offers a useful discipline for deferral. Before acting on a fall in traffic, it suggests looking at 16 months of data to make sure the drop is not one that happens every year because of a festivity or a trend. A yearly pattern is a reason to wait and compare, not to rush a fix.

Reasons to defer: the change depends on something not yet built; the evidence of benefit is weak; the area is hard to win; or the effort is out of proportion to the likely gain. Hypothetical example: a site has thousands of near-identical archive pages with little traffic, and a rebuild is due in six months. Cleaning them up now may be wasted work, so the plan records the reason and the date to revisit it.

On our strategy grid, the low-demand, hard-to-win corner is labelled leave alone.

A roadmap a team can execute is one where each line can be picked up, built, tested and checked by someone who was not in the room when it was written. The test is practical: can a developer or an editor start the work without asking what it means?

In our SEO Strategy work, every line of the roadmap says three things. The action is the specific change, named precisely enough to build or brief. The evidence is what was observed that supports it, so the priority can be challenged. The dependency and effort say what has to happen first and how big the job is. Our Technical SEO work writes findings the same way, as tickets with the fault, the evidence, the fix and the acceptance test.

The roadmap also needs a place to stop. Google's SEO Starter Guide suggests waiting a few weeks to assess whether work had a beneficial effect, so the plan should state when each result will be checked and against what, which links it to the measurement stage.

Many of our strategy engagements end with a roadmap that an internal team executes, and we can stay on as consultancy for reviews and decisions. A roadmap that is handed over has to carry its reasoning with it. Our Insights articles on audit findings that get implemented and on judging an SEO strategy fairly cover what makes a plan usable and how to assess one.