Website Redesign SEO: How to Redesign Without Losing Rankings

Website redesign SEO comes down to one rule: every page that earns traffic today must either keep its URL or be permanently redirected (301) to its closest new equivalent, with its content, title and internal links preserved. Most ranking losses after a redesign are not caused by the new design itself but by broken URLs, deleted content, and a staging site that was accidentally left blocked from Google. If you plan the migration before the designers start, you can launch a faster, better-looking site and keep your rankings.

Key Takeaways

• Crawl and export every URL on your current site before anything changes, and record which pages bring traffic and links.
• Map each old URL to one new URL and use permanent 301 redirects, never a blanket redirect to the homepage.
• Keep the content, headings and title tags of your best pages unless you are deliberately improving them.
• Test the new site on a staging server that is blocked from indexing, then remove that block on launch day.
• Watch Google Search Console daily for the first few weeks and fix 404 errors quickly.

Why Do Websites Lose Rankings After a Redesign?

Websites lose rankings after a redesign because Google suddenly finds different URLs, missing content or technical blocks where it used to find pages it trusted. Search engines rank individual pages, not brands. When a page that ranked for "English course Kabul" disappears or moves without a redirect, Google treats the new page as a stranger and the old one as gone.

The most common causes we see are:

• URLs changed from something like /about-us.html to /about with no redirect in place.
• Pages that brought steady traffic were removed because they "looked old".
• Text was replaced with images, sliders or short marketing lines, so the page no longer answers the query.
• The staging site's noindex tag or robots.txt block was copied to the live site.
• A new JavaScript framework rendered content in a way crawlers struggled with.
• Internal links, menus and breadcrumbs were rebuilt and important pages became hard to reach.

None of these are design problems. They are planning problems, which is why SEO needs a seat at the table from the first meeting.

What Should You Do Before the Redesign Starts?

Before any design work begins, take a complete snapshot of the current site so you know exactly what you must protect. This is the step most businesses skip, and it is the one that makes everything else possible.

1. Crawl the whole site. Use a crawler to list every URL, its status code, title tag, meta description, H1 and canonical tag. Save the export.
2. Export performance data. From Google Search Console, download the pages and queries report for the last 12 months. If you need a refresher, our Google Search Console beginner's guide explains where to find it.
3. List your linked pages. Note which pages other websites link to. Those links carry authority you do not want to throw away.
4. Mark your priority pages. Combine the data into a short list of pages that bring traffic, enquiries or links. These pages get the most care.
5. Record a baseline. Write down current clicks, impressions, top keywords and Core Web Vitals so you can compare after launch.

For a multilingual Afghan business, do this for every language version. A Dari page that ranks well in Herat is just as valuable as the English page that brings diaspora customers from Germany or Canada.

How Do You Map Old URLs to New Ones?

You map old URLs to new ones by building a simple spreadsheet with two columns, old URL and new URL, and filling in a match for every page that matters. This redirect map becomes the most important document in the whole project.

Follow these rules when filling it in:

• Keep URLs where you can. The safest redirect is the one you never need. If /services/web-design already works, keep it.
• One to one, not many to one. Redirect each old page to the most relevant new page. Sending everything to the homepage is treated much like a deleted page.
• Use 301 redirects. A 301 tells search engines the move is permanent and passes the old page's signals to the new one. Temporary 302 redirects are the wrong tool here.
• Avoid chains. If a page was already redirected in the past, point the oldest URL directly at the final destination.
• Handle every language. If your site uses /da/ and /pa/ paths, map those too and keep your hreflang tags consistent.
• Decide what truly goes. Pages with no traffic, no links and no business value can be removed and return a 404 or 410. That is fine, as long as it is a decision rather than an accident.

On modern frameworks such as Next.js, redirects can be defined in the project configuration or at the hosting level, so they work instantly and do not depend on a plugin.

How Do You Protect Content and On-Page SEO?

You protect on-page SEO by carrying over the elements Google already associates with each page: the main text, the headings, the title tag, the meta description and the internal links pointing to it. A redesign is a good moment to improve weak pages, but change ranking pages deliberately, one decision at a time.

Practical guidance:

• Keep the body copy of your top pages. You can restyle it, split it into sections and add images, but do not cut the substance.
• Keep title tags and H1s close to the originals unless the data shows they are underperforming.
• Preserve structured data such as Organization, LocalBusiness, Product or FAQ markup.
• Keep image alt text and file names meaningful when you replace photos.
• Rebuild internal links so priority pages are no more than a few clicks from the homepage.
• Make sure the new site is faster, not slower. Heavy hero videos and animation libraries can hurt Core Web Vitals, especially on mobile data in Afghanistan. Our guide to Core Web Vitals and INP in 2026 covers what to measure.

How Should You Test and Launch the New Site?

Test the new site on a private staging server, run the same crawl you ran on the old site, and only launch when every priority URL resolves correctly. Treat launch day as a checklist, not a celebration.

Pre-launch checklist:

1. Staging is password-protected or set to noindex, so Google does not index a duplicate site.
2. Every row in the redirect map has been tested and returns a single 301 to a live page.
3. Title tags, meta descriptions, canonicals and hreflang tags are present on every template.
4. The XML sitemap lists only the new, indexable URLs.
5. Analytics and conversion tracking fire on forms, calls and WhatsApp buttons.
6. Pages render their main content in the HTML that crawlers receive.

On launch day, remove the staging noindex and any robots.txt block, submit the new sitemap in Search Console, and spot-check the top 20 old URLs in a browser. Launch early in the week, when your team is available to fix issues, rather than before a holiday.

What Should You Monitor After Launch?

After launch, monitor Search Console coverage, 404 errors, rankings for priority keywords and organic conversions every day for two weeks, then weekly for at least two to three months. Some fluctuation in the first weeks is normal while Google recrawls the site; a steady, deep decline usually points to a specific technical issue you can find and fix.

Look for pages reported as "Not found", unexpected "Excluded by noindex tag" warnings, and priority pages that dropped out of the index. Fix redirects as soon as you spot gaps, and keep the redirects in place for the long term rather than removing them after a few months. A full technical SEO audit around six weeks after launch is a sensible checkpoint.

Work With Sheen

Sheen plans redesigns with SEO built in from day one: we crawl your current site, build the redirect map and launch on a fast Next.js build in English, Dari and Pashto. See our web design service and SEO service, or contact us at info@sheen.af or +93 784 966 018 to plan your redesign.