Ask a Philadelphia business who built its website and you usually get a first name and a decade. The domain has outlived the nephew, the agency and the freelancer, and what the company needs first is an inventory, not a dashboard.
The sequence is familiar across the collar counties. A nephew registered the domain in 2009. An agency rebuilt it in 2015 and set up analytics under an account nobody wrote down. A freelancer maintained it until 2021, then stopped answering email. The site still ranks, still takes calls, and nobody on the payroll can say how it works.
That is not a ranking problem, and publishing more pages will not fix it. It is a record problem, and it produces search problems steadily: a page nobody dares edit, a subdomain nobody can log into, a decision reversed because its reason was never written down. What follows describes the part of a workspace built for that problem.
Three questions most owners cannot answer on the spot
Before any chart is worth reading, a business has to answer three questions about its web presence. Very few can.
- Which domains exist. Not the one on the business card — every domain the company pays for, redirects from, or launched and never retired.
- Who is verified on them. Which Google account holds verification, and whether the person behind it still works here.
- What was decided, and when. Which changes were deliberate, who made them, and what the reasoning was.
A workspace is sold as a reporting surface. For an older business its first value is a register: one place where properties are listed, access is visible, and everything done from now on leaves a dated line behind it.
Nothing below is exotic: a feed, a chat, filters, tags, permissions, exports. What they share is that using them leaves text behind — dated and searchable, written without anyone deciding to write it. The unified Semalt panel is built around that assumption.
Nobody chose to run four websites
Portfolios here are rarely designed. They accrete one reasonable decision at a time, and whoever made each is gone by the time it counts.
The name the company traded under before
A family HVAC business rebranded in 2018 but kept the old domain live because the trucks still carried it.
- Often outranks the current site for the founder's surname
Built for one season, never taken down
A hospital system launches a site for a screening program; a law firm builds one for an intake push.
- Thin, dated, still crawled, often competing with the parent
A page that quietly became a site
A restaurant group's second location got its own domain because the manager wanted a different menu.
- Separate reviews, separate hours, in nobody's report
Whatever came with the acquisition
A dental practice buys a retiring dentist's patient list in Delaware County; the domain arrives as an afterthought.
- Verification usually still sits with the seller
The difficulty is not complexity. Each came in attached to a single person who was also the only documentation, and properties outlast people. A university department, a construction firm and a specialty pharmacy describe the same shape: several live domains, partial memory, one person who might have the password. Pulling them into one workspace does not merge them, it lists them — a smaller and more useful act.
My SEO Stream, and what a project feed is actually for
Stream is a conversational feed attached to one project. Entries of every kind sit on one timeline in the order they occurred: model answers, generated reports, new backlinks with the donor domain's rating and traffic, open tasks, campaign notices.
A dashboard reports the present tense. A feed reports sequence, which is what a successor needs — the only thing connecting an edit in April to a movement in June. Where three web people left without a handover, a feed starting today beats reconstructing fifteen years.
One running account per property
Written for whoever opens this site next, with nobody left to ask.
- Dated entries, permanent. Nobody files anything; the campaign writes the log while it runs.
- Placements arrive with evidence. Each link carries the host domain's authority and traffic, so quality can be judged rather than trusted.
- Documents keep their context. A report generated mid-dispute about the microsite stays attached to the dispute.
- Lists go in wholesale. Keyword and URL lists are accepted in batches — how an inherited property is onboarded years late.
One feed per property matters more than it sounds. Everything is recorded against a specific domain rather than the account, so nobody can assert later that one quarter of content work also served the legacy site. When a business weighs retiring a property, that record is the only honest input.
A chat tied to the project's own numbers
The assistant in the My SEO area is not a general model told about your company. It reads the project's actual data, and that changes which questions are worth typing.
A router model sees the question first, and its single job is deciding what has to be fetched. There are four block types — Search Console, SERP, campaign and custom — of which zero to three get pulled, ranked by relevance. A question about impressions in March pulls Search Console. One about who holds the top slots in Chester County pulls SERP. One about how canonical tags behave pulls nothing, which is the right result.
Questions about method
How something works in principle, what a status code means, why two reports disagree.
- No project data is pulled at all
Questions about this domain
Anything naming a date range, a page, a rival domain or a campaign state. Broader questions pull more blocks.
- Name the site and the window explicitly
Output arrives a token at a time instead of as a finished block. The benefit is practical: within a second you see where the answer is heading, and a question that missed can be cut off rather than sat through. History runs to twenty messages per thread — room for one line of inquiry, and a prompt to start fresh when the subject changes.
Cutting the timeline down: four filters, three states
Length eventually defeats a timeline, so four filters sit over it. All leaves the sequence intact. Links strips it back to placements, which is how a link profile gets reviewed. Files brings up earlier documents. To-do shows what is waiting on a decision.
| Filter | What it isolates | Who reaches for it | Typical moment |
|---|---|---|---|
| All | The whole sequence for one property | A newly arrived coordinator | Day one |
| Links | Placements and their donor figures | Whoever approves link spend | Once a month |
| Files | Everything already generated | Owner, account manager | Ahead of a client meeting |
| To-do | Open items and their state | Anyone holding a grant | End-of-week pass |
Each to-do sits in one of three states, and the middle one keeps the list credible. Something active has an owner and an intention behind it. Something dismissed was read and rejected. Something deferred was read, judged correct, and cannot be done yet.
In a small company deferred carries most of the list, and it is the only state reflecting the situation. Nobody rewrites the service pages while the crew is booked through November. The old domain stays until printed invoices stop carrying its number. Strip the state out and those items masquerade as urgent, or vanish and get reinvented in the spring.
Search covers the full text of every message, which converts a chronology into something a person can interrogate. The request is never "show me the second week of August." It is "why are two of our domains chasing the same roofing term," and that is one query away.
Reconstructing who can still get in
The access problem here is not staff rotation. Access was granted repeatedly over fifteen years and withdrawn approximately never. The nephew's Gmail still holds verification on the original property. The 2015 agency's shared account is still an owner in Search Console. The freelancer who went quiet in 2021 holds analytics and, more often than owners expect, the registrar login.
Multi-tenancy exists for precisely that mess. Google accounts can be linked into a group, which matches how verification accumulates in a company that has changed hands and changed suppliers: a personal address in 2011, an agency login in 2016, the owner's Gmail last year. Grouped, the portfolio resolves into one view rather than several incomplete ones.
Grants that can be taken back
For a domain handed to four people, two of whom cannot be reached.
- Account groups. Verification spread over personal and agency logins from different years collapses into one portfolio.
- Sharing is per site. A contractor engaged for the microsite gets the microsite, nothing else.
- Withdrawal is one action. Closing out a supplier means cancelling a grant, not changing a password three previous vendors memorized.
- One authorization. Gmail, Search Console and Analytics clear in a single OAuth consent instead of three approvals collected over weeks.
Tags are how you separate the portfolio from the residue
Tags attach to any site and act as a global filter rather than a folder: pick one and the dashboards, ranking views and exports contract to that subset.
Most people reach for brand first, since brand is how the history is remembered internally. As an axis it reveals almost nothing — only which logo sits at the top of the page. Intent repays the effort instead: is this domain run deliberately, or left behind by a decision whose author has moved on?
| Axis | Typical values | What it reveals | Structure |
|---|---|---|---|
| Intent | core, secondary, legacy, orphan | Which properties deserve budget, which need a decision | Flat |
| Sector | clinical, campus, professional, trade, hospitality | Why two properties behave nothing alike | Flat |
| Geography | city, montco, bucks, delco, chesco, south-jersey | Which part of the region is moving | Flat |
| Access | in-house, agency, contractor, unknown | Who loses reach when a contract lapses | Flat |
| Language | en, es | Filtered independently of the rest | Flat |
Resist the urge to nest. A tree of brand, then geography, then sector reads well for a month, and then a property refuses to sit on one branch: a practice with offices in two counties belongs under both. Hierarchies also freeze whatever the company looked like the day they were drawn, a poor bet at this age.
The orphan tag earns its place immediately. It marks a domain that is live, indexed and unclaimed by anyone working here, so it surfaces in every filtered view as a standing question rather than vanishing into a list nobody finishes.
Reporting, visualization, and what a week costs
Reporting works in two registers, and mixing them costs an afternoon. CSV and JSON run to 10,000 rows and exist to be worked on — dropped into a spreadsheet, matched against job tickets, appointment records or the phone log. The PDF is a different object: 250 rows, rendered on the server, produced to be read rather than processed. The builder accepts your logo and colors, which matters when the reader is a practice manager.
The chart types offered by the reporting section of the panel are deliberately ordinary, and each earns its keep once the portfolio has been tagged.
- Series charts and metric cards. The curve shows direction; the single large figure is what gets quoted in a meeting.
- Tables you can filter and sort. Pagination at 50 to 200 rows, the range where a five-site table stays readable.
- Sparklines. A miniature curve per property, all of them on one screen, and the broken one announces itself.
- Heatmaps for country and device. Device tells a phone in a truck apart from a workstation in billing; country exposes the out-of-state research traffic that swells a hospital property.
Take a professional services firm in Montgomery County with five properties: the current domain, the legacy domain from the previous name, a campaign microsite, a recruiting site and an acquired practice's domain. Two staff, an outside content agency, a contractor on recruiting.
| Day | Task | Screen |
|---|---|---|
| Monday | Scan the core properties; note what moved | Dashboard, intent tag |
| Tuesday | Read legacy and orphan properties separately | Dashboard, second tag |
| Wednesday | Keyword candidates approved, rejected or deferred | Campaign keyword pool |
| Thursday | Branded PDF to partners, CSV to the agency | Report builder |
| Friday | Open items read across all five | Stream, To-do filter |
Monday runs to twenty minutes because the intent tag reduces five properties to the two that pay. Wednesday is the only fixed appointment: keyword candidates drawn from the verified property, live results pages and the firm's own seed list, handled one at a time — approve, reject, set aside. Friday diagnoses the firm rather than the sites: a list of nothing but set-aside items means the shortage is staff time.
Five sites cost about a day a week to keep in order. That is the honest claim — not that software raises rankings, but that it shrinks the routine half until two people can carry it, and what it writes down survives both of them. Worked examples sit in our blog archive; what we actually run for clients is set out under services.
Common questions
We think we own four domains but we are not certain. How do we find out?
Work from three sources rather than memory: registrar accounts anyone can still log into, card statements for annual renewals, and redirects landing on your current site. Add every property to the workspace and tag anything unclaimed as an orphan. The list is usually longer than the owner expects.
An agency from 2015 still shows as a verified owner. Can we simply remove them?
Yes, provided you keep at least one verified owner you control, and confirm that first. Verify a company account, check that it holds ownership rather than delegated access, then remove what you cannot account for. Verification is a business asset, not a vendor's.
Should a legacy domain be retired or kept?
Read its data first. If it holds impressions, external links or branded searches for the old name, redirect it page by page into the current site rather than switching it off. If it holds nothing measurable, retire it. What you should not do is leave it live and unmonitored.
Nobody here has time to maintain a record. Does this survive that?
That is the design constraint. Entries come from the campaign, the reports and the assistant rather than from a person typing, so the feed stays accurate in the months when nobody tends it. The one habit worth adding is a sentence explaining why an item was deferred.
That list is not modesty. It marks out what is left. Gathering, aggregating, watching and much link placement have gone into software for good. The residue requires knowing the business: picking the fight worth picking, running a movement back to its cause, saying the result out loud to somebody who wanted better news. The campaign automation side absorbs the first group and does not touch the second.
On a domain that has outlived three web people, that residue is dearer than it looks, because every arrival pays for the same thinking twice. Where the feed is dated and searchable, a newcomer spends the first week debating the next move instead of excavating the last one, and the export and reporting layer carries the reasoning outside the building.
If one person's memory is the only index of your properties, the place to start is unremarkable. Create a workspace and connect the Google accounts you can still reach, write down every domain you can find, label each by intent and by access, then read the verified users list before anything else. What usually turns up is a domain untouched since 2019 — indexed, still forwarding calls, missing from every report the firm has sent a client.