Morphos / Guide

Redesigning without losing your rankings

The fear is justified and the fix is boring: keep the URLs, keep the metadata, redirect what moves, and watch it for six weeks.

A stone building facade at blue hour partly covered by fine metal scaffolding, one window lit

A redesign does not have to cost you visibility, but it will if the URLs change without redirects or the markup gets thinner. Almost every post-redesign traffic drop traces back to one of five causes, and all five are avoidable.

The five causes of a post-redesign drop

In order of how often they are the culprit.

What actually goes wrong

The pre-launch checklist

Print it, or hand it to whoever is doing the work.

Ten things to confirm before you launch

#CheckWhy
1Export the current list of indexed URLsYou cannot redirect what you have not listed. This is the baseline for everything else.
2Map every old URL to a live equivalentOne-to-one where possible. A homepage catch-all loses the accumulated authority of each page.
3Carry over title and meta descriptionEven where you plan to improve them, start from the existing text rather than a template default.
4Keep the H1 and heading structureHeadings are how both search engines and screen readers understand the page.
5Preserve internal links to key pagesRooms, location, offers and contact should keep receiving links from the same places.
6Rebuild structured dataHotel, Offer, FAQ, Breadcrumb and LocalBusiness markup — verify it parses before launch.
7Regenerate the sitemap and submit itA stale sitemap pointing at dead URLs is worse than none.
8Check robots.txtRedesigns frequently inherit a staging noindex that nobody removed.
9Verify canonical tagsEvery page should point at itself, not at the homepage.
10Watch Search Console for six weeksCoverage and Core Web Vitals first, then queries. Drops show up here before they show up in bookings.

What to expect in the first six weeks

Some movement is normal. Subtle ranking shifts while search engines reprocess the site are expected, and a brief dip in impressions is common. What is not normal is a sustained drop in coverage — that means URLs are being lost, and it is fixable if you look within the first fortnight rather than the third month.

One thing the new site should improve

If the redesign does nothing for structured data, it is leaving something on the table. A growing share of travel questions are answered by AI assistants rather than search result lists, and assistants quote sites whose markup they can read. Adding Hotel, Offer and FAQ markup during a rebuild costs a day. Adding it afterwards costs a project.

Will a redesign always hurt my rankings temporarily?

Not always, and never much if the URLs, metadata and content are carried over. A small fluctuation in the first few weeks is normal while search engines reprocess the site. A sustained drop in indexed pages means something was lost and should be investigated immediately.

Should I redirect everything to the homepage?

No. Redirect each old URL to its closest equivalent page. Sending everything to the homepage discards the authority each page earned and confuses anyone who follows an old link from a review or an email.

How long until the new site ranks as well as the old one?

If URLs and content are preserved, usually days to a couple of weeks. If the URL structure changed, expect four to eight weeks while redirects consolidate — and longer if the content also got thinner.

Do I need to keep the old site online somewhere?

Keep a full copy of the old pages for at least six months — not serving them, but available. If a redirect turns out to be wrong, having the original content makes the fix trivial.

Three things, not one

Web design is where most projects start. The other two are what clients stay for.

01

Web design

Sites that carry the place, and make the next step obvious

Design and build, from the first conversation about a place to the day it goes live — hand-written front end, real photography, motion where it carries meaning.

  • Website design and build for hospitality, heritage and culture
  • Brand systems and storefronts
  • Redesigns that keep your existing search visibility

See what a project includes

02

Forward-deployed engineering

Embedded inside your operation, not at arm’s length

Someone who sits inside your tools and your weekly rhythm, and fixes the thing in front of you rather than writing a report about it.

  • Working inside your repository, dashboard and stack
  • Internal tooling for a small team that has to move fast
  • Integrations, automation and the middle layer

How the studio works

03

AI systems

Applied narrowly, where it saves a real hour

No AI for its own sake, and none of it near copy that goes out under your name without review. Only the parts that measurably remove work from a week.

  • Enquiry triage and content pipelines
  • Comment and review monitoring
  • An eight-source opportunity radar and follow-up sequencing

How the AI layer is scoped