A customer opens the Jumeirah location page and sees the correct address. Behind the page, its structured data still contains the Al Quoz telephone number and Saturday hours. The template was copied from the first branch and the visible text was updated separately. The markup has a valid shape. It describes the wrong shop.
When you maintain several locations, compare the structured data with the public facts for each branch and check that the branch identities stay distinct across pages. AI Visibility’s Article markup checklist applies this principle to published articles. This walkthrough applies it to location templates, where a single copied value can send someone across town or to a closed door. AI Visibility Article structured data checklist
Give each physical branch a record
Start with the location list used by the operations team. Give each customer-facing branch an internal key that survives copy edits and temporary closures. Record the approved display name, branch page, street and unit, phone route, hours, exceptions and the staff member who can confirm a change. Add the group name and relationship separately. A shared brand is useful for navigation, while a visitor still needs a specific branch to call or visit.
Choose the closest accurate subtype of LocalBusiness for the branch. Schema.org describes LocalBusiness as a particular physical business or branch. Google’s documentation similarly describes a location-level item, with a more specific supported subtype where applicable. A shop and a clinic within the same group may require different descriptions. If a location has several functions, check what customers can actually do there and consult the documented treatment of departments before creating additional entities. Schema.org LocalBusiness · Google LocalBusiness structured data
| Branch field | Where to confirm it | What to check across pages |
|---|---|---|
| Identifier | Location record and canonical branch route | Each distinct branch has a distinct identifier |
| Name and page URL | Approved public name and branch page | Both identify the branch the visitor selected |
| Postal address | Branch owner and visible address | Unit, building and district belong together |
| Telephone | Branch owner and published contact route | Local number or labelled shared number matches the page |
| Regular and exception hours | Current branch schedule and notices | Days, midnight crossings and date limits are correct |
A stable public identifier can use a branch URL with a fragment such as #branch. Use the same identifier wherever the website refers to that branch, including translated pages when both describe the same location. Use the group’s separate identifier when the node refers to the larger organization. Schema.org’s branchOf property can express the relationship where it is accurate. Keep that relationship in the record even when the branch has its own phone, hours and services. Schema.org branchOf
If a business relocates, ask whether customers will continue to recognise it as the same branch and decide how the website should handle the old route. Update the destination, address and instructions together. An old address may need a notice or a redirect depending on what a person reaching that page expects to find. When one branch closes and a different one opens, have operations confirm the two statuses independently. A nearby new store can be suggested to readers without reusing the closed branch’s facts or identifier.
Compare the location page with the public locator
Start by opening the branch detail page directly, then find the same branch through the locator. Match the name, building, phone and operating window. A locator can also show nearby branches in the same district. Inspect the heading and card boundaries before pulling data from the page. A comparison that grabs the first address or telephone number on screen can accidentally pick a neighbouring location, a support line or the office shown in the footer.
DESCO’s Dubai Marina branch page illustrates the scope problem. Its main location block identifies a unit in Marina Diamond 1 and lists an operating window that extends past midnight on Monday through Saturday. The same page shows a nearby Jumeirah Beach Residence branch under a separate heading with a 24-hour label. DESCO’s location directory also lists the branches separately. A reviewer should preserve those boundaries when assigning facts to markup. The observations concern published pages and do not establish whether either shop was open when checked. DESCO Dubai Marina branch · DESCO location directory
A footer phone number shared by the group can still serve a purpose. If it is the supported route for a branch, identify it as central support on the branch page and confirm where it leads. Where the branch has a direct number, compare the visible digits and the link destination. For a map pin, confirm that it resolves to the branch entrance or the appropriate site. A shopping centre’s general pin can be too imprecise for a reader collecting an order from a specific unit.
DESCO’s official Instagram Reel about finishing services is an example of a different scope. It promotes the company’s capabilities across branches. That caption can help a reader recognise the publisher and the advertised service. Assign hours, branch availability and other operating details from the applicable location’s approved record. Official DESCO Instagram Reel
Keep regular hours and exceptions together
Use a schedule that records days and times in local branch time. If the branch opens on Saturday evening and closes early on Sunday, identify Saturday as the starting day of that interval. Google’s LocalBusiness documentation models hours that cross midnight as one specification with the opening day and both times. Test this case independently from an ordinary daytime interval. In a fixture, it is easy for a formatter that sorts times to swap them or for a validation rule to reject a closing time earlier on the clock. Google LocalBusiness hours examples
Keep date-limited changes separate from the usual schedule. If only two shops change hours for a holiday, attach the change to those branch records and include the relevant dates. Schema.org defines a property for special hours, and Google documents date-bounded examples for its implementation. Review the exact pattern supported by the destination where the hours will appear. Once the period ends, inspect both the visible notice and emitted markup to see whether the regular hours have resumed. Schema.org special opening hours · Google LocalBusiness hours examples
Avoid treating the opening window as a promise about every service. A print shop may close later than its collection desk, or a service may need an appointment. Make the service conditions clear in the branch copy. When the same schedule powers a booking calendar and a location page, ask the owner to clarify which window each system uses. That prevents the team from treating a normal branch-hours update as a change to order cutoffs.
Test the same template with two different branches
On 6 November 2026, a local fixture test compared two fictional branch pages. Each page contained visible name, address, telephone and Saturday hours plus a JSON-LD block. The simulated copy error left the Jumeirah page with the Al Quoz identifier, street address, phone and hours in JSON-LD. The visible Jumeirah details stayed correct. The checker parsed both pages, tested selected property domains and nested types against a captured Schema.org graph, and compared each branch’s structured facts with the text and the identifiers seen across the pair.
The incorrect fixture produced four findings on the Jumeirah page. The address, phone and hours differed from the visible text, and the branch identifier duplicated the Al Quoz identifier. After updating the structured values and using a separate branch identifier, the checker returned zero findings. The vocabulary checks alone accepted both fixtures. Comparing visible values and identifiers was what caught the copy error. Schema.org vocabulary distribution
The corrected Jumeirah markup contains this Saturday interval. It is a fictional sample covering one day.
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "https://schema.org/Saturday",
"opens": "10:00",
"closes": "01:00"
}
In the full fixture this object sits inside openingHoursSpecification on a Store node. The Store also has a location page URL, branch identifier, phone, address and reference to the larger organization. For a live release, validate the complete rendered node. The local test checks a bounded set of fields and does not emulate Google’s rich results checks, select a canonical page or determine whether the search system will display any of the values. Use the example to reproduce the branch mix-up before running platform checks.
For a useful regression test, choose two locations whose data cannot accidentally match. If both have the same opening hours, a template that copies one schedule to the other may appear to pass. Use a second branch with a different closing day or a later closing time. Keep the rendered HTML used for the comparison. If a component later emits a second node, inspect the new output and confirm the checker sees every relevant node before relying on a green result.
Sign off the location records before publishing
Use a Branch markup record with the branch key, visible page, current JSON-LD identifier, checked facts, exception dates and approver. If a difference appears, determine whether the location record, page copy or markup template is stale. Correct the authoritative value first, then regenerate the affected outputs and compare the pages again. If the location directory and branch page use different sources, record who owns each source and what change should keep them aligned.
Review Google Business Profile separately. Its rules for storefronts, service-area businesses and individual locations determine what belongs in a profile. The website markup can describe a branch accurately without establishing profile eligibility. Compare the website’s approved location data with the corresponding profile where you have access. Keep profile updates, website updates and any actual search appearance in separate columns of the release record. Google Business Profile representation guidelines
After release, open a changed branch and a neighbouring unchanged branch in a fresh browser. Check the visible hours and address, the rendered JSON-LD and the locator card. If the release involved a holiday, replay the check when the date passes. A team can then tell whether the change reached the intended pages and whether the exception expired on schedule.
Build the first release sample around the changes customers are most likely to notice. Check one store with overnight hours, one store with a date-limited exception and one that shares its name with a nearby branch. Compare at least one corresponding location in each supported language. A template can read the correct branch key in one locale and silently fall back to the first branch in another.
For ongoing changes, have the location manager send the branch key and the effective date with each correction. If a phone change goes live today and revised hours start next week, give them separate checks. A reviewer should be able to see which facts are effective now, which are scheduled and who approved each one. Save the before and after examples with the change record so another editor can reproduce the comparison.
AI Visibility is published by Lunasol, which offers GEO and AEO services. The public example used DESCO’s published branch information and the technical comparison used local fictional pages. About AI Visibility



