← All notes

Website redesign

Website Redesign vs Website Refresh

Compare a difficult contact button with missing product information. Two examples help you choose between a website refresh and a broader redesign.

Sunlight breaking through rain clouds above a green alpine lake and snowy peaks
Landscape bookmark

Distinguish a difficult button from missing decision information.

Example A: a buyer can find the correct product and complete specifications, but the phone contact button is too small and the table overflows. Improve the controls, layout and mobile implementation, then test the same product-to-enquiry path. A focused refresh may cover this work.

Example B: the site lists categories without models, conditions or documents, so sales repeatedly sends the missing material by email. A font change cannot supply that path. Plan category, detail, document and enquiry connections as a broader redesign. Both examples are hypothetical, not measured site results.

Use a change inventory to define the boundary.

List the pages, content, URLs, systems and tasks that must change. Retaining the information structure while improving components and mobile delivery can be a refresh scope. New product structures, changed URLs or a replacement system add content, migration and verification responsibilities.

The project label does not replace a deliverable list. A visual update still needs checks for stale claims, links and contact details. If URLs stay the same, do not automatically add migration work the project does not need.

Accept the work through the same task.

For example A, write a phone task: inspect the specification, open contact, submit a test enquiry and verify receipt. For example B, start at a category, locate the requested model, open its document and prepare an enquiry retaining that model. Record blockers and their correction owners.

Compare those tasks with sales feedback and the relevant page records before choosing the scope. A traffic change alone does not establish acceptance; record content, channel and seasonal changes too. Keep unresolved tasks visible in the next-phase list.

Sources and scope

Written by ZequnWeb

ZequnWeb implementation record

Website redesign planning questions

Questions to settle before changing an existing website

When is a website refresh enough?

A refresh can be enough when the positioning and page structure still work, while the real problem is an ageing visual system, uneven implementation, or an incomplete mobile experience. It should still remove stale claims and improve weak calls to action.

What is a website reskin?

A website reskin updates the visual layer—such as the color system, typography, imagery, and component styling—while mostly retaining the existing page structure, content responsibilities, and technical setup. It is often close to a visual refresh, not a full redesign. If the offer, information hierarchy, URLs, buyer path, content, or technology need to change, the project needs a broader redesign plan rather than only a reskin.

How often should you redesign your website?

There is no fixed calendar. Reassess when your positioning, offer, audience, decision pages, proof, technology, or visitor path has changed—or when the current site no longer answers the questions buyers need answered. If the structure remains sound and the issue is visual age or an incomplete mobile experience, a refresh can be enough.

When does a business need a website redesign?

A redesign is more appropriate when the offer, audience, market, information hierarchy, navigation, proof, URL structure, or next-step path needs to change. It revisits the story and structure rather than only changing the visual surface.

How much does it cost to redesign a website?

ZequnWeb's public starting packages are USD $1,800 for a Starter Website of up to five pages, USD $2,800 for a Business Website of up to eight pages with custom design and optimization, and USD $4,000+ for larger sites and advanced features. A redesign may also require an existing-page and content audit, retention or rewrite decisions, migration, redirect mapping, and launch checks; the final proposal states those agreed responsibilities, exclusions, timeline assumptions, and revision rounds.

How long does a website redesign take?

There is no responsible fixed duration before the scope is agreed. Timing depends on whether the work is a refresh or a structural redesign, the number and readiness of pages and assets, content decisions and approvals, CMS or integration work, migration, redirect mapping, testing, and launch responsibility. The proposal should state the agreed timeline assumptions and how changes to scope are handled.

Can a redesign guarantee SEO rankings?

No. A redesign should inventory important pages and content, decide what to retain or rewrite, plan redirects where URLs change, and complete technical and content QA before launch. These steps reduce avoidable risk but do not guarantee rankings, traffic, enquiries, or business results.

ZequnWeb

Want to make the scope clearer?

Send your current site or starting point, what needs to change, and where you need the site to lead. I will help define a useful first release.

Discuss your project