Skip to content

Join the Seedly owners community →

Help Center

Smart Locations

Bind a section to one of a site's locations, let a grid render every location as a service-area block, and list the cities each location serves.

Last updated

A site's locations live in Settings. Smart Locations is how a page uses them without you retyping an address into every section.

Three pieces:

  1. Bind a section to a location so everything inside it fills from that location.
  2. Location tokens that fall back sensibly when nothing is bound.
  3. A locations grid that renders every location as a service-area block.

Binding a Section to a Location#

Select a section, open its settings, and choose a location. Every {{location.*}} token inside that section now resolves to that location.

This is what makes a per-location page practical. Build one "Visit us" section, bind it, and the address, phone, hours link, and map all follow the binding rather than being typed in.

What an Unbound Token Does#

A {{location.phone}} that is not inside a bound section still resolves. It looks for, in order:

  1. The location the section is bound to
  2. The location the page is set to
  3. Your primary location

So a single-location business never has to think about binding at all: every location token resolves to the one location. A multi-location site binds only the sections that need to differ.

To name one location no matter the context, address it by position: {{location.1.phone}} is always the primary, {{location.2.phone}} always the second. See Merge Tokens.

A Grid That Lists Your Locations#

Give a grid the locations source and it renders one entry per location on the site. Add a location in Settings and it appears; retire one and it goes. The service-area section maintains itself instead of drifting out of date the first time a client opens a new branch.

This is the block to reach for on a "Areas we serve" or "Our locations" page.

Service Cities#

Each location has a Service Cities field: the towns and suburbs that location covers.

Fill it in and the service-area blocks can list real coverage rather than a single city name. For a trade business whose one address serves twenty surrounding towns, this is the difference between a page that says where the office is and a page that says where they will actually come out to.

A Practical Setup#

For a two-location business:

  1. Add both locations in Settings, primary first, and fill in Service Cities for each.
  2. On the home page, leave contact sections unbound. They resolve to the primary.
  3. Give each location its own page, set the page's location, and leave the sections on it unbound. They follow the page.
  4. On the "Areas we serve" page, use a grid with the locations source.
  5. In the footer, use {{location.1.phone}} so the primary number is pinned everywhere regardless of which page a visitor is on.
Was this page helpful?