If I only have time to focus on one, should I prioritise traditional SEO or AI SEO?

Traditional SEO first — the technical foundation and link authority it builds also powers AI SEO. You can't earn AI Overview citations without the credibility signals that traditional SEO builds. AI SEO is the enhancement layer, not the foundation.

Does Google's AI search use backlinks to decide what to cite?

Yes. Research and Google's documentation confirm that the same authority signals that influence traditional rankings — particularly high-quality backlinks and E-E-A-T signals — influence which sources get cited in AI Overviews and AI Mode responses.

How long does it take to start appearing in AI Overviews?

Appearing in AI Overviews follows a similar timeline to earning featured snippets — typically weeks to months for sites with existing domain authority, longer for newer sites. Building topical authority clusters (multiple interlinked comprehensive articles on a topic) is the fastest path.

Website Redesign Checklist 2026: Upgrade Without Losing Rankings

Redesigns kill rankings when done carelessly. Follow the complete 2026 checklist — pre-launch audit, URL mapping, 301 redirects, launch-day steps, and post-launch monitoring.

Website Redesign SEO Migration Redirects Checklist Rankings Relaunch

Here's the horror story every SEO knows: a business redesigns its dated website into something beautiful — and organic traffic falls off a cliff the week after launch. Rankings built over five years, gone in five days. Cause of death: nobody mapped the old URLs, preserved the ranking content, or told Google what moved where.

Redesigns don't have to cost rankings — done properly, they improve them (better speed, structure, and UX are ranking food). The difference is process.

This is the complete checklist we run on every relaunch: pre-work, build-phase, launch day, and the 90 days after.

Phase 1

Pre-Redesign Audit (Protect What Works)

Before anyone opens Figma or Elementor:

☐ 1. Inventory every URL. Crawl the current site (Screaming Frog free tier, or your sitemap + GSC) into a master sheet. You cannot redirect what you haven't listed.

☐ 2. Identify your ranking assets. From GSC (12 months): pages with clicks/impressions, their top queries and positions. From GA4: pages driving conversions. From a backlink tool (or GSC links report): pages other sites link to.

These pages are load-bearing walls — mark them.

☐ 3. Record benchmarks. Export current rankings, traffic by page, Core Web Vitals, and conversion rates. Post-launch arguments about "did the redesign help?" are settled by pre-launch data.

☐ 4. Save what ranks. Full content backups of top pages — their titles, headings, body copy, and schema. Redesigns love rewriting the exact paragraphs Google was rewarding. Those answer-first passages can also be earning citations.

☐ 5. Define redesign goals in numbers. "Modern look" is not a goal. "Mobile conversion +30%, LCP under 2.5s, enquiries +25%" is. Design decisions get judged against these.

Phase 2

Build-Phase Rules (Where Rankings Are Saved or Lost)

☐ 6. Build on staging, blocked from Google. Password-protected or noindexed staging. Remember: that noindex checkbox must be unchecked at launch.

☐ 7. Keep URLs stable wherever possible. The golden rule: a URL that isn't changing needs no redirect and carries zero migration risk. Fight URL-structure "improvements" that add risk without SEO benefit.

☐ 8. Map every changing/removed URL — one to one. Old URL → most relevant new URL, in your master sheet. Homepage-dumping everything is a soft-404 factory that vaporises page-level rankings. No relevant target? Redirect to the closest category — or let a truly dead page 404/410 honestly.

☐ 9. Preserve on-page SEO furniture. Title tags, meta descriptions, H1s, image alt text, internal links, and schema from ranking pages — carried over or consciously improved, never silently dropped by a new theme.

☐ 10. Bake in performance and structure. The new site should launch meeting speed-guide standards (lean theme, image discipline, caching plan) and AEO-ready structure (question headings, FAQs, schema). A redesign is the cheapest moment to fix both.

☐ 11. Rebuild tracking before launch. GA4, conversion events, GSC access, pixels, and phone/WhatsApp click tracking — tested on staging.

☐ 12. Full pre-launch QA. Every form submits (and notifications arrive), mobile layouts on real phones, all internal links resolve on the new structure, 404 page exists and helps.

Phase 3

Launch Day (The Two-Hour Window That Matters)

☐ 13. Launch in low-traffic hours; full backup of the old site first. Rollback insurance.

☐ 14. Deploy all 301 redirects the moment the new site goes live. 301s (permanent) — never 302s — via Redirection plugin, Rank Math's module, or .htaccess for bulk patterns.

This step is the migration.

☐ 15. Un-block indexing. Reading-settings checkbox, robots.txt, staging noindex tags — all cleared.

☐ 16. Verify SSL/HTTPS intact. Across the new build, including a mixed-content sweep.

☐ 17. Submit the new sitemap in GSC. Then Request Indexing on your top 10 pages.

☐ 18. Spot-test 20 old URLs. From the master sheet, weighted toward ranking assets: each must 301 to its mapped target in one hop.

Phase 4

Post-Launch Monitoring (Days 1–90)

☐ 19. Daily, week one: GSC Pages report for 404 spikes and coverage errors (fix by adding missed redirects); crawl the new site for broken internal links; watch server logs/uptime.

☐ 20. Weekly, month one: Rankings on benchmark keywords, traffic vs pre-launch baseline, Core Web Vitals field data, conversion events firing.

☐ 21. Expect — and don't panic at — a settling dip. A 5–15% wobble for 2–6 weeks while Google recrawls is normal on well-executed migrations.

What's NOT normal

30%+ drops, 404 floods, or specific money-pages vanishing — those mean a missed redirect or dropped content; your master sheet finds it in minutes.

☐ 22. Days 30–90: Compare against Phase-1 benchmarks; reclaim any lost snippet/citation placements (the answer-first passages from step 4); update GBP, ads, email signatures, and social links to any changed URLs; archive the master sheet — it's gold for the next redesign.

Frequently Asked Questions

How long should redirects stay in place?

Effectively forever — at minimum a year, but old URLs live on in bookmarks, backlinks, and printed materials indefinitely, and redirects cost nothing to keep. Removing them early is how "mystery" 404 traffic appears years later.

We're redesigning AND changing domains. Anything extra?

Yes: the full checklist plus GSC's Change of Address tool, domain-level 301s (every-old-URL → same-path-new-domain where possible), updating all citations/backlinks you control, and doubled monitoring patience — domain moves settle slower than redesigns.

Combine both changes only if you must; separately is safer.

What does a rankings-safe redesign cost in India vs a basic one?

The migration work itself (audit, mapping, redirects, monitoring) adds roughly ₹10,000–₹30,000 to a redesign project depending on site size — against which a rankings collapse on an established site costs months of traffic and revenue.

On our own projects it's not an add-on; it's the definition of "redesign done."

Final Thoughts

A redesign is heart surgery on a living asset: the patient should wake up stronger, not flatline. Inventory everything, protect the ranking organs, map and 301 every move, verify at launch, and monitor like it matters — because it does.

Beautiful and found is the only acceptable outcome.

Redesign With Rankings Preservation