Welcome to Linden Workshop
We are a family-run workshop making custom built-ins, interior joinery, and practical storage for homes. Please browse our services and contact us to discuss your requirements.
Contact us
Website Redesign & Relaunch
A website redesign updates your existing site's layout, content and navigation to make your business clearer and the site easier to use.
Redesign the experience. Prepare the transition. Keep the important context.A redesign may change the message, layout, page structure, or the platform underneath them. We review existing content and customer journeys before deciding what to retain or rebuild. The relaunch plan connects these design decisions to URL mapping, redirects, metadata, forms, and integrations within the agreed scope. Before-and-after comparisons should use the same underlying content so the effect of hierarchy and presentation is understandable.
Compare the wider approach in our website design services overview. For a more specific need, explore SEO Migration or Content Marketing.
The transformation
Move the divider to compare two treatments of the same fictional business. The services and image stay consistent so the effect of hierarchy, spacing, and direction is easier to see.
Three connected decisions
Turn each card to see the practical outcome behind the design decision.

Make the value, audience, and next step easier to understand.

Give every screen a more useful hierarchy and a more distinctive rhythm.

Connect the new experience to the systems and search signals already in place.
Two parts of one change
Shape what people will experience, then make the move to that new version clear and reviewable.

Shape the message, layout, and interactions around the website's next purpose.

Keep the move to the new version clear, with defined responsibilities and checks.
The work
Each area informs the others. The final scope should say which responsibilities belong to SEO Supreme, the client, and any other partner.

Clarify what the business offers, who the website is for, and which details help people decide.
Message hierarchy, page roles, and content requirementsReorganize the journey, visual hierarchy, and responsive behavior around the decisions visitors need to make.
Information architecture, interface direction, and interactionPlan how important paths, search signals, integrations, and tracking move into the new experience.
URL mapping, redirects, metadata, and agreed integrationsCheck the agreed experience, record open questions, and make ownership after launch understandable.
Responsive review, launch checks, and documentationA controlled relaunch
Follow one short transition from the current website to a documented next state.
Record important URLs, content, search signals, integrations, and responsibilities before launch work begins.
Illustrative relaunch workflow. Scope and responsibilities are agreed for each project.Record important URLs, content, search signals, integrations, and responsibilities before launch work begins.
Connect redirects, forms, tracking, metadata, and the agreed technical checks to a clear launch sequence.
Confirm the agreed paths after publication and leave a useful record of what changed and what still needs attention.
Continuity matters
Keep the useful recognition, content, and paths. Change what obscures the offer, slows the journey, or no longer fits the business.
A tangible outcome
The exact scope varies, but these three outcomes create a useful line from strategic direction to a reviewed relaunch.
Page roles, content requirements, priority journeys, and an agreed visual direction.
Reusable layouts and components shaped around desktop, mobile, and real content.
Agreed launch responsibilities, mapped paths, checks, and a record of open items.
Copywriting, photography, development platform, hosting, analytics, legal content, migration, and ongoing maintenance are included only where they form part of the agreed project scope.
The route forward
A clear sequence gives decisions enough room while keeping the destination visible.
01Understand the current website, the business change, and the decisions the new experience needs to support.
02Develop a coherent content and visual system, then review the important journeys across relevant screens.
03Connect the approved website to the agreed relaunch plan, responsibilities, and follow-up checks.
Common questions
Use these answers to make the first scope conversation more concrete.
A redesign can include content structure, visual direction, responsive layouts, interaction, implementation, and relaunch preparation. The exact responsibilities and deliverables should be defined for the project.
No. Redesign shapes the next experience. Relaunch is the controlled transition from the current website to that experience, including the agreed technical, search, tracking, and ownership checks.
Yes. Existing content, search paths, brand elements, integrations, or functionality can be reviewed for what should be kept, revised, moved, or retired.
A careful transition can preserve important signals and reduce avoidable risk, but no redesign can guarantee rankings. URL mapping, redirects, metadata, content, technical checks, and post-launch review all need appropriate scope.
That depends on the quality and fit of the current materials. The project should identify what can carry forward and what needs to be rewritten, reshot, or newly created.
A focused redesign can be possible when the affected pages and shared components are clearly defined. The wider system still needs review so the revised area does not create an inconsistent journey.
Responsive behavior should be designed and reviewed as part of the experience, not treated as a smaller desktop layout.
Important current URLs should be mapped to their best new destinations. Redirect implementation and validation need clear ownership in the relaunch scope.
Timing depends on the size of the website, content readiness, functionality, decision process, and technical transition. A useful estimate follows a concrete discovery and scope conversation.
Ongoing updates and monitoring can be scoped separately. The handover should make clear who owns content, technical maintenance, measurement, and future improvements.
A closer look SEO Supreme
A redesign is an opportunity to improve how a website explains an offer and supports its users. Begin by identifying what should remain: useful pages, recognizable brand elements, working functions, and content people already rely on. The new design needs a transition plan as well as a visual direction.
A dated appearance, unclear navigation, slow pages, and missing information are different issues. Use representative visitor tasks to locate the problem. Replacing the whole site may be appropriate, but it should follow a defined need rather than serve as the default answer to every complaint.
Decide which pages stay, merge, or need substantial rewriting. Then design around their new role. A dramatic layout cannot compensate for an offer the business has not yet explained. Preserve facts and useful detail while removing repetition and dead ends.
Record URL changes, integrations, editorial responsibilities, and acceptance checks. If the redesign changes domains, paths, or platforms, involve migration planning early. Test the actual forms and important pages, not only the visual presentation of the homepage.
A useful redesign brief begins with an observable problem. Visitors may struggle to identify the right service, understand the offer, compare options, or reach the business. The team may struggle to keep content current. Describe the affected task and a representative page before choosing the scale of the project. “Make it modern” leaves too many important decisions open.
Use available evidence to refine the question: customer comments, repeated sales questions, the current page content, usability observations, and relevant website data. A low inquiry count does not by itself prove that the layout is the cause. Identify what can be checked now and what remains uncertain. The design direction should respond to that finding rather than assume a full rebuild is always necessary.

