Machina

Machina — Marketing that moves numbers.

Reach out today

Industries

One growth engine.

Design, advertising, development, and marketing built for the sectors driving what comes next — AI, fintech, health tech, and beyond.

All industries

Machina — Marketing that moves numbers.

Reach out today
Technology

When a website redesign needs a rebuild

Two proposals for the same website can put very different prices on your desk. The costly choice is buying a new site when a repair would solve the problem, or keeping a broken structure that stops customers on several pages. Rebuild when one underlying fault breaks several of the pages customers depend on and no single repair fixes it.

Francisco Contreras

Francisco Contreras · Founder, Machina

5 min read

A vermilion dome shell, cut open at the front, is held up by a new framework of fine cream struts, on a black background.

Start with the pages customers need

One proposal replaces every page. The other offers to fix a few. Buy either before you know where customers stop, and you could pay to remake working pages or leave the failure untouched. We begin with the pages that lead to a call, order, visit or application, then find which fault belongs to one page and which reaches the rest of the site.

We walk the site on a real phone, from arrival to action. Can someone find the right service, understand its terms and take the next step? Ask the person who updates the site to change a routine detail, such as hours or a price. Those two checks give a proposal something more useful than a preference for a new look.

We separate the symptom from the repair. A confusing paragraph needs clearer words. A service hidden in the menu may need a better route. If staff cannot update hours or pricing, check permissions and the shared page layout before proposing a replacement. The work should follow the fault you can actually see.

Which pages need an edit, a redesign or a rebuild?

Take these questions through the pages that matter to your customers. Write down what happened on your site before asking anyone to price the work.

A page-by-page scope worksheet for a website proposal
Page or pathWhat to inspectScope when the finding holds
Home and main navigationCan a visitor reach the relevant service, product or location without guessing?Edit labels if the destinations work. Redesign the navigation when the page hierarchy hides the right destination.
Service or product pageDoes it answer who the offer fits, what it includes and how to proceed?Revise the copy and layout when the page structure can carry the answer. Change the shared template when several pages need the same new fields.
Menu, catalog or resourceCan someone find the current item and read it on a phone?Replace a faulty file or page first. Change the shared content setup if staff repeatedly need a workaround to publish current information.
Contact or checkout pathCan a visitor complete the form or purchase, and does the team receive it?A form that submits but never reaches sales has a connection fault. Ask whoever owns that connection to fix it. Redesign steps customers cannot complete.
Staff editingCan the person responsible change a routine detail without risking unrelated pages?Fix permissions and instructions first. Replace the publishing setup if its shared structure cannot support the required updates.

Machina scope worksheet.

The answer may be mixed. Keep the service page that already explains the offer and brings inquiries to the right team. Redesign a neighboring page if people cannot find a price or eligibility detail. Change a shared menu layout if every menu needs the same new fields. Each finding earns its own scope.

What can a rebuild still keep?

At Portobello’s On Main, the old homepage offered “Eat, Drink and Visit.” All three links led to missing pages, the menu went to a banquet PDF, and there was no hours or contact page. Changing the menu link alone would still have left guests without a page for hours or contact. That is the pattern we treat as a rebuild: every main route failing at once, with pages missing that no link repair can supply. We kept the familiar words as the headline and organized the new site beneath them. We moved breakfast and lunch into searchable menus, put call and directions buttons on the homepage, and built an editor where staff can change hours, events, photographs and contact details.

What should a web proposal make clear?

We map what each page must do before design begins. A proposal should then mark important pages as keep, edit, redesign, build or retire, with a reason beside each choice. Ask what happens to existing pages and files. A quote for a “new website” can leave out the very menu, guide or contact page a customer still uses.

For Moniveo, we built the marketing site, from the homepage to pricing and contact. Platform, Solutions and Pricing each open on a different buyer question. Dipa Inhouse designed the interface. Ask the same of any proposal: which question each page answers and where the visitor goes next.

  • Name the customer task for each page and show the proposed route from arrival to action. A menu, service comparison and contact form solve different problems.
  • List what the client supplies and who verifies it, including prices, service terms, opening hours, product details, photographs and approval of retired pages.
  • Name the page layouts and editing responsibilities planned for the job. Ask someone on your team to demonstrate a routine update before accepting the finished site.
  • Define the acceptance check for phone use, forms, purchases and accessibility. The WCAG 2.2 standard includes keyboard operation and labels for input fields, which give the team concrete checks for interactive pages.
  • Identify who owns hosting, domain access, redirects, analytics and the ability to fix a release fault. Put the handoff in the proposal.

Give both teams the same hypothetical situation. A service page lists three offers, and its inquiry form confirms submission but never reaches sales. Ask each team for a written explanation of how it would handle the page, who would fix the form connection and how staff would update an offer. A focused proposal may cover the page and connection. A whole-site proposal should name the shared fault it would investigate, such as a layout that blocks offer updates across several pages, and explain how it would check that fault before replacing the site.

Will the new site move pages people already use?

When we rebuilt the Veterans Transition Center site off Wix, we mapped 51 old addresses to 26 new pages with permanent redirects and checked every destination before launch. We also moved the files the old site served. That is the kind of work a new design proposal can overlook when it only shows the new pages.

A rebuild can change page addresses even when the domain stays the same. An old search result, bookmark or outside link still needs to lead somewhere useful. Google’s site-move guidance calls for an old-to-new address map, redirects and monitoring after launch. It also says to move the images and downloads the old site hosts. Ask for the map while the page plan can still change, then name who will test the live destinations and fix a broken route. The website migration checklist covers the checks before, during and after launch.

A visual refresh that keeps the same addresses may need little migration work. New page names, consolidated sections or a new domain make the address map part of the scope. Ask who owns it and who checks the moved pages and files after the site launches.

Choose the scope that fixes the task

Approve the scope only when the team can name what customers will be able to do afterward and who will check it on the live site.

In our web design and development work, we map the pages and customer routes before design, build the site, and test on real phones before launch. If you want us to assess your scope, reach out to Machina with the pages customers rely on, the updates your team struggles to make and the proposals you need to compare. The first useful answer may be to keep more of the site than you expected.

Next steps

Let's talk about your project

Tell us what you're working on. We'll tell you if we can help — and exactly what we'd do.

We use cookies and analytics to understand how visitors use our site and improve your experience. Privacy Policy · Do Not Sell or Share My Personal Information