How to redesign your website without losing SEO: a checklist for Saudi businesses
Build the keep list, decide whether addresses change, keep staging closed, check launch day against the old site, watch four weeks, and time the launch away from your peak. With a tag check of 19 Saudi store pages and a reading of 15 redesign checklists shown in Riyadh.
The Khaleej SEO team
Published · Updated · 13 min read
A redesign loses rankings when it changes what Google reads: the addresses, titles, headings, text, internal links or crawl access of the pages that earn traffic. Keep those pages stable, or redirect each changed address to its closest match, keep the new site closed until launch, compare old and new on launch day, and watch Search Console for four weeks.
Free 5-point SEO audit. Send us your website or your Google Business Profile. Within 48 hours a senior specialist sends you 5 prioritized fixes with the evidence, and tells you which to do first. If you are about to redesign, we also check which of your pages carry your traffic. Get your free SEO audit.
This guide is for owners and managers of online stores, clinics, travel companies and service firms in Saudi Arabia who are about to restyle or rebuild a site on the same domain. It rests on Google’s own documents, opened on 27 October 2026, on our reading of the 15 redesign checklists that Google showed in Riyadh, and on a check of the tags printed by 19 Saudi store pages. A move to a new domain or a new platform is a bigger job, and our guide to store migration SEO covers it.
The short answer
| Step | What to do | Done when |
|---|---|---|
| 1. Keep list | List the pages that bring clicks, orders, enquiries and links | You have one row per page, with its address and traffic |
| 2. Addresses | Decide which addresses change and map each to its closest new page | Every changed address has one target |
| 3. Page | Keep the text, headings, links and tags that make those pages rank | A crawl of the staging site matches the old crawl |
| 4. Staging | Put the new site behind a password until launch day | Google cannot reach it, and you can |
| 5. Languages | Check Arabic and English separately, with matching pairs | Each page links to its twin, not to the other home page |
| 6. Launch | Test redirects, tags, sitemap, tracking and forms on the live site | The launch-day table below passes |
| 7. Watch | Read Search Console for four weeks against last year | You act on errors the same day |
Source: Khaleej SEO method, built on the Google Search Central pages listed under Sources, read on 27 October 2026.
What a redesign changes in Google’s eyes
Google does not see colours or layout the way an owner does. It reads addresses, text, links and tags. A redesign is risky exactly where it touches those:
| What changes | What can go wrong | Check before launch |
|---|---|---|
| Addresses | Old addresses return errors or land on the home page | Run the redirect list; each gives one 301 |
| Titles and headings | The main heading is removed or duplicated | Compare title and H1 with the old crawl |
| Text | Text is cut so a page looks cleaner | Compare word counts on the keep list |
| Internal links | Menus become buttons that Google cannot follow | Links are real a elements with an href |
| Hidden content | Text sits behind tabs or loads only on a click | Read the rendered HTML in URL Inspection |
| Mobile layout | Sections are dropped on phones | Same text, headings and markup on both |
| Tags | Canonical, hreflang or schema stop printing | Compare the tags of old and new |
| Crawl access | Staging settings go live (noindex, a robots block) | Check robots.txt and robots meta on the live site |
Source: Google Search Central, Site Moves and Migrations, Redirects and Google Search, JavaScript SEO basics, Mobile-first indexing best practices, Localized versions of your pages and Block Search indexing with noindex, read on 27 October 2026.
Step 1: write the keep list before anyone draws a screen
Most redesign damage is decided before design starts, because nobody wrote down what must survive. Build a list with one row per page, from three sources:
- Search Console, Performance, Pages: every page with clicks in the last 12 months, and the main queries for each.
- Analytics: every page where an order, a form or a booking started.
- Links: every page that other sites link to, from the links report in Search Console.
Then crawl the old site and save the result: address, status, title, H1, canonical, hreflang, word count. This crawl is your reference. After launch the old site is gone, and without the reference you cannot tell a deliberate change from a loss. Our e-commerce SEO audit checklist lists the same fields for stores.
The rule for the keep list is simple: a page on it keeps its address, its main heading and its text unless someone decides otherwise on purpose, in writing. Designers can restyle it. They cannot delete it.
Step 2: decide whether addresses change
This is the fork that sets the size of the risk.
If addresses stay the same, you need no redirects, but you still test them. On hosted platforms the platform often fixes the address pattern. Among the 11 Salla category pages in our set, all 11 addresses end with the letter c and a number, the platform’s pattern, so a theme change need not touch them. Confirm that in the theme preview before you assume it.
If addresses change, Google’s site move guide gives the rules:
- Map each old address to the matching new address before launch.
- Use server-side redirects. Google’s redirect page says to use JavaScript redirects only if you cannot do server-side or meta refresh redirects.
- Do not redirect many old addresses to one irrelevant destination such as the home page. Google says this can confuse users and may be treated as a soft 404.
- If an old page has no equivalent on the new site, make sure its address returns 404 or 410.
- Keep the redirects as long as possible, generally at least a year. Google says that gives it time to transfer signals, including links from other sites.
- Google also says permanent redirects do not cause a loss of PageRank, so the redirect itself is not the danger; a missing or wrong one is.
A redirect map is a plain table. Ours has three columns, with invented example addresses:
| Old address | New address | Rule |
|---|---|---|
| /product/watch-123 | /watches/watch-123 | Pattern: same product, new folder |
| /services/old-name | /services/new-name | One to one, renamed page |
| /blog/2019/old-tips | /blog/ | No equivalent: closest category, or 404 or 410 |
Source: Google Search Central, Site Moves and Migrations and Redirects and Google Search, read on 27 October 2026. The addresses are examples.
Google’s Change of Address tool is not part of this. Search Console Help describes it for moving a site from one domain or subdomain to another, so a redesign on the same domain does not use it.
Step 3: keep what ranks on the page
A page ranks for its text, headings, links and tags. The new design must carry all four.
Text and headings. Redesigns tend to shorten pages and push explanations into tabs. Keep the text that answers the query, in the page itself, under a heading that names the topic.
Rendered content. Google’s JavaScript guide says it queues every page that returns 200 for rendering and uses the rendered HTML to index the page. So test the rendered HTML, not the design: use URL Inspection on the staging copy or on the live page after launch, and look for your main text and links in it. Google says of its renderer that content it cannot see in the rendered HTML cannot be indexed.
Links. The same guide says Google can only discover links that are a elements with an href. A new menu built from buttons or click handlers can cut the site into pieces.
Mobile. Google’s mobile-first guide says the same content, headings and structured data should be on the mobile and desktop versions, because the two versions can then rank for the same keywords. Check the phone version for dropped sections.
Tags. On a hosted platform, the theme or platform prints most of the SEO tags for you, which means you do not see them until they stop. We saved 19 category pages from Saudi stores on 26 October 2026 and read the tags in the raw HTML:
| Tag in the page code | Pages that print it (of 19) | Note |
|---|---|---|
| Canonical | 18 | One page prints none |
| hreflang | 16 | Language pairs |
| Exactly one H1 | 15 | One page has none, 3 have two |
| Meta description | 18 | |
| Any structured data | 16 | Raw HTML, before scripts |
| Product list markup | 4 | Product, ItemList or CollectionPage |
Source: Khaleej SEO check of 19 category pages (11 on Salla, 2 on Zid, 6 on other platforms), saved on 26 October 2026, raw HTML before scripts.
Two details matter for a redesign. All 11 Salla pages print the same two structured data types, Organization and WebPage, and none prints product list markup, so on those pages the platform, not the merchant, sets the markup. And the H1 count varies on Salla (8 pages with one, 3 with two), so part of what prints comes from the theme or the store settings, and we cannot separate the two from outside. The practical rule: before you change theme or platform, crawl both versions and compare these tags, because a change of theme is a change of tags.
Limits of this check: 19 pages, one category page per store, not a random sample; raw HTML only, so a tag added by a script would not show; we do not know which pages sit in a redesign.
Step 4: keep the new site closed until launch
Google’s guide to launching an ecommerce site describes the cleanest method: require a password. A password blocks Google but lets testers in, and you then open the site at a time you choose. Two points follow.
First, do not use noindex or robots.txt as the lock. Google says a noindex rule works only if the page is not blocked by robots.txt and the crawler can reach it, so a robots.txt block hides the tag, and the page can still appear in results if other pages link to it. A password avoids the problem.
Second, the opposite mistake is just as costly: the settings of the closed site go live with it. Before and after launch, check four things on the live address: the robots meta tag and header carry no noindex, robots.txt does not disallow the whole site, canonical tags name the live address and not the staging address, and the sitemap lists live addresses.
Step 5: Arabic and English together
Most Saudi business sites run two languages, and a redesign touches both. Three checks:
- Pairs. Google says each language version must list itself and all the others, with fully qualified addresses, and that a missing return link can make the annotations be ignored. After the redesign, page A in Arabic must still point to its English twin and the twin must point back.
- The switcher. A language button that sends visitors to the other language’s home page breaks the pair. It should link to the equivalent page.
- Both redirect maps. If addresses change, the Arabic addresses need their own map. Test the Arabic version on a phone as a separate job, because the layout flips and sections that fit in English can break.
Step 6: launch-day checks on the live site
Run these on the day, in this order. Each row has a pass condition, so the person running it can say yes or no.
| Check | How | Pass when |
|---|---|---|
| Old addresses | Request every address in the redirect list | One 301 each, no chain, final page 200 |
| Keep-list pages | Request every keep-list address | 200, canonical to itself, no noindex |
| robots.txt | Open /robots.txt |
It does not disallow the whole site |
| Sitemap | Open the sitemap | Live addresses only, submitted in Search Console |
| Rendered HTML | Test home, one category, one product or service page in URL Inspection | Main text and links are present |
| Language pairs | Open one page in each language | Each links to its twin and back |
| Tracking | Place a test order or send a test enquiry | The purchase or lead event arrives in Analytics |
| Forms and calls | Use checkout, booking and call buttons on a phone | Everything works |
Source: Khaleej SEO method, built on Google Search Central pages listed under Sources, read on 27 October 2026.
After the checks, submit the sitemap. Google’s recrawl guide says to use the URL Inspection tool for a small number of addresses and a sitemap for many, that crawling can take from a few days to a few weeks, and that requesting a recrawl more than once for the same address does not make it faster. If the tracking row fails, fix it before anything else: without events you cannot read the result later, as our guide to measuring SEO ROI explains.
Step 7: the first four weeks
Google says to expect temporary fluctuation after a significant change, and that Googlebot has to visit the pages again. That is why a dip is not by itself a failure, and why you need rules for when to act. These are ours, not Google’s:
| When | Look at | Act the same day if |
|---|---|---|
| Days 1 to 3 | Page indexing errors, redirect results | Any keep-list address returns an error or a chain |
| Week 2 | Are keep-list pages indexed? Are new addresses in the sitemap report? | Pages are missing from the report and the sitemap is fine |
| Weeks 3 and 4 | Clicks and impressions of keep-list pages | They fall and the same weeks of last year did not |
Compare with the same weeks of last year, not with the weeks before launch. Google’s guide to debugging traffic drops lists seasonality as a cause on its own, and a launch in November or February lands in the busiest weeks of the year. Do not quote the average position from Search Console as a ranking; use clicks and impressions of the keep-list pages.
Keep a way back for the first weeks: the old site’s files or a backup, and a named person who can restore redirects or settings. A launch with no rollback turns a fixable error into a lost month.
When to launch: the Gulf calendar
Google’s own wording is a few weeks or more for medium-sized sites, so do not launch inside the weeks before a peak. Our planning rule, which is ours and not Google’s, is to launch at least eight weeks before a peak or after it ends. For stores, the dates are:
| Peak | Date | Latest launch, eight weeks before |
|---|---|---|
| White Friday 2026 | Friday 27 November 2026 | 2 October 2026 (passed) |
| Ramadan 2027 | About 8 February 2027 (estimate) | 14 December 2026 |
| After Eid al-Fitr | About 10 March 2027 (estimate) | Launch from here |
Source: Khaleej SEO calculation. Dates as used in our guides on timing and Ramadan; Ramadan and Eid are estimates until the moon sighting.
On 27 October 2026, White Friday is 31 days away, so a redesign that is not live and tested should wait. The practical windows are 28 November to 14 December, only for a site that is already built and tested, or after Eid al-Fitr in March 2027. Our guide on White Friday SEO for stores covers what still fits before the sale. Clinics and travel companies have different peaks: take the three busiest months of last year’s bookings and keep the eight weeks before them clear.
What the top redesign checklists leave out
We loaded five Riyadh searches on 27 October 2026, two in English and three in Arabic. Four of them returned 21 redesign checklist pages (12 in English, 9 in Arabic). We read 15 of them (9 English, 6 Arabic). Six we could not read: three refused the request, two answered with HTTP 202 and no page, and one returned only a script shell. We searched each page for the points below and read the matching sentences. The table counts pages that say it, not whether the advice is right.
| What the page says | English (of 9) | Arabic (of 6) |
|---|---|---|
| Do not send old addresses to the home page | 4 | 2 |
| Keep redirects at least a year | 3 | 1 |
| Names hreflang | 2 | 3 |
| Launch away from a busy season | 2 | 0 |
| Names Salla or Zid in the text | 0 | 0 |
Source: Khaleej SEO reading of 15 pages from Google results shown in Riyadh on 27 October 2026. The one Arabic page that names Salla and Zid does so only in a services menu.
Three readings. The Arabic checklists cover the two-language problem better than the English ones: three of six name hreflang, against two of nine in English, one of which is a case study. Nobody covers the Gulf stores’ own platforms: none of the 15 pages discusses Salla or Zid in its text. And almost none ties the launch date to a busy season: two pages advise it, both in English, and the Arabic page that mentions seasonality does so only to say that data should be compared across equal periods.
The fifth search, «تغيير قالب المتجر سلة السيو» (changing a Salla store theme and SEO), returned ten results from Salla’s help center, YouTube, TikTok and agency pages on theme customization and Salla SEO. None is about what a theme change does to search, and the four we opened contain no sentence with the Arabic words for changing or switching the theme.
Limits: 15 of 21 pages read, from five searches on one evening; the English results also held two Reddit threads and a Dribbble story, which we left out as not checklists; result pages change between loads; a keyword hit does not prove a page’s whole advice.
What a bad launch costs
Take a store that gets 300 orders a month from non-branded search. Suppose a bad launch cuts them by 40% in the first month, 40% in the second and 20% in the third before they recover. These inputs are illustrative:
| Month after launch | Drop (assumed) | Search orders lost (of 300) |
|---|---|---|
| 1 | 40% | 120 |
| 2 | 40% | 120 |
| 3 | 20% | 60 |
Source: Khaleej SEO calculation with hypothetical inputs. Total lost: 120 + 120 + 60 = 300 orders, one month of search orders.
The loss equals a whole month of orders from search, and it grows if the launch lands in a sale month. Multiply by your profit per order, using the method in our SEO ROI guide, and you have the figure to weigh against the cost of the checks above. Our guide on how long SEO takes shows why the recovery months cannot be bought back.
Questions to ask your designer or agency
- Which of my addresses will change? Give me the list before design is signed off.
- Who builds the redirect map, and who tests it on launch day?
- How is the staging site locked, and who removes the lock?
- Will the new theme print the same canonical, hreflang and structured data? Show me a crawl comparison.
- What is the launch date against my peak, and who can roll back?
- Who reads Search Console for the first four weeks, and what do they report to me?
Our guide to choosing an SEO agency covers the contract questions around these.
If you want the technical side done for you, see our technical SEO service. For stores, our e-commerce SEO work covers redesigns on Salla, Zid and Shopify, and for clinics our dental SEO service does the same. For how we work with Saudi businesses, see our SEO agency in Saudi Arabia page.
Sources
Opened on 27 October 2026, all pages returned 200 without redirects. Google Search Central: Site Moves and Migrations (updated 20 August 2026), Redirects and Google Search (14 April 2026), Block Search Indexing with noindex (10 December 2025), How To Launch an Ecommerce Site on Google (10 December 2025), Understand JavaScript SEO Basics (4 March 2026), Mobile-first Indexing Best Practices (10 December 2025), Localized Versions of your Pages (21 September 2026), Ask Google to Recrawl Your Website (10 December 2025), Debug Google Search Traffic Drops (10 December 2025). Search Console Help: Change of Address tool. The tag check and the checklist reading are Khaleej SEO work; the Salla and Zid labels come from the code of each saved page.
Planning a redesign? Our free 5-point audit lists the pages that bring you traffic today, so your designer knows which ones must survive, and it checks the tags and tracking that a new theme can drop. It is the first step of our SEO service for growing businesses in Saudi Arabia. No obligation, delivered within 48 hours. Request your free SEO audit.
Arabic and English SEO specialists for e-commerce stores, dental clinics and travel companies. Our team has led SEO for some of the largest e-commerce brands in the Gulf, across 7 MENA markets.