What actually ranks for a location search
Someone searching for a brand plus a town, or a product plus near me, sees two kinds of result: the map pack, which is built from Google Business Profiles, and ordinary web results, which are pages. A store locator widget is neither. It is the tool a visitor uses once they reach your site.
So the SEO work splits in two. The profile work is done in Google Business Profile, one listing per real location. The page work is done on your website: something indexable for each location or each city, linked from the rest of the site, marked up so a search engine can read the address and hours without guessing.
| Search surface | What feeds it | Where you do the work |
|---|---|---|
| Map pack and Maps | Google Business Profile listings | Google Business Profile, per location |
| Web results for brand plus town | Indexable location or city pages | Your website |
| Rich results and AI answers | Structured data on those pages | JSON-LD in each page |
| Your own locations page | The locator, plus crawlable text and links | Your website |
Crawlable store lists versus JavaScript-only maps
Google's JavaScript SEO documentation describes three phases: crawling, rendering and indexing. Pages are queued for rendering, a headless Chromium executes the JavaScript when resources allow, and the rendered HTML is then parsed for links and indexed. That queue can take seconds or longer, and nothing guarantees every interaction a visitor might make will be rendered. A locator that shows nothing until someone types a postcode shows a crawler nothing at all.
Google's link guidelines add the second constraint: it can follow a link only when it is an anchor element with an href attribute. A click handler on a card, or a map marker, is not a link to a crawler.
The practical rule: the page the locator sits on should stand on its own without the widget. Give it a heading that says what it is, a paragraph about your locations, and plain links to your location or city pages. Then the widget adds search and a map for people, and the page still makes sense to a machine.
Location pages: one URL per place
A location page is a normal web page for one location: its name, full address, phone, hours, what it offers, directions, and something specific to that place. It ranks because it is the most specific answer to a specific search. Google's Business Profile guidelines also ask for a website that represents your individual business location, and a location page is exactly that URL.
Thin pages hurt. Fifty pages that differ only by the town name are near-duplicates, and search engines treat them that way. If you cannot write something specific for each location, publish city pages instead: one per town, listing the locations there, with a paragraph that is true of that town.
- Pick the URL shape and keep it: /locations/houston/heights or /stores/austin.
- Give each page a unique title and intro: the location's name, town and what it is known for.
- Show the address, phone and hours as text, not only on a map image.
- Add LocalBusiness JSON-LD (next section) with the same facts.
- Link each page from a locations index page, and the index from your footer.
- Set each Google Business Profile's website field to that location's page.
LocalBusiness and Store JSON-LD
Google's LocalBusiness documentation lists address as the required property, asks you to use the most specific LocalBusiness subtype you can, and shows opening hours as OpeningHoursSpecification. For a shop, the subtype is Store or one of Store's more specific types on schema.org, such as BikeStore, FurnitureStore or GroceryStore. A restaurant is Restaurant, a clinic MedicalClinic, and so on.
Put one JSON-LD block in each location page, describing that location only. Do not put a list of every location's markup on the locator page: the visitor cannot see those details there, and structured data should describe what the page shows.
| Property | What to put | Google's status |
|---|---|---|
| @type | Store, a Store subtype, or another LocalBusiness subtype | Use the most specific type |
| name | The location's name as customers know it | Recommended |
| address | A PostalAddress: street, locality, region, postal code, country | Required |
| geo | GeoCoordinates with latitude and longitude | Recommended |
| telephone | The location's own number, with country code | Recommended |
| openingHoursSpecification | Days with opens and closes times | Recommended |
| url | This location page's own URL | Recommended |
The Google Business Profile tie-in
Your profiles and your pages should agree. Same name, same address format, same phone, same hours. Google's guidelines ask for a phone number that connects to the individual location and a website that represents it. When a profile links to the location's own page rather than your home page, the two reinforce each other: the profile sends visitors to the most relevant page, and the page confirms the profile's facts.
Hours are where they drift. Whoever changes a location's hours should change them in one place that feeds both, or change both on the same day.
Internal links that carry weight
A page a crawler reaches through your own links is found faster than one it reaches only through a sitemap, and the same links send real visitors.
- Link the locations index from the footer of every page.
- Link each location page from the index and from its city page, with the location's name as the link text.
- Link back from each location page to its city page and the index.
- Link related locations: other branches in the same town.
- Use real anchor tags. A link that only exists inside the locator widget's JavaScript is not a link to a crawler.
What Handled does for each, and what it does not
This is a vendor's guide, so here is the vendor's own position in the same terms. Handled is an embedded locator. It is good at the visitor's search and at keeping the data current. It does not do the SEO publishing for you today.
| SEO job | Handled today |
|---|---|
| Location pages | Not offered. Handled does not generate pages; build them on your own CMS |
| LocalBusiness or Store JSON-LD | Not added to your page by the widget; add it to your own location pages |
| Crawlable store list | Not from the widget. Export the list or read it from the Query API and publish it as HTML |
| City pages | Supported as an embed: the snippet takes a starting place and a tag list, so a city page can open the locator on that city |
| Data for your pages | CSV and JSON export, the REST Location API, the Query API and signed webhooks when a location changes (API and webhooks on Pro and Business) |
| Google Business Profile | No sync. Keep hours consistent by updating both |
A setup that works with any locator
If you use Handled, or any embedded locator, this arrangement gives you the search experience and the SEO surface together.
- Keep the locations in one source: the locator's dashboard or a synced Google Sheet.
- Publish a locations index page with crawlable text and links to each city or location page.
- Build the city or location pages on your CMS. On each, embed the locator scoped to that place, and add the JSON-LD.
- When a location changes, update the source; a webhook or the API tells your CMS to refresh the matching page.
- Point each Google Business Profile at its page.
- Review in Search Console which location pages are indexed, and fix the thin ones first.
Sources
Google Search Central: Local business structured data, JavaScript SEO basics and Make your links crawlable. Google Business Profile Help: Guidelines for representing your business. Schema.org: Store. All read on 15 November 2026.
Frequently asked questions
Does a store locator help SEO?
Directly, very little. The map and results are drawn by JavaScript after the page loads. Location pages, structured data, Google Business Profiles and internal links do the SEO work; the locator serves visitors once they arrive.
Should I use LocalBusiness or Store schema?
The most specific type that fits. Store is a subtype of LocalBusiness for retail, and schema.org lists more specific Store types such as BikeStore or GroceryStore. Google's documentation asks for the most specific subtype.
Can Google crawl a JavaScript store locator?
Google renders JavaScript in a separate queue and follows only real anchor links. Results that appear after a search are not reliably indexed. Put the locations in crawlable HTML on location or city pages.
Does Handled Locator create location pages?
No. Handled is an embedded locator and does not generate pages today. Its export, API and per-page embeds feed pages you build on your own site.
How many location pages should I create?
One per location if you can write something specific for each; otherwise one per city. Near-duplicate pages that only swap the town name are thin content.