Give every material customer decision its own research record. Give it a new page only when a customer needs a distinct answer and the company has enough evidence to maintain that answer. A request for a mobile bicycle mechanic, a request for workshop directions and a request for a bike fitting might all involve the same company. They call for different checks. Some can be answered in separate sections of one page. Others may need a different destination because the customer is choosing a different service or taking a different action.
The practical deliverable is a map from customer questions to evidence and public destinations. It should show which questions can share an answer, where a qualifier changes the outcome, and who confirms that each answer is still true. Start with the services you sell today and the claims a buyer needs to decide between them.
Disclosure. AI Visibility is published by Lunasol, which offers GEO and AEO services. The bicycle example uses public sources. The facilities company and its decision map are fictional. No client files or live assistant runs were used. About AI Visibility
Separate the research question from the publication decision
Begin by listing real actions a customer could take. They might book a visit, compare service packages, ask if their site is covered or send specifications for a quote. Record what the customer needs to know to make that choice. This is different from listing everything the company could sell or collecting every phrase that might describe it. Several variations of a question can depend on exactly the same answer.
For example, a customer asking whether a mechanic will come to an apartment and one asking whether a mechanic can work at an office may be checking the same mobile service. If the company has different access requirements for each kind of property, capture those conditions in the research. A single page can present both conditions if the service and booking path are shared. If a third customer needs to bring a bicycle to a workshop, a street address and visiting instructions are now relevant evidence. Map that question to a place where the visitor can get those details.
Separate variants by the thing that changes. It could be fulfilment, eligibility, geography, a service commitment or the next action. The answer could also vary by buyer. A facilities manager may need a site survey and procurement documents where a household buyer can book a visit. Confirm those differences with the relevant service owners. A marketing team can group questions confidently only after it understands which distinctions operations actually uses.
The existing AI Visibility audit guide describes the broader evidence and fix list a business can expect from an audit. The measurement guide discusses commercially relevant questions. A multi-service team can use those guides after deciding which service decisions belong together and what page should answer them. This map is useful even before there is a formal tracking programme. AI Visibility audit guide · Why UAE businesses should measure AI search visibility
Read the handoff as carefully as the service name
Vélo Presto provides a public example of why a service label alone can be insufficient. Its homepage describes mobile bicycle servicing in Dubai and Abu Dhabi, identifies online booking as a Dubai option and asks customers to call or use WhatsApp for Abu Dhabi services. The same site gives an Umm Al Sheif workshop address on its contact page. A reader asking whether the company serves Abu Dhabi and one asking whether it has an Abu Dhabi workshop are checking different facts. The public pages establish the described service and the published Dubai address. They provide no basis here for giving an Abu Dhabi workshop address. Vélo Presto homepage · Vélo Presto contact page
The business also published an Instagram post on 26 February 2026 describing its mobile vans and its Umm Al Sheif workshop. That is useful historical context for the two ways customers may encounter the company. Use the current website or a business confirmation for the appointment process. If the team later changes one emirate's booking route, an editor should be able to identify the relevant pages without changing the workshop directions. Official Vélo Presto Instagram post
A useful exercise is to write a short answer to each question using only the sources available to a customer. Note where you needed a different page or where a qualifier was essential. For a mobile visit you may need the area, service type and appointment route. For a workshop visit you need the address and any relevant drop-off instructions. For a bike fitting you need the business's description of the service and the fitting appointment route. One provider can support these decisions with overlapping company facts and separate service evidence. This public reading is an illustration of mapping. It did not test fulfilment or visibility in an assistant.
Build a decision map for the site you already have
Start with a small number of services that staff recognise, then write the question in the customer's language. Record the answer and the precise scope where it applies. Add the current public destination, the intended next action and an owner who can confirm the underlying fact. Where the answer is unknown, assign a research action. That keeps a missing operations decision from turning into an invented statement on a website.
Consider a fictional UAE facilities company offering scheduled maintenance, emergency callouts and commercial maintenance agreements. It uses one enquiry desk, but that desk triages requests differently. The table shows how an editor could decide where to place information after confirming the relevant policies. Proposed pages and route names below are illustrative.
| Customer decision | Evidence needed | Preferred destination | Editorial action |
|---|---|---|---|
| Can I request routine maintenance for a flat in my area? | Confirmed household scope, coverage and enquiry process | Scheduled maintenance page | Add a coverage section if the existing page can answer it |
| Can somebody assess an urgent leak at my site tonight? | Operations-approved coverage window, triage process and exceptions | Emergency callouts page | Give the emergency process its own page if the distinct service and evidence exist |
| Can my business request a maintenance agreement for several sites? | Supported site types, survey process and quote inputs | Commercial agreements page | Explain what procurement needs to submit and what happens next |
| Where should I send a question that spans several services? | Verified desk ownership and escalation route | Services overview or contact page | Use one shared explanation and link from the service pages |
| Is scheduled maintenance available in a second city with the same terms? | Confirmed area coverage and any difference in fulfilment | Scheduled maintenance coverage section | Extend the existing section if the answer and action are shared |
The public page is one column in the map. Teams can keep separate rows for the two city questions even if both answers live on one page. That preserves evidence for each area and gives a future reviewer a specific fact to check. It also means you can revise the map if the second city develops its own schedule or team. If one company fact appears everywhere, record a single authoritative internal source and identify the places that display it. A customer-facing page can then present the relevant portion without maintaining a separate policy for every service.
Decide when a new page earns its own place
Try answering the question in the best existing page first. A heading or short comparison can work where people already arrive in the right context. An overview can explain when to choose among several services. A specific service page should explain how the selected service works and what to do next. A separate page earns its place when the reader has a materially different decision and the team can provide enough service-specific detail to resolve it.
Use a side-by-side brief to test proposed pages. Describe the audience, conditions, evidence, decision and action for each. If swapping two service names would leave both briefs usable, investigate whether the existing page can answer the questions together. If a proposed page needs a different appointment process, clear exclusions and a separate accountable team, it may have enough to stand alone. A shared contact number can still serve both pages if each one prepares the reader to make a different request.
Google's spam policies describe doorway abuse, including examples of pages targeted at similar queries or regions that funnel visitors to a single destination without giving them a useful intermediate answer. Google's canonical guidance separately deals with duplicate or very similar URLs. Treat these as distinct checks. If the problem is that two planned pages have the same purpose and little unique value, fix the briefs and site structure first. If the problem is that multiple URLs expose the same piece of content, review the technical signals with the site owner. A canonical preference helps indicate the representative URL for similar content, and Google may choose a different one. Google Search spam policies · Google guidance on consolidating duplicate URLs
Review existing pages before deciding to merge anything. One may contain a customer instruction the other lacks. Check whether it is still accurate, whether any links or campaigns depend on the URL and where the surviving answer belongs. Agree on the replacement content before changing links or routes. Keep a short record of which claims moved and what the editor verified after release. This helps the service owner identify anything that was dropped during consolidation.
Share the company facts and verify the service conditions separately
Build a small set of shared facts such as the company identity, its general contact route and any policy genuinely common across services. Then keep the details that vary by service with their own owners. The customer support lead may confirm the shared enquiry number. The emergency duty manager confirms response windows. The commercial lead confirms the inputs for a survey. Reusing a contact detail saves maintenance, while reusing the emergency response policy across the wrong service can create a promise nobody can meet.
Geography deserves explicit wording. A company may have a branch in one emirate, visit customers in another and sell a third service remotely. A map of branches answers a different question from a map of service areas. Use the location that matters to the customer decision. If staff can verify fulfilment by district but the company publishes a broader area description, preserve the more precise evidence internally and publish only the level the business can support and maintain.
Do the same for language. If a customer asks the same question in Arabic and English, test whether the two answers carry the same conditions and action. A language variant may need its own publication workflow, and the underlying policy should still come from the same owner. If the company provides a different contact route by language, record that difference explicitly and check that each destination matches the promise. A translation can be accurate sentence by sentence while a button leads to the wrong team.
Review the map with two customer paths
Pick two paths that would reveal a wrong assumption. For the fictional facilities company, start as a household customer checking routine maintenance in the second city. Then start as a commercial buyer seeking an agreement for several sites. Read the destination for each, look for the qualifying detail and follow the next step far enough to verify that it matches the team's process. Record which fact or handoff failed if either path is unclear. Fix that issue in the existing destination if it can carry the answer.
If the company later measures assistant answers, keep observations tied to the decision that prompted them. A mention in an answer about household maintenance supplies no evidence that the company was recommended for a commercial agreement. An answer may name the right company but describe the wrong service or next step. The decision map tells the reviewer which specific facts to check. Date the observation and keep the prompt and surface with it so a colleague can interpret the result.
Bring the service owners together to agree what to keep, revise, combine or create. For every new page, require a defined customer decision, a confirmed answer and a named owner. For every combined page, check that each distinct research question still has a place in the finished answer. You can cover more of the company's real work while keeping the number of pages within the team's ability to maintain them.



