Skip to content
SEO18 minJuly 27, 2026

Website redesign: how not to kill SEO

Robert MirovUpdated Jul 27, 2026

Website redesign: how not to kill SEO

Redesign often starts “to look nice” — and a month later rankings and Google leads drop. The problem is not the new design itself, but a broken migration: URLs changed without redirects, Titles and copy vanished, speed worsened, indexing was closed “just in case.” This article is for a business owner in Tashkent and Uzbekistan whose site already brings organic traffic or is at least indexed. Below — the order: what to keep, what you can change, checklists before / on launch day / after. UZNEO: redesign and SEO work together if migration is run as a project, not as “we pushed a new layout Friday night.”

01What breaks SEO in redesign most often

• URL change (`/uslugi/remont` → `/services/repair`) without a 301 redirect (permanent redirect). • New pages with thin content instead of old copy that ranked. • Missing Title, meta description, H1, internal links. • `noindex` / password left on after staging. • Sharp mobile speed drop (Core Web Vitals). • Domain change or HTTP→HTTPS without a redirect map. • A “pretty” menu killed landings that were ranking.
BeforeAfter
“Design is outdated — rebuild everything”Change UI, keep the SEO frame
New pretty URLs “as the developer likes”Old URLs or a 301 for each
Content “we’ll fill later”Key copy moves on day X
Launch without Search ConsoleBefore/after — coverage and errors

02Before redesign: inventory SEO assets

Collect what you cannot afford to lose: ☐ Top pages by traffic from GA4 / Metrika for 3–6 months ☐ Top queries and pages from Google Search Console ☐ All indexed URLs (sitemap / export) ☐ Title, H1, meta description of key URLs ☐ Inbound external links to important pages (at least top ones manually) ☐ Forms, `tel:`, conversion events, GTM ☐ RU/UZ language versions and their links (hreflang), if any Rule: top-20 pages by traffic/leads get a separate row in the migration table: `old URL → new URL → 301 → content moved`. Bilingual — bilingual RU/UZ site and SEO.

03URLs and 301 redirects — the main risk

Ideal for SEO: keep URLs as they were, changing only layout and UI. If URLs must change — every old address needs a 301 to a relevant new one (not everything to the homepage). Redirect map:
Old URLNew URLTypeChecked
/usluga-a/uslugi/a301
/blog/post-1/blog/post-1301/no change
Redirect chains (A→B→C) and “all 404s to homepage” dilute equity and confuse users. After launch, spot-check 20–50 old links on a phone and in Search Console → Pages.

04Content, Title, H1: what must move

Design can update. The meaning frame of commercial pages is better kept or improved, not zeroed: • H1 close to the old query intent; • Title not “Romashka LLC”, but service + geo if that ranked; • main copy and FAQ not deleted “for minimalism” without replacement; • images: keep meaningful alt where they existed; compress without killing LCP.
On prod beforeRisky in redesignCalm
2000 words of service copyEmpty “card”Move + light edit
Title with cityTitle “Home”Keep intent
FAQ with keysFAQ removedKeep as a block
If redesign aims at conversion, combine: new UI + old strong copy. On leads — why the site gets no leads.

05Tech: index, speed, markup

☐ robots.txt does not block what you need ☐ No accidental `noindex` on prod ☐ sitemap.xml updated and submitted in Search Console ☐ Canonicals on new URLs are correct ☐ Schema (Organization, LocalBusiness, FAQ) not broken ☐ HTTPS, mixed content checked ☐ Core Web Vitals: LCP/INP/CLS acceptable on mobile ☐ Custom 404 with paths to key sections A stack change (e.g. to Next.js) helps speed if you do not load heavy media in the first screen. Tech guide — CWV and Schema.

06Analytics and ads: do not break measurement

Redesign often “drops” leads not because of SEO, but because forms and tags broke. ☐ GTM / GA4 / Metrika on the new template ☐ Events: form, `tel:`, messenger ☐ Google Ads / Meta conversions match the test ☐ UTMs in ads point to current URLs (or 301) ☐ Call-tracking / numbers on the site checked Test a lead before opening ads fully. Otherwise SEO and Ads both look like a “fail” — and the cause is one button.

07Launch day and the first week

Day X: 1. Enable redirects before or at DNS/deploy switch. 2. Check homepage, top-10 URLs, form, phone. 3. Remove `noindex`, submit sitemap. 4. Save a Search Console / rankings snapshot (something to compare against). Days 1–7: • Coverage / pages in GSC: 404 spike? • Logs or hosting 404 report; • Mobile speed on 4G; • Leads: test + real; • Ads: landings return 200 OK.
SignalAction
Many 404sAdd 301s
Index dropCheck noindex/canonical
0 leadsForm/GTM, not SEO only
Slow LCPMedia, fonts, scripts
Full post-launch checklist — in the sibling article 7 days after launch.

08When to expect recovery — and what not to do

After migration Google may recrawl pages for days and weeks. Short ranking noise is normal; a months-long crash usually follows the errors above. Do not: • change URLs daily “by feeling”; • mass-delete old URLs without redirects; • redesign again in 2 weeks “because we’re not used to it”; • buy links “to offset the drop” instead of fixing 404s. Calm order: keep the frame → 301 → content → tags → a week of control → targeted fixes.

Summary

Redesign does not have to kill SEO. Haste does: new URLs without 301s, empty pages instead of copy, forgotten noindex, and broken forms. Change the design; move the SEO frame as an asset. Order: inventory → URL map → content and Title → tech and analytics → day X → week of control. If you need a site with careful migration — website development in Tashkent and corporate website. UZNEO combines UI updates with keeping the search frame — without promising “top-1 again tomorrow.”

Ready to discuss your task

Tell us about your business on Telegram — estimate in 24 hours.