Local search in a country without postcodes

Local search ranking depends heavily on consistency: the same business, the same name, the same address, the same phone number, everywhere it appears. In most countries the address format does much of that work, because a street number and a postcode leave little room for variation. In the Emirates there is far more room. A single office can be described by its tower, its community, its street, a nearby landmark, or a Makani number, and all of those descriptions are correct. Left unmanaged, a business ends up with a dozen versions of its own address in circulation.

Two inconsistencies do most of the damage here. The first is addressing: listings created at different times by different people describe the same office differently, and nothing in the format flags the mismatch. The second is transliteration. An Arabic business name can be rendered into Latin script in several reasonable ways, and once two spellings are in circulation they propagate, into directories, into review sites, into the way customers search. Neither problem announces itself. The symptom is a business that performs worse in Maps than its actual prominence suggests, with no obvious technical fault to point at.

The first deliverable is a single agreed record of your name, address and phone number, which sounds trivial and is usually the hardest part of a UAE local engagement. Getting there means deciding which transliteration is yours, which tower or community naming you will use, and which phone number is the one that appears publicly. Until that record exists, correcting listings is pointless. Each correction is a new opinion. Once it exists, the clean-up work becomes mechanical, and future listings stop adding variants.

The standard nine stages, discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement and continuous improvement, apply to every project. The paragraph above is what differs for this one.