By Built to Appear · Practical notes from our website and search work. Updated .
Write the outcome before the wish list
Start with three statements: who the website needs to reach, what they need to understand, and what action they should take. “Make it modern” describes a direction, but it does not tell a designer whether to prioritize bookings, quote requests, product information, or a portfolio.
For a consultant, the brief might be: help an operations manager understand a fixed-scope assessment and request a discovery call. That points to the engagement outline, deliverables, relevant evidence, common questions, and a clear contact route. A restaurant’s brief would lead somewhere different.
Sort the content into keep, improve, and create
Keep accurate material that already does its job. Improve pages that are vague, outdated, or difficult to scan. Create a new page when an important question has no useful answer. Collect approved photographs, brand files, testimonials you have permission to use, and examples before setting a launch date.
Use a page brief with five fields: visitor question, main answer, evidence, related page, and next action. This is more useful than choosing a page count first. Our ten-page plan gives you room for a core business site, while the planner can model additional pages when the content calls for them.
Review the experience you will actually deliver
Read the main pages on a phone. Check type size, spacing, navigation, image cropping, and the path to contacting the business. Motion should support the explanation; visitors should not need to discover a hidden play button before the page makes sense. A complete still state and a pause control keep visual work usable.
Ask which features have been tested and what the test covered. Check the public build after launch as well as the preview. A polished screenshot cannot tell you whether a form reaches the correct destination or whether a booking link works.
Protect the useful parts of the old site
Record the current URLs and identify pages with important traffic, links, or customer use. Decide which addresses stay and map any that change. Keep the domain and account access clear. A redesign is also a transition, so the scope should include who handles the switch and how the new site will be checked.
Separate the first build payment from the total commitment and the ongoing care. Include third-party licenses, usage, and any special integrations in the comparison. Our plan builder shows the base payment schedule and optional services before you send a scope request.
Give the next ninety days a purpose
Launch with a short list of priorities rather than a promise to “do SEO.” One month might focus on clarifying service pages; another might add a useful cost guide and connect it to the offer. Search data can help choose the next change once there is enough of it.
A monthly update should distinguish work completed, what was observed, and what happens next. The website should have an owner after launch, a realistic scope for edits, and a way to review progress. Those decisions make the redesign an ongoing business asset.