What did your old SEO leave behind?
For years, SEO rewarded creating more: more links, more profiles, more websites, more citations, more accounts, and more places repeating the same information. Some of those tactics worked. But years later, businesses are discovering what was left behind — low-value links, duplicate properties, forgotten Gmail accounts, inaccessible social profiles, abandoned YouTube channels, and digital assets still speaking in the business’s name that nobody at the business can control.
Modern search visibility is not just about adding another signal. It is about making the business easier to identify, understand, verify, and retrieve. Sometimes the next step forward starts with cleaning up what was left behind.
From the Campfire: cleanup is not cosmetic
Kalyn Wright. One thing that has become very clear in recent client work is that cleanup is not busywork. We are finding businesses with old accounts nobody controls, overlapping pages, conflicting information, legacy URLs, outdated profiles, and years of decisions made by different people at different times. Some of that looks harmless until you start tracing how the pieces connect.
Google’s own documentation supports the point. Its systems use site structure and internal links to understand relationships between pages and which pages appear important, and Google recommends clear, logical site structure with relevant internal linking. Google treats duplicate or substantially similar URLs as a canonicalization problem: it clusters those pages and chooses the version it considers most representative — the site owner can signal a preferred canonical, but Google can choose differently. And structured data is not just decoration: Organization markup can help Google understand and disambiguate a business, while LocalBusiness markup provides specific business details such as name, address, telephone, and location information.
So when we talk about cleaning up old SEO, we are not talking about making a website prettier. We are asking whether the site, accounts, links, structured data, and business information are all describing the same business clearly. That is work worth doing before we add another layer on top.
Meet the team: clean up the digital debris
Daryl Osborne. A lot of websites are carrying years of accumulated SEO debris, and it goes well beyond thin content or old keyword stuffing. Poor site structure, overlapping pages, weak internal linking, duplicate entities, conflicting schema, inconsistent business information, and even competing brands or URLs referenced in structured data can all create what I have talked about for years: entity pollution. Instead of reinforcing who you are, what you do, and which pages own which topics, the site starts sending mixed signals.
This is by far the most common issue I see when auditing client sites. That weak foundation matters more now, not less — and it is essential to clean it up before applying more advanced methods and processes, such as Surge V3. Search engines and AI systems are increasingly trying to understand entities, relationships, authority, and context. If your website contradicts itself, duplicates itself, or has no clear topical hierarchy, adding more content will not necessarily help.
Before chasing advanced AI-SEO tactics, clean up the foundation. Remove ambiguity. Consolidate overlap. Fix the structure. Make every important page and entity have a clear purpose.
Practical how-to: reclaiming an orphaned social account
One of the most frustrating problems we are finding when taking over established businesses is not a missing social profile. It is a social profile that still exists, still represents the business, still appears in search — and nobody at the business can access it. Maybe a former SEO created the Facebook Page. Maybe an Instagram account was attached to a Gmail account nobody recorded. Maybe a YouTube channel is owned by an old SEO email address. Maybe a TikTok account was originally created using a login method the platform no longer supports. The account is still live. The business is still being represented. But control has been lost.
Start with recovery, not deletion. If the account has history, followers, content, reviews, authority, or a valuable username, reclaiming it is usually better than deleting it. Use this order:
- Try the original login and recovery methods. Search old password managers, emails, phones, employee records, agency notes, Gmail accounts, and recovery addresses.
- Trace connected assets. A Facebook Page may still be connected to a Meta Business account. An Instagram account may be linked to Facebook. A YouTube channel may still have another owner or manager attached.
- Use the platform’s official recovery or business support process. Be prepared to provide proof that the business is legitimate and that you are authorized to act for it.
- Use impersonation or trademark reporting only when it genuinely applies. An inaccessible old account is not automatically an impersonation account.
- If recovery fails, document the account as an orphaned asset. Record the profile URL, username, platform, known ownership history, recovery attempts, and what information it is still publishing about the business.
There is no guarantee that every orphaned account can be recovered or deleted. That is why preventing the problem is much easier than fixing it later. If an account speaks for the business but the business cannot access it, that is an entity-governance problem — not just a social-media problem.
Agency standard: the business should own the asset; the agency should have access
There is an important difference between owning a client’s digital asset and having permission to work in it, and the major platforms are already built around that distinction. Google Business Profile allows a business to keep a primary owner while adding other owners and managers — and Google specifically says each person should use their own Google Account rather than sharing a password. YouTube provides channel permissions so multiple people can work on a channel without being given the owner’s Google login; Google says this is safer than sharing passwords, and it recommends regularly reviewing who has access. Facebook Pages likewise support different levels of access so trusted people can help manage the Page without becoming the business itself.
That gives us a straightforward agency standard: when the platform allows it, the client keeps ownership, and we work through delegated access. When we create or inherit an important asset, we should be able to answer four questions: Who legally or operationally owns it? Which account is the primary owner? Who currently has access, and at what level? And can the client remove us and continue operating normally if the relationship ends? If we cannot answer those questions, the access setup is unfinished.
The goal is not to make ourselves indispensable by controlling the keys. The goal is to do work that remains usable by the business after we are gone. That is stewardship.
Stop collecting client access in email threads
There is a separate problem from account ownership: how the agency collects sensitive access information in the first place. Client onboarding often involves domain registrars, hosting accounts, CMS logins, analytics, social platforms, recovery information, and other credentials. That information should not be casually scattered across inboxes, texts, shared notes, and spreadsheets.
OWASP’s guidance for secrets management recommends transmitting credentials securely and treating secrets as information with a lifecycle that includes creation, rotation, revocation, and expiration. NIST defines a secure channel as one designed to protect the confidentiality and integrity of information while it is being transferred. That is why we built a secure encrypted client intake system for Super-Intelligent AI-SEO: a structured way to request and organize the access information needed during onboarding, without turning an employee’s email inbox into the permanent record of a client’s digital credentials. The intake application itself is protected behind Cloudflare Access — an authentication layer that sits between the user and a protected application and checks whether the user is permitted to enter before allowing access.
For agencies, the practical lesson is simple: your client-access workflow deserves the same deliberate design as the work you perform after you log in.
Quote of the month: “Repetition is not corroboration. Creation is not stewardship.” — Team Human, August 2026