From a branch list to markup
Prepare the CSV
Required columns: name, street, town, postcode. Optional: phone, email, url, lat, lng, hours, map_url, image, region, id. Common header variations such as
city,post codeorlatitudeare recognised.Paste it or open the file
Use Open a CSV file for an export from your spreadsheet or booking system.
Pick the business type
Choose from 23 schema.org types, from
StoreandRestauranttoDentist,PlumberandAccountingService. UseLocalBusinessif none fits.Add the brand
With a brand name and main website, an Organization entry is created and every branch points to it as its parent organisation.
Choose the output and fix the warnings
One @graph block suits a locations page listing every branch. One block per location page gives a separate script for each branch's own page.
Example: two optician branches, one with swapped coordinates
A two-branch opticians (fictional) exports its locations. The Chester postcode was typed in lower case and is tidied to CH1 1NQ. The Wrexham row has latitude and longitude the wrong way round, which would put it in the Indian Ocean; the generator warns but still writes the values, so fix the row before publishing.
name,street,town,postcode,phone,lat,lng,hours,url Brightside Opticians Chester,22 Bridge Street,Chester,ch1 1nq,01244 496000,53.1889,-2.8915,Mo-Fr 09:00-17:30; Sa 09:00-13:00,https://www.brightside.example/chester Brightside Opticians Wrexham,5 Hope Street,Wrexham,LL11 1BG,01978 496111,-2.9925,53.0466,Mo-Sa 09:00-17:00,https://www.brightside.example/wrexham Type: Optician. Brand: Brightside Opticians, https://www.brightside.example
Row 3: -2.9925, 53.0466 is outside the UK. Check that latitude and longitude are not swapped.
"@type": "Optician",
"@id": "https://www.brightside.example/chester#location",
"address": { ... "postalCode": "CH1 1NQ", "addressCountry": "GB" },
"openingHoursSpecification": [
{ "dayOfWeek": ["Monday", ... "Friday"], "opens": "09:00", "closes": "17:30" },
{ "dayOfWeek": ["Saturday"], "opens": "09:00", "closes": "13:00" }
],
"parentOrganization": { "@id": "https://www.brightside.example/#organisation" }Checks made on each row
| Problem | What you see |
|---|---|
| No name, street, town or postcode column | A warning to check the header row |
| Postcode not in a valid UK format | A warning naming the row; the value is kept as typed |
| URL without https:// | A warning naming the row |
| Coordinates outside the UK | A warning suggesting they may be swapped |
| Hours the tool cannot read | A warning with the expected form, Mo-Fr 09:00-17:30; Sa 10:00-14:00, and no hours in the markup |
| Two rows with the same @id | A warning, and a number added to keep them apart |
Why one block per branch page often works best
Search engines match LocalBusiness markup to the page it sits on. A branch page that carries its own block, with its own phone number, hours and address, is a clean signal that this page is about that location. The @graph option is best kept for a store finder that genuinely lists every branch on one page.
The address country is always set to GB, so the generator is meant for UK branches. Every branch also gets an @id built from its page URL, which keeps the entries distinct even when the names are similar.
Questions people ask
How do I add schema for a business with several locations?
Give each location its own page with its own address, phone and opening hours, then add a LocalBusiness block to each page that describes only that branch. Link every branch to one Organization for the brand with parentOrganization. This generator writes those blocks from a single spreadsheet of branches.
What format should opening hours be in?
Two-letter day codes and 24-hour times, with parts separated by semicolons: Mo-Fr 09:00-17:30; Sa 10:00-14:00. Day ranges and lists such as Mo,We,Fr are understood. Each part becomes an OpeningHoursSpecification entry. Rows with hours the tool cannot read get a warning and no hours.
Do I need latitude and longitude?
They are optional but useful, because they pin the branch precisely when an address could be ambiguous. Use decimal degrees, latitude first. The generator warns when a pair falls outside the UK, which usually means the two columns were swapped in the spreadsheet.
Can I use it for branches outside the UK?
Not as it stands. Postcodes are checked against the UK format and addressCountry is fixed to GB, so branches elsewhere would get warnings and the wrong country. For a single non-UK location, the general schema markup generator lets you write the address fields yourself.
Where your data goes
Your branch list is read and converted on this device, including any file you open. The addresses, phone numbers and coordinates are not uploaded or geocoded.
Checked against the tool on