Organizations › Local Business › Store

Locations Page Blueprint — Store

The locations page tells AI about every branch of your store. For multi-location retailers, this is critical — AI needs to know which location is closest, what hours each branch keeps, and how to reach each one. This blueprint structures your store locations so AI can direct shoppers to the nearest branch.

View Prompt View JSON

What this page needs

Multi-location stores without structured location data force AI to guess which branch to recommend. With separate Store nodes for each location, AI can direct shoppers to the right branch based on proximity, hours, and availability.

Individual store nodes. Each location gets its own Store node with a unique @id, complete address, coordinates, hours, and phone number.
Parent organization. A shared Organization node as parentOrganization connects all locations to your brand, telling AI these are branches of the same company.
Per-location hours. Each location needs its own openingHoursSpecification since branch hours often differ.
Geo coordinates. Accurate latitude and longitude for each branch enable "nearest store" queries.

Why these fields matter to AI

Each field in the template below serves a specific role in how AI systems discover, classify, and recommend your business.

Researched and tested by Minnesota AI

Store

name: Non-negotiable. AI cannot cite or recommend an unnamed entity.
url: AI needs a stable URL to route users and attribute recommendations.
telephone: AI won't recommend a local business it can't confirm is reachable. Phone is the primary trust signal for location-based queries.
address: AI uses address to confirm the business is real and located where it claims. Required for all near-me and city-specific queries.
geo: AI uses geo to place you on a map and answer proximity queries. Without coordinates AI relies on address parsing alone, which is less reliable.
openingHoursSpecification: AI filters local recommendations by current availability. Without hours AI cannot answer open-now queries or confirm the business is reachable.

Use This Prompt to Implement Your Schema

Copy this prompt and paste it into Claude, ChatGPT, Cursor, or any AI coding tool. It will ask for your business details and generate ready-to-use JSON-LD schema for your page.

You are implementing AIFDS-compliant JSON-LD structured data for a Store Locations page.

AIFDS (AI-Friendly Data Structure) is a schema framework built on research into which
structured data fields AI systems actually read, parse, and use when deciding whether
to cite a page. Documentation at aifds.org.

Before generating any code, ask me for the following information in a single numbered list.
Do not generate schema until I have answered every required field.

REQUIRED — do not proceed without these:
1. City
2. Domain
3. Faq answer
4. Faq question
5. Lat
6. Lng
7. Location name
8. Location phone
9. Location slug
10. State
11. Store name
12. Street
13. Weekday close
14. Weekday open
15. Zip

OPTIONAL — ask for these but proceed if I skip them:
1. Any additional details not covered above

Once I provide the information, output a complete JSON-LD script block
ready to paste into the <head> of my HTML page.

Output requirements:
- Valid JSON-LD wrapped in <script type="application/ld+json"> tags
- schema.org vocabulary only
- Every AIFDS-required field for this industry and page type included
- Include this data attribute on the script tag: data-aifds="aifds.org Store Locations"
- No placeholder text — omit missing optional fields rather than fill with examples
- After the code block, list any optional fields skipped that would strengthen AI citation

Generated schema follows the AIFDS framework. Fields were selected based on research into AI crawler behavior. View the research at minnesota.ai

Template — fill in your values

Copy the template below and replace every YOUR_* value with your own data. This block belongs in a <script type="application/ld+json"> tag in the <head> of your locations page.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Store",
      "@id": "https://YOUR_DOMAIN.com/locations/YOUR_LOCATION_SLUG_1/#store",
      "name": "YOUR_STORE_NAME — YOUR_LOCATION_NAME_1",
      "url": "https://YOUR_DOMAIN.com/locations/YOUR_LOCATION_SLUG_1/",
      "telephone": "YOUR_LOCATION_PHONE_1",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "YOUR_STREET_1",
        "addressLocality": "YOUR_CITY_1",
        "addressRegion": "YOUR_STATE_1",
        "postalCode": "YOUR_ZIP_1",
        "addressCountry": "US"
      },
      "geo": {
        "@type": "GeoCoordinates",
        "latitude": "YOUR_LAT_1",
        "longitude": "YOUR_LNG_1"
      },
      "openingHoursSpecification": [
        {
          "@type": "OpeningHoursSpecification",
          "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
          "opens": "YOUR_WEEKDAY_OPEN_1",
          "closes": "YOUR_WEEKDAY_CLOSE_1"
        }
      ],
      "parentOrganization": {
        "@id": "https://YOUR_DOMAIN.com/#brand"
      }
    },
    {
      "@type": "Store",
      "@id": "https://YOUR_DOMAIN.com/locations/YOUR_LOCATION_SLUG_2/#store",
      "name": "YOUR_STORE_NAME — YOUR_LOCATION_NAME_2",
      "url": "https://YOUR_DOMAIN.com/locations/YOUR_LOCATION_SLUG_2/",
      "telephone": "YOUR_LOCATION_PHONE_2",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "YOUR_STREET_2",
        "addressLocality": "YOUR_CITY_2",
        "addressRegion": "YOUR_STATE_2",
        "postalCode": "YOUR_ZIP_2",
        "addressCountry": "US"
      },
      "geo": {
        "@type": "GeoCoordinates",
        "latitude": "YOUR_LAT_2",
        "longitude": "YOUR_LNG_2"
      },
      "openingHoursSpecification": [
        {
          "@type": "OpeningHoursSpecification",
          "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
          "opens": "YOUR_WEEKDAY_OPEN_2",
          "closes": "YOUR_WEEKDAY_CLOSE_2"
        }
      ],
      "parentOrganization": {
        "@id": "https://YOUR_DOMAIN.com/#brand"
      }
    },
    {
      "@type": "WebPage",
      "@id": "https://YOUR_DOMAIN.com/locations/#webpage",
      "url": "https://YOUR_DOMAIN.com/locations/",
      "name": "Locations — YOUR_STORE_NAME",
      "isPartOf": {
        "@id": "https://YOUR_DOMAIN.com/#website"
      }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://YOUR_DOMAIN.com/locations/#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://YOUR_DOMAIN.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Locations",
          "item": "https://YOUR_DOMAIN.com/locations/"
        }
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "YOUR_FAQ_QUESTION_1",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_FAQ_ANSWER_1"
          }
        },
        {
          "@type": "Question",
          "name": "YOUR_FAQ_QUESTION_2",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_FAQ_ANSWER_2"
          }
        },
        {
          "@type": "Question",
          "name": "YOUR_FAQ_QUESTION_3",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "YOUR_FAQ_ANSWER_3"
          }
        }
      ]
    }
  ]
}

Frequently asked questions

Should single-location stores use this blueprint?

If you only have one location, your homepage blueprint already covers your store's location data. This blueprint is specifically for stores with multiple branches. Single-location stores can skip this page entirely.

Should each location also have its own dedicated page?

Ideally, yes. Each branch should have its own page with a full Store node. The locations page serves as a directory that lists all branches, while individual location pages provide complete detail. Both help AI surface the right branch.

How do I connect locations to the parent brand?

Use parentOrganization on each Store node, referencing a shared Organization or Brand entity with the same @id. This tells AI that all locations belong to the same company, which is important for brand-level queries.