When a spreadsheet is the right source
Google Sheets works well when several people need to maintain locations and the data is simple enough to review in rows. Keep the sheet focused on publishable location data, and use a separate tab for internal notes or change requests.
Design the sheet for predictable updates
Use a stable header row, one location per row and consistent values for categories. Keep column names clear and avoid renaming them after the first sync. A stable location ID helps you understand whether a row is a new location or an edit.
- Name the sheet and tab clearly
- Keep addresses in separate fields when the workflow benefits from it
- Use one value format for hours and phone numbers
- Remove blank rows and test rows before syncing
- Limit edit access to people responsible for location data
Connect and review
After connecting the sheet, review the first sync rather than assuming every row is ready. Check geocoding, duplicates, filters and public fields. The Google Sheets sync documentation covers the current connection and sync workflow.
Protect the visitor experience
A spreadsheet change can affect a live locator quickly. Keep a review step for address changes, closures and new categories. If a sync fails, fix the source data and confirm the result list before communicating that the update is live.
Know when to use CSV instead
CSV is often simpler for a one-time migration or a controlled batch update. Use the CSV import guide when the file needs a deliberate review before it changes the public locator.