Blog / Digital growth /
A one-page SEO plan for a small business
Forty tabs. Colour-coded. Nobody has opened it since March. That’s what SEO turns into when a small business tries to plan everything.
I’d rather have one page. It links the business goal to a handful of pages, actions and measures, and makes clear what can wait. It’s no promise of rankings. It’s a way to pick the next sensible piece of work.
Begin with the business, not a keyword list
Write down what the business wants to make easier over the next few months. That could be more relevant enquiries, more sales of a particular product group, or helping existing customers find support information. Keep the goal specific enough that the owner can recognise progress, but don’t pick a target number just because a template asks for one. Use a number only with a defensible baseline.
Next, describe the audience and the problem they are trying to solve. Say a plumber’s customers want a particular service in an area the business really covers. A generic page about plumbing won’t help them. Likewise a shop doesn’t need an article for every product colour when the product page can explain the options. The plan should reflect the actual offer.
Choose a small set of pages
List the homepage, the key service or category pages and any guides that answer genuine questions. Give each page one sentence describing its job. If two pages share a job, they may be confusingly similar. If a vital service has no clear landing page, fix that before writing another blog post.
Use Search Console, customer enquiries and conversations with staff to find questions people actually ask. Search volume can help with prioritisation, but it is only one input. The wording should fit the business and the visitor. A page targeting a phrase nobody uses internally may become awkward copy, while a useful customer question may be worth answering even if a tool reports limited data.
Turn the plan into actions
Choose actions someone can finish: improving a service page’s explanation, fixing broken internal links, clarifying delivery and returns, updating old facts, checking key pages can be indexed. Write who owns each task and what “done” means. “Improve SEO” is not an action; “rewrite the service page introduction so it states the audience, service area and next step” is closer.
Keep dependencies visible. A rewrite may need the person who delivers the service. A redirect may need the developer who controls the server. If the owner can’t make a change, say what decision or access is needed, rather than pretending the work is underway.
Measure the right things
Select a few measures that match the goal. Search Console can show search impressions, clicks and queries. GA4 can show sessions and key events when tracking is configured. The business’s own enquiry or order records may provide context that analytics cannot. Record the period, filters and definitions so the next review uses comparable data.
Don’t confuse a measure with a cause. More clicks don’t automatically mean more revenue, and a good week may be seasonality or a campaign. Pair numbers with a short note on what changed. If tracking is unreliable, make fixing it a task rather than reporting false certainty.
Give the plan a rhythm
A one-page plan should be reviewed, not laminated and forgotten. I’d set a check-in that suits the business’s capacity. Ask what was completed, what is blocked, what the evidence shows and what should stop. If a task has sat untouched for months, determine whether it still matters. A useful plan can remove work as well as add it.
Avoid filling every week with new content. Publishing is one way to help people, not the only way. Improving a confusing landing page, correcting product details or fixing a broken journey may be more valuable. Leave room for operational issues; a small business needs a plan that survives busy periods rather than one built for an imaginary team with unlimited hours.
Put the page together
Keep the document simple: goal, audience, priority pages, actions, owner, measure, review date and known limitations. Add links to the relevant pages and reports. Make it readable by the people who will do the work. If the plan needs a presentation to explain every row, it is probably too complicated.
Start with one goal and three actions you can genuinely complete.
Decide what not to include
The most useful part of a one-page plan may be the list of things you have chosen not to do yet. A business with limited capacity cannot improve every page, publish every idea and rebuild every report in one quarter. Put lower-priority actions in a backlog with a reason for waiting. That reason might be missing information, a dependency on a developer, weak evidence or a more urgent customer problem. Revisit the backlog at the next review instead of letting it become a graveyard. This helps the business distinguish deliberate sequencing from forgotten work. It also makes the plan easier to discuss: people can see not only what has been chosen, but what would need to change for a deferred task to become important.
Which page would make the biggest difference to a customer if it were clearer next month?