CSV import
Move the spreadsheet in without losing the problem rows.
Upload the location file you already maintain, map its columns and review the rows that need attention before applying anything. Addresses are geocoded and failures return with a reason instead of disappearing.
7-day trial · No card required · Every working self-serve feature included
What this changes for the visitor and the team.
- 01
Keep the spreadsheet shape you already use.
Map your headings to Handled fields instead of renaming every source column before the first upload.
- 02
See what will not import and why.
Review missing address information, coordinate problems and duplicate candidates before the ready rows are applied.
- 03
Check the public result after the data operation.
Verify a representative location, category, timezone and map pin in the real widget rather than treating a successful upload as the finish line.
Workflow
From configuration to a checked public result.
- 1
Export a UTF-8 CSV with one location per row and stable, consistently named columns.
- 2
Map the columns and review every warning, duplicate and address that could not be geocoded.
- 3
Import the ready rows, then spot-check location details, categories, hours and coordinates in the widget.
Included capability
- Column mapping for existing spreadsheet headings
- Address geocoding during import
- Duplicate detection before apply
- Per-row status and failure reasons
- Category and custom-field values
- CSV export for corrections and portability
The boundary
A CSV import is a reviewed batch operation, not a live connection to the source file. Use Google Sheets synchronization when one spreadsheet should remain connected, and correct ambiguous addresses before relying on their coordinates.
Continue with the task documentation.
Try the feature against your own location list.
Start with representative data, test the real visitor journey and keep the locator only if it handles the job your website needs.