Every old URL
Mapped one to one, before launch
A redirect to the homepage is a lost page. We map each one to its real replacement
04 Fast. Secure. SEO ready.
Sites built by the people who then have to rank them. Which is why they are fast on a mid-range phone, crawlable on day one, and do not lose you a single page on launch.
The dashed line is the limit, set before the design is signed off rather than chased afterwards.
/old-services /seo/ Mapped /about-us-2019 /about/ Mapped /boiler-repair homepage Lost Most of the traffic disasters we are called in to fix were launches. A new site goes live, it looks far better than the old one, and three weeks later the enquiries have halved. Nobody redirected the old URLs, or the new theme ships eleven hundred kilobytes of JavaScript before anything appears, or the staging site went live with its noindex tag still attached.
None of that is bad luck. It is what happens when the people who build a site and the people who have to rank it are different companies who meet at the handover. We do both, so the search questions get asked while the thing is still a wireframe: what is this page for, what search does it answer, where does it link, and what happens to the URL it replaces.
The result is less exciting to talk about than a redesign. It is a site that loads in under two seconds on a phone on a train, that a crawler can read completely, and that you can edit yourself without filing a ticket.
Six things, from a new build to keeping an existing site fast and patched.
This is the list we work through on every launch, and it is the reason our launches are dull.
Mapped one to one, before launch
A redirect to the homepage is a lost page. We map each one to its real replacement
Measured on a mid-range phone, not a laptop
Budget set at the design stage, because you cannot optimise a heavy design later
Content and links in the initial HTML
If the navigation needs JavaScript to exist, half your site may as well not
Carried across, not quietly dropped
Reviews, products, FAQs and local markup rebuilt in the new templates
Analytics and conversions tested before go live
Launching blind means you cannot prove what the launch did either way
Removed on launch, and verified
Astonishingly common, invisible for weeks, and it costs everything
Four stages. Nothing in stage three is worth buying until stage one has been done, and we will say so rather than invoice for it.
What you sell, where you sell it, and the page each of those needs. The sitemap comes before the design, because the design has to hold the sitemap rather than the other way round.
Layouts, type and images chosen with a weight limit attached. Everything is checked on a mid-range Android before it is signed off, not after.
WordPress where you need to edit it, Shopify where you need to sell, static where you need it to be fast and cheap to host. Chosen for your situation rather than ours.
Redirect map, index coverage, vitals and conversion tracking checked on the day and again at a week. If something moves the wrong way we find it in days rather than quarters.
Not everyone needs this, and the ones who need it least are usually the ones being sold it hardest.
A redesign is often the wrong answer. Sometimes the build is sound and the problem is three plugins and an uncompressed hero image.
Six to twenty pages, a clear enquiry path, and fast on a phone. Most of this sector is being sold far more website than it needs.
Shopify or WooCommerce builds where the category structure is designed for search rather than bolted on afterwards.
Changing platform, merging two sites or moving domain. This is where the losses happen and where planning actually pays.
Anything not answered here, ask it on the form. You get a person, not a sequence.
WordPress if you want to edit content yourself and need flexibility. Shopify if selling is the point and you would rather not maintain anything. Static or headless if speed and hosting cost matter more than a visual editor. We will recommend the boring option whenever it fits, because it is cheaper for you to live with.
It can, badly, and that is usually down to redirects and page speed rather than design. Done with a URL map and a performance budget, a rebuild normally improves rankings because the technical debt goes with the old site.
A focused service site is usually four to six weeks from signed off content. A shop or a migration is eight to twelve. The delay is almost always content rather than development, so we start that first.
Yes, and we would rather. A build waiting on copy is the single most common reason projects slip, and pages written by whoever is nearest tend not to answer any particular search.
You do. Your hosting, your domain, your repository, your logins, documented. No proprietary page builder that only we can edit and no licence that lapses if you leave.
Usually, yes. We will look at it first and tell you honestly whether fixing it is cheaper than replacing it. Sometimes it is, and we will say so even though the smaller job is worth less to us.
A rebuild, a repair, or nothing at all. You get a written answer with the actual numbers: load time on a mid-range phone, how many pages are indexed, and what is costing you most.
We have opened your email app with the answers already written out. Press send in there and it reaches us.
Nothing opened? Copy the details below into an email to info@nwestradigital.co.uk, or call 07403 641273.