How to Improve an Existing Business Website: A 12-Month Plan
Organise a year of website improvements around customer tasks, useful content and measured results, with a manageable quarterly review cycle.
To improve a business website over 12 months, start with customer problems and business priorities. Choose changes you can implement and assess, leaving time to review the results before planning more work.
The schedule below is a suggested working framework. Move urgent security, accessibility or broken-enquiry issues to the front rather than waiting for their allotted quarter.
Establish the baseline
Record the important services, customer tasks and current problems. Note which pages attract suitable enquiries, where staff repeatedly explain missing information and which technical failures are already known.
Use the measurement guide to choose a small set of meaningful indicators. Keep a dated change log so later results can be interpreted in context.
Confirm account ownership and access before commissioning work.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
Months 1 to 3 focus on essential journeys
Carry out a homepage audit and test the route from a service page to contact. Fix broken controls, unclear service descriptions and obvious mobile barriers.
Compare the site with alternatives using a structured competitor review, but do not copy their design or assume their decisions work.
Build a short backlog of content gaps based on actual customer questions. Use the 90-day plan to keep the first phase realistic.
Months 4 to 6 improve the content library
Review old pages for accuracy, usefulness and overlap. Decide whether to update, merge or remove them using evidence, not age alone.
Investigate content decay before rewriting pages that have lost visits. A technical issue or seasonal change needs a different response from outdated advice.
The original content guide helps keep each page focused on a customer task rather than a target word count.
Months 7 to 9 build useful depth
Create carefully selected answers that support your main services. Add seasonal pages where there is a genuine recurring offer and enough time to maintain them.
Use FAQs for real questions and consider a resource centre or glossary only when the growing collection needs better organisation.
Do not publish a new URL for every keyword variation. Check whether an existing page already answers the same intent.
Months 10 to 12 review the system
Revisit navigation, internal links, performance and accessibility. Identify improvements that should become part of the reusable templates rather than one-off fixes.
Use the sustainable website guide to check unnecessary resources added during the year. Review forms and third-party integrations after updates.
Assess whether the current platform still supports the business. The website-upgrade guide helps distinguish ongoing improvement from a justified rebuild.
Give each change a testable purpose
For every task, record the problem, proposed change, owner and verification method. “Improve SEO” is too vague; “make the service page answer our three repeated pricing questions” is more actionable.
Use the SEO fundamentals guide to connect content with discovery and technical access. Rankings alone should not replace judgement about customer usefulness.
Where traffic is low, combine analytics with direct task testing and enquiry quality rather than forcing a statistical conclusion.
Keep dependencies visible
Some work needs other decisions first. A new service page may require a confirmed offer, approved photographs and a working booking route.
Do not schedule publication before the evidence exists. Keep provisional ideas in the backlog rather than filling gaps with invented examples.
The good website guide provides a simple check that the basics remain intact while the library grows.
Review the programme quarterly
Use task-based usability testing to observe where customers struggle, and the broken-link repair checklist to restore failed routes. Record the source of each problem, the chosen correction and the retest result.
Compare the original problem with the current experience. Keep changes that help, revise those that do not and document what remains uncertain.
Allow time for maintenance and unexpected issues. A realistic programme with a few completed improvements is more valuable than a crowded calendar nobody can sustain.
If you would like help prioritising the next year of website work, contact AfterWorks with your main services and recurring customer questions.
