URL inventory
Every indexed page, listed from your sitemap, a crawl, Search Console and analytics, with its clicks, links and conversions beside it. You receive: the inventory sheet, with a keep, merge or retire call on each group of pages.
Website redesign
We list what your current site earns, redirect or retire the old addresses, carry your content over and measure the result against a baseline taken before launch.
Get your redesign reviewPortfolio · selected work
Every site below is live and owned by the client. Each window is a capture of the real page, not a drawn mockup.
What a redesign covers
Website redesign services change how a site looks and works while keeping the pages, links and search traffic that already earn their place. The work starts by finding out which those are.
Pages that bring visitors from Google, pages other sites link to, and copy that already answers a buyer’s question. We find them in your analytics and Search Console, then carry them over or redirect them on purpose.
The layout, the menu, the page templates, the speed and the accessibility of each. Pages that no one reads or finds are merged or retired. The new design is built around the pages that earn, not around a blank screen.
Every old address is tested on a staging copy before launch, and the new templates are checked against WCAG 2.2 AA. After launch search clicks, quote requests and speed are read against the baseline taken first.
Two ways to start
Both end with a new site. They differ in what the first week is spent on.
| Blank page firstStarts fresh | Inventory firstKeeps what earns | |
|---|---|---|
| The first task | Mood boards, a new sitemap and a visual direction | A list of every indexed page with its search clicks, links and conversions |
| Old addresses | Redirects set once the new pages exist, for the main addresses | Each one mapped to a new page, or retired on purpose with a 410 |
| Existing content | Rewritten in full, or copied across as it is | Kept where it works, merged where pages overlap, rewritten where it misleads |
| Accessibility | Checked against the finished pages near launch | WCAG 2.2 AA set as the target for each template, with a written result |
| How it is judged | Stakeholder review of the new look | Search clicks, quote requests and speed against a baseline taken before |
A site whose traffic and leads have been steady usually has something worth keeping, and the inventory shows what. A site that gets almost no search traffic and has no links has less to protect, and a fresh start costs it little.
The standards
What Google says about moving URLs and what the accessibility data and WCAG 2.2 ask of a rebuilt site, with the source under each.
Google’s guide says any significant change can cause ranking fluctuations while it recrawls and reindexes. For a medium-sized site it can take a few weeks or more before the new URLs replace the old ones in results, and longer for larger sites.
The same guide tells owners not to worry about link credit: 301 and other permanent redirects do not cause a loss in PageRank. It recommends server-side redirects, 301 or 308, sent straight to the final page rather than through a chain.
Google advises against redirecting many old URLs to one irrelevant destination, such as the new home page. Pages merged into one can redirect to the merged page, and content that is gone should return a 404 or 410 error.
Google says to keep redirects as long as possible, generally at least 1 year, so it can transfer signals to the new URLs, including links from other sites. For visitors, it suggests considering keeping them indefinitely.
WebAIM tested the top 1,000,000 home pages in February 2026. Low-contrast text appeared on 83.9% of them, missing image alternative text on 53.1% and missing form labels on 51%. WebAIM notes that automated tools find only part of the failures.
Accessible Authentication (Minimum), Redundant Entry, Consistent Help, Target Size (Minimum), Dragging Movements and Focus Not Obscured (Minimum) are the six. A redesign is the natural time to meet them, because the page templates are being rebuilt anyway.
The scope
Six parts, each leaving a file or record you hold after launch.
Every indexed page, listed from your sitemap, a crawl, Search Console and analytics, with its clicks, links and conversions beside it. You receive: the inventory sheet, with a keep, merge or retire call on each group of pages.
Each old address matched to the new page that answers the same question, or marked to return a 410. The map is run against a staging copy before launch. You receive: the redirect map and the test results.
Pages that work move across with their headings, text and image descriptions. Overlapping posts are merged into one stronger page, and pages that mislead are rewritten with you. You receive: a content sheet showing what happened to each page.
Contrast, focus, tap-target size, labels and keyboard use are set for each template, then tested on the built pages by tools and by hand. You receive: a written check of each template against WCAG 2.2 AA, with what failed and how it was fixed.
Pages are built and tested against Google’s thresholds for loading, responsiveness and layout shift on a mid-range phone, and the scores are reported whether or not they pass. You receive: before and after scores for the main templates, and the field data to read once the site is live.
Search clicks, quote requests and speed are recorded before the launch, then read against that baseline on the dates in the scope. You receive: the measurement plan, the baseline and a comparison once the new site has run.
How it runs
Four stages, from the page list to the post-launch comparison. You approve each one and keep its document.
URL inventory
| Group | Old URLs | Search clicks, 90 days | Call |
|---|---|---|---|
| Product pages | 62 | 4,310 | Keep all 62 |
| Blog posts | 38 | 2,150 | Keep 24, merge 9 into 3 guides, retire 5 |
| Service and showroom pages | 24 | 1,180 | Keep all 24 |
| Project gallery pages | 18 | 390 | Merge into 6 project pages |
| Cart, login and test pages | 6 | 70 | Retire |
| Total | 148 | 8,100 | 119 pages on the new site |
Our stack
The tools that produce the page list, test the redirects and take the baseline. Open any one for its job in a redesign.
Google Search Console shows which pages Google has indexed, which searches they appear for and how many clicks they get.
We use it for the clicks behind the inventory, to submit the new sitemap at launch and to watch indexing afterward.
Questions
Keep exploring
A site built on a stack your team can maintain.
Theme and app work in your own Shopify store.
Lean WordPress: few plugins, logged updates, backups you can restore.
A whole store, from platform choice to launch.
Research with your users, then designs developers can build.
A store inside your WordPress site, with tax and payments set up.
One page for one offer, built to match the ad.
Updates, backups and checks, with a log you can read.
Research first, then tests sized to your traffic.
Start here
Send us your site and tell us roughly how many pages it has. We’ll look at which pages bring visitors in, flag what a move would put at risk, and tell you what we’d list and measure first.