A home-care agency with an office on each side of the bay ends up with two of everything, and one office manager looking after all of it between phone calls. The question worth asking about a workspace here is whether a part-time person can still hold the whole thing on a Friday afternoon.
Portfolios in this market are not built by ambition. They are built by water. A firm opens a second location because the first cannot reach the far shore, and that location needs its own address, hours, crew and page — sometimes its own domain. Nobody decided to run four web properties. The bay decided it.
One business, one presence per side of the water
Elsewhere companies collect spare domains through rebrands and acquisitions. Here the multiplication is geographic and deliberate. Nobody in Palm Harbor is served by a crew dispatched from Riverview, and both parties know it, so a firm wanting both sides opens both sides — then has to say so where a search engine can read it. The portfolio ends up organized by map rather than by brand, in four recurring shapes.
An office on each shore
Home care, staffing, bookkeeping, insurance back offices: one entity, two licensed offices, two scheduling teams that never share a calendar.
- Two listings, two phone numbers
- Often two sites, the second built later
A yard here, a yard across the bay
Marine contractors and dock builders: a yard in Tampa near the port and a second in Clearwater working the gulf side.
- Different waters, different permits
- Seasonal load that peaks at opposite times
Four clinics under one name
Practice groups grow by absorbing retiring physicians. Each location arrives with patients, a page and occasionally a domain.
- Verification often still sits with the seller
- Reviews and hours differ per site
A beachfront property and a downtown one
Hospitality operators run a rental site on the barrier islands and a second, unrelated business inland.
- One books ahead, one books same-day
- Nothing about them should be averaged
None of these is complicated alone. They are awkward together because they look alike from outside and behave nothing alike underneath. Two sites for one company can run opposite trends all quarter — one filling with winter residents, the other emptying — while the combined figure reports them as flat.
The maintainer also answers the phone
The second condition is who does the work. A firm this size has no marketing department. It has an office manager handling scheduling, invoicing, the answering service and, on Thursday afternoons, the websites. A practice administrator. A dispatcher.
That person is competent and interrupted. The constraint is not skill: any task needing twenty uninterrupted minutes gets started three times before it finishes.
The last two tiles matter most to an interrupted person. One consent screen covers mail, Search Console and Analytics, instead of three approvals gathered over separate weeks, and background workers keep pulling data while nobody watches, so a screen opened cold on Thursday is already current.
The rest of the value is that the work leaves a written trail without anyone deciding to write one. A shared folder of notes survives about a quarter in an office like this. A record produced as a byproduct survives indefinitely.
My SEO Stream, one thread per property
Stream is a dialogue-shaped feed belonging to one project. Everything arrives on a single timeline in the order it occurred: replies from the assistant, each report as it is produced, fresh backlinks listed with the host domain's authority and traffic, open tasks, campaign notices.
A dashboard describes this morning. A timeline describes order, and order is the only way anybody later ties a page rewritten in February to a movement in April. Where the maintainer gives ten hours a week, order is what goes missing.
A dated line per property, kept without effort
For the location whose page nobody has touched since the last hire left.
- One stream per project, not per account. Work is recorded against the property it was done for, so Clearwater cannot claim credit for effort spent on Tampa.
- Every placement arrives with its numbers. Authority and traffic sit beside the link, so an owner judges the spend instead of taking it on faith.
- Documents keep their surroundings. A report generated during a dispute about the second office stays where the dispute is.
- Whole lists are accepted at once. Keywords and URLs go in by the batch — how a location bought last year finally joins the account.
Because entries attach to a property rather than a person, the record survives the maintainer changing — which here happens about as often as the office moves.
A chat that reads the project before it answers
The chat inside My SEO is not a general-purpose model handed your company name. It reads the project's own figures, which changes what is worth typing.
A router model reads the question first and decides what has to be fetched. Four block types exist — Search Console, live results, campaign state and custom material — and anywhere from none to three are loaded by relevance. Impressions on the St. Petersburg pages pull the search record. Who else appears for dock repair terms on the gulf side pulls results data instead. What a canonical tag does pulls nothing at all, which is correct rather than a failure.
General questions about method
How a mechanism works, what a term means, why two screens disagree. No project data is touched.
- Fast, and safe to ask badly
Questions about one of your sites
Anything naming a location, a date range, a page or a rival domain. Wider questions pull more sources.
- Name the property and the window
Answers arrive a token at a time rather than complete. For an interrupted reader that matters: the direction shows within a second or two, so a badly phrased question can be cut off instead of waited out. History holds twenty messages — one line of inquiry, and a fair signal that a new subject wants a new thread.
Four views over the timeline, three states on a task
Length eventually defeats any feed, so four filters sit above it. All keeps the sequence whole. Links narrows to placements and their host figures, which is how link spend gets reviewed monthly. Files returns the documents already produced. To-do shows what waits on somebody.
| Filter | What it leaves on screen | Who reaches for it | When |
|---|---|---|---|
| All | The full chronology for one location | Whoever inherited the account | First week |
| Links | New placements with rating and traffic | The owner approving the spend | Monthly |
| Files | Every report already produced | Practice administrator, bookkeeper | Before a meeting |
| To-do | Open items and the state each sits in | The part-time maintainer | Friday |
Every task sits in one of three states, and the middle state is what keeps the list believable. Active carries an intention. Dismissed was considered and turned down. Deferred was considered, accepted as correct, and blocked by the calendar.
Here the deferred pile holds most of the list for months on end, and that is the calendar rather than procrastination. A roofing contractor does not rewrite service pages between June and November. A rental operator on the beach does not rebuild a booking flow in March. A clinic group leaves its location pages alone while the winter population is in town and every chair is full. Take the state away and those items either pose as neglected work or vanish and get reinvented next year.
Search covers the full text of every message, which turns a chronology into something you can question. Nobody needs the third week of August. What they need is why two of their own pages chase the same phrase in Largo — one query rather than an afternoon of scrolling.
Linked accounts, and handing over one location
Access in a multi-location business is fragmented by history. The first site was verified under a personal Gmail. The second office was set up by whoever ran it then. A contractor received something in 2021 nobody has checked since.
Multi-tenancy answers that. Several Google logins join into one linked group, which is how verification accumulates in a company that opened its offices years apart. Joined up, the portfolio becomes a single view rather than three partial ones.
Per-site grants that can be taken back
For the contractor who needs the Clearwater site and nothing else in the account.
- Linking is not merging. A personal address and two office logins keep their own verifications and still produce one portfolio; nobody hands over a password.
- Sharing is granted per property. An outside address gets the site it was hired for. The other locations never appear to it.
- Taking access back is one step. Ending an engagement cancels a grant, rather than changing credentials three past suppliers know.
- The Google services clear together. Mail, Search Console and Analytics come through one consent screen — ten minutes instead of a fortnight of chasing.
Tags by shore and by location, kept flat
A tag pins to any site and works as a filter across the account rather than as a folder. Pick one and every screen — dashboards, rank views, exports — narrows to that subset. In a portfolio built by geography this is the panel's most useful organizing device, since geography is what actually separates these properties. Two axes pay for themselves at once: the shore a site serves, and the office behind it.
| Axis | Values that work locally | What filtering by it reveals | Shape |
|---|---|---|---|
| Shore | hillsborough, pinellas, both | Whether the two halves of the market move together or apart | Flat |
| Location | tampa, st-pete, clearwater, brandon, largo | Which single office is carrying or losing the quarter | Flat |
| Service line | home-care, marine, clinical, trades, lodging | Why two properties behave nothing alike | Flat |
| Season | winter-peak, summer-peak, year-round | Which comparison window is honest for this property | Flat |
| Language | en, es | Filtered independently of everything above | Flat |
Do not nest them. Shore above location above service line looks orderly on a whiteboard and fails the moment a site belongs on two branches — immediately, since the mobile crew works both shores. Two flat labels fit one property; a branch does not, so the property lands wherever is wrong.
Turnover is the second reason. A tree freezes the company as it stood the day somebody drew it, and locations here open and close on the timescale of a lease. A sixth label costs nothing; redrawing a hierarchy costs an afternoon.
Exports for people who do not work in marketing
Two kinds of output leave the panel, and mixing them wastes a morning. The machine-readable pair, CSV and JSON, carries up to 10,000 rows and is meant for further work — lined up against the appointment book, the job tickets, the call log. A PDF is something else: 250 rows at most, rendered server-side, meant for reading. Both carry your own logo and colors.
Who reads these is the whole design problem. Nothing goes to a marketing lead. It goes to an owner who builds docks, a practice administrator with a clinical background, or a family that owns the business between them. None of them will interpret a chart they were not walked through, and none will ask what a term means in front of the others.
So an export that states its own scope beats a prettier one that does not. A page labeled with the property, the date range, the shore covered and the two-day reporting lag can be handed over cold. The same figures unframed invite the worst question in this business — "so is that good?" — which nobody in the room can answer.
- Time series. Direction over a window, which is all most readers need. Set it against the same period last year for anything seasonal.
- Metric cards. The single large figure that gets quoted afterward — choose it deliberately, since it is the only number anyone remembers.
- Sortable, filterable tables. Pages hold 50 to 200 rows, which keeps a four-office table legible in print.
- Sparklines and heatmaps. One small curve per property fits the portfolio on a screen; country and device heatmaps tell out-of-state browsing from a phone in a work truck.
Now a week, using a clinic group with four locations across both shores and an office manager giving it roughly three hours.
| Day | What gets done | Where |
|---|---|---|
| Monday | Glance at the two locations that carry the revenue | Dashboard, filtered by location tag |
| Tuesday | Read the far shore separately, against last year | Dashboard, shore tag, 90-day range |
| Wednesday | Term candidates cleared one by one | Campaign keyword pool |
| Thursday | PDF out to the partners, CSV to the bookkeeper | Report builder |
| Friday | Open items across all four sites | Stream, To-do filter |
Monday is short because one tag cuts four properties to the two that pay. Wednesday cannot slip: the term pool, fed by the verified property, live results pages and the practice's own seed list, is cleared one candidate at a time. Friday says more about the firm than the sites — nothing but set-aside items means the office is short a person.
Common questions
Should each location have its own domain, or sections of one site?
Sections, unless the locations are separate businesses with separate ownership or licensing. One domain concentrates whatever authority you build; four split it and quadruple the upkeep for a part-time person.
Our second location was set up by someone who has left. How do we get it back?
Verify a company-controlled account there, confirm it holds ownership rather than delegated access, and only then remove what you cannot identify. Once the logins are linked, the location appears beside the others.
How many tags is too many?
Judge it by whether each tag was used as a filter last quarter. Shore and office cover most of what a four-site portfolio needs. A label nobody has filtered by in three months is a note rather than a tag, and belongs in the feed.
Our list is almost entirely deferred items. Is something wrong?
Not necessarily. A long deferred list with reasons attached is an accurate picture of a seasonal business. It turns into a problem when one item has been deferred through two off-seasons running, which usually means nobody ever intended to do it.
What do we send to an owner who never opens a dashboard?
A short branded PDF per location, well under the 250-row limit, naming the property, the window and the comparison period on the page itself. The CSV goes separately to whoever reconciles it. Never one combined document covering both shores.
None of that is a disclaimer; it marks a boundary that has genuinely moved. Gathering figures, keeping them current, watching for movement and placing most of the links now happen without a person — the placement network runs beyond 230,000 sites, and campaign automation at either level keeps it going unattended. The leftovers need somebody who knows the firm.
On a portfolio stretched across a bay and looked after by somebody with another job, that leftover is where the value sits; the rest is upkeep. An assistant tied to your own project figures answers about your locations instead of in general, the timeline writes itself, and the reporting side of the panel carries the conclusion out to readers who never sign in. More examples sit in this blog; what we handle directly is described under services.
If your locations are currently four browser tabs and one person's memory, the first hour is unglamorous. Open a workspace and link the Google accounts you can still reach, add every property, tag each by shore and by office, then read the verified users list before looking at a chart. What usually turns up is a location page nobody has edited in two years — still indexed, still taking calls, missing from every report the business has ever sent.