Start with one row per location
A good import file is easy to review. Give every location a stable name and include the address, country, phone number, website, opening hours and the products or services visitors need to filter. Keep one location per row and avoid putting several addresses in one cell.
Review the file before it goes live
Do not treat a successful upload as proof that every row is useful. Check the import preview for missing addresses, duplicate rows, invalid coordinates and fields that did not map to a destination. Fix the source file when possible so the next update stays clean.
- Use a header row with clear column names
- Keep phone numbers and postal codes as text so leading zeroes survive
- Use a consistent format for opening and closing times
- Give each row a stable identifier if the file will be updated later
- Resolve duplicate and incomplete rows before publishing
Map columns to locator fields
Map the columns that visitors will see first, then map search and filter fields. A product or service column can become a filter. A notes column can become supporting content on the result card. Keep internal notes out of public fields.
Test the visitor journey
After importing, search for a town near several locations, apply each important filter and open a result. Check the address, hours, phone link, website link and directions action on a phone. The CSV import guide shows the current Handled workflow and review states.
Keep updates predictable
Save the reviewed file as the source of truth and record who owns changes. If a location closes, archive or remove it deliberately instead of leaving an old row that still appears in search. For ongoing spreadsheet updates, use Google Sheets sync when it fits your workflow.