A Site Per State: Running SEO as a Team When the Portfolio Splits at the Border

A firm working both Carolinas usually ends up with more than one website, because the license, the service list and sometimes the trading name change at the border. The workspace question is not how to merge those properties into one number — it is how to keep them apart while running them as one job.

Two forces make portfolio work here harder than the site count suggests. One is legal: a combined report averages two jurisdictions under different rules. The other is human: whoever holds the passwords rotates about as fast as the customers.

The portfolio splits where the license splits

Nobody decides to run four domains. The second appears the year a contractor registers in South Carolina and finds the existing site claiming a scope of work that holds in Mecklenburg County and not in York County. The third arrives with an acquisition. The fourth was a campaign page nobody switched off. From outside it looks like duplication. It is not: the menus differ where permitting does.

The reporting problem then states itself. Roll those properties into one figure and it is honest arithmetic about nothing anybody can act on: clicks rose eleven percent — on which side of the line?

The people move on about as fast as the customers

Churn is discussed here as a customer phenomenon, and it applies equally to whoever runs the marketing. An office manager builds the website over three years, then leaves for better hours. A coordinator is hired away by a bank, a hospital system or a distribution center paying more for the same skills. An agency is dropped after the owner sells and the acquirer already has one.

Each exit removes reasoning, not files. What remains is a South Carolina section with no note explaining why three services were left out, and a successor who reads the omission as sloppiness and restores them.

• Deliberate gaps read as mistakes. A missing service page is often a compliance decision. Undated and unexplained, it gets filled in by the next person, creating a claim the firm cannot support.
• Access outlives employment. Verification sits in a personal Google account two jobs away, unnoticed until a report stops updating.
• Attribution drifts. A decline that began in February is pinned on whoever arrived in June, because nothing carries a date.

The usual answer is documentation, and documentation written as a separate task decays within two quarters because nobody is measured on keeping it fresh. What follows produces a written record as a side effect of the work instead — the only kind that stays accurate. The unified Semalt panel treats that record as infrastructure: automation, Google data, research and indexing share one workspace, each leaving a dated entry.

A feed that logs itself, site by site

My SEO Stream is a chronological feed attached to one project. Entries of every kind share a single column in the order they occurred: campaign notices, generated reports, tasks awaiting a decision, model replies, each new backlink placement carrying the donor domain's rating and traffic.

The value is sequence: it connects a March change to a June movement. The feed also belongs to one site, which matters across a state line — work logged against the account could later be claimed to have covered both, while work logged against the South Carolina property cannot.

Placement inventory comes from a partner network exceeding 230,000 sites, and logging it per property is what makes link work auditable: whoever takes over the Lancaster County site reads what was built there.

A chat bound to the project's own figures

The assistant in Stream is not a general model handed a briefing about search engines. It is wired to the project's data, and that governs what is worth asking it.

Every question meets a router model whose sole job is deciding what the answer requires. Four blocks exist — campaign state, custom data, live results readings and Search Console — and none to three load, by relevance. Ask how canonical tags behave in general and nothing loads, correctly. Ask which terms lost ground on the South Carolina property since April and analytics comes in; ask who took those slots and results joins it.

Replies arrive token by token rather than whole, so you see where an answer is heading almost at once and can stop a misfired question early. Twenty messages of history are kept per thread — room for a question and two rounds of narrowing, and a hint that a new subject belongs in a fresh thread.

All, Links, Files, To-do — and the state most lists lack

A year-long timeline stops being readable, so four filters sit above it. All keeps the full sequence. Links reduces it to placements, which is how link quality gets reviewed without a second tool. Files surfaces earlier documents. To-do leaves what needs deciding.

A task holds one of three states, and the middle one keeps the list honest in a company with no slack. Active means it has an owner and an intention. Dismissed means it was considered and rejected on the record. Deferred means correct, but not yet.

Here the deferred pile is usually the biggest, for reasons unrelated to search. Crews are booked through the fall. A clinic waits on credentialing before publishing a provider page for the other state. A carrier cannot advertise a lane until the second building is signed. Remove that state and those items either pose as urgent or get discarded and rediscovered a year later.

