Solution
Website redesign & replatforming
Redesigns lose traffic for boring reasons: missing redirects, deleted pages that ranked, a heavier site. We fix those first.
Why redesigns go wrong
What usually breaks
URLs change without redirects. A page with steady search traffic gets merged away. Analytics stops on launch day. None of it is a design problem, and all of it is avoidable.
You may recognise
- The site looks dated
- The CMS is painful to use
- You are rebranding or changing platform
Order of work
Audit, map, then redesign
-
01
Inventory
Every URL listed with traffic, inbound links and purpose.
-
02
Decide
Keep, merge, rewrite or retire each page. Write the redirect map.
-
03
Redesign
New templates and design system, built on the audit.
-
04
Migrate
Content moved, redirects tested on staging, tracking checked.
-
05
Launch
Go live by the checklist, then watch search and analytics for the first weeks.
The redesign
What changes, and what doesn’t
Most redesigns don’t need new structure everywhere. The audit shows which pages work and which only look old. We keep what works and rewrite what doesn’t.
At handover
What you have at the end
-
No orphaned URLs
Every old address resolves to a page or deliberate redirect.
-
A record of decisions
Why each page was kept, merged or retired.
-
Before and after numbers
Load times on the same pages, old site and new.
-
A stack you can run
Chosen for your team, not our convenience.
In this offer
What is included, and what is not
Included
- An inventory of every URL, with its traffic, inbound links and purpose
- A written keep, merge, rewrite or retire decision for each page, and the redirect map
- New templates and a design system, built on the audit
- Content migrated, redirects tested on staging and tracking checked before launch
- Load times on the same pages, old site and new
Not included
- Traffic figures we cannot see: the inventory reads your analytics and Search Console, with your access
- Replacing an e-commerce or back-office platform: we rebuild the front end, with your engineers
- Promised rankings after launch: we keep what ranks and report what happens
Fit
When to call us, and when not to
Worth a conversation if
- The site looks dated or is hard to edit, but some of its pages bring visitors
- You are rebranding or changing platform
- You can share read access to your analytics and Search Console
Probably not if
- You want a new look without time for the inventory
- The offer itself is still undecided
Work
Projects close to this problem
Built by the studio itself and labelled with their status. None is client work.
-
Transit Boréal
A bilingual site for a Québec–Toronto carrier with waybill tracking, a server-priced rate estimator and a staff console, on Cloudflare Pages and D1. : Transit Boréal -
Café Ruelle
A French-language site for a neighbourhood café with a live open/closed status, the day’s board, order-ahead pickup and the counter’s order queue. : Café Ruelle
Services
Services this draws on
-
01
Web design & development
Company websites designed and built in the same place: the page you approve is the page that ships. -
02
Frontend engineering
Senior frontend work on fast, accessible interfaces: performance, design systems in code and dense data views. -
03
SEO
Technical foundations, search data, the pages your buyers actually look for, and monitoring that tells you what changed. No rankings promised.
FAQ
Questions people ask about this
Do we need a full redesign?
Often not. A short audit (content, structure, speed, accessibility, the code) shows what is worth keeping. See website redesign.
Will the site rank well?
Nobody can promise rankings. What we can do is build the parts we control properly: content in the HTML, one clear topic per page, structured data that matches the page, internal links, redirects from old URLs, and fast pages.
How long does a website take?
It depends on the scope, and even more on whether the content is ready. The studio works in short cycles: AI agents take on much of the research, building and testing, and a person reviews every step, so a working version comes early and improves from there instead of arriving after months of documents.
We give a dated plan once the scope is agreed, not before, and we do not promise a date the scope cannot support.
Who owns the code and designs?
You do, once the project is paid for, as the contract sets out. Open-source libraries keep their own licences, which we list at handover.
Planning a redesign? Start with the inventory.
Tell us what you need and by when. We read every enquiry and reply in writing, with questions, a next step, or a plain no if we’re the wrong studio.


