Website Redesign Checklist: How to Avoid Losing Your Google Rankings

Before you start

Crawl and archive the existing site. Every URL, title, meta description, heading and internal link. You cannot map what you did not record.

Export analytics and Search Console data. Identify your highest-traffic and highest-converting pages. These are the ones you must not break.

Record your ranking positions. Baseline your top hundred keywords so you can detect problems quickly after launch.

Identify your backlinks. Which external sites link to which pages. Those pages must either survive or redirect properly, or you lose the authority.

During the build

Map every old URL to a new one. Every single one. This mapping document is the single most important artefact of the migration.

Preserve content on high-performing pages. Redesigns often trim copy for aesthetic reasons. If a page ranks well, its content is part of why. Restructure the presentation, keep the substance.

Maintain heading structure. One H1 per page, logical hierarchy, keywords retained.

Carry over metadata. Titles and descriptions that perform should not be rewritten casually.

Rebuild schema. Structured data is routinely lost in redesigns.

Keep internal linking depth. If important pages become three clicks deeper, they will lose ranking strength.

At launch

Implement 301 redirects, not 302s. Permanent, one hop, no chains.

Never redirect everything to the homepage. It is the classic error and it destroys page-level relevance.

Update the XML sitemap and submit it.

Check robots.txt. Staging sites are frequently set to block crawlers, and that setting ships to production more often than anyone admits.

Remove noindex tags from the staging build.

Verify canonical tags point to the new URLs.

After launch

Week one: Crawl the new site for broken links and redirect errors. Watch Search Console coverage daily.

Weeks two to four: Monitor rankings for your baseline keywords. Some fluctuation is normal; sustained decline is not.

Month two: Compare traffic against the pre-launch baseline, segmented by page.

Expect a short dip as Google recrawls. If traffic has not recovered within six to eight weeks, something in the migration is wrong and needs diagnosing rather than waiting out.

The single most common cause of failure

Nobody owned SEO during the project. The designer designed, the developer built, and the redirect map was assembled hastily the night before launch.

Assign it explicitly, at the start.

---

# Publishing plan

Order to publish. Lead with the five cost articles, one per category. They target the highest-intent queries, they are the pages most likely to convert, and they establish the honest-pricing positioning that differentiates you.

Then publish the UAE-specific pieces: Arabic SEO, WhatsApp automation, Ramadan, influencer licensing, real estate portal dependency. These face the thinnest competition and signal genuine local expertise.

Then the emerging and technical pieces: AI Overviews, Core Web Vitals, platform comparison.

Cadence. Two per month, published consistently, beats twenty published at once and then nothing. Consistency is a quality signal.

Every post needs before publishing:

• A named author with credentials, for E-E-A-T
• Article schema with author and datePublished
• FAQPage schema where the post answers discrete questions
• A descriptive internal link up to its service page
• Two or three internal links across to related posts
• A real featured image with descriptive alt text and filename
• The primary keyword in the URL, H1, first 100 words and one H2

Refresh cycle. Update the cost articles every six months. Pricing content decays fast and refreshed content frequently outranks new content.