Every message is searchable in full text, which converts a long feed into institutional memory. Nobody inheriting a site looks for a date. They look for a subject — two pages fighting over one roofing term, or why the Indian Land URL was kept out of the sitemap — and a phrase finds the exchange where it was settled.

Linked accounts, per-site sharing, and revocation

Every handover either transfers access properly or passes a password along in a group message, and the second is what usually happens. Where agency changes follow mergers, that debt compounds fast.

Multi-tenancy is built in. Several Google accounts link into one group, matching how verification ends up scattered: one property in a former office manager's personal account, another in an agency's, a third under the owner's Gmail from the year the site launched. Google OAuth2 covers Search Console, Analytics and Gmail in one consent flow, so linking is a single pass rather than three approvals chased over a fortnight.

Tag by state and service line, and keep it flat

Tags attach to sites and act as a portfolio-wide switch: pick one and every screen, ranking table and export restricts itself to the properties carrying it. For a business divided by jurisdiction that does the heavy lifting. North Carolina alone, South Carolina alone, or both — and the combined figure becomes a choice rather than the only thing on offer.

Most people reach first for brand names, since that is how acquisitions get talked about internally. It tells you almost nothing: a logo is not a market or a rulebook. Jurisdiction earns its place at once, and service line follows, because a company with a residential arm and a commercial arm is two businesses sharing a fleet.

Flat beats deep for a plain reason. A nested scheme such as carolinas / south-carolina / york-county / residential forces one classification per site, then fails the moment a property serves two categories — which most do. Independent flat axes let a site carry sc and commercial and freelance at once, so combining them is filtering, not restructuring. Deep trees also rot at handover: the successor cannot see the reasoning behind the branches and grows a parallel one beside them.

Exports, visualizations, and a week that actually happens

Reports are where portfolio work meets people who never open the panel: an owner, a partner, a bank reviewing marketing spend. The builder is configurable and carries your logo and colors, which matters more than it sounds — a page resembling a screenshot gets skimmed, a document gets read.

Know the limits before promising a deliverable. CSV and JSON run to 10,000 rows, covering any list a firm this size produces. PDF renders server-side and stops at 250 rows, making it a summary whether or not you meant one. Send the PDF to the owner, the CSV to whoever sorts it.

The visualizations are deliberately ordinary. Time series carry direction and metric cards carry current state, while filterable sortable tables paginating fifty to two hundred rows are where an argument ends, because somebody can sort by the column they doubt. Sparklines fit a trend inside a row. Heatmaps cover countries and devices, and the device one earns its keep here: phone-heavy residential against desktop-heavy commercial has budget consequences.

Two things sit alongside that routine. Keyword dynamics logs every crossing into or out of the top three, ten and thirty, each dated — a record that survives a staffing change. And generative market research reads the live competitive landscape rather than your own past, which is what you need opening a service line across the border.

Pricing is per domain at both levels, which is the arithmetic to run before splitting a site by state. A separate property earns its subscription when the service lists truly differ; otherwise a section on the existing domain is cheaper. Worked examples sit on our blog, the engagements under what we do.

Questions that come up when the team changes

None of this is automation in the sense people usually mean. Background workers keep figures current, the router decides what a question needs, exports render themselves, grants open and close on request. What that buys is time and an accurate record, not judgment.

Four things stay firmly human, and they decide outcomes. Prioritization: which property gets the quarter, given crews and cash. Cause-finding: whether the drop on the South Carolina side is a competitor, a redesign, a lapsed registration or a season nobody wrote down. Goal-setting: what a good year looks like for a firm that may be sold before it ends. And client communication, which in a market this transient means explaining the same result to somebody who was not there when the work began.

The workspace makes those conversations possible by keeping the evidence in one place and making sure it outlasts the people. Link your Google accounts and tag every property by state before the next report goes out. What most firms find first is not a ranking problem. It is a property still verified in the account of somebody who left two years ago, quietly feeding a number nobody has been able to break apart since.