Most SEO problems on small business sites are not caused by missing keywords. They are built in: a slider that hides the main message inside an image, a menu search engines cannot follow, an English version Google never connects to the Arabic one, or a redesign that deletes every old URL. SEO-friendly web design means making the right technical and layout decisions while the site is being built, so the content you publish can be found, read and ranked. Here are the 15 decisions that matter most, what to ask your designer about each, and how to check them yourself.

In short:
- The build decides whether Google can crawl, understand and fairly judge your pages. Content and reputation then decide how high they rank.
- The costliest decisions to fix later are structural: URLs, navigation, page templates, language versions and redirects.
- Google's page experience targets are public: LCP within 2.5 seconds, INP of 200 ms or less and CLS of 0.1 or less, measured on real visits.
- A bilingual Saudi site needs one URL per language, reciprocal hreflang tags and a language switcher that links page to page.
- No designer can guarantee rankings. A good one can make sure the build does not hold you back.
In this guide
What SEO-friendly web design actually means
SEO is often treated as something you add after launch: install a plugin, write some meta descriptions, submit a sitemap. Those steps help, but they sit on a foundation the designer and developer have already poured. If it is weak, every article you write works harder for a smaller result. It helps to separate what the build controls from what it does not:
| The build controls | The build does not control |
|---|---|
| Whether every page has its own clean URL that search engines can reach | How many other sites link to you or mention your business |
| Whether menus and internal links are real, crawlable links | How useful and original your content is |
| How fast pages load and how stable they are on a phone | Your reviews and reputation on Google Maps |
| Whether Arabic and English versions are connected correctly | How strong your competitors are for the same searches |
| Whether old URLs keep their value after a redesign | Changes Google makes to its ranking systems |
This article covers the left column. For the right column, how to get your business noticed once the site exists, read how to get found on Google and our guide to the Google Business Profile in Saudi Arabia. The 15 decisions below are grouped in five areas, each with something concrete to ask or check, so you can use this page as a review sheet for a proposal or a preview link.
Decisions 1 to 3: site structure, URLs and navigation
1. A URL structure people can read
Google's SEO Starter Guide recommends URLs with words that are useful to people, because searchers see the URL before they click. /services/air-conditioning-maintenance/ tells a visitor exactly what to expect; /?p=482 tells them nothing. The guide also notes that grouping pages in folders mainly helps sites with thousands of URLs, so a small business does not need deep nesting.
| Weaker URL | Clearer URL | Why |
|---|---|---|
| /?page_id=482 | /services/office-cleaning/ | Describes the page in words |
| /services/cleaning/offices/riyadh/2026/new/ | /office-cleaning-riyadh/ | Short, no dates that will age |
| /Office_Cleaning_Services.html | /office-cleaning/ | Lowercase, hyphens, no file extension |
| An Arabic slug that becomes a long %D8%... string when shared | A short slug decided once for each language | Readable when pasted into WhatsApp or email |
Arabic URLs are a real choice for Saudi sites: search engines handle them, but apps often show them as percent-encoded strings when copied. Whatever you choose, decide before launch and keep it, because changing URL patterns later means a redirect for every page.
Ask: "What will each service page's URL look like, and are WordPress permalinks based on the page name rather than an ID?"
2. Navigation and internal links that search engines can follow
Google discovers most pages by following links and uses the link text to understand the target page. That makes navigation an SEO decision, not only a design one.
- Every important page should be reachable from the menu or footer within two or three clicks of the home page.
- Menu items should be standard links, not buttons that only work through a script. The mobile hamburger menu should still contain real links.
- Related service pages should link to each other with descriptive text, such as "duct cleaning" linking to "air conditioning maintenance", rather than "read more".
- Blog articles should link to the service they relate to. Many sites lose value here: articles get visits but never pass visitors, or relevance, to the pages that make money.
Check: pick any service page and count how many other pages link to it. If the answer is "only the menu", internal linking has not been designed.
3. Page templates built for one topic per page
A common shortcut is one long "Services" page listing everything in a few lines each. It gives Google one page to rank for a dozen different searches, and none of them well. Someone searching for "commercial kitchen hood cleaning" wants a page about exactly that.
The better approach is a reusable service template: a clear heading, a short answer to "what is this and who is it for", the process, areas covered, common questions, project photos and a contact block. Each service gets its own page and its own text, and adding the next one becomes a content task, not a development job.
Be careful with city pages. They only help if each says something genuinely local, such as a branch address or local projects; ten copies with the city name swapped are thin, duplicated content. Our page plan by business type helps you decide how many pages you need.
Decisions 4 to 6: headings, titles and accessible markup
4. A heading structure that matches the content
Designers sometimes make a decorative line like "Welcome" the main heading because it looks right in large type, while the line that says what the business does sits in a plain paragraph. Google's Starter Guide is relaxed about heading order, saying it does not matter for Search, but it notes that semantic order helps screen readers, and clear headings help everyone scan. The practical rule:
- One main heading per page that states the topic plainly: "Office cleaning in Riyadh", not "Welcome to our world".
- Section headings that say what the section answers: "What the service includes", "Areas we cover".
- Visual size set by CSS, not by choosing a heading level because it happens to be the right size.
5. Editable titles and descriptions for every page
The page title is usually the clickable headline in Google's results. The Starter Guide describes a good title as unique to the page, clear and concise, and accurate about its contents. Themes often generate "Page name | Site name" automatically, which is a fine default, but you need fields to override the title and write the meta description on every page type, including services, posts and projects. On WordPress this usually comes from an SEO plugin. One thing to skip: the meta keywords tag, which Google says Search does not use.
Check: a few weeks after launch, search Google for site:yourdomain.com. If many results share one title, or show "Home", the templates need attention.
6. Accessibility, where good design and SEO overlap
Many choices that make a site usable for people with disabilities also make it easier for search engines to understand. Accessibility matters in its own right, but the overlap is large:
| Accessible practice | Why it helps people | Why it helps search |
|---|---|---|
| Real text instead of text inside images | Screen readers can read it; it scales on small screens | Search engines can read and index it |
| Descriptive alt text on meaningful images | Describes the image to visitors who cannot see it | Explains how the image relates to the page |
| Descriptive link text | Links make sense out of context | Anchor text tells Google what the target page covers |
| Logical headings | Visitors can jump between sections | Makes the page structure clear |
| Captions or transcripts for video | Content available without sound | Adds indexable text about the video |
For the full list, see our website accessibility checklist based on WCAG 2.2.
Decisions 7 to 9: mobile-first layouts, Core Web Vitals and images
7. A mobile version that contains everything
Google mainly uses the mobile version of a page for indexing and ranking. The risk is not that the mobile layout looks different; it is that it contains less. Designers sometimes hide the detailed description, the FAQ or the price table on small screens to keep pages short. Collapsing content into accordions is fine; removing it asks Google to rank a thinner page.
Watch for full-screen pop-ups too. Google's guidance says ads and interstitials should not stop people reading the content. A floating WhatsApp button in a corner is fine; a pop-up covering the whole phone screen on arrival is not. Our article on designing for mobile first covers the layout side.
8. Core Web Vitals budgets agreed before the design
Core Web Vitals measure loading, responsiveness and visual stability as real visitors experience them. web.dev publishes the targets:
| Metric | What it measures | Good result | Design choices that affect it |
|---|---|---|---|
| Largest Contentful Paint (LCP) | How soon the main content appears | 2.5 seconds or less | Hero image size, sliders, web fonts, hosting |
| Interaction to Next Paint (INP) | How quickly the page responds to taps | 200 milliseconds or less | Heavy page builders, chat widgets, many scripts |
| Cumulative Layout Shift (CLS) | How much the layout jumps while loading | 0.1 or less | Images without dimensions, late banners, font swaps |
They are assessed at the 75th percentile of visits, separately for mobile and desktop, so a page passes only when most visitors get a good experience, not just the developer on office Wi-Fi. An autoplay video background, a five-slide carousel and three decorative fonts each look fine in a mock-up and each cost loading time.
Every element on the first screen should earn its loading time.
Agree a budget at the start: one compressed hero image and no slider; at most two font families, ideally one that covers Arabic and English well; and every third-party script, from chat to tracking pixels, justified. Speed also affects whether people stay, as we explain in why website speed drives sales.

