Website Revival

Website revival: keep what works, rebuild what does not.

We rebuild B2B websites that have stopped carrying their weight, without throwing away the pages, the rankings and the URLs you already earned. This is for teams whose site is three years old, hard to edit, and no longer describes what the company sells.

Most sites do not need to start over. They need the good parts kept, the broken parts rebuilt, and the search equity carried across intact.

Revival, Not Redesign

A redesign starts with a blank canvas and treats everything before it as a mistake. That is how a site loses its ranking pages, its inbound links and the handful of URLs that quietly bring in most of the demos.

We start with what you have. We find the pages that earn attention, the content worth keeping, and the structure worth defending. Then we rebuild around them.

What we do

  • Audit the current site. Every page, every template, every URL. What works, what is dead, what is duplicated, what nobody has opened in a year.
  • Map the content that earns. Which pages bring in search traffic, which ones sales actually sends, and which ones are only there because someone made them once.
  • Keep the equity. Every URL is accounted for: kept, rewritten in place, or redirected to the closest match. Nothing is dropped without a decision behind it.
  • Rebuild the structure. Navigation, page hierarchy, heading order and internal linking, so people and answer engines can both follow it.
  • Design the surfaces that need it. New page design where the current one is failing, and restraint where it is not.
  • Rebuild in Webflow. A documented class system, reusable components, and a CMS your team can edit without a developer.
  • Rewrite the pages that misdescribe you. Structural copy on the pages where the product has moved on and the words have not.
  • Set up for AI search visibility. Clean semantics, structured data, and content shaped so ChatGPT, Perplexity, Gemini, Claude and Google AI Overviews can quote it accurately.
  • Launch with the redirect map verified. We check it live, page by page, not just in a spreadsheet.

How we run it

Step 1 · The audit. We review the site and send you what we find in writing: the pages worth keeping, the structural problems, and what we would rebuild first. Ask for it and it costs you nothing.

Step 2 · The plan. Together we mark every page keep, rebuild, merge or retire. This becomes the scope. Everything after this point is executing an agreed list, not discovering it.

Step 3 · Structure. New sitemap, new content model, new templates. We settle hierarchy before design, because hierarchy is what carries the traffic.

Step 4 · Design and build. Page design where it is needed, then the Webflow build. Pages land on a staging link as they are finished.

Step 5 · Content and redirects. We move the content across, keep what stays, rewrite what changed, and build the redirect map for everything that moved.

Step 6 · Launch and watch. We push live, verify redirects against the real site, and watch search behaviour and errors closely in the weeks after.

What you get every week. A staging link, a written note on what moved and what is decided next, and one call. The keep, rebuild, merge and retire list is shared and always current, so you can see exactly what happened to any page.

Deliverables

  • A written audit of the existing site
  • A page-by-page keep, rebuild, merge or retire decision list
  • New sitemap and content model
  • Rebuilt page designs where the current ones are failing
  • A rebuilt Webflow project with a documented class and component system
  • CMS collections your team can edit
  • Structural copy rewrites on the pages that misdescribe the product
  • A verified redirect map covering every moved URL
  • Metadata, structured data and semantic heading order across all templates
  • A recorded editor walkthrough and a support window after launch

Who it is for

  • B2B SaaS teams from Series A to C whose site is two or three positioning changes behind the product.
  • Companies that have search traffic worth protecting and cannot afford to lose it in a rebuild.
  • Marketing leaders who need to publish and cannot, because every change needs a developer.
  • Teams whose site works well enough that starting over would destroy more than it fixes.

Who it is not for

  • Pre-launch companies with no site and no traffic. That is a new build, and we should scope it that way.
  • Anyone who wants a new visual layer over the same broken structure. The structure is the work.
  • Teams who want to keep the current platform and only change the styling.
  • Sites with no one available to decide what stays and what goes.

Related services

Questions we get asked

Start with the audit.

Send us the site. We will review it and send back what we would keep, what we would rebuild, and what is quietly costing you traffic.

Start a project

Tell us what you are building.

Tell us where you want to go and we'll build the site that gets you there: fast, findable, and built to convert.