SGEN for multi-location business

In short. Running multiple branches, franchises, or storefronts on SGEN comes down to five steps: model each location as a data record, stand up a site per location, manage all of them from one dashboard, organize them in Site Manager, and tune local SEO for each address. That's the full shape — the numbered journey below threads the detail guides in order.

On this page: Is this you? · Why location records come first · The multi-location journey · Why local SEO is per-branch · Key concepts at a glance · Growing past the first few branches · Pricing, briefly

Is this you?

• Multiple physical locations — branches, franchises, clinics, stores — each needing its own web presence.
• Local search visibility per address, not just one generic site.
• One place to manage all of them — no re-logging-in per branch.

Why location records come first

The mistake that makes multi-location sites painful is treating each branch's address and hours as text you type onto a page. Do that across ten branches and you have ten copies of information that all have to be kept in sync by hand — and the day a branch changes its hours, you're hunting through pages trying to find every place the old hours were pasted.

SGEN's answer is to model each location as a data record rather than as page text. You add a branch once — its name, address, and hours live in one place — and the right information flows to the right pages and local listings from that single source. Change a branch's hours in its record and the change carries everywhere that branch's details appear. No copy-paste, no drift, no stale Saturday hours on a page you forgot about.

That's why the journey below puts modeling your locations before building pages. Set the single source of truth first, and every page you build afterward pulls correct, consistent details automatically. Build pages first and you're back to copy-paste maintenance forever.

The multi-location journey

Follow these steps in order the first time.

1. Start with the launch playbook. Your end-to-end map — what to set up, in what order, and how the pieces fit. → Launch a multi-location business on SGEN

1. Model your locations. Set up each physical location with its address, hours, and details so the right information shows on the right pages and in local listings. → Locations

1. Stand up your sites. Configure the multi-site deployment that holds a site (or distinct pages) for each location. → Set up a multi-site SGEN deployment

1. Run them all from one dashboard. Every location's site visible and editable from a single account — no re-logging-in per branch. → Manage multiple sites from one org account

1. Organize with Site Manager. Keep all location sites grouped, labeled, and easy to jump between as the count grows. → Manage sites in Site Manager

Site Manager gives you one screen for every location's site — live status, last modified, and a direct jump to each:

1. Win local SEO for each location. Set site-wide defaults, then tune each location's page so it ranks for its own area. → Set up your SEO defaults · Optimize your site for SEO

After SEO defaults are saved, each location page inherits them — tune per-branch for the local address:

Why local SEO is per-branch

A common instinct is to treat search as one job for the whole business — set the SEO once and move on. For a multi-location business that leaves money on the table, because the customer searching near your North branch and the customer searching near your East branch are looking for different pages.

Local search works on proximity and relevance to a specific area. So the goal isn't one generic site that ranks vaguely everywhere; it's each location's page tuned to rank for its own neighbourhood — its address, its area name, its local landmarks. On SGEN you set your SEO defaults once at the site level so every page starts with a sensible baseline, then tune each location's page for its own area on top of that baseline.

That two-layer approach — global defaults, per-branch tuning — is why steps 2 and 6 of the journey work together. Modeling locations puts the correct, single-source address on each page; the SEO step makes each of those pages findable to the people nearest it. Read the SEO defaults guide for the baseline and Optimize your site for SEO for the per-page tuning.

Key concepts at a glance

Growing past the first few branches

The setup that works for three branches should still work cleanly at thirty — and the two pieces that make that true are the org account and Site Manager.

The org account is the single login that every location's site is managed from. You don't log in and out of separate accounts per branch; you sign in once and every site is there. When you open a new branch, you add its site to the same account rather than spinning up a separate world to keep track of.

Site Manager is what keeps that account navigable as the count grows. It's one screen listing every location's site — its live status, when it was last modified, and a direct jump into each. With three sites you might not feel the need; with fifteen, it's the difference between a tidy operation and a tab-hunting mess. Set the multi-site deployment up once and it expands as you open more branches, so growth is adding a record and a site, not rebuilding your setup. See Manage sites in Site Manager.

Pricing, briefly

SGEN is flat-rate — every plan includes the whole platform. The only difference between plans is how many live sites you can publish, which for a multi-location business maps directly to your number of locations. Move up a plan as you open new locations. → Choose your SGEN plan

Your next step

Start with the multi-location launch playbook, then model your locations before you build pages. One dashboard, many sites — set up in that order and it stays that simple as you grow.