The site does not work on a phone
Text too small, buttons too close, menus that do not open: most of your visitors are on a phone, and so is Google’s crawler.
Most redesigns start for good reasons: a site that looks dated, does not work on a phone, or cannot be edited without a developer. Most of the damage they do is avoidable. It comes from treating the redesign as a design job, so pages are shortened, headings are restyled into something that is no longer a heading, URLs change without redirects, and a few months later nobody can say why the enquiries fell.
PageSpeed Insights on the home pages of the 7 sites we link as our work, 14 Oct 2026.
We start a redesign from your Search Console. The pages that earn impressions and enquiries are listed before any design work, each one is given a place in the new site, and the design is built around keeping them. Then the site gets the redesign it needed: faster, easier to use on a phone, easier for your team to edit.
Text too small, buttons too close, menus that do not open: most of your visitors are on a phone, and so is Google’s crawler.
Every change waits on a developer, so the site falls behind the business.
When the theme or the page builder is the cause, fixing it in place costs more than rebuilding.
If the site works and only looks dated, a design refresh inside the same build is often enough, and it carries none of the migration risk.
Every page with its impressions, clicks and enquiries, so what to keep, merge or drop is decided on evidence.
Designed with your actual pages at phone width first, reviewed in the browser on a staging address.
The same platform where it works, a different one where it does not: WordPress, Shopify, Webflow or a custom build.
Every old URL mapped to its new home, redirects tested before the switch, and Search Console read daily for two weeks after.
On most redesigns the SEO is called in after launch, to find out what went wrong. Here it runs from the first day. The page map comes from Search Console, the titles and headings of the pages that earn are carried across on purpose, internal links are rebuilt in the new navigation, and the staging site is kept out of the index so it cannot compete with the live one.
On top of the speed, accessibility, SEO, hosting handover and training that come with every build.
A migration is the riskiest part of a redesign, and sometimes it is the whole job: Wix to WordPress, WooCommerce to Shopify, one domain to another, a page builder to a static build. The risk is almost always the same short list: URLs that change without a redirect, redirects that point at pages the new site does not have, content dropped in the move, and a staging noindex that ships with the site.
Every one of those is preventable. Our SEO migration page describes the method, and the checklist is the list we work from.
Each of these replaced a WordPress site, among them an unfinished template and one serving the wrong business entirely, with the old addresses mapped to the new pages. They are now static Astro sites.
Open the live site of the aircon repair business (opens in a new tab)
A home-services site for an aircon cleaning and repair business, with two calculators customers use before they book.
Open the live site of the architecture practice (opens in a new tab)
A site for an architecture practice: custom homes, renovations and permits, with the process drawn stage by stage and a lot coverage calculator.
Open the live site of the pest control company (opens in a new tab)
A home-services site for a pest control company: a page for each treatment, a library of pest guides and a droppings identifier.
Open the live site of the solar installer (opens in a new tab)
A site for a solar panel installer, built around a calculator that sizes a system from the customer’s own electricity bill.
Open the live site of the plumbing business (opens in a new tab)
A home-services site for a plumber open seven days, with a water meter leak check customers run themselves.
Open the live site of the tattoo artist (opens in a new tab)
A site for a tattoo artist who travels to the client, with a library of designs and aftercare guides.
Six stages on every site, whichever platform it is built on. The scope and the quote are agreed in writing after the first call, before any design starts.
01
What the site has to do, who it is for and what exists today. If there is a site already, we read its Search Console first, because the pages earning impressions decide what the new one must keep.
02
Every page listed with the search it answers and the action it asks for. On a redesign, every old URL is written beside its new home. You sign the map off before design starts.
03
Pages designed with your actual words and pictures, at phone width first. You review in the browser, on a staging address search engines are told to ignore.
04
Titles, descriptions, headings, schema and internal links are written as each page is built, so nothing is added at the end by somebody who never saw the page map.
05
Speed measured on a phone, every page at 320px wide and at 200 percent text, keyboard and screen reader checks, forms sent and received, redirects tested against the new build.
06
The switch, then Search Console read daily for two weeks. The domain, hosting and logins stay in your name, with a written note of how the site is built and a recorded session on editing it.
Speed
Measured in PageSpeed Insights on a phone before launch. Images sized for the slots they fill, fonts that do not block the page, no script a page does not use.
Accessibility
Colour contrast, keyboard use, visible focus, alt text written for each picture, 44px tap targets on phones, and every page readable at 200 percent text.
SEO foundations
One title, description and H1 per page, schema, a sitemap that matches the site, clean URLs, redirects from every old address, and Search Console set up in your name.
Hosting handover
The domain, the hosting and every login in your name. We set the site up on your host, recommend one, or host it for you; either way you can move it.
Training
A recorded call showing whoever edits the site how to change a page, add a post and swap a picture, and a short written guide to keep beside it.
Two weeks after launch
Search Console, forms and errors checked daily for the first fortnight, and anything the launch broke fixed straight away.
It can, and that is the reason to plan it. The risk comes from changed URLs without redirects, removed content and lost internal links. All three are preventable, and preventing them is the first half of the process.
It depends on how many pages there are and how much of the content changes. The planning, from Search Console to an agreed page map, is usually two to four weeks of it, and the written scope gives you dates for the rest.
No. If the platform is not the problem, we redesign on the one you have, which is faster and carries less risk. We recommend a move only when the platform is the reason the site is slow or hard to edit.
Usually some of it can be recovered. The first step is comparing Search Console before and after the launch to find which URLs lost what, then putting back the redirects or the content that went missing. Our SEO migration service covers this.
A 30-minute call in your working hours. Tell us what you sell and where, and we will tell you what we would do first and what it involves. Prefer email? Send your website through the form and the Passieon Team will reply within two working days.
Message us
Ask anything about your site or where your enquiries are going. It goes straight to a person, not a bot. Leave an email and you get a reply.