Tanzeel

Service 03Profile diagnosis

Know what theprofile is doingbefore adding to it.

A manual backlink audit for inherited, declining, or penalised domains — with evidence for what to keep, what to investigate, and what to remove from the next plan.

6 of 18 links flagged after manual review, not a tool score

Manual review of an inherited or declining profile — what to keep, what to investigate, and what to remove before anything new is built.

Commissionable services
03/03
Method stages
06
Deliverables
07
01The problem

A toxicity export looks like an answer.It is a spreadsheet that still needs a decision made on it.

  • A tool score with no context

    The same flag applied whether the domain is genuinely dangerous or simply unfamiliar to the tool that scored it.

  • No acquisition timeline

    Nobody can say when a suspicious cluster arrived, which makes it impossible to connect it to a traffic change with any confidence.

  • Isolated flags, no pattern

    Networks, sitewide links and shared outbound behaviour matter more than any single domain's score — and a row-by-row export cannot show that.

  • Disavowal as a reflex

    Everything flagged gets disavowed, including links that were doing no harm and quietly removing useful signal along with the risk.

  • The roadmap treats everything as equally broken

    Urgent cleanup, passive monitoring and future acquisition conditions, all handed over with the same priority.

  • No manual review at all

    A risk decision that affects the domain's recovery, made entirely by an automated column nobody opened to check.

02What it is

Same forty links. Two different things.

Strategic systemRandom placements

Drag the divider — or use the arrow keys

What it is
A manual backlink audit: link history, anchor concentration, target-page distribution, domain patterns and traffic timing reviewed together, ending in a prioritised roadmap and a disavow file only where the evidence supports one.
What it is not
An automated toxicity export handed over as a spreadsheet, with the keep-or-remove decision left for the client to make and no manual review behind any of the flags.
03Who it is for

Six situations, six sets of publications.

01

SaaS companies

Products whose buyers search the problem long before they search the category.

In the record

  • Lumin PDF
  • CloudCall
  • Agistix

02

Local service businesses

One chain per market: the service, the city, a topic that belongs to both.

In the record

  • Beltway HVAC
  • Voyager Plumbing
  • Spartan Plumbing

03

Multi-location brands

Service-area pages that each need their own authority, not one campaign stretched thin.

In the record

  • Select Garage Door
  • Beltway HVAC

04

Real estate companies

Community and development pages, where the market name is the search.

In the record

  • Rodland Real Estate

05

Technology platforms

Category pages competing against directories and every other agency in the city.

In the record

  • Texas Web Design
  • Infintech Designs
04The method

One opportunity, six decisions.

  1. 01

    Establish the timeline

    Access, exports, known campaigns, migrations, traffic changes and any manual-action history put on one chronology before anything is classified.

  2. 02

    Classify the profile

    Domains, anchors, targets, networks and acquisition spikes grouped so the profile reads as behaviour rather than isolated URLs.

  3. 03

    Establish context

    Industry, market, acquisition history and the date of any traffic loss are set before a single link is labelled risky or safe.

  4. 04

    Review the evidence manually

    Material domains opened, ownership and outbound patterns checked, and ambiguous cases separated from clear risk.

  5. 05

    Build the disavow file

    Included where the evidence justifies it — never as a default artefact for a package that expects one.

  6. 06

    Sequence the roadmap

    Urgent cleanup, monitoring, internal fixes and the conditions required before acquisition restarts, ordered rather than flattened into one list.

ResultA verified live URL, logged against the campaign.

05Deliverables

Seven things that exist afterwards.

Every row is an artefact — something you are holding at the end of a week. None of them is an outcome, because an outcome is not something a supplier can hand over.

  • Domains, anchors, destination pages, acquisition patterns, loss timing and competitor context covered in one pass.

  • Access, exports, known campaigns, migrations and traffic changes placed on one chronology before classification starts.

  • Flagged domains grouped by reason and confidence, with manual evidence attached to the decisions that actually matter.

  • Material domains opened and checked by hand — the review's own evidence, not a summary of a tool's opinion.

  • The subset of flagged domains where the pattern, not a single score, supports treating them as genuine risk.

  • Included only where the evidence justifies it, so a client is never asked to remove signal that was doing no harm.

  • Cleanup, monitoring, on-site dependencies and the conditions required before acquisition restarts, ordered by priority.

How an engagement is scoped and priced
06Evidence

What the record actually holds.

Tracked placements

48

Client accounts

1

Industry verticals

1

In the largest campaign

48

Audits investigate a profile rather than add to the delivery record, so this page cites one related account rather than summing placements — the record's figures belong to the acquisition services above.

07Featured campaign

One account, reviewed with the same discipline an audit applies

Voyager Plumbing

48

Tracked placements

  • Local plumbing, San Diego County
  • Five-month record, one row rejected on review
  • Disclosed rather than quietly dropped from the total

What the review checked

  • Acquisition timing
  • Anchor concentration
  • Target-page distribution
  • Source-domain pattern

San Diego plumbing and service-area pages. One product, opened into the questions its buyers were already asking somebody else.

See the delivery ledger
08Before you commit

The questions that decide it.

  • No. A disavow is included when the evidence supports it, not because the package needs an artefact. Many strange-looking links can be ignored safely; unnecessary disavowal can remove useful signals.

  • No. A decline can involve content, technical changes, competitors, demand or algorithms as well as links. The audit narrows the evidence and defines the next action; it cannot control Google's response.

  • Not inside this scope. The audit supplies the evidence, cleanup record and recovery roadmap. A reconsideration request can be scoped separately if the case genuinely requires it.

  • Yes, as a separate engagement once the baseline is understood. In some cases the right answer is to pause acquisition until cleanup or on-site work is complete.

  • That is reported as the finding. A short cleanup list and a clear baseline is a better outcome than a padded disavow file manufactured to justify the engagement.

  • A tool can flag a pattern; it cannot tell you whether a domain is relevant to this business or whether a strange anchor is dangerous in the context of the whole profile. Material domains here are opened and reviewed by hand before anything is classified.

  • Full findings typically land in two to three weeks, covering the timeline, classification, manual review and the roadmap. Complex or long-lived profiles can run longer — that is scoped at the outset, not discovered partway through.

  • No. No audit can promise that a manual action will be lifted or that a decline reverses. What it guarantees is a defensible baseline: evidence for what to keep, investigate, and remove before anything new is built.

Available for projects

Still something here unanswered?

Send the question with the domain and the page it is about. It is read the same day, by me — there is no auto-responder.

Start here

Inherited a profileyou would not defendin a review?

Send the domain, the date the problem became visible, and any known campaign history. The reply says what evidence is needed before an audit is scoped.