Redesigning Your Website Without Losing Your Google Rankings: A Migration Checklist

To redesign your website without losing your Google rankings, keep every page that earns traffic and give every URL that changes a permanent (301) redirect to its closest new equivalent. Carry over the content, titles and internal links that made those pages rank, make sure nothing blocks Google on launch day, and watch Search Console for the next two to three months. Google’s guide to site moves with URL changes says to keep redirects “for as long as possible, generally at least 1 year”, and that for medium-sized sites it can take “a few weeks or more” before Google shows the new URLs instead of the old ones. Most traffic lost after a redesign is lost through a skipped step, not because Google dislikes new designs.

The story is a familiar one. A business replaces a tired WordPress or Wix site, the new one looks far better, and three weeks later the phone rings less. Usually nobody mapped the old URLs, or a setting from the test site was left switched on. Both are cheap to prevent before launch and expensive to discover in July.

This checklist is for Greek small businesses replacing an old site, perhaps also changing domain (say from .gr to .com), changing platform or adding an English version. Where Google has published guidance we quote and link it; where the advice is our own judgement, we say so.

Why redesigns lose traffic

A redesign changes many things at once, and Google has to work out which new URL replaces which old one. Traffic drops when that chain breaks. The usual causes:

• Changed URLs without redirects. /υπηρεσίες becomes /services and the old address returns a 404.
• Dropped pages that ranked, such as an old prices page or a blog post that brought steady visitors.
• Content thinned for a “clean design”. Google can only rank what is on the page.
• A noindex or robots.txt block left on from staging. In WordPress, one ticked box (“Discourage search engines from indexing this site”) is enough.
• Content that only appears through JavaScript. Google can render it, but rendering is queued and can fail.
• Slower pages, weighed down by sliders, video backgrounds and heavy page builders.
• Internal links in menus, footers and text that still point at old URLs.
• Lost language versions, or English pages rebuilt without hreflang.
• Images and PDFs that had traffic, moved to new paths without redirects.
• Google Business Profile, Facebook and directory links still pointing at old URLs.

First, decide what kind of move this is

Google treats each kind of change differently, and the work involved varies a lot. Be clear which one you are doing before anyone quotes for it.

Google’s advice is to split big changes: “if you want to move your site to a new domain name, change your content management system (CMS), and update your site to use a new layout, do them one at a time”. Its Change of Address help page warns that if you combine a domain move with a new content and URL structure, “you will probably see some traffic loss”. Small businesses often do everything at once to avoid paying twice. If you do, expect a dip and follow another of Google’s tips: “Time your move to coincide with lower traffic, if possible.” On the Pieria coast, that means winter, not June.

Moving from .gr to .com

Think twice before changing domain. Google’s guide to multi-regional sites says country-code domains such as .gr “provide a strong signal to both users and search engines that your site is explicitly intended for a certain country.” If most of your customers are in Greece, adding English pages under /en/ on your .gr domain is usually simpler than moving everything to .com.

If you do move, keep the old domain. Google recommends “continuing to pay for the old domain for at least a year to prevent others from buying and using your abandoned domain for malicious purposes”, and your redirects only work while it stays registered. A .gr domain is registered through a registrar; EETT, the Hellenic Telecommunications and Post Commission, publishes information on .gr and .ελ domain names and a list of registrars. Check that the domain is registered in your business’s name, not a former agency’s or employee’s.

Before: inventory the old site

You cannot redirect what you have not listed. Build one spreadsheet of every old URL and what it is worth to the business.

1. Crawl the old site with a tool such as Screaming Frog, which Google’s guide mentions. Export every URL with its status code, title, meta description and main heading, including images and PDFs.
2. Export Search Console data for at least 12 months, so the summer is included: clicks per page, the queries behind them, and your most-linked pages from the Links report.
3. Export GA4 landing pages that lead to calls, forms or bookings, including visits from Facebook, newsletters or the QR code on your menu.
4. Add the URLs no crawler finds: old campaign links, printed QR codes, booking platform listings.
5. Benchmark monthly clicks, positions for the 10 to 20 searches that bring customers, speed in PageSpeed Insights and monthly enquiries. Keep a full backup of the old site.

Google’s Core Web Vitals give a clear speed target: main content visible within 2.5 seconds, taps answered within 200 milliseconds and layout shift of 0.1 or less. Whatever the design, the new site should be at least as fast as the old one on a mid-range phone over 4G.

Keep, merge or drop: decide for every URL

Add a “decision” column to the spreadsheet and fill it in for every row.

• Keep pages with clicks, links or enquiries, with the same or better content. Change the URL only for a real reason.
• Merge thin pages on one subject, such as three short posts about the same tax deadline, into one stronger page. Google says that if you have consolidated content “to a new single page, you can redirect the older URLs to that new, consolidated page.”
• Drop pages with no traffic, links or business value, such as an offer that expired in 2019. Google says to make sure those URLs “correctly return an HTTP 404 or 410 error response code on the new site.”

Do not redirect everything to the homepage. Google is explicit: “Don’t redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site. This can confuse users and might be treated as a soft 404 error.” And the best redirect is the one you never need: if an old URL is clean and descriptive, keep it.

Build the redirect map

The redirect map has one row per old URL, the new URL it goes to and the action. Here is an example for a fictional accountancy office in Katerini, moving from an old WordPress site with Greek slugs to a bilingual site on the same domain, with Greek at the root and English under /en/.

Use server-side permanent redirects (301 or 308). Google’s redirects documentation explains that with a permanent redirect “the indexing pipeline uses the redirect as a signal that the redirect target should be canonical”; temporary 302 and 307 redirects do not send that signal, so the old URL may stay in results. Some plugins and hosting panels create 302s by default, so check.

