Ask a Front Range company why its site is built the way it is and the honest answer is often that nobody still employed there knows. A workspace earns its keep for one unglamorous reason: it keeps writing things down after the people who knew have gone.
Growth is fast and staffing loose. A trades company goes from nine people to forty in three years, hires a coordinator, lets her build everything, and loses her in March to a better-funded employer down the corridor. Her successor inherits a login and no explanation.
None of that is a search problem. It is a memory problem that produces search problems steadily: decisions reversed, work repeated, a page nobody dares touch. What follows is the half of a workspace that addresses memory rather than rankings.
Nobody planned a portfolio; it accumulated
Very few businesses along the corridor set out to run several websites. Growth added them one at a time, each sensible on the day it happened.
The company that bought two competitors
A mechanical contractor absorbs a Longmont firm and a Greeley firm, keeps both names because the numbers are painted on trucks, and now runs three domains.
- Two legacy sites nobody edits
- Town pages overlapping on all three
The brand with a wholesale side
A Boulder gear maker sells direct and to shops, with a dealer site a departed ecommerce manager built over a weekend.
- Different buyers, different vocabulary
The taproom that became four taprooms
A brewery opens in RiNo, then Lakewood, then Fort Collins, then a production facility with a distribution page.
- One brand, four local fields
The regulated storefront and the agent roster
Cannabis retail with a store site and a supplier site; a brokerage where agents keep pages beside the parent domain.
- Access scattered across personal accounts
The common thread is not complexity. Each site arrived attached to one individual, who is the only documentation. The person leaves; the site stays, still spending crawl attention and still sending leads to an inbox nobody reads.
The March problem, and why it repeats every year or two
Marketing roles at growing Front Range companies turn over fast, and so do the outside firms. A coordinator lasts eighteen months; an agency is swapped after a bad quarter; a contractor takes a full-time job and stops answering.
Each departure removes a layer of reasoning nobody wrote down, leaving the artifact without the argument: forty town pages and no record of which towns were tested, a supplier site kept out of the sitemap on purpose that the next person quietly puts back.
- Reversal. A newcomer undoes a deliberate decision because it looks like an oversight, and the old problem returns.
- Repetition. The same experiment runs twice at full price, because its result sits in a departed inbox.
- Paralysis. A page that might matter is left alone for two years, and untouchable pages accumulate.
- Blame drift. Without dated entries, a decline is pinned on whoever is responsible now — usually the person who arrived after it began.
The mechanisms below are ordinary: a feed, filters, tags, permissions, exports. Each produces durable, searchable text as a by-product of the work. The unified Semalt panel treats that record as infrastructure rather than an afterthought.
My SEO Stream, one timeline for each property
Stream is a feed attached to one project, and entries of different kinds sit on a single timeline in the sequence they happened: campaign notices, open tasks, model answers, generated reports, each new placement carrying the rating and traffic of its host domain.
A dashboard answers what is true this morning. A feed answers what happened and in what order, which is what a new hire needs — and sequence ties a change in May to a movement in July.
The running account of one site
For whoever takes over a property with nobody left to ask about it.
- Entries are dated and stay put. Nobody has to remember to log anything; the log is a side effect of the campaign.
- Placements carry their evidence. A link is stored with the host domain's figures attached, so a successor can judge quality rather than trust a summary.
- Documents sit beside their cause. A report produced during an argument about the Fort Collins taproom stays next to that argument.
- Lists go in wholesale. Keywords and addresses can be handed over in batches — how an inherited site gets onboarded, months late.
One feed per property also enforces something a growing company needs: work is logged against a named site rather than the account. A brewery with four taproom sites cannot be told afterward that one piece of content covered all four.
A chat wired into the project's own figures
The assistant is not a general model handed a briefing about SEO. It is bound to the project's data, and that binding decides what is sensible to ask.
Every question first meets a router model whose sole task is deciding what the answer needs. Four blocks are available — campaign, custom data, SERP and Search Console — and anything from none to three is pulled in, by relevance. Ask about impressions since June and Search Console comes in; ask who holds the top slots in Aurora and SERP comes in; ask how redirects behave in general and no block loads at all.
General method questions
How something works in principle. Nothing loads, and that is correct: your data would not improve the answer.
Questions about this site
Anything naming a period, a page, a competitor or a campaign state. The wider the question, the more blocks arrive.
- Name the site and the date range
Output arrives token by token instead of in one piece, which is practical rather than decorative: the shape of an answer shows within a second, so a badly aimed question can be abandoned instead of waited out. A thread keeps twenty messages of history — enough for the ask, narrow, narrow again pattern, short enough that a new subject deserves a new thread.
All, Links, Files, To-do — and the state that admits the truth
A long timeline stops being usable, so four filters sit above it. All keeps the whole sequence; Links leaves only placements, which is how link quality gets audited; Files surfaces documents; To-do reduces it to what needs deciding.
| Filter | What it isolates | Who opens it | Typical moment |
|---|---|---|---|
| All | The whole sequence for one property | Whoever inherited the site | First week in the job |
| Links | Placements, with the host domain's figures | Whoever signs off on link quality | Monthly review |
| Files | Documents produced earlier | Owner, account manager | Before rebuilding a report |
| To-do | Everything active, deferred or dismissed | Everyone with access | Weekly triage |
To-do items hold three states, and the middle one is why the system survives a busy company. Active means somebody intends to act; dismissed means the item was judged wrong; deferred means it is right and cannot happen yet.
Deferred is the honest state, and in a fast-growing business it carries most of the list. The crew that would rewrite the service copy is on a job through October; the dispensary awaits a licensing change; the brewery's replacement site is mid-build. Without it, all of that sits open pretending to be urgent, or is dismissed and reinvented next spring.
Full-text search runs over every message, which converts a timeline into memory the company owns. Nobody arrives asking for the third week of August; they ask what was decided about the two sites competing for one roofing query.
Sharing one site, and taking it back the same afternoon
Marketing work here rotates constantly between in-house staff, freelancers and small agencies. Every handover is a point where access is either transferred properly or left as a password in a group chat, which is still what happens.
Multi-tenancy is built in. Several Google accounts link into a group, which fits how verification ends up scattered at a company that grew fast: an ex-developer's account holds two properties, an agency a third, the founder's Gmail the remainder. A single site can then be granted to a named address, and the grant pulled back.
Built for people who arrive and leave
Why swapping agency should be paperwork rather than a scramble.
- Linked Google account groups. Properties verified in different accounts in different years land in one workspace instead of three partial views.
- Grants are per site. A contractor hired for the dealer site gets the dealer site, not the flagship's numbers and not the acquired brands.
- Revocation is routine. Closing out a supplier means removing one grant, not rotating a password three former contractors also know.
- One consent flow. Search Console, Analytics and Gmail are authorized in a single pass, not three approvals chased over a fortnight.
Scoped sharing also lowers the cost of a trial: the acquired Greeley domain can go to a new agency for sixty days at little risk when the grant ends with a click.
Tag by stretch of corridor, not by brand
Any site can carry tags, and a tag works as a global filter rather than a list label: select one and every dashboard, ranking view and report narrows to that subset.
The instinct is to tag by brand, because brand is how acquisitions are remembered internally, and it is the least useful axis available: it says which logo is on the page and nothing about who the site competes with. Position along the corridor pays instead, because the Front Range is a line and demand varies along it.
| Axis | Values in practice | What it exposes | Shape |
|---|---|---|---|
| Corridor segment | north, boulder-spur, core, south | Which stretch of the line is performing | Flat |
| Audience | consumer, trade, wholesale | Two vocabularies that must never be averaged | Flat |
| Status | active, acquired, legacy, rebuild | Why a property's numbers look strange | Flat |
| Who works on it | in-house, agency, contractor | What breaks when an engagement ends | Flat |
| Language | en, es | A separate field, filtered in one click | Flat |
Keep the list flat. Nesting audience inside segment inside brand looks tidier for a month and then fails, because a property routinely belongs in two places at once: a wholesale site serving the whole corridor cannot sit on one branch. A hierarchy also freezes an org chart, the least stable thing in a company opening a location every year.
Reporting, and what a week actually looks like
Reporting works in two registers, and mixing them up wastes time. CSV and JSON carry as many as 10,000 rows for analysis: the file opens in a spreadsheet and is joined against job tickets or a call log. A PDF is rendered on the server, holds 250 rows, and is meant to be read by a client or an owner. The builder is configurable and takes your logo and colors.
The visualizations in the reporting section are deliberately conventional, and each earns its place once the portfolio carries tags.
- Series charts and metric cards. Curves show direction; a single figure carries the number an owner retains.
- Filterable, sortable tables. Pages of 50 to 200 rows, which keeps a multi-property table readable.
- Sparklines. Five properties, a miniature curve apiece, a single screen — and the one that broke stands out without arithmetic.
- Country and device heatmaps. Device separates a phone on a job site from a desk in procurement hours; country matters for outdoor brands selling abroad.
Take a mechanical contractor with five properties: the main domain, two acquired brands still trading under their own names, a recruiting site and a supplier microsite. Two people inside; an agency on content and a contractor on recruiting.
| Day | What gets done | Where it happens |
|---|---|---|
| Monday | Scan by corridor segment; note which stretch moved | Dashboard with the tag filter |
| Tuesday | Read the two acquired brands apart from the flagship | Dashboard, status tag |
| Wednesday | Keyword candidates approved, refused or held back | Campaign keyword pool |
| Thursday | Owner gets the branded PDF; the agency gets a CSV | Report builder |
| Friday | Open tasks reviewed on every property | Stream, filtered to To-do |
Monday takes twenty minutes because the segment tags collapse five properties into the two groups that changed. Wednesday is the only scheduled meeting: candidates surface from the verified property, live results-page readings and the company's own seed terms, each cleared, refused or held back one at a time. Friday's sweep is diagnostic — an almost entirely deferred list says the constraint is the operations calendar.
About a day a week covers the housekeeping on five sites. That is the defensible claim: not that a workspace lifts rankings, but that it shrinks the mechanical half enough for a small team to keep up, and leaves a record outlasting the payroll. Walkthroughs sit on our blog, and the campaign side under the services we run.
Common questions
We inherited three sites and no notes. Where does a new coordinator start?
Connect the properties, tag them by corridor segment and status, then read each feed from the beginning with the All filter before changing anything. Two hours of reading explains most of what looks inexplicable.
Our Google properties sit in four accounts, two belonging to people who left. What now?
Linked account groups are designed for exactly this, so the properties resolve into one workspace without a migration. Separately, move verification onto a company account for anything still held personally: a group makes the data visible, but the verification itself is a business asset.
Can the assistant compare two of our sites in one answer?
Not dependably. The chat is scoped to a single project, so put a tag filter on a dashboard when two properties need to sit side by side. Depth in the chat, breadth in the views.
Should an acquired brand keep its own project, or be folded into the main one?
Separate, for as long as it is a live domain. It competes in its own field, often on a different stretch of the corridor, and merging its numbers into the flagship hides what it earns and how fast it is decaying. Tag it as acquired so retiring it is an evidence-based decision.
Our agency changes roughly every eighteen months. What should a handover cover?
Revoke the outgoing grant the day the engagement ends, issue a scoped one to the incoming firm, and send them to the feed instead of a briefing call. The record does the explaining.
That list is not balance for its own sake; it is where the remaining work sits. Gathering, aggregating, monitoring and much placement work now live in software permanently. What stays human is everything depending on knowledge of the business: choosing which fight is worth having, finding the cause behind a movement, putting it to somebody disappointed. The campaign side of the platform handles the first and leaves the second alone.
High turnover changes what that second category costs. Judgment is expensive to exercise twice, and without a record it is exercised twice every time somebody new arrives. A dated feed, searchable in full, means the next coordinator argues about what to do next instead of reconstructing what was tried, and the export and reporting layer gets the reasoning out of the building in a form another person can open.
If your own portfolio is held together by one person's memory, the first step is small. Open a workspace and link the Google accounts, tag every property by its stretch of corridor and its status, and read the feeds before touching a page. Most owners find the same thing waiting: a site nobody has opened since the person who built it resigned, still ranking, still taking calls, absent from every report the company produces.
