Different website text for US and UAE buyers: options for brokerages
Short answer: For a brokerage selling to both US and UAE buyers, the safest setup is two real pages per market on separate web addresses, linked with hreflang tags (small page labels that tell Google which version is for which place), plus a visible region switch. Swapping text by the visitor's location on one address is fine for small things like a phone number or a currency hint. Ploy, an AI marketing platform that builds and hosts websites through chat, has a feature that does this using the visitor's location, but its own docs call location an estimate and say never to use it for legal wording.
You sell to people in two very different places, with different prices, different rules and different people answering the phone. Showing everyone the same page costs you leads, and showing the wrong legal wording can cost more.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The direct answer: give each market its own page, with its own offer, currency, legal text and form, and let the visitor choose the region with a visible link. Use location only as a helper, for example to suggest the region or show the right phone number, and always keep a default page that works for everyone else.
This is information, not legal advice. Rules change, so check the regulator's current page for each rule below.
This page may contain affiliate links from which Blur Studio earns commissions.
What really differs between a US buyer and a UAE buyer
Start with a list of what must change per market, not the tool. If only the currency changes, one page with a switch is enough. If the offer, the proof and the rules change, you need two pages.
| Item | US page | UAE page |
|---|---|---|
| Offer and price text | US listings, mortgage and tax wording, USD amounts if you invoice in USD | Dubai listings, off-plan or ready, payment plans, AED amounts if you invoice in AED |
| Currency | Show the currency you will actually charge | Show the currency you will actually charge; do not convert on the page |
| Property ad rules | Fair Housing Act wording for US listings | Trakheesi permit number for property ads (see below) |
| Privacy and consent text | State privacy laws, mostly opt-out (the visitor can say stop) | PDPL, the UAE data law, which centres on consent |
| Email and messaging rules | CAN-SPAM, the US marketing email law, with no exception for business email | Opt-in for marketing messages, telemarketing rules, Do Not Call Registry |
| Language | English | English, often with Arabic (a separate topic, see the bilingual page) |
| Who answers | US team, US hours | UAE team, local hours, often WhatsApp |
For Arabic and English pages in the UAE, read the bilingual website guide. For the permit side of Dubai property sites, read real estate brokerage websites in Dubai.
Five ways to build it, from least to most effort
| Option | How it works | Cost shown | Weak point |
|---|---|---|---|
| No tool: two separate pages linked from your menu | A US page and a UAE page, each with its own text, joined by a "Change region" link | $0 beyond your current site | You maintain both by hand |
| WordPress, a widely used site builder with plugins | Plugins can add language and region versions | Check the vendor page and each plugin's page | Plugin choice, speed and upkeep are yours |
| Webflow, a visual website builder | Build separate pages or use Localize, a paid add-on for translated versions (a locale is one language or region version) | Starter free, Basic $15 a month billed yearly ($25 billed monthly), Premium $25 a month billed yearly ($39 billed monthly); all USD (Webflow pricing page, as of November 2026). Localize is priced separately per locale and shown as a price for one locale: Essential $9 a month billed yearly ($12 monthly) with 10,000 words a month, and Advanced $29 a month billed yearly ($35 monthly) with 50,000 words a month and up to 10 locales | Check whether the add-on fits region-specific offers or only translation |
| Custom-coded site by a developer | Any logic you want, including routing and per-region data | Quote only | Every change needs a developer unless you add an editor |
| Ploy | Pages that read the visitor's location and change content, with region rows in a table | Free $0, Starter $50 a month, Pro $300 a month, Enterprise by quote (Ploy pricing page, as of November 2026); credits do not roll over | Location is an estimate; see the limits below |
The pattern: separate addresses, hreflang, and a region link
Google's guidance for sites that serve more than one language or region is consistent on four points:
- It recommends a different address (URL) for each version, rather than changing content with cookies or browser settings.
- It says to avoid automatically redirecting people from one language version to another, and to use visible links to the other versions instead.
- Pages that change content based on the visitor's perceived country might not be crawled, indexed or ranked for every place, because Googlebot, Google's crawler, often appears to come from the United States and sends no language preference. Google recommends separate locale addresses with hreflang.
- Local currency and language are among the signals of a site's intended audience, together with local addresses, phone numbers and links. They are signals, not switches, so changing the currency alone does not make Google show the page to one country.
Hreflang is a tag in the page header. It tells Google that two pages are the same content for different audiences. The rules from Google's page:
- Each page must list itself and every other version. If two pages do not point to each other, the tags are ignored.
- The language code comes first (two letters), then an optional region code. You cannot give a country code on its own, so do not write
hreflang="ae". x-defaultis the fallback for visitors who match none of your versions. It suits a page where people choose their region.
For a brokerage that writes in English for both markets, the labels follow the language-plus-region format. Google's page gives examples such as en-US and en-GB; en-AE follows the same format (AE is the UAE's country code), so test it in your own site tools after you publish. A simple set looks like this:
<link rel="alternate" hreflang="en-US" href="https://example.com/us/" />
<link rel="alternate" hreflang="en-AE" href="https://example.com/ae/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />
Put the same three lines on all three pages. The home page at / is a region chooser. Never send people to one region automatically based on where they appear to be. Show a clear "Change region" link on every page instead.
Do not make two near-identical pages
Google's spam policies name pages made for several regions or cities that all funnel users to one page, and "substantially similar pages", as doorway abuse. They also describe scaled content abuse as many pages made mainly to manipulate rankings, however they are made. Two pages that differ only by currency and a flag are not what a buyer needs and they put you near that line. Each market page should have its own listings, its own proof (past deals, local team, local process) and its own legal text. Where the content is the same, keep one page. See service-area landing pages that stay useful.
Where Ploy fits: personalize by visitor location
Ploy has a documented feature called Personalize by Visitor Location. Its docs (last updated 23 October 2026) describe it like this:
- Ploy passes location headers (small labels sent with each page request) with the visitor's country, state or region, and city, plus values such as postal code and time zone. Your site can change a headline, show local numbers, pick a currency or point to the nearest office.
- You ask Ploy's agent what to personalize, and it builds the page to read the headers. Content for each region can live in a PloyDB table, a spreadsheet-style table, with one row per region, so you update a region without a code change.
- Limits. It works on server-rendered pages and API routes (pages that return data to other software). A page built once at publish time (prerendered) cannot read the headers, so the page must be server-rendered. Headers are not sent to an existing site that Ploy forwards traffic to with a routing rule.
- Location is an estimate. It comes from the IP address, so a VPN, a company network, a mobile carrier or a privacy relay can show the wrong place. Ploy says never to use it for tax, legal eligibility or access control.
- Keep a default. A header can be missing, so every personalized section needs a version for unknown locations.
- Caching and search. Personalized pages should not sit in shared caches, and search crawlers see the version for their own location, often the United States, so keep the important search content on the default version.
- Privacy notice. If you save location with a form or in a table, describe it in your privacy notice.
What this means for you: use it for light local touches on a page, and use separate addresses for the two market pages. The docs do not describe Arabic or right-to-left layout support, live property feeds, or hreflang handling. Ask Ploy before you depend on any of them.
A note on visitor identification
Ploy also sells a visitor identification feature that tries to name the company behind a visit. Ploy says its net-new person-level identification is US only, so it does not apply to UAE visitors. Do not plan UAE lead capture around it. See Ploy visitor identification and outreach.
Lead routing and consent differences
The form behind each page should send leads to the right people with the right consent text.
- Add a hidden market field to each form (US or UAE) based on the page, not the visitor's guessed location. That field drives who gets the email and which CRM (customer database) pipeline the lead enters.
- Use region-specific consent text. The UAE data law (PDPL) is in force since 2 January 2022 according to the UAE government portal, requires consent that is specific, clear and unambiguous according to law-firm summaries, and has no "legitimate interests" basis. Its executive regulations were still not issued as of mid-2026 according to law-firm notes from June 2026 (one compliance vendor guide says otherwise, but no official or law-firm source backs that, so check the current position). Companies in the DIFC and ADGM free zones (Dubai and Abu Dhabi financial centres) have their own data laws. US privacy rules are mostly opt-out and vary by state; California requires that a user's global privacy control signal is honoured as an opt-out for sale or sharing. Ask your lawyer which applies to your brokerage.
- Separate marketing consent. Do not bundle it with "contact me about this property".
- Channel rules. In the US, CAN-SPAM covers marketing email, makes no exception for business-to-business email, and requires honouring an opt-out within 10 business days. In the UAE, marketing messages need opt-in under the telecom regulator's rules, telemarketing needs approval and calls fall between 9am and 6pm, and personal mobile numbers must not be used for marketing. The regulator's page says residents register on the Do Not Call Registry by SMS to 2211 or 1012. Check the regulator's current page.
- Routing by working hours. Set an auto-reply that says when a person will answer.
For the fuller UAE picture, see website data and marketing rules in the UAE, and for the US side, whether website visitor tracking is allowed under privacy law.
Property advertising rules that differ by market
UAE: Trakheesi permits and the website question
Dubai Land Department (DLD) and RERA, the real estate regulator, publish a Brokerage Practice Guide (second edition, issued November 2024). It says brokerages must obtain a permit for any real estate advertisement or marketing material through the Trakheesi system, which is the DLD permit portal, and that the permit number must be displayed on the ad. Its list of permit types includes electronic ads. DLD's permit service page shows AED 1,000 for most permits plus a AED 20 fee, and AED 5,000 for a project launch event permit. A separate DLD circular adds a QR code (Madmoun) for print and audiovisual ads.
The guide does not name websites or social media. Whether a permit number and QR code must appear on your own website is not spelled out in the guide. Ask RERA in writing, and keep the answer. See area and developer pages for Dubai brokerages for how to store permit number, expiry and sold status per listing. Off-plan marketing has more checks (registered project, escrow account, marketing contract with the developer).
US: fair housing wording
The US Fair Housing Act bars discriminatory statements in housing ads, and HUD's overview (HUD is the US housing department) names seven protected classes: race, color, religion, sex, national origin, familial status and disability. HUD issued guidance dated 29 April 2024 on advertising through digital platforms. After HUD withdrew some guidance documents in 2025, whether that document still stands is disputed, so check HUD's current page and do not describe it as current. The Act itself is unchanged. State and local rules can add protected classes.
Worked example (made-up numbers)
A Dubai brokerage with a US-based investor desk plans to show US buyers off-plan Dubai projects in USD terms and UAE residents the same projects in AED terms. These numbers are invented.
- Two pages for the same project:
/us/marina-tower/(price shown in USD with a note that the contract is in AED, the form says a US desk will call) and/ae/marina-tower/(price in AED, permit number shown, a WhatsApp link for the UAE team). - Each page lists both versions in hreflang, and each has its own consent text.
- The home page is a chooser with two buttons. Visitors from other countries see the chooser and pick.
- Leads: 30 form fills in a month, 18 tagged US and 12 tagged UAE. The market field routes each to the right team in minutes.
Test plan with pass and fail criteria
- Open each market page from a private browser window. Pass: it shows its own currency, text and form. Fail: mixed currency or shared legal text.
- Check that each page lists itself and the other version in hreflang. Pass: all three pages carry the same set. Fail: a missing return link.
- Use a VPN (a service that shows a different location) set to the UAE, then the US, and to a third country. Pass: the chooser or the default page appears, with no forced redirect. Fail: an automatic redirect, or a blank section.
- Submit a test form on each page. Pass: the right team gets it, tagged with the market.
- View the page source as a search crawler would, without location. Pass: the main content is there. Fail: content only appears after a location check.
Who should skip location-based text
- Anyone planning to switch legal wording by location. Ploy's own docs say not to use location for legal eligibility, and IP location is wrong often enough to matter.
- Teams that need Arabic and right-to-left layout or live property feeds from the same tool. Ploy's docs do not describe either; ask first.
How I'd approach this
I would split the problem in two. First, decide which items truly differ per market, using the table at the top, and write two pages only where they do. Second, add location as a helper at the end, not at the start. Put the pages on separate addresses, add the hreflang set and a region link, and test with a VPN. If your site is mostly pages and forms, Ploy is a reasonable place to try the location feature, with region rows in a table and a default for everyone else. If you need Arabic layout, live listing feeds or exact legal switching, pick a developer-built site or another tool. Blur Studio builds the custom version, including AI agents that use your business knowledge, CRM and calendar connections, finishing a half-built site and taking it live, and ongoing care; see what that includes.
First week. Day 1: list the items that differ per market. Day 2: write the two offers and the consent texts. Day 3: ask RERA in writing about your website and permit display, and ask your lawyer about consent wording. Day 4: build the two pages, the chooser and the hreflang set. Day 5: run the test plan. Decision rule: if the pages pass and the legal answers are in hand, go live with the pages; add location text only for phone numbers and currency hints after that.
A closely related page covers the same ground from another angle: A Page for a Big Property Owner or Developer Lead.
Related guide: Weekly Social Posts for Property Listings: Options and Costs.
I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.
Questions people ask
Can I show different content to US and UAE visitors on the same page?
You can, but Google's international guidance recommends separate web addresses with hreflang, and warns that pages that vary by location might not be crawled or ranked for every place. Use location text for small things and separate pages for the real offer. See the bilingual website guide for the same pattern with Arabic.
What hreflang codes should a Dubai brokerage use?
Language first, then region: en-US for the US page and en-AE for the UAE page, plus x-default for a chooser. A country code on its own is not valid. Each page must list itself and every other version, or Google ignores the tags. Check en-AE in your own site tools after you publish.
Should I redirect visitors to the right country automatically?
Google says to avoid automatic redirects based on language, and to use visible links to other versions instead. Location from an IP address is also an estimate that VPNs and company networks get wrong. Suggest the region with a banner, and let the visitor choose.
Can I show prices in both USD and AED?
Show the currency you actually charge, and keep any second figure labelled as an indication with the rate and date. Do not convert silently. Currency is one signal of audience for Google, not a switch.
Does a UAE property website need a Trakheesi permit number?
DLD's practice guide says permits are needed for any real estate ad or marketing material and lists electronic ads, but it does not name websites. Ask RERA in writing and keep the reply. See real estate brokerage websites in Dubai.
Does Ploy visitor identification work for UAE visitors?
No. Ploy says net-new person-level visitor identification is US only. Use consent forms and your own lead capture for UAE visitors.
Does Ploy support Arabic or right-to-left pages?
Ploy's docs do not describe Arabic or right-to-left support, so ask Ploy before you rely on it and test a sample page on desktop and mobile.
Is location-based text a legal compliance tool?
No. Ploy's docs say not to use location for tax, legal eligibility or access control. Show the legal text that matches the page the visitor chose, and check local law for each market. See website data and marketing rules in the UAE.
More in this topic: Websites: Dubai and property lead pages (5 guides) →
Sources
- Ploy docs: Personalize by Visitor Location
- Ploy pricing
- Google: localized versions and hreflang
- Google: managing multi-regional and multilingual sites
- Google: locale-adaptive pages
- Google: spam policies (doorway and scaled content abuse)
- DLD Brokerage Practice Guide 2024 (PDF)
- DLD real estate permit application
- UAE government portal: data protection laws
- California Attorney General: CCPA
- HUD: Fair Housing Act overview
- Webflow pricing