Website Redesign in Riyadh 2026: The Complete Technical Checklist

A website redesign is not a design project. It is a systems migration with commercial consequences that last three to five years. Most Saudi companies discover this six months after launch, when rankings have dropped, leads have dried up, and the new site looks beautiful and performs worse than the old one.

Here is what the data says about redesign failure: 40% of website redesigns result in a measurable decline in organic search traffic within 90 days of launch, according to industry-wide SEO migration analysis. The cause is almost never the design. It is the systematic omission of technical decisions  redirects not mapped, schema not rebuilt, page speed not validated in Arabic  that collectively unwind years of accumulated search authority.

For companies operating in Riyadh and the Saudi market in 2026, the stakes are higher than they have ever been. Google's Search Generative Experience and AI Overview features are now actively pulling structured content from Saudi-market websites into zero-click answers. Perplexity, ChatGPT, and Copilot are citing authoritative websites when answering B2B vendor research queries. A redesign that breaks your technical SEO infrastructure does not just hurt your Google.com.sa rankings  it removes you from the AI-powered research layer that Saudi decision-makers are increasingly relying on.

This checklist covers every decision point a Riyadh-based company needs to validate before, during, and after a website redesign in 2026. It is organized by phase. Work through it in sequence  the later phases depend on decisions made in the earlier ones.

Phase 1: Strategic Foundation  Before You Brief Any Agency

The most expensive redesign mistakes are made before a single wireframe is drawn. These are the strategic decisions that determine everything downstream.

1.1  Define the Primary Commercial Objective with a Single Metric

A website redesign without a single primary success metric produces a beautiful website that satisfies everyone and converts no one. Before briefing any agency, your leadership team must agree on one primary metric the redesign is accountable for.

The options for Saudi B2B companies are typically: qualified inbound lead volume, WhatsApp Business inquiry rate, demo or consultation booking rate, or organic search ranking for a defined keyword set on Google.com.sa.

The decision: What is the one number that will tell you, six months after launch, whether the redesign succeeded?

1.2  Audit Your Existing Site Before You Abandon It

The assumption that a redesign starts from zero is the source of most post-launch traffic collapses. Your existing website, however outdated, has accumulated technical equity: indexed pages, backlinks from other domains, established Core Web Vitals history, crawl authority, and keyword rankings on Google.com.sa.

Audit every piece of that equity before redesign begins:

• Run a full site crawl using Screaming Frog or Ahrefs to export every indexed URL
• Pull your top 50 traffic-generating pages from Google Search Console
• Pull your top 20 backlink-receiving URLs from Ahrefs or SEMrush
• Document every URL that receives organic traffic  these are protected assets that require redirect mapping in the new architecture

The deliverable: A complete URL inventory with traffic and backlink data, used to build the 301 redirect map and inform the new site architecture.

1.3  Map the New Information Architecture Against Real Search Demand

The most common structural redesign error is organizing the site around how the company internally categorizes its services, rather than how Saudi buyers search for them.

Before finalizing the sitemap, conduct keyword research in both Arabic and English on Google.com.sa. Identify the specific queries your target buyers use. Build the site architecture so that each high-intent query cluster has a dedicated, optimized page. If Saudi buyers search for "شركة تصميم مواقع الرياض" and you do not have a page specifically optimized for that query, your redesign has a structural gap from day one.

The deliverable: A keyword-mapped sitemap where each page is assigned a primary target keyword, a secondary keyword cluster, and an estimated search volume on Google.com.sa.

1.4  Choose the Technology Stack With Saudi Market Requirements First

Technology selection is frequently driven by agency preference, developer familiarity, or global trend  rather than the specific technical requirements of performing well in the Saudi market. In 2026, the technology decision has direct SEO and performance consequences.

The evaluation criteria that matter for Saudi market performance:

• CDN with Middle East edge nodes: Does the CMS or hosting platform support Cloudflare or a CDN with a Riyadh or Dubai PoP? Without this, your TTFB for Saudi visitors will be 200–500ms higher than it needs to be  a direct Core Web Vitals penalty.
• Native RTL support: Does the platform support true RTL layout without CSS hacks? Webflow supports RTL but requires manual configuration. Some platforms handle it cleanly; others require a parallel CSS architecture.
• Schema markup flexibility: Can you add custom JSON-LD schema markup to individual pages without a developer? For 2026 SEO and GEO, this is not optional.
• Arabic font rendering: Does the platform serve Arabic-optimized web fonts (Tajawal, Cairo, IBM Plex Arabic) without degrading page speed?
• Core Web Vitals baseline: What are the typical Lighthouse scores for sites built on this platform? Some website builders produce structurally slow output regardless of individual optimization effort.

