How do I protect my hotel's rankings during a website redesign?
Short answer
To protect rankings during a redesign, treat it as a migration: list every URL that currently gets traffic or links, decide where each one will live on the new site, and set up permanent (301 or 308) redirects from old to new before launch. Keep the content that earns rankings, carry over titles and structured data, and make sure the staging site's noindex doesn't go live. After launch, monitor Search Console closely. Some temporary fluctuation is normal while Google recrawls; large, lasting drops usually mean missing redirects or lost content.
By Lodging Engine Editorial Team· Reviewed by Eric Zwanenburg· Last reviewed
Before launch
1. Inventory what matters
Export your current URLs from your sitemap, Search Console's performance report (pages with impressions or clicks), analytics landing pages, and any pages with external links. Room, location, offer, and destination pages are typically the most valuable.
2. Map old URLs to new URLs
Create a spreadsheet: old URL → new URL. Each old page should go to its closest equivalent, not all to the homepage. Pages with no equivalent can redirect to the most relevant parent page.
3. Preserve what earns rankings
- Keep or improve the text content of high-performing pages.
- Carry over unique titles, meta descriptions, and headings.
- Re-implement structured data (for example,
Hotelmarkup). - Keep
hreflangrelationships for language versions.
4. Protect the staging site — and remember to unprotect it
Block staging from indexing (password protection is safest). Make a launch checklist item to remove any noindex on the live site.
At launch
- Deploy permanent redirects for every mapped URL. Google recommends keeping redirects generally for at least a year.
- Update internal links to point directly to new URLs (not through redirects).
- Update canonicals, the XML sitemap, and your Google Business Profile website link.
- If you're changing domain, use Search Console's Change of Address tool — for every verified variant of the old domain (www, non-www, and subdomains). It isn't needed for HTTPS or www changes on the same domain.
After launch
- Test a sample of old URLs: each should return a single redirect to the right page.
- Watch Search Console's page indexing and performance reports for several weeks.
- Fix 404 errors for previously valuable URLs promptly.
Google notes rankings can fluctuate while it recrawls; for medium-sized sites it can take a few weeks or more before the new URLs replace the old ones, and longer for large sites.
Already launched and lost rankings?
- Find the pages that lost traffic (compare performance before and after).
- Check whether their old URLs redirect correctly.
- Compare old and new content — was important information removed?
- Check for leftover
noindextags and robots.txt blocks.
Common mistakes
- Redirecting everything to the homepage.
- Launching with the staging
noindexstill active. - Dropping detailed room or location text in favour of image-heavy designs.
- Changing URLs, design, and content all at once without a plan.
Checklist
- Complete list of valuable old URLs
- Old-to-new redirect map, page by page
- Content, titles, and structured data carried over
- Permanent redirects live at launch
- No
noindexon the live site - Sitemap and internal links updated
- Search Console monitored for several weeks after launch
Sources
- Site moves and migrations — Google Search Central
- How to specify a canonical URL with rel="canonical" and other methods — Google Search Central
- Get started with Search Console — Google Search Central