No public thread from a Dubai or Abu Dhabi agency describes this exact loop yet. The working shape below comes from how agencies elsewhere already talk about the deliverable. Label those sources as outside the UAE when you reuse them with a client.
One location, not the brand roll-up
Write the client's location into the scope before you run anything. The city goes in every prompt. The engines you will ask are listed by name. The dates of the baseline run are on the first page.
If you manage two branches for the same brand, they are two reports. A note from one Dubai neighbourhood does not cover another, and an Abu Dhabi location is not covered by a Dubai run.
Incomplete answers are not the same as "not named." If an engine refused the question, returned an empty list, or never searched when the check needed a search, log that row as unusable. In a May 2026 thread on agency AI reporting, one commenter argued for a data-quality row: "we weren't mentioned" and "the check didn't return a usable answer" need different treatment. That thread was not about Dubai. The split still belongs on the first page of the report.
What goes in the findings
For each prompt, keep four fields. Whether the client's location was named, not named, or the answer was unusable. Every other business named, in order. Any citation or source link the answer showed. The engine and the date.
Do not blend those rows into one "AI score." In a June 2026 AMA on delivering AI search visibility for clients, an agency operator wrote that they never trust one blended visibility number and split results by engine. Weak and zero-visibility prompts were the roadmap. That AMA was not a UAE case study, and it is not a retainer pitch for this article. Keep the per-engine split and the gap list.
Another working pattern is a short fixed set the client can reproduce. In September 2026 on r/aeo, one reply said to pick five questions a real customer would type, keep them unchanged, ask ChatGPT and Claude separately, and tell the client "2 out of 5 this week, 1 last week," nothing out of 100. The client can sit next to you, type the same question, and see the same kind of answer. That is what stops arguments about screenshots nobody can replay.
Some agencies still paste ChatGPT or Gemini screenshots into monthly decks to show a brand appeared. That habit showed up in the same agency reporting thread. Screenshots are fine as evidence next to a row. They are not the report by themselves.
When you measure for a client, track the prompts themselves: whether the brand appears, who shows up instead, and which sources get cited. That three-part row is what practitioners asked for when clients ranked on Google but barely appeared in ChatGPT answers. Use it as the findings table, not as a ranking claim about Dubai.
Actions the client owns
Each finding that needs work becomes one row the client can act on. What you observed. The answer or source that supports it. The proposed fix. Who on the client's side owns it. When it will be reviewed.
The same agency-reporting thread put it as one decision per finding: observation, supporting answer or source, proposed action, owner, and review date. The agency does not need to execute every fix to make the report useful. Getting onto a cited page, correcting hours on the location page, or publishing a service page the prompts keep missing are client-side moves. Naming who owns each one stops the report from becoming a list of suggestions with no return date.
Do not claim in the report that a later mention proves the strategy worked. In May 2026 on r/DigitalMarketing, one post argued that when a client eventually gets cited, agencies sometimes claim the strategy worked after the fact. That is not a repeatable process. The recheck is the only honest link between the fix and the next result.
Recheck the same set
After the client ships the fixes on the agreed dates, run the same prompts on the same engines in new chats. Report what moved: named where it was absent, still absent, or still unusable. Keep the second run next to the baseline. Two runs are still two runs, not a rate for the year.
The AMA above described the useful close of the loop as watching the number move after the work ships. Keep that idea. Drop any talk of juniors, retainers, or topic percentages.
One location's recheck does not cover a second branch. If the client has another address, that address needs its own baseline and its own recheck.
Put the owner checks inside the report, don't rebuild them
The engine-specific methods already live on whereon. Point to them once inside the report pack; do not paste those articles into the client PDF.
- How to check if ChatGPT names your restaurant in Dubai or Abu Dhabi
- What to fix when ChatGPT describes your Dubai or Abu Dhabi beach club wrong
- How to check which pages Perplexity cites for your hotel in Dubai or Abu Dhabi
- How to check if Claude names your salon in Dubai or Abu Dhabi
Adapt the prompts to the client's category and neighbourhood. Keep the rule those pieces share: guest wording without the brand name when you are testing whether the location is offered, city in the sentence, and a separate note per city.
A longer measurement pass across many prompts is a different deliverable: how to measure AI visibility for a local business. This report is the short pack one location can act on this month.
Whereon runs the same kind of prompt set for a location and keeps the other names and the sources. The agency version above is the part you can hand a client without inventing a score.