The decision: Document the Saudi-specific technical requirements before evaluating platforms  not after a platform has already been selected.

1.5  Define the Bilingual Content Strategy Before Design Begins

Arabic and English are not two versions of the same website. They are two separate content systems that share a visual design language. The bilingual architecture decision  made before design begins  determines the URL structure, the CMS configuration, the content workflow, and the hreflang implementation.

The three architecture options and their trade-offs:

For most Saudi companies, the subdirectory structure (/ar/ and /en/) is the technically correct choice: it consolidates domain authority, simplifies hreflang implementation, and is the architecture Google explicitly recommends for multilingual sites targeting a single country.

The decision: Confirm the bilingual URL architecture in the strategy phase. Changing it post-launch is a major SEO migration event.

Phase 2: Design and Content  The Decisions That Determine Performance

2.1  Build the RTL Design System as a Parallel System, Not a Mirror

Arabic RTL design is not an English design flipped horizontally. Spacing logic, typographic hierarchy, icon directionality, form field alignment, and reading flow are all structurally different in Arabic. A design system built RTL-first  and then adapted for LTR  produces a better Arabic experience than one built LTR and retrofitted.

The RTL design checklist:

• All flexbox and grid layouts validated under dir="rtl" before design sign-off
• Arabic-optimized typeface selected (Tajawal, Cairo, Noto Kufi Arabic, or IBM Plex Arabic)
• Line-height and letter-spacing recalibrated for Arabic script (Arabic requires more vertical line spacing than Latin equivalents)
• Navigation menus, breadcrumbs, and progress indicators mirrored correctly
• Form fields, input labels, and error messages aligned for RTL input
• Icons with inherent directionality (arrows, chevrons, back indicators) mirrored
• Mixed LTR/RTL content (English product names within Arabic paragraphs) handled with dir="auto" or explicit Unicode bidirectional markup

2.2  Write Arabic Content Natively  Not Via Translation

This point was made in the first Astra Trio article on why Saudi websites lose business and it bears repeating here in the context of redesign: every Arabic page on your new site should be written by a native speaker in Gulf formal business register.

Machine translation  including the current generation of AI translation tools  produces Arabic content that is grammatically plausible but tonally wrong for Saudi professional audiences. The register mismatch signals inauthenticity in the same way that a non-native speaker's slightly-off idiom signals in conversation.

The practical workflow: Brief your Arabic copywriter with the English content strategy and keyword targets, then have them write the Arabic content independently  using the English as a reference for intent, not a source for translation. This produces Arabic content that ranks on Google.com.sa and reads as credible to Saudi buyers.

2.3  Design Every Page to Pass Core Web Vitals on Mobile Before Desktop

Google's ranking algorithm measures Core Web Vitals on mobile first. For Saudi Arabia, where 79% of web traffic is mobile, this is doubly important  both for ranking and for actual user experience.

The 2026 Core Web Vitals targets for Saudi market performance:

The design decisions that most commonly cause Core Web Vitals failures:

• Hero images not sized for mobile viewport and not served in WebP format
• Arabic web fonts loaded via @font-face without font-display: swap causing layout shift
• Animations triggered on page load before content is visible
• Third-party scripts (chat widgets, analytics, marketing pixels) loading synchronously

Run every page design through Lighthouse mobile simulation during the design phase  not after development is complete.

2.4  Build the Schema Markup Architecture During Content Design

Schema markup is not a post-launch SEO task. It is a content architecture decision that should be mapped during the design phase because it determines how content is structured on each page.

The schema types that matter for Saudi B2B companies in 2026:

• Organization  with Saudi address, phone, CR number, service areas, and sameAs links to LinkedIn and social profiles
• LocalBusiness or ProfessionalService  for service-area pages targeting Riyadh, Jeddah, and other Saudi cities
• Service  for each individual service page, with areaServed: Saudi Arabia, provider, and description properties
• Article  for every blog post, with author, datePublished, dateModified, and publisher
• FAQPage  for FAQ sections on service pages and blog posts
• BreadcrumbList  for all pages beyond the homepage
• WebSite  with SearchAction for sitelinks search box

Why this matters for GEO in 2026: AI-powered search engines  Google AI Overviews, Perplexity, Copilot  extract structured entity information from schema markup when constructing answers to user queries. A website without schema markup is structurally invisible to the AI citation layer, regardless of how good the written content is.

