Selling the same product in Egypt, Saudi Arabia, and the UAE raises three different questions: What language does the page use? Which market is it designed for? In what currency can the customer complete the purchase? hreflang helps search engines understand the relationship between language or regional versions. It does not change currency, translate content, or guarantee that Google will show a particular version to a particular user.
Keep language and regional targeting separate from price and inventory. You may need an Egyptian Arabic version and a Saudi Arabic version, and perhaps an English version for each market. Currency needs to match across the product page, offer data, and checkout.
Decide whether localized versions are genuinely needed
Map URLs before writing annotations. For each product and category page, record its language, intended country, currency, price, inventory, shipping, returns policy, and final URL. A possible planning structure:
| Market and language | Example hreflang value | Illustrative URL | What should distinguish the version |
|---|---|---|---|
| Egypt, Arabic | ar-EG |
/eg-ar/ |
EGP, delivery and returns in Egypt, relevant product details |
| Saudi Arabia, Arabic | ar-SA |
/sa-ar/ |
SAR, Saudi shipping options, taxes, and policies |
| UAE, Arabic | ar-AE |
/ae-ar/ |
AED, availability and delivery choices for the UAE |
| Saudi Arabia, English, if offered | en-SA |
/sa-en/ |
English content intended for customers in Saudi Arabia |
These are structural examples, not a recommendation to change existing URLs. Do not create separate versions if the content, product, and service are identical and users have no actual need for them. Do not change a published URL just to insert a country code. A URL change requires a redirect and measurement plan; it is not necessary for this method.
Google recommends using distinct URLs for language versions instead of relying on cookies or browser settings that change the same page. Google systems use visible page content to determine language; lang or hreflang alone does not translate a page. Managing multi-regional and multilingual sites.
When hreflang is useful
Use it when alternate pages are available in the same or different languages and are clearly intended for different users. Google identifies fully translated pages as a relevant case, as well as small, intentional regional variations in the same language. If the main content remains untranslated and only the template differs, Google may treat those pages as duplicates.
Each version should reference itself and the other alternates, and the annotations should be reciprocal. Use complete URLs, including https://, and supported language-region codes. The first part is a language such as ar or en; the optional second part is a region such as EG, SA, or AE. Do not use a country code without a language. An x-default URL can point to a market or language selector when there is no single targeted version for everyone. Google: Localized versions of your pages.
Do not treat hreflang as a user-facing redirect or a currency switch. Provide visible language and market choices so people and crawlers can reach the alternatives. Avoid location-based redirects that prevent access to other versions; Google notes that locale-adaptive pages may not all be crawled or indexed.
Treat currency as product and checkout data
hreflang does not set priceCurrency. For Google's product results, the documented guidance recommends a separate URL for each currency when the same product is sold in multiple currencies. Merchant Center has separate multi-country targeting and currency-conversion options, but its landing-page and checkout requirements still apply: the product data, visible page, and purchase path must be consistent for the chosen setup. Do not assume a product-feed conversion changes your organic product-page currency. Google Search Central: Multiple currencies in product results · Merchant Center: Multi-country product targeting · Landing page requirements.
Match price and currency among the page, structured data, Merchant Center feed, and checkout. Use the correct ISO currency codes such as EGP, SAR, and AED in priceCurrency; do not display an amount in one currency while submitting another. Changing only the currency symbol in the interface is not enough if the price or shipping charges still come from a different market. Check taxes, discounts, availability, and returns for the destination.
If the store theme or platform does not create a separate URL for each market or currency, verify the platform’s supported behavior before creating URL parameters or extra versions yourself. Google: Merchant listings and product structured data · Ecommerce URL structure.
Check four signals before publishing a new version
Visible content: Open the URL in a private session and verify that its language, price, and intended market are visible before user interaction. Do not rely on IP-based or automatic redirects that prevent crawlers or customers from reaching other versions; provide a market or language selector.
hreflang: Check the supported codes, self-reference, and reciprocal links among every alternate. Confirm that URLs return HTTP 200 instead of redirecting or opening an error page.
Canonical: Decide how the versions relate. Local pages with genuinely different prices, stock, or shipping may need to remain distinct. Duplicate URLs created by tracking parameters may need a stable canonical. Do not use canonical to erase a real market difference before reviewing the page and its purpose.
Product data: Compare name, offers.price, priceCurrency, and availability with the page and checkout, then validate structured data on the final page. Do not mark up a rating, offer, or availability that is not real.
Monitor language and region after launch
Use Search Console to inspect URL samples from each market, the version Google selected when the data is available, and indexing or redirect issues. Review queries and pages by country and device, but do not blame a click difference on hreflang alone; demand, price, stock, and competition may also change.
Keep an auditable map connecting each page with its market, alternates, currency, and inventory update owner. When a product is added or its price changes, update the feed and page from a shared product source, then test each version before rolling out the change.
Official Google references
- Localized page versions and hreflang.
- Managing multilingual and multi-regional sites.
- Merchant listings and product structured data.
- Ecommerce URL structure.
These guidelines help clarify page variants and product data to search engines; they do not guarantee that every page will be indexed or shown to a particular user.
Short-video script: language is not currency
Length: 50 seconds. Visual: Show a page map, then switch between Egypt, Saudi Arabia, and the UAE versions.
Hook: “Selling in three countries? hreflang will not turn pounds into riyals.”
Scene 1: “Give each genuine local version a URL with the right language, market, shipping, and policy.”
Scene 2: “Connect the alternates with reciprocal hreflang links; each page should reference itself and the others.”
Scene 3: “Match the currency and price in the page, structured data, and checkout.”
Close: “Check the URLs and product data before expanding. The tag alone is no ranking guarantee.”
Educational carousel: map three markets
- Cover: Egypt, Saudi Arabia, UAE: language, market, or currency?
- Language describes page content;
aris not a country code. - Market describes the intended audience:
ar-EG,ar-SA, orar-AE. - Currency must match in product data, page, and checkout:
EGP,SAR, orAED. - Every alternate page links to itself and the other alternates.
- Do not create a URL only to add a country code; confirm the need first.
- Takeaway:
hreflangdescribes the relationship between versions; it does not translate or set the price.
Field experiment thread: test an alternate product-page group
This is a controlled implementation checklist, not a promise of search performance.
1/ Select a small group of products sold in more than one market. Record the source-of-truth product ID, each intended language-region, currency, and final URL.
2/ Confirm that each version differs where the customer needs it to: availability, price, shipping, returns, language, or local instructions. Do not publish a copy just to multiply URLs.
3/ Add complete alternate URLs and verify self-reference and reciprocal hreflang connections across the group.
4/ Open each URL in a normal and cookie-free session. Confirm the correct language and market are visible and that no redirect blocks another version.
5/ Check product structured data and feed data against the page and checkout for every currency.
6/ Test internal links and sitemap entries, then monitor a representative sample in Search Console over a suitable period.
7/ Fix confirmed conflicts before expanding the group. Indexing one URL does not prove the rest of the group is indexed.
Tool-neutral prompt pack: audit market versions
Alternate map
From this table [URLs, language, country, price, currency], map every alternate page. Flag unsupported codes, missing reciprocal links, and different currencies without separate URLs. Do not recommend changing an existing URL without a redirect and operational approval plan.
Product data match
Compare price, currency, and availability in the HTML, Product structured data, Merchant Center feed, and checkout capture below [data]. Show discrepancies only. Do not assume which source is correct until the commerce owner confirms it.
hreflang check
Validate this group [HTML or sitemap] for self-reference, reciprocal alternate links, valid URLs, language and region codes, and the
x-defaultdestination. Show evidence for each issue and leave uncertain items for human review.
Stop-doing swipe file: stop confusing hreflang and currency
- Stop: “Add
EGalone as hreflang and we targeted Egypt.” Use: Specify language first and region second, such asar-EG, and make the page appropriate to that audience. - Stop: “hreflang will show Egyptians the price in pounds.” Use: Manage market and currency in the URL, page, and commerce data; hreflang describes alternate versions to search engines.
- Stop: “Copying a page and swapping the country name will rank in more markets.” Use: Create a local version only when a real user or operational difference warrants it, then make it useful and test the signals.
- Stop: Redirecting everyone by IP so they cannot reach other versions. Use: Provide visible language and market choices and make each intended URL accessible.
Hook–Value–Template: connect the page to the right market
Hook: “Your product pages show three currencies? Map the URLs before adding tags.”
Value: “Separate language and region from price, create accessible alternate versions, and connect the pages with reciprocal hreflang annotations.”
Template: “URL [address]; language [ar/en]; market [EG/SA/AE]; currency [ISO]; alternates [list]; self-reference [yes/no]; reciprocal links [yes/no]; checkout price [matches/does not match].”
Example: “The ar-SA page shows a SAR price, its Offer data uses SAR, and the page links to its ar-EG and ar-AE alternates with reciprocal references.”