SEO Site Structure for a Small Business in the UAE

A small business site needs one page for every service, product and location a customer searches for. Group those pages under a few hubs and link them so that each one is at most two clicks from the home page. Build that list from what you sell before anyone opens a design tool, and the menu, the URLs and the sitemap follow from it.

Start with an offer list

Open a spreadsheet with three columns: what you sell, where you serve, and what buyers ask before they pay. Fill it in with your own words first, then with the words customers use in WhatsApp and on calls. If you are commissioning a website, hand this sheet to the developer before the design brief.

Hypothetical example: a dental clinic in Jumeirah.

Sells: implants, clear aligners, whitening, children's dentistry, emergency visits.
Serves: a Jumeirah branch and an Umm Suqeim branch, each with its own parking and hours.
Gets asked: how long aligners take, whether insurance covers implants, whether there is a dentist on Friday.

Any row that people type into Google is a candidate for its own page. A row nobody searches for becomes a paragraph or an FAQ item on a broader page.

Search demand also splits by intent, and intent decides the page type. In OpenSEO data (October 2026, UAE), "website development company in dubai" gets about 1,600 searches a month and "website development cost in dubai" about 90. The first person is choosing a supplier and needs a service page. The second wants numbers and needs a price guide. A small query can still be worth a page: "local seo dubai" shows about 170 searches a month with a cost per click of $43 in the same dataset, so advertisers pay a lot for each of those visitors.

The page types a small business needs

Most small sites in the UAE need five types of page. Each has one job and one place in the tree.

Page type	Its job	Example URL	Links to
Home	Says who you are, what you sell and where, in the first screen	`/`	Every hub
Hub	Lists one group of services or products with a short line on each	`/services/`	Every child page, the contact page
Service or item page	Answers "can you do this for me, how, for how much, where"	`/services/clear-aligners/`	Its hub, 2 to 3 related guides, contact
Guide	Answers one pre-purchase question in full	`/guides/aligner-treatment-time/`	The matching service page, 2 sibling guides
Contact or booking	Takes the request with as little friction as possible	`/contact/`	Nothing that pulls the visitor away

Add case pages, an about page and legal pages as needed. They sit outside the main sales path and link back into it.

URLs that mirror the tree

A URL should tell a person where they are before the page loads. Keep URLs lowercase, use words in the page's language, separate words with hyphens, and leave out dates and IDs.

The Lucent Rental site I built for a supercar rental in Dubai follows one pattern: /car/<model>/ for a car, /brand/<brand>/ for a brand, /rent/<brand>/<location>/ for a brand in a given area, and a /ru/ branch for the Russian version. Once you know the pattern, you can predict the address of any page in it.

Decide the pattern once. If you rename /services/ to /treatments/ after launch, every old address needs a permanent 301 redirect, every internal link needs updating, and you wait for Google to recrawl.

How three sites I built are organised

The same logic works at different sizes.

Moon Mars (case) sells shisha outsourcing to venues in Dubai, Abu Dhabi and Doha. The site has four service sections (outsourcing, catering, consulting, technology), city pages for Abu Dhabi and Doha, a catalogue of 133 shisha lounges, 33 articles in each language, case pages and a PDF one-pager. It runs in English and Russian, 128 pages in the build. In the first month of the site, 10 restaurants in a narrow segment got in touch. Within that month, organic search (the site plus Google listings) brought direct requests for meetings and consulting.

Lucent Rental (case) is built around the fleet. The database holds 61 cars, 18 of them marked available, and the site has page templates for cars, brands and brand by area. Eight guides in English and Russian cover rental questions. The client has not connected the site to a public domain yet, so there is no traffic data to report. I describe it here for its structure only.

Lucent Legal (case), a law firm for Russian speakers in the UAE, sits at the other extreme. It has 213 guides in Russian and 213 in English, 426 guide pages in total, against 10 service pages in Russian. The sitemap lists 448 URLs. Guides answer the questions people search before they talk to a lawyer, and service pages take the request. Each layer has a clear job, which is why the ratio can be that lopsided.

Location pages: when they help

A location page earns its place when something on it differs from the other location pages. That can be a branch address, delivery zones, travel time, local prices or stock. Moon Mars has city pages for Abu Dhabi and Doha because the business operates in those cities.

The common mistake is 40 pages titled "Dentist in [Area]" with identical text and the area name swapped. Google's spam policies describe this as doorway abuse. Before you add an area page, ask yourself one question: what would a customer from this area learn here that the main service page does not tell them? If the answer is "nothing", skip the page and list the areas on the service page instead.

The same test applies to combination pages like brand plus location. A combination page holds up when it shows different content, such as the cars available for delivery to that area. If it shows the same list as the brand page, it adds crawl load and no value.

Guides and where they point

A guide answers one question well enough that the reader does not need to go back to Google. It should end with a link to the service page that solves the problem, plus two or three links to guides on neighbouring questions.