2.5  Define the CTA Architecture for the Saudi Buyer Journey

Every page needs a mapped CTA sequence that corresponds to where a Saudi buyer is in their decision process. The three-stage model that works for Gulf B2B:

Awareness stage CTAs (for blog posts and educational content): Content downloads  a framework PDF, a sector report, a checklist  gated behind a simple name and email form. These capture prospects who are researching but not yet ready to buy.

Consideration stage CTAs (for service and about pages): Free consultation, free audit, or free strategic session offer. The word "free" matters  Gulf buyers are being asked to invest time in an early-stage relationship. Reducing the perceived risk of that investment increases conversion.

Decision stage CTAs (for case study and pricing pages): WhatsApp Business direct link with a pre-populated message, calendar booking integration (Calendly or equivalent), and a Saudi phone number. In the Saudi market, WhatsApp Business is not an optional channel  it is the primary B2B communication tool and its absence on a website is a trust-negative signal.

Phase 3: Development  The Technical Decisions That Protect SEO Equity

3.1  Build and Validate the Complete 301 Redirect Map Before Launch

Every URL on your existing site that has inbound traffic, backlinks, or indexed status needs a 301 redirect to its equivalent on the new site. This is not a nice-to-have  it is the mechanism through which your existing search authority transfers to the new architecture.

The redirect map requirements:

• Every URL from the existing site crawl mapped to its new equivalent
• All redirects validated as 301 (permanent), not 302 (temporary)
• No redirect chains longer than one hop (A to B to C should be collapsed to A to C)
• No redirect loops
• All old Arabic URLs redirected to new Arabic URLs  not to English equivalents
• Old XML sitemap URLs cross-referenced against redirect map for gaps

The consequence of skipping this step: Every unredirected URL becomes a 404. Every 404 loses the link equity from any backlinks pointing to that URL. For sites with established Saudi backlink profiles  the single most valuable SEO asset in Google.com.sa ranking  this is an irreversible loss.

3.2  Implement hreflang Tags Correctly Across Every Page

hreflang is the technical signal that tells Google which language and regional version of a page to serve to which user. Incorrect hreflang implementation is the most common technical SEO error on Saudi bilingual websites  and it causes Google to serve the wrong language version to Saudi Arabic-language users, directly suppressing Arabic-language rankings.

The correct hreflang implementation for a Saudi bilingual site:

The validation requirements:

• Every Arabic page links to its English equivalent and vice versa
• hreflang tags are reciprocal  if Page A references Page B, Page B must reference Page A
• x-default is set correctly for users outside the targeted language regions
• hreflang is implemented in the <head> of every page  not only in the XML sitemap
• Validated using Google Search Console's International Targeting report post-launch

3.3  Configure CDN With Middle East Edge Nodes Before Launch

Page speed for Saudi users is determined primarily by the geographic distance between the user and the nearest CDN edge node serving your content. Without a CDN configured with Middle East presence, your content is being served from European or US origin servers  adding 150–400ms of latency to every page load for Riyadh users.

The configuration checklist:

• Cloudflare configured with Riyadh or Dubai PoP enabled (Cloudflare has a Riyadh edge node as of 2024)
• Static assets (images, CSS, JS) served from CDN, not origin
• Brotli compression enabled (15–25% better compression than gzip)
• HTTP/2 or HTTP/3 protocol enabled
• Browser caching configured for static assets (minimum 1-year cache-control for versioned assets)
• Arabic web fonts served from CDN or self-hosted  not from Google Fonts (external font calls add DNS lookup latency)

3.4  Image Optimization for Saudi Mobile Performance

Images are the single largest contributor to slow LCP scores on Saudi mobile connections. Every image on the new site must meet the following specifications before launch:

• All images converted to WebP format (30–50% smaller than JPEG at equivalent quality)
• srcset attribute implemented so mobile devices receive appropriately sized images, not desktop-scale files
• Hero and above-the-fold images preloaded using <link rel="preload"> in the <head>
• All below-the-fold images lazy-loaded with loading="lazy" attribute
• No image file exceeds 200KB after compression
• All images have descriptive alt text in both Arabic and English (separate alt tags per language version)
• Arabic image alt text contains Arabic-language keywords  these are indexed by Google for Arabic image search

3.5  JavaScript Performance Audit Before Launch

Excessive JavaScript is the second-largest cause of Core Web Vitals failures after unoptimized images. The 2026 standard for a well-performing Saudi market website:

