Website Redesign That Protects The Traffic You Already Have

Not when the URL map is written before the design and every redirect is live ahead of the switch. Traffic is lost when pages are deleted or renamed without a plan, which happens because the mapping gets left to launch week. We do the inventory first, name the pages that must survive, and crawl the site on launch day to catch anything missed.

Template count, integrations, and the speed of your decisions and content all decide it. Content and sign off are what stall a project, far more often than the build itself. We quote in stages with a date on each stage rather than one date at the end. Slippage becomes visible early enough to act on.

Templates, migrated pages, and integrations set the number rather than page count alone, which is why published ranges tell you very little. The readiness review comes first, then a fixed fee built from your site rather than an average. If you want to understand how we would scope it before going further, that is a conversation rather than a proposal.

A redesign changes how the site looks and how people move through it while keeping the platform and most URLs. A rebuild replaces the underlying site and often the platform. The URL question is what separates them in practice, and it is also what decides how much search risk the project carries.

Often, and that is usually the cheaper and safer answer. A supported platform with a tired design is a redesign. An unsupported one, or one your team cannot update, is a rebuild. The review says which you have rather than assuming the more expensive option.

Decisions, mostly, and faster than you expect. Sign off on the structure, approval of the protected page list, and access to whoever owns the CRM or booking system. Then either your content or permission for us to write it. Slow decisions are the single most common cause of a late launch.

Yes, and we will also tell you if the brief contains something we think is a mistake. A common one is a fixed launch date set before the inventory exists. We would rather raise that during the process than agree to it and manage the consequences later.

One hop from old address to new, with no chains, mapped in a spreadsheet you get a copy of. They go live before the switch, not after. We crawl the old URL list on launch day to confirm every one resolves. The deeper mechanics live on our technical SEO page.

We build to the WCAG 2.2 AA standard and test against it, and that is what any honest agency can promise. Nobody can promise legal compliance or protection from a claim. We will also say plainly that overlay widgets are not a fix and have lost repeatedly in court.

One senior lead owns the strategy, the structure, and the copy, and stays on your account. Freelance designers and developers we have worked alongside for years handle the visual design and the build, under that lead. No design floor sits behind us, and you should know that before hiring rather than after.

As many as it takes, with the structure approved before any visual work begins. Most revision spirals are really disagreements about structure being argued through colour and typography. Settling the skeleton first removes most of them.

Yes, from early in the build, and you are welcome to break it. Everything gets built and reviewed on staging, and nothing reaches live without a backup first. Making changes directly on a live site is how launches go wrong.

Redirects go live first, then the switch, then a full crawl of the old URL list to confirm every address resolves. We submit every form, confirm analytics and ad platforms are receiving, and stay available that day. Then the first month watch starts.

Yes. Komplex is based in Austin with a presence in New York City and Reykjavik, and redesigns happen remotely by nature. Sites serving several countries get the market and language structure decided during the inventory stage, because retrofitting it means changing every URL twice.