How to decide whether to redesign or rebuild your website
Decide which problems need a repair, redesign or rebuild. Compare two scopes using customer tasks, platform limits and maintenance requirements.
THE WEBSITE OWNER'S HANDBOOK
50 practical guides for planning, designing and launching a business website. Start with the task in front of you.
Browse every guide below, or search by a task such as redirects, quotes or contact forms.
50 guides
Decide which problems need a repair, redesign or rebuild. Compare two scopes using customer tasks, platform limits and maintenance requirements.
Review service information, navigation and enquiries on your existing website. Record evidence and prioritise the fixes before asking for quotes.
Prepare a clear project brief with page purposes, content owners, features and acceptance checks so a developer can quote the actual work.
Turn a vague website goal into a customer task and a measurable outcome. Establish a useful baseline without inventing conversion claims.
Choose pages by the questions customers need answered. Map a focused route from your offer to an enquiry and identify missing content.
Organise page text, approved assets and content responsibilities. Use a content inventory to expose missing material before development starts.
Compare the project fee with domain, hosting and future-change costs. Work through an illustrative first-year total and check the exclusions.
Assess website packages against one shared brief. Check delivery limits, editing, account ownership and the handover before choosing a supplier.
Review relevant work and ask practical questions about delivery. Record evidence, supplier details and unresolved scope before commissioning a site.
Compare redesign proposals by content, migration, testing and handover. Identify assumptions that a headline price can hide.
Follow a real customer task on a phone. Check stacking order, text, menus and enquiry controls before approving a responsive website layout.
Choose predictable menu labels and test how visitors find services. Review keyboard and mobile behaviour as well as destination links.
Draft the offer and the next action before choosing homepage imagery. Arrange service information and truthful evidence around customer decisions.
Explain service fit, deliverables, exclusions and the project sequence. Write a page that helps customers send a useful enquiry.
Describe your business and working process with verifiable details. Review unsupported claims, imagery and responsibility on the About page.
Choose an enquiry route, request useful information and provide an alternative. Check what the contact button actually does before launch.
Match button labels to the next customer decision. Check competing priorities and make the destination fulfil the promised action.
Separate commissioned work from concepts and explain your contribution. Publish examples with permission and avoid invented results.
Select images by purpose and publishing permission. Use practical examples to review informative, decorative and functional alternatives.
Review real text, heading hierarchy, contrast and zoom. Find typography problems without fixing overflow by shrinking important content.
Compare editing tasks and operating needs before choosing static files or a CMS. Confirm the update process and what the handover contains.
Match hosting to the website runtime and features. Verify compatibility, account responsibilities and a tested preview before switching providers.
Inventory domain and service accounts, renewals and recovery ownership. Agree supported developer access and verify control at handover.
Test the public HTTPS domain, loaded resources and secondary-hostname redirects. Record the real result instead of relying only on a dashboard.
Follow a website enquiry from entry to receipt. Test validation and delivery with authorised data and distinguish email drafts from submitted forms.
Plan a clear handoff to an external booking provider. Review the destination, mobile journey, location and fallback without making an unintended booking.
Agree the service and reconcile orders before adding a hosted payment link. Check provider eligibility and separate a return page from payment proof.
Investigate slow pages with repeatable evidence. Separate lab and visitor data, identify a bottleneck and verify the customer task after changes.
Prepare suitable crops and image variants while keeping originals. Compare file size, useful detail and loading behaviour in the actual page.
Assign security responsibilities for accounts, data, updates and recovery. Check the website components instead of treating HTTPS as a full assessment.
Coordinate a redesign through brief, content, preview, switch and handover. Keep owners, blockers and verification evidence visible at each stage.
Prepare an old-to-new URL map and test relevant permanent redirects. Keep removed content, final destinations and updated internal links explicit.
Move hosting while preserving related domain services. Prepare a working copy, agree a fallback and verify the public site and relevant email routes.
Find broken destinations in menus, content and downloads. Choose a correction that preserves the customer journey and retest from the source page.
Review preview access, test integrations and production differences. Consolidate feedback against a named version before approving the public launch.
Write feedback with a page, observed problem and desired outcome. Resolve conflicting requests and distinguish corrections from additional scope.
Create an acceptance test plan around customer journeys. Record content, interface and feature checks with honest coverage and clear defect reports.
Check the actual public domain, content and enquiry route on launch day. Record pass, fail and unperformed checks with ownership and recovery details.
Verify source files, setup notes, accounts and licensed assets against the quote. Demonstrate a safe update before closing the handover.
Set owners and review tasks for content, renewals, software and recovery. Define the maintenance scope and keep a practical change log.
Write titles from each page purpose and compare them together. Review visible headings and avoid repeated boilerplate or keyword stuffing.
Summarise the useful detail of each business page. Check descriptions against visible content and understand why search snippets may differ.
Group related keywords by customer task rather than creating one page per phrase. Check intent and assign a service page or practical guide.
Connect guides, topic hubs and services where readers need the next answer. Use descriptive links and check that important pages are reachable.
Build a sitemap from preferred public URLs and verify the deployed file. Keep dates accurate and distinguish publication from submission and indexing.
Inspect crawler and indexing settings before launch. Separate robots.txt, noindex and access protection, then verify the production configuration.
Record useful pages before redesigning and verify the migration. Keep technical changes separate from promises about future search performance.
Define suitable enquiries and count completed outcomes. Separate button clicks, drafts and received messages before comparing website performance.
Classify search results by the task they serve. Record market limits and assess customer fit alongside keyword volume and difficulty estimates.
Review a new site through publication, discovery, queries and enquiries. Use authorised evidence when available and mark unverified outcomes honestly.
No guides match. Try a simpler task or clear the search.
Free CSV worksheets for a brief, content inventory, quote comparison, redirect map and launch checks are included in the relevant guides.