Crawl and map.
I crawl every URL on your current site and pull its Search Console history. Every page with clicks, impressions or links pointing at it gets a new home before design starts.
Website redesign services that protect your rankings.
Two weeks, old site to new. Every URL, redirect and piece of schema your old site earned moves across first. Then the design, speed and lead capture get rebuilt in a structure AI engines can read.
Where redesigns
lose traffic.
Rankings don't drop because the new site looks different. They drop because of what breaks in the move.
- 01
The staging block goes live.
The noindex tag or robots.txt rule that kept the dev site hidden ships with the launch. Google lists it first in its own site-move troubleshooting.
- 02
Redirects point to pages that don't exist.
Google says it frequently sees sites redirect old URLs to wrong, non-existent URLs on the new site.
- 03
Everything redirects to the homepage.
It's the fast option. Google may treat it as a soft 404, a page that's gone.
- 04
Old URLs live on inside the new site.
Internal links, canonical tags and the sitemap still point at the old addresses, so every click becomes a redirect hop. Google wants self-referencing canonicals and short chains, ideally no more than 3 hops.
- 05
Schema stays behind.
Schema that came from an old plugin or theme doesn't follow you to the new one. The new pages go live without it.
- 06
AI crawlers get shut out.
A fresh robots.txt blocks GPTBot or ClaudeBot by accident. I keep finding this one in audits.
Day 10 of the sprint checks every one of these on staging before anything goes live.
Even a clean move wobbles. Google says to expect temporary fluctuation in rankings, and that they settle down over time.
What the redesign
includes.
Your old site earned its rankings. Those move with you. The design, the speed and the way leads reach you get rebuilt.
Carried over from your old site
- 01
Every old URL mapped and 301-redirected.
Google recommends server-side permanent redirects, kept for at least a year.
- 02
Titles, meta descriptions, headings and schema moved across.
Page by page.
- 03
An automated sitemap.xml.
It rebuilds on every publish, with a real last-modified date on each URL.
- 04
Indexing submitted on launch day.
The sitemap goes to Google Search Console and Bing Webmaster Tools, plus an IndexNow ping. Fastest so far: a page indexed and ranking in under 22 hours.
New design
- 05
Designed for AI engines.
One clear answer per section, and headings written the way buyers ask.
- 06
Better UX and easy navigation.
Every service page one click from the menu.
- 07
Semantic HTML structure.
Header, main, article, section and nav where they belong, so machines read the page the way people do.
- 08
Static render, fast loading.
Pages ship as pre-rendered HTML.
- 09
Automated lead capture.
Every form sends the lead to HubSpot or your CRM and adds them to your email list and newsletter.
- 10
Better analytics.
GA4 and Search Console connected, with every form tracked as a conversion.
Two weeks,
old site to new.
The order follows Google's own site-move guide: test the new site, map URLs, redirect, then monitor.
-
Days 1 to 2 -
Days 3 to 5 Design.
You see the homepage, a service page, a blog post and the contact page by day 5. You approve, or we fix it the same week.
-
Days 6 to 9 Build.
Pages, schema, forms wired to your CRM, analytics and the sitemap.
-
Day 10 Test, then launch.
Every old URL is tested against its redirect, and robots.txt, canonicals and schema are checked on staging first. Then the site goes live, and the sitemap, IndexNow ping and Search Console requests go out the same day.
B2B website redesign,
built for how buyers research.
Your buyer has done most of the homework before they fill in your form. More of that homework now starts in a chatbot.
AI ModeG2's 2026 AI Search Insight Report polled over 1,000 B2B software buyers.
51%
now start their research in an AI chatbot more often than in Google.
69%
said a chatbot led them to a different vendor than they planned.
A B2B redesign has to work for both: the buyer, and the AI answering on their behalf.
- 01
One page per service.
Who it's for, how it works, how long it takes. Answered in the first lines, where a buyer and an AI can both find it.
- 02
Proof next to the claim.
Case files labelled by industry and region, with the numbers, on the pages where the decision happens.
- 03
Forms that qualify.
Ask what your sales team asks on the first call, then send it straight to your CRM.
- 04
Schema that names you.
Organization, Service and FAQ markup, so AI engines can tell who you are, what you sell and who you sell it to.
Industries I work withSee the case files
- Logistics
- 3PL
- Import/Export
- Ecommerce
- SaaS
- Software Development & Agencies
- Manufacturing
- Consultancies
- Hospitality
- Dental & Med Spa
- Scaffolding
- Trades and Home Services
- HVAC
- Real Estate and Property
Stay on your platform, or move.
The URL map comes with you.
Most redesigns don't need a new CMS. Some do. You get a straight answer on which one before anything is built.
-
WordPress
Stay if your team publishes every week and lives in the editor. A WordPress website redesign rebuilds the theme and keeps your slugs. Anything that has to move gets a 301 through the Redirection plugin.
-
Webflow
For marketing teams who want to change a page without waiting on a developer. The URL map and the 301 plan work the same way.
-
Framer
Pick it when motion is part of the brand. Framer writes the sitemap and handles permanent redirects in its site settings. Schema goes in through its custom code, page by page.
-
Astro
The one I reach for when speed matters most. Pages ship as static HTML, and the sitemap rebuilds on every deploy. This site runs on it.
Moving off Wix, Squarespace or a custom build? Same process. Every old URL gets mapped before anything moves.
No old site to protect? That's a new build.
Questions before
you redesign.
Not on the list? Ask it in the brief below. I reply within 4 hours.
-
Two weeks. Ten working days from the first crawl to launch. That assumes your copy and brand files are ready on day one. If they aren't, the sprint starts when they are.
-
It can. The damage comes from the move, not the design: broken redirects, a staging block left live, schema left behind. Every one of those gets checked on staging before launch. Expect a short wobble while Google processes the move. Google itself says rankings settle down over time.
-
Start with what you already have: a full crawl, your Search Console data and a URL map. Then the 301 plan. Metadata and schema carried across. Internal links pointed at the new URLs. robots.txt and noindex checks. A fresh sitemap, and indexing requests on launch day.
-
Map, design, build, test, launch. In that order. The URL map comes first because it sets what the new design has to keep. Design comes before build so you approve the look before a single page is coded.
-
Fix it if the site is fast, your team can edit it, and leads come in. Redesign it if pages take seconds to load, every change needs a developer, or buyers and AI engines can't tell what you sell from the homepage. A free audit tells you which, before you spend anything.
-
Give vendors what they need to quote: your goals, current platform, page count, the pages that bring traffic and leads, integrations like your CRM, and your deadline. Then ask each one how they handle redirects and SEO during the move. A vague answer to that question tells you enough.
-
Pages that earn traffic or links keep their content, or merge into a stronger page with a 301. Pages nobody visits get merged or retired. Nothing disappears without a redirect or a reason.
Shivam Attri AI SEO Consultant · AEO Specialist
Every brief gets a personal reply from hello@seoshivam.pro within 4 hours.
WhatsApp ShivamLet’s build something
AI engines actually cite.
Have a project in mind? Drop the details and I will reply within 4 hours with a 1-page audit of where your brand stands and exactly what to fix.