Review important pages for their actual purpose, current accuracy, useful detail, and next action. Decide which content should remain, be improved, be combined, or be removed. Keep the reason beside the decision. An older page may still answer a valuable question, while a newer one may repeat material that belongs elsewhere. Age and appearance alone are incomplete selection criteria.
Check the explanation as well as the page list. A service page may contain practical conditions that disappear when the copy is shortened for a new layout. Preserve useful facts in an appropriate form and confirm any business change with its owner. This helps the new structure improve clarity while retaining the information customers still need.
A redesign becomes easier to assess when the team can see how a real question will be answered. Take one representative page and write the essential explanation before polishing its presentation. Compare the old and proposed versions for meaning: what is offered, who it suits, what details matter, and what someone should do next.
For a fictional garden-design business, “Creative outdoor solutions” gives little practical direction. A clearer opening could explain that the service plans compact city courtyards, then describe the actual deliverables and site information needed for an inquiry. The business would need to confirm those facts. The example shows a messaging decision; it does not imply that different words alone produced more leads.
A homepage concept cannot establish that every service page, resource, or contact route will work. Select representative page types and the variations that matter: a long heading, several supporting images, a detailed explanation, or an unavailable option. Review the information order and main action on small screens as well as larger ones.
Include navigation, keyboard focus, form instructions, and error or confirmation states in the review. Check image crops against what the image needs to explain. A component should accommodate the content the business actually publishes. Record decisions about shared components so an improvement on one sample page does not introduce a confusing pattern across the rest of the website.
The people maintaining the site should be able to carry out the routine changes defined in the project. Ask them to update a realistic service detail, replace an image, or publish the type of page they will use. Identify which information lives in a shared field and which belongs to an individual page. This reveals editing requirements while they can still be addressed in the build.
Document the account owner, permissions, relevant source files, and support route. Clarify which changes are included in handover and which need later technical help. A successful editing rehearsal is more informative than a broad promise that the site will be easy to manage. It gives the business a concrete view of the work it can perform after launch.
Plan the transition while the design is still being developed. Record important existing destinations, any URL changes, connected systems, content approvals, and the checks needed on the public version. A staging page and a live page can differ in configuration or integrations. Assign someone to verify the actual customer journey when the redesigned site becomes available.
Separate launch acceptance from later performance review. The team can check whether information is present, navigation works, and an inquiry reaches its destination. Search visibility and business outcomes need observation over appropriate periods and may be affected by other changes. Return to the original problem and use the evidence to choose the next improvement, with unresolved questions and responsibilities kept visible.
The next chapter
Tell us what feels out of date, what still matters, and what the new website needs to help people understand or do.
Explore website design