9. Images that are light, sized and described
- Format and size. Export photos in a modern format such as WebP, at the size they are displayed. A 4,000-pixel phone photo shown at 800 pixels still downloads in full.
- Dimensions in the code. A set width and height reserve the image's space while loading, which keeps CLS low.
- Lazy-loading below the fold only. Google recommends lazy-loading to save bandwidth, but the main image at the top should load at once, or it delays LCP.
- Alt text and placement. The Starter Guide asks for short, descriptive alt text and for images placed near related text. A project photo beside its description says more than 40 unlabelled images in a separate gallery.
- Descriptive file names.
riyadh-office-fit-out.webpbeatsIMG_4471.jpg.
Decisions 10 to 12: crawlability, duplicate URLs and indexing controls
10. JavaScript that does not hide content or links
Google can process JavaScript. Its documentation describes three phases, crawling, rendering and indexing, with a headless Chrome running the scripts before the rendered page is indexed. But there are limits:
- Google can only discover links that are standard
<a>elements with anhref. A project card that opens a page only through a click handler is a dead end for crawlers. - Single-page apps should use real URLs through the History API, not hash fragments such as
/#/services. - Server-side rendering or pre-rendering is still recommended, because not every bot runs JavaScript.
A standard WordPress site sends complete HTML from the server, so these issues rarely arise unless a heavy plugin or custom front end changes that. Custom-built sites and AI site builders deserve a closer look; we compare platforms in WordPress or custom code.
11. One URL for each piece of content
The same page can often be reached with and without www, over http and https, or with ad tracking parameters. Google's Starter Guide says duplicate content is not a spam violation, but it can waste crawling and confuse which version appears. Ideally each piece of content has one URL, with a redirect or a rel="canonical" tag pointing to it; otherwise Google chooses for you.
The build decisions are small but permanent: pick one host name, force https, redirect the other variants and output a canonical tag on every page. Watch blog archives too: tag, category, author and date pages can create several near-identical lists of the same five articles.
12. Sitemaps, robots rules and the staging trap
An XML sitemap lists the pages you want found, and Search Console is where you submit it and see how Google reads your site. The sitemap should contain only real, indexable pages: no thank-you pages, test pages or empty tag archives.
The costliest mistake here is also the simplest. During the build, designers rightly block search engines from the preview, for example with WordPress's "Discourage search engines" option or a noindex tag. If nobody removes it at launch, the finished site stays invisible. Google adds that when it finds noindex in the original page code it may skip rendering, so a script that removes the tag later will not reliably help. Our website launch checklist puts this check on launch day.
Check: after launch, run your home page and one service page through Search Console's URL Inspection tool. If either is excluded by noindex, fix that first.
Decisions 13 to 15: structured data, bilingual sites and redesigns
13. Structured data that describes what visitors can see
Structured data labels the facts on a page in a format search engines understand: business name, address, opening hours, or an article's author and date. It can make a page eligible for richer search results, though it does not guarantee them. Google recommends JSON-LD where possible and asks site owners not to mark up information users cannot see.
For a typical business site the useful set is short: business details on the home or contact page, breadcrumbs on inner pages and article markup on posts. The design decision is to make sure the facts are on the page. If the address and hours only appear inside an image or an embedded map, there is nothing visible to mark up. Keep name, address and phone in plain text, identical to your Google Business Profile.
14. Bilingual sites: separate URLs and correct hreflang
Many Saudi businesses need Arabic and English, and the first rule is that each language needs its own URL. A switcher that swaps text on the same address with a cookie or script leaves Google one version to index. A common, clean pattern is Arabic at the root and English under /en/, which is how webnaa.com is organised. The versions are then connected with hreflang annotations, and Google's documentation sets rules that are easy to get wrong:
- Each language version must list itself as well as all other versions.
- The links must be reciprocal; if the Arabic page does not point back to the English one, the tags are ignored.
- Alternate URLs must be full addresses, including
https://. - Codes start with an ISO 639-1 language, such as
aroren, optionally followed by a region, as inar-SA. A country code alone is invalid. - An optional
x-defaultmarks the page shown when no language matches. - Tags can go in the HTML head, HTTP headers or the sitemap; Google treats the three as equivalent, so use one consistently.
Google also says it does not use hreflang or the lang attribute to detect a page's language; it reads the content. An "English" page with Arabic menus and footer sends mixed signals. And the switcher should link each page to its direct counterpart, so a visitor on an Arabic service page who taps "English" lands on the same service. Planning details, including right-to-left layouts, are in our bilingual website design guide.
15. Redirects when you redesign or move
A redesign is when a site is most likely to lose its visibility. New page names, a new structure or a new domain mean the URLs Google knows, and other sites link to, start returning errors. Google's site-move guidance gives a clear sequence:
- Map every old URL to its new equivalent before launch.
- Use permanent server-side redirects, such as 301 or 308.
- Send each old URL straight to its final destination and avoid redirect chains.
- Do not redirect many old pages to one unrelated page such as the home page; Google may treat that as a soft 404.
- Update internal links to point at the new URLs directly.
- Submit a sitemap of new URLs in Search Console, plus a Change of Address if the domain changes.
- Keep redirects in place generally for at least a year.
Google warns that rankings may fluctuate temporarily during a move and that a medium-sized site can take a few weeks or more to settle. A lasting drop usually points to missing redirects. See our website redesign checklist; our website redesign service is quoted in writing once we have seen your current site.
SEO-friendly web design checklist: questions for your designer
You do not need to read code to hold a designer to these standards. Use the questions when you compare proposals, and the steps when you review the preview link.
Questions to ask before you sign
- Will each main service have its own page, built from a template I can reuse?
- Can I edit the title and meta description of every page, post and project?
- How will you keep the home page within the Core Web Vitals targets on a mid-range phone?
- Does the mobile version contain the same content as the desktop version?
- How are the Arabic and English versions connected, and where does the language switcher send visitors?
- Who sets up Search Console and the sitemap, and in whose account?
- If this replaces an existing site, who prepares the redirect map?
- What do you promise about rankings? The honest answer is that nobody can promise positions on Google.
How to review the preview yourself
Read the addresses
Click every menu item and look at the URL bar. Each page should have a short, readable address of its own.
Use only your phone
Browse the preview on mobile data. Note any page that feels slow, jumps while loading or hides content the desktop version shows.
Switch languages on an inner page
Open an Arabic service page, tap the switcher and confirm you land on the same service in English.
Try to select the text
Long-press the headline and key sentences. If you cannot select them, they are part of an image, and search engines cannot read them either.
Common mistakes to avoid
The headline is a picture
A banner with the offer and phone number inside the image looks sharp and says nothing to Google.
All services on one page
One page competing for every search ranks well for none.
English as an afterthought
Machine-translated pages, Arabic menus, no hreflang and a switcher that always returns to the home page.
A redesign without a redirect map
Years of links pointing at pages that no longer exist. This is the hardest mistake to undo.
For problems outside SEO that also cost enquiries, see mistakes that cost customers.
How Webnaa builds SEO into every website
Webnaa is a website design service based in Riyadh that builds professional WordPress websites for businesses across Saudi Arabia. The decisions above are part of how we build, not an extra. Our website design service starts from SAR 39 a month, and a two-language WordPress website of 5 pages includes:
- A fast, mobile-friendly site with readable URLs, and 5 pages, so your main services each get a clear page.
- Each page in Arabic and English, with content written for you.
- Search engine setup and connection to Google, including Search Console and the sitemap.
- Hosting, SSL and a standard domain in your name, with a preview link before launch.
- Technical support, fixing technical faults, security updates and backups included in the subscription; you edit the site yourself from the dashboard.
Prices start from SAR 39 a month and that WordPress website is SAR 324 a month, with no setup fee and no long contract, paid every 6 months or with 10% off when you pay for a year upfront; from the second year you pay the monthly base only. We send the preview link within 24 hours at most from receiving all the information and content we need from you, and a money-back guarantee applies if you do not like the design during the design stage, per the refund policy. Work out the price for your own pages and languages in our price calculator. For ongoing work such as keyword research, content plans or audits, our separate SEO service is priced in a written quote first. We will not promise you a position on Google, because nobody honestly can.
Choose what you need, see your exact price
The price updates with every choice. No surprises, no hidden fees.
The calculator is off. Press the power button to start
Where will your website live: on a Webnaa address, or on a domain in your business name?
Who edits your website after launch? On static we edit it for you; on WordPress you edit it yourself from a dashboard.
How many languages will your visitors read?
How many pages does your business need? If you are not sure, five pages suit most businesses.
A subscription paid every 6 months or yearly that keeps your website with us, or buy the website in one payment and own it.
From Zoho, a global provider with data centres in Riyadh and Jeddah. More than 10 addresses are quoted separately.
A website built to be found
See what the website design service includes, from clean URLs to Search Console setup, then tell us about your business.
Running WordPress? The plugin-level setup for Arabic and English sites is in our WordPress SEO Saudi Arabia guide.
FAQ
What is SEO-friendly web design?
Building a website so search engines can crawl, understand and fairly evaluate it: readable URLs, crawlable navigation, one page per topic, fast mobile pages, connected language versions and safe redirects. It does not replace good content or reviews, but it stops the build from holding them back.
Does website design affect SEO?
Yes. Design decides whether text is real text or an image, whether menus are crawlable links, how fast pages load on a phone and whether the mobile version holds all the content.
Is WordPress good for SEO?
It is a sound base: it sends full HTML from the server, supports readable URLs and has mature tools for titles and sitemaps. Results still depend on the theme, plugins, hosting and content.
Should a bilingual Arabic and English site use one URL or two?
Two. Each language version should have its own URL, connected to its counterpart with reciprocal hreflang tags.
Will a redesign hurt my Google rankings?
It does not have to. Map every old URL to a new one, use permanent 301 or 308 redirects, update internal links and submit the new sitemap. Some temporary fluctuation is normal.
Can a web designer guarantee first page on Google?
No. Rankings depend on competition, content, reputation and Google's own systems. Treat any guarantee of positions as a warning sign.
Summary
SEO-friendly web design is a set of build decisions that are cheap to get right at the start and expensive to fix later: readable URLs, crawlable navigation, one page per service, clear headings and editable titles, a complete mobile version within the Core Web Vitals targets, light images, clean JavaScript, one URL per page, no leftover noindex tags, honest structured data, connected Arabic and English versions, and a redirect map for every redesign. Ask about each before you sign, check them on the preview, and let content and reputation do the rest.
Sources: Google Search Central: SEO Starter Guide, Google Search Central: JavaScript SEO basics, Google Search Central: localized versions of your pages, Google Search Central: site moves with URL changes, web.dev: Web Vitals. Webnaa: pricing, SEO service.