• Total JavaScript payload under 300KB (uncompressed) for the critical path
• All non-critical JavaScript deferred with defer or async attributes
• Third-party scripts (analytics, chat, marketing tools) loaded conditionally  triggered by user interaction or loaded after the critical rendering path is complete
• No render-blocking CSS in the <head> beyond critical above-the-fold styles
• Tag manager (if used) configured with performance governance rules  each new tag requires performance impact sign-off

Phase 4: Pre-Launch Validation  The Checklist Before Going Live

4.1  Technical SEO Pre-Launch Audit

Run a full technical audit against the staging environment before the DNS is pointed to the new site. The items that most commonly cause post-launch ranking drops:

• robots.txt on staging site is set to Disallow: /  confirm the production robots.txt removes this block
• XML sitemap includes all Arabic and English URLs, submitted to Google Search Console and Bing Webmaster Tools
• Canonical tags correctly set on all pages  no self-referencing canonical errors, no cross-language canonical conflicts
• All 301 redirects tested and returning correct status codes
• No broken internal links (run a post-build crawl with Screaming Frog)
• hreflang implementation validated with a dedicated hreflang checker tool
• Schema markup validated with Google's Rich Results Test on all page types
• Google Search Console property created for both the root domain and the new sitemap submitted

4.2  Core Web Vitals Validation on Real Saudi Mobile Connections

Lighthouse scores in a Chrome DevTools simulation are useful proxies but not final validation. Before launch, test real-world performance:

• Google PageSpeed Insights scores: LCP under 2.5s, CLS under 0.1, INP under 200ms  tested on mobile simulation
• CrUX (Chrome User Experience Report) data reviewed in Search Console for Field Data  not just Lab Data
• WebPageTest run with a Riyadh-based test node (or Dubai as the nearest available) to validate actual TTFB for Saudi users
• Test conducted on the Arabic version of the site separately  Arabic fonts and RTL layout can produce different performance profiles than the English version

4.3  Saudi Trust Signal Audit

Before launch, verify that every trust signal Saudi buyers expect to see is present and correct:

• Saudi Commercial Registration (CR) number visible in footer
• Saudi or GCC office address (or partner address with disclosure) in footer and contact page
• Saudi phone number with +966 country code  not only a form
• WhatsApp Business link in header, footer, and contact page
• Arabic-language testimonials from named Saudi or Gulf clients (with name, title, company)
• Client logos from Saudi or Gulf companies visible on homepage and services pages
• Privacy Policy and Terms of Service pages present in Arabic  PDPL compliance is now legally required for Saudi websites collecting user data

4.4  GEO Readiness Audit

Generative Engine Optimization is the emerging discipline that determines whether AI-powered search tools cite your website when answering relevant queries. Before launch, validate:

• Every service page and article has a clear, factually dense opening paragraph that directly answers the most likely query for that page  this is what AI tools extract for citations
• All proprietary frameworks, methodologies, and data points are named and defined  AI tools cite named entities, not generic claims
• Schema markup is complete and validates without errors  AI crawlers use structured data to extract entity information
• Author schema is implemented on all articles with a named author profile  LLMs weight attributed content over anonymous content
• Internal linking structure creates a clear topical cluster around your core service areas  AI systems recognize content authority through topical depth and coherent internal linking

Phase 5: Post-Launch  The 90-Day Monitoring Protocol

A website redesign is not complete at launch. The 90-day post-launch period is when most of the recoverable issues surface  and when prompt intervention prevents temporary ranking fluctuations from becoming permanent losses.

Week 1–2: Monitor Google Search Console daily for crawl errors, 404 spikes, and indexing issues. Verify all 301 redirects are functioning. Confirm Arabic pages are being indexed with correct hreflang assignments. Submit the new XML sitemap.

Week 3–4: Check Core Web Vitals Field Data in Search Console for real-world performance data from Saudi users. First-party data from actual Saudi mobile users is more reliable than lab simulation scores. Address any metrics outside target ranges.

Month 2: Compare organic traffic and ranking positions against pre-launch baseline. Expect some fluctuation  Google re-evaluates sites after significant structural changes. Ranking recovery for sites with correctly implemented redirects and preserved content typically completes within 60–90 days.

Month 3: Run a full site re-crawl to identify any new broken links, missing schema, or content gaps that emerged during the post-launch period. Review conversion rates on the new CTA architecture against the pre-launch baseline. If conversion rates have not improved against the pre-redesign site, diagnose by CTA type and page.

What a Riyadh Website Redesign Costs in 2026  And What Drives the Variance