Avoid chains such as http://example.gr/υπηρεσίες going to https, then to www, then to /services. Google advises “redirecting to the final destination directly”, and otherwise keeping chains “ideally no more than 3 and fewer than 5” hops long.

Greek characters in URLs, or Latin?

Google’s URL structure guidelines recommend words in your audience’s language “(and, if applicable, transliterated words)”, encoded in UTF-8, so /υπηρεσίες is allowed. The trade-offs are practical. Pasted into an email or WhatsApp, that address becomes /%CF%85%CF%80%CE%B7%CF%81%CE%B5%CF%83%CE%AF%CE%B5%CF%82. Accents matter too: /υπηρεσίες and /υπηρεσιες are different URLs, so redirect rules must match exactly what links request. Test both the decoded and encoded forms.

We know of no Google documentation saying either form ranks better. For bilingual sites we prefer short Latin slugs, in English (/services) or Greeklish (/ypiresies), because they are easier to share and maintain. If your old Greek URLs rank well, keep them or redirect them precisely.

During the build: protect what already works

Keep staging private, properly

Put the test site behind a password, not just a noindex tag. Google’s robots.txt introduction says robots.txt “is not a mechanism for keeping a web page out of Google”; for that, use noindex or a password. A page blocked in robots.txt “can still be indexed if linked to from other sites”, and Google never sees its noindex tag. A password also leaves nothing hidden in the code to forget on launch day.

Carry over what made pages rank

• Keep titles and meta descriptions that already bring clicks. Rewrite them only with a reason.
• Keep the main text, headings and answers to common questions. A new layout can hold the same depth.
• Keep the alt text and file names of images that appear in Google.
• Point internal links straight at the new URLs.
• Put the main text in the HTML the server sends. Google’s JavaScript SEO basics note that server-side or pre-rendering “makes your website faster for users and crawlers, and not all bots can run JavaScript.”

Canonicals, hreflang and structured data

Give each new page a canonical tag pointing to its own new URL. For Greek and English versions, add hreflang: Google’s guide to localised versions says “each language version must list itself as well as all other language versions”, using full URLs, and annotations without a return link may be ignored. Carry over structured data such as LocalBusiness and opening hours, update the URLs inside it and test it with Google’s Rich Results Test.

A redesign is also the cheapest moment to fix accessibility: contrast, labelled forms, keyboard navigation and alt text. If you sell to consumers online, read our note on the European Accessibility Act before you sign off the design.

Launch-day checklist

1. Take a full backup of the old site, files and database, and keep it somewhere you control.
2. Freeze edits on the old site.
3. If the domain or host is changing, lower the DNS TTL a day or two ahead.
4. Publish the new site, then remove the staging password, every noindex tag and any robots.txt block. Check the page code yourself.
5. Switch on the redirects and crawl the full list of old URLs: each should return a 301 and reach a working page in one hop.
6. Check that dropped URLs return 404 or 410, not a “not found” page with a 200 status, and not the homepage.
7. Spot-check titles, canonicals and hreflang on your 20 most important pages.
8. Verify the new site in Search Console (copy any verification file or tag across) and submit the new XML sitemap.
9. If the domain changed, submit a Change of Address for the old property. You must own both properties with the same Google account.
10. Update links on your Google Business Profile, social profiles, directories such as vrisko.gr and xo.gr, and booking platforms.
11. Send the contact form, tap the call button and make a test booking, and confirm analytics records each one.
12. Run URL Inspection in Search Console on the homepage and your top pages.

After launch: what to watch for 4 to 12 weeks

Some movement is normal. Google’s guide says: “you may experience ranking fluctuations while Google recrawls and reindexes your site. This is normal and a site’s rankings will settle down over time.” For medium-sized sites, “it can take a few weeks or more for Google to gradually start showing the new URLs instead of the old ones (and for larger sites, even longer).” Check these weekly for the first month, then every two weeks:

• Performance report: clicks compared with the weeks before launch and the same weeks last year, since many Greek businesses are seasonal.
• Page indexing report: watch “Not found (404)”, “Soft 404” and “Excluded by ‘noindex’ tag”.
• 404s and chains: redirect any old URL still getting visits, and recrawl the old list once a month.
• Rankings for the searches you benchmarked.
• Enquiries: calls, forms and bookings. Traffic is only the means.

Keep redirects and the old domain for longer than you think

Google says to keep redirects “for as long as possible, generally at least 1 year”, and adds: “From users’ perspective, consider keeping redirects indefinitely.” After a domain change, the Change of Address page asks for at least 180 days, and longer while the old URLs still get search traffic. Our advice is simpler: keep them for good. They cost almost nothing, and old links in Facebook posts and on printed QR codes keep working. Store the redirect map with the site’s code, so the next redesign starts from it.

Questions to ask whoever builds your new site

• Who builds the redirect map, and can I see it before launch?
• Is the staging site protected by a password?
• Will I have admin access to the domain, hosting, Search Console and analytics?
• Are the redirects and the post-launch checks written into the quote?

If you are still deciding whether a redesign is worth it, our guides to business website costs in Greece and the real cost of a “free” website explain where the money goes.

How Orya One can help

Orya One is a software house in Paralia Katerinis, and you work directly with the people building your site. We give fixed written quotes, design for GDPR from the start, and once the project is paid in full, the code is yours. Our websites start from €400 for Essential (up to five pages, live in one to two weeks), €1,000 for Growth (custom design, Greek and English, content you edit yourself, booking and analytics) and €2,500 for Signature (bespoke, with an e-shop or booking engine). A care plan for hosting, updates, backups and small edits starts from €25 a month.

Before you replace your current site, ask for our free website check: a written report on speed, phones, Google and accessibility that doubles as the baseline for your redesign. Or send us a short note with your address and what you want to change, and we will tell you honestly what is worth keeping.