Skip to main content

SEO, Indexing, and Location Pages

How search engines interact with your store locator widget, and how to make individual location pages indexable.

Updated yesterday

The StoreRocket widget is a JavaScript-based embed, which means search engines (Google, Bing) handle it differently from regular HTML content. Here's what you need to know.

Can search engines see my store locator?

The standard embedded widget loads via JavaScript, which means search engine crawlers typically don't index the content inside it. The map, location list, and search functionality aren't visible to Google's crawler in most cases.

If SEO is important for your store locator, StoreRocket offers individual location pages with unique, crawlable URLs. These are server-rendered HTML pages that search engines can index.

Location pages with slugs

Each location can have a unique URL slug (like /locations/new-york-store). These pages are crawlable by search engines and contain structured data that helps with local SEO.

To enable slugs for your locations:

  1. Go to Slugs in your dashboard

  2. Generate slugs for your locations

  3. Each location will get a unique URL

Nofollow / noindex for location pages

If you DON'T want location pages indexed by search engines, you can control this through your website's robots.txt or meta tags. StoreRocket's hosted location pages follow standard HTML conventions for crawl directives.

Making your store locator content SEO-friendly

For the best SEO results:

  1. Create a dedicated page on your website for the store locator (like /locations or /store-finder)

  2. Add descriptive text above and below the widget embed explaining what visitors will find

  3. Use proper heading tags (h1, h2) on the page

  4. Include your key locations in regular HTML text on the page for crawlers

Canonical tags

If you're seeing duplicate content issues with location pages, check the canonical tags. Each location page should have a unique canonical URL pointing to itself. If you're experiencing indexing issues with slugged URLs, reach out on live chat and we'll check the canonical configuration.

Questions? Hit us up on live chat.

Did this answer your question?