Group guides by topic under the same hub as the related service. "Aligner treatment time" and "aligners vs braces" both belong near /services/clear-aligners/. When the guides on a topic link to each other and to one service page, search engines see a cluster with a clear centre.

Write the answer in the first two sentences of each guide. Those sentences are the ones Google and AI assistants tend to quote. There is more on that in writing articles that AI cites.

Internal links: the path to a request

Every page should connect to a way of contacting you within one scroll. The Savage Media study of 537 Dubai restaurant and venue websites found that 76 of the 409 fully analysed sites (18.6%) used the word "book" with no online booking and no WhatsApp. Only 139 of 409 (34.0%) had a WhatsApp button. On those sites the visitor reaches the end of a page ready to act and has nowhere to click.

Four rules cover most small sites:

Every page is reachable in two clicks from the home page.
Breadcrumbs on service pages and guides show the hub above them.
No orphan pages: each page has at least one link from another page, beyond the sitemap.
Each page has one main action, such as a WhatsApp, booking or call button, with the same wording across the site.

To see which pages bring requests after launch, tag the contact buttons per page. The setup is in tracking SEO leads from WhatsApp.

Files and markup that machines read

Search engines and AI crawlers read the structure through a few files and tags. Check each one at launch.

sitemap.xml lists every page you want indexed, and only those. Submit it in Google Search Console.
robots.txt blocks admin areas, internal search results and test folders, and points to the sitemap.
llms.txt gives AI tools a short map of the site: what you sell, the main pages, the facts. Moon Mars and Lucent Rental both have one. The format is covered in llms.txt: what it is and how to write one.
Schema markup labels the business type, address, hours and services. In the same study, only 90 of 409 sites (22.0%) used Restaurant schema, and 22.7% had no meta description at all.

Content locked inside files counts as structure too. The study found 147 of 409 venues (35.9%) published their menu only as a PDF, against 130 (31.8%) with a menu as a web page. A menu web page can rank for a dish name and carry a booking button next to it, while a PDF opens in a viewer with no route back to booking.

Languages: one tree per language

If you serve customers in English, Arabic and Russian, give each language its own branch, such as /ru/ and /ar/, with the same tree inside. Each page links to its counterparts through hreflang tags. In the study, 82 of 409 sites (20.0%) had an Arabic version, 50 (12.2%) had a Russian one, and 38 (9.3%) had all three.

Keep the trees parallel, but write each language for its own reader. A Russian-speaking customer in Dubai may search for different services than an English-speaking one, so a page can exist in one language and not in another. The common tagging errors are in hreflang mistakes on RU/EN/AR sites.

What not to do

Put five services on one "Services" page. It cannot rank for any of them, and the visitor scrolls past four to find theirs.
Clone area pages. Identical text with a new area name is doorway abuse under Google's rules.
Hide content in PDFs, images or Instagram embeds. Menus, price lists and service details need to be text on the page.
Let the design decide the pages. A menu with six slots does not mean the business has six things to say.
Change URLs without redirects. Every old link and every saved bookmark breaks.
Publish guides that link nowhere. A guide without a link to a service page answers the question and lets the reader leave.
Split one topic across near-duplicate pages. "Teeth whitening" and "tooth whitening Dubai" on two URLs compete with each other.
Index thin pages. Tag archives, empty category pages and internal search results belong in robots.txt or behind a noindex tag.

Checklist

Offer list in a spreadsheet: services, areas, buyer questions.
Each row checked for search demand and marked as page, section or FAQ.
Page types assigned: home, hubs, service pages, guides, contact.
URL pattern agreed in writing before design.
Area pages only where content differs.
Every guide links to one service page and two sibling guides.
Every page has one main contact action, tagged for tracking.
Nothing more than two clicks from the home page, and no orphans.
sitemap.xml, robots.txt, llms.txt and schema in place and checked.
Menus and price lists published as web pages.
Language branches parallel, hreflang tags paired both ways.
Sitemap submitted in Search Console. After four weeks, open the Pages report and look at which URLs are excluded from the index and why.

Questions and answers

How many pages does a small business website need for SEO?

As many as you have distinct things people search for: each service, each product line, each area you serve in a different way, and each pre-purchase question. As a hypothetical example, a clinic with six services and two branches might need 15 to 25 pages before any articles. Page count follows the offer list.

Should every Dubai area get its own page?

Only areas where something differs: a branch, a delivery zone, travel time, prices or available stock. Pages that repeat the same text with a new area name are what Google's spam policies call doorway abuse, and they weaken the whole site.

Can I change the structure after launch?

Yes, but every changed URL needs a permanent 301 redirect from the old address, and the sitemap and internal links must be updated. It is cheaper to agree on the page tree and URL pattern before design starts.

Does site structure help with ChatGPT and other AI assistants?

AI assistants read the same public pages search engines do, so a clear page per service with facts on it is easier for them to quote. Nobody can guarantee that an assistant will recommend a business.