Pricing for website redesigns in the Saudi market in 2026 varies enormously based on scope. The variables that drive cost:

Scope drivers that increase investment: number of pages, bilingual Arabic/English content production, custom CMS configuration, e-commerce functionality, API integrations, custom animation, and GEO-ready content architecture.

Scope drivers that compress cost: template-based design versus custom, English-only launch with Arabic phased later, limited page count, and straightforward service or portfolio site without complex functionality.

Realistic market ranges for Riyadh in 2026:

The variable that most Saudi companies underinvest in: Arabic content production. A technically perfect bilingual website populated with machine-translated Arabic content is commercially equivalent to an English-only website for Google.com.sa Arabic-language ranking. The content investment is as important as the technical investment.

How Astra Trio Handles Website Redesigns for Saudi Companies

Astra Trio builds Saudi-market websites for companies that need to perform commercially  not just look credible. Every redesign project we deliver is built against the 47-point checklist above, with three additional guarantees:

Technical performance guarantee. Every site we deliver passes Core Web Vitals thresholds on mobile before handover. LCP under 2.5 seconds, CLS under 0.1, INP under 200ms  measured from a Saudi mobile simulation, not a desktop lab test.

Bilingual by architecture. Arabic is not an add-on on Astra Trio websites. Every site is designed RTL-first, with native Arabic content written by Gulf business register specialists, and full hreflang implementation validated against Google's international targeting requirements.

GEO-ready from launch. Every site we build includes complete schema markup, structured content optimized for AI citation, and a content architecture designed to compound authority on both Google.com.sa and AI-powered research tools over time.

If you are planning a website redesign in Riyadh or anywhere in Saudi Arabia in 2026, speak to our team before you brief another agency. The decisions made in the first two weeks of a redesign project determine 80% of the commercial outcome.

Frequently Asked Questions

How long does a professional website redesign take in Saudi Arabia?

For a bilingual, custom-designed Saudi-market website built to the technical standards described above, the realistic timeline is 10–16 weeks from strategy sign-off to launch. Template-based projects with limited content can be completed in 6–8 weeks. Projects requiring custom CMS integrations, e-commerce functionality, or large content volumes (50+ pages) typically run 16–24 weeks.

Will a website redesign hurt my Google.com.sa rankings?

A poorly executed redesign will. A properly executed redesign  with full 301 redirect mapping, preserved URL structure where possible, correct hreflang implementation, and maintained content quality  typically produces a ranking improvement within 90 days of launch, as the technical improvements compound against the preserved equity from the old site.

Do I need to rebuild my website if I just want better SEO results in Saudi Arabia?

Not always. Before committing to a full redesign, conduct a technical SEO audit of your existing site. If the core technical infrastructure  RTL architecture, Core Web Vitals, hreflang, schema markup  is fundamentally broken, a rebuild is more cost-effective than remediation. If the issues are addressable through optimization, a rebuild is not necessary.

What CMS platform is best for a Saudi bilingual website in 2026?

There is no universally correct answer, but the leading options for Saudi market performance are Webflow (strong design flexibility, adequate RTL support, good performance baseline), WordPress with a performance-optimized stack (maximum flexibility, more maintenance overhead), and custom-built headless CMS solutions (highest performance ceiling, highest cost). The decision should be driven by the technical requirements documented in Phase 1 of this checklist  not by agency familiarity.

Is PDPL compliance required for Saudi websites?

Yes. Saudi Arabia's Personal Data Protection Law (PDPL), enforced by the Saudi Data and Artificial Intelligence Authority (SDAIA), requires websites collecting personal data from Saudi residents to publish a compliant Arabic-language Privacy Policy, obtain explicit consent before data collection, and implement appropriate data security measures. Non-compliance carries financial penalties. PDPL compliance should be treated as a technical and legal requirement of every Saudi website redesign, not an optional addition.

How do I measure whether my website redesign was successful?

Against the primary commercial metric defined in Phase 1 of this checklist. Additionally: organic traffic volume on Google.com.sa at 90 days versus pre-launch baseline, Core Web Vitals Field Data scores in Google Search Console, conversion rate on primary CTA, and inbound lead volume from organic and direct channels. A redesign that improves aesthetics but does not improve at least two of these metrics against the pre-launch baseline has not delivered commercial value.

Astra Trio builds technically rigorous, commercially focused websites for companies operating in Saudi Arabia and the Gulf. If you are planning a redesign in 2026, speak to our team about the decisions that determine whether it performs.

‍

‍