Update your website or build a new one?
List what your website gets wrong. Check whether customers can understand your offer, find what they need and contact you. Use that list to decide how much work the site needs.
Look at the pages a prospective customer would use. Can they understand what you do today, find the information they need and contact you? Record the specific places where that becomes difficult.
Keep what works
List the pages whose content is accurate and the parts of the site that work. Keep track of the pages customers mention or that you regularly send to people.
If you have Analytics or Search Console, use the data to check which pages receive visits or appear in searches. Without that information, don’t assume an old page has no value. Include it in the review before deciding to remove it.
A useful set of notes might look like this:
| Page or feature | What is wrong | What needs to happen |
|---|---|---|
| Homepage | Leads with a service we no longer sell | Explain the current main service |
| Project examples | Good photos, but no explanation of our work | Add accurate descriptions |
| Contact form | A test message did not reach us | Investigate delivery and test the fix |
| Service page | Accurate and often sent to prospects | Keep the useful content |
This is an example of a review, not a diagnosis of your website. Your list may be much shorter.
Fix specific problems first
Consider targeted changes when the page structure still suits the business and most content is usable, provided someone can reliably maintain the site.
An outdated service description does not by itself justify replacing every page. Ask what it would take to correct the content, repair the affected features and check the result on phones as well as larger screens.
If the problem is that nobody is responsible for changes, discuss the ongoing arrangement too. Rebuilding the site will leave that question open unless someone agrees to handle it afterwards.
Know when to rebuild
A rebuild is worth discussing when the business needs a different set of pages, the existing setup cannot support a required feature, or extensive repairs would still leave you with a difficult site to maintain.
Ask the provider to explain which problems require a rebuild and which can be fixed within the current site. Request a scope for each realistic option. If they have not inspected the site or discussed your needs, treat their recommendation as provisional.
Your own preference matters as well. A website you want to edit yourself needs a different arrangement from one you want someone else to manage.
Agree what moves to the new site
Before approving a rebuild, identify the content and accounts to keep, and the old addresses people may still use. Ask who will map old page addresses to their replacements and check those links after launch. Include forms and any connected services in the launch checks.
Dori builds websites from scratch and looks after them for the first year. That offer may suit a business ready to replace its site and hand over its care. If your review points to a few contained repairs, ask your current provider for a repair scope before committing to a new build.
Use the proposal comparison guide once you have the options in writing. It will help you compare the work involved and the responsibilities left with you.
Back to guides