Do Not Fire the Agency Until You Have Secured the Evidence

The first decision is whether you are dealing with weak results, poor communication, a contractual failure, or a false representation. These categories require different responses. An agency can perform agreed work and still fail to improve rankings.

It can also produce a positive traffic graph while failing to deliver the work listed in the agreement. Start with the exact statement under dispute. Write it in plain language, record when it was made, identify who made it, and note what evidence would confirm or contradict it.

A promise such as 'we optimized the service pages' is too vague until it is connected to named URLs, expected changes, completion dates, and a responsible person. A statement such as 'we published the approved revisions on these URLs on this date' is reviewable.

Next, compare the statement with the contract, task system, CMS history, repository history, analytics annotations, Search Console records, and copies of the page before and after the claimed work. Assign one of five findings: verified, partially verified, unverifiable, not delivered, or delivered outside the agreed scope.

This prevents a common mistake: treating every disappointing outcome as proof of deception. It also prevents the opposite mistake, accepting an attractive report as proof that contracted work occurred.

The operational lesson is simple. Outcomes may be uncertain, but inputs, decisions, changes, and deliverables should have a Reviewable Visibility trail. The owner of this review should be someone who can compare commercial terms with technical evidence, not the account manager whose work is being questioned.

The output should be an evidence table that lists the claim, contract reference, supporting record, finding, impact, and required response.

The Forensic Visibility Audit (FVA) is a verification exercise, not a general list of SEO recommendations. Build the audit from the statement of work and invoices so every test answers a commercial question.

Begin with account ownership and access. Confirm who owns the domain, hosting, CMS, repository, Google Search Console, Google Analytics, Google Business Profile, tag manager, reporting tools, and any call or form tracking systems.

Export current user lists and permission levels before changing anything. Then review implementation evidence. In Google Search Console, look for page discovery and crawl activity around the dates the agency says pages were created or materially changed, while recognizing that a crawl record alone does not prove the quality of the work.

In the CMS, repository, or hosting logs, identify actual edits, deployments, redirects, templates, scripts, and configuration changes. Use the Wayback Machine where relevant to compare public versions over the last six months, but treat missing captures as an absence of archive evidence, not proof that no work occurred.

Review content deliverables against approvals, publication records, and page history. Review links against the agency's placement list, live source pages, destination URLs, attributes, relevance, and ownership terms.

Test analytics events directly rather than relying on screenshots. For regulated content, compare published claims with the approved copy and the applicable internal review process. The audit output should not say merely 'SEO was bad.' It should identify exact discrepancies, their commercial or technical impact, the evidence still missing, and the corrective action required.

That record can support remediation discussions, a handover, or advice from qualified counsel without overstating what the evidence proves.

A disputed SEO engagement often contains a commercial design problem before it contains a technical one. The Incentive-Process Gap (IPG) appears when the client pays for a broad promise while the agency is accountable for few specific outputs.

In that arrangement, the agency can reduce account effort without creating an obvious contractual failure. Test the gap by mapping each fee to a required activity, owner, output, due date, acceptance rule, and evidence source.

For example, 'ongoing optimization' is not an operational commitment. A reviewable commitment names the pages or systems to be assessed, the decision criteria, the approved changes, the implementation owner, and the record that confirms completion.

Also compare the staffing represented during sales with the people who actually approve strategy and execute work. A junior team member is not inherently a problem, but billing for senior involvement that cannot be evidenced is a reviewable discrepancy.

Examine whether automated outputs are being presented as manual analysis, whether recurring reports replace substantive work, and whether the agency can explain why priorities changed from one period to the next.

Review the effective hourly rate only as a diagnostic, because a skilled team can create value without maximizing logged hours. The stronger question is whether the documented inputs and outputs justify the fee and advance the agreed objective.

The remedy may be a revised scope with deliverable acceptance, a credit, a remediation period, or termination. The decision owner should be the person accountable for budget and business results, supported by technical review where necessary. The output is a contract-to-process map that exposes where accountability is clear and where it depends on trust alone.

Technical risk is highest when performance depends on an asset that is hidden, temporary, or controlled by the agency. Review links, redirects, hosting configurations, scripts, content ownership, and third-party accounts before changing the relationship.

A 301 redirect from an expired domain is not automatically deceptive, but it requires a defensible reason, relevance, ownership record, and documented risk review. A Private Blog Network (PBN), undisclosed paid placement, hidden content, or removable agency-controlled link can create exposure that was never explained to the client.

Do not assume that every unusual link caused a ranking change. Record what exists, when it appeared, who controls it, what destination it affects, and whether its use was approved. Compare sudden link growth with the agency's placement records and invoices.

Confirm whether link attributes and disclosures match the nature of the placement. Identify domains, pages, or accounts that will be removed when payment stops. Review redirect chains and server rules for destinations that do not match the stated strategy.

Confirm that all content, creative files, research, data exports, and technical documentation created under the agreement can be transferred under the contract. For a regulated or high-trust business, add legal or compliance review when tactics affect advertising disclosures, claims, privacy, or reputation.

A single manual penalty is a serious possibility when guidelines are violated, but the audit should not claim a penalty exists without direct evidence. The output should be a dependency register showing each asset, owner, purpose, risk, transferability, and required action.

Most SEO reports are designed to be scanned, not read. Agencies often use colorful charts and 'upward-trending' lines to create a sense of progress. However, if you look closely, you may find that the data is decoupled from your bottom line.

For example, they might report a 50 percent increase in 'organic traffic,' but if that traffic is going to a single blog post about a trending news topic that has nothing to do with your services, that traffic has zero value.

In practice, I have seen agencies 'filter' data to hide negative trends. They might show you year-over-year growth while ignoring a significant month-over-month decline. This is why I advocate for Evidence over Promises.

A real report should link SEO activities directly to lead generation or sales. It should show how specific keyword improvements have led to more qualified inquiries in your specific industry. When I work with clients, I insist on Industry-Specific Metrics.

For a law firm, this might be 'calls from high-intent keywords.' For a healthcare provider, it could be 'appointment bookings from organic search.' If your agency is only reporting on 'rankings' and 'impressions,' they are likely hiding a lack of Conversion-Focused Strategy. You need a system that measures what actually matters to your board or partners.

Once the evidence supports termination, sequence matters. A rushed exit can interrupt tracking, remove useful assets, or leave the former agency with unnecessary access. The Clean Break Protocol (CBP) begins with an ownership inventory.

Confirm administrative control of the domain, DNS, hosting, CMS, repository, backups, Google Search Console, Google Analytics, Google Business Profile, tag manager, advertising accounts, call tracking, form systems, reporting tools, and any third-party platforms used for SEO work.

Preserve current user lists, configurations, exports, invoices, reports, work logs, communications, and copies of the disputed deliverables. Change passwords before notice where appropriate, but avoid disabling a system in a way that destroys logs or breaks active services.

Review the contract for notice, transfer, confidentiality, ownership, deletion, refund, dispute, and post-termination obligations. Request a final export of technical audits, content plans, keyword research, link records, implementation notes, open tasks, source files, and known risks.

Establish a handover date and a named recipient. Test backups and critical tracking before removing access. Communicate the decision calmly and factually, citing documented discrepancies rather than speculating about intent.

Where financial recovery or alleged misrepresentation is material, obtain qualified legal advice before making public accusations or taking irreversible action. After the handover, remove permissions, rotate credentials, verify the site, and record the final state.

The output should be a signed handover checklist showing asset ownership, transferred materials, unresolved risks, removed access, and the person accountable for each next step.

Generic advice often begins with firing the agency, publishing a complaint, or starting the website again. Those actions can destroy evidence, interrupt tracking, remove useful work, and weaken your position in a contractual dispute.

Other advice treats SEO as inherently unknowable, as though clients should accept vague explanations because outcomes are uncertain. Outcomes are uncertain, but work products are still reviewable. A content brief can be inspected.

A redirect can be tested. A page change can be compared with its prior version. A link placement can be identified. An analytics event can be triggered and verified. Recovery therefore starts with preserving the current state and comparing promised work with observable evidence.

The goal is not to prove bad intent. The goal is to establish what was agreed, what was represented, what exists now, who controls it, and what decision follows from that record.

The most useful question in a disputed SEO engagement is not whether the agency seemed trustworthy. It is whether another qualified person can reconstruct the work from the contract, decisions, records, and outputs.

When that reconstruction is possible, mistakes can be corrected and responsibility can be assigned. When it is impossible, even legitimate work becomes difficult to defend. Industry context also matters.

A legal, financial, or healthcare organization may need additional review for advertising claims, privacy, professional rules, or internal approvals. That does not mean every SEO decision is a compliance issue.

It means the operating process should identify which work requires specialist review and record that approval. The durable lesson is to trust a reviewable system more than a persuasive relationship. People can disagree about results, but a documented process makes the disagreement specific enough to resolve.

Day 1-7

Preserve evidence, confirm account ownership, and perform the Forensic Visibility Audit (FVA) against the contract and invoices.

Outcome: A factual list of work that is verified, partially verified, unverifiable, not delivered, or delivered outside scope.

Day 8-14

Review the Incentive-Process Gap and reconcile current reports with source systems, qualified leads, and agreed deliverables.

Outcome: A documented decision on whether the engagement can be repaired through remediation or no longer provides reviewable value.

Day 15-21

Execute the Clean Break Protocol and provide formal notice of termination if the evidence and contract support that decision.

Outcome: Control of the digital assets, preserved records, transferred work products, and a documented end to the partnership.

Day 22-30

Interview replacement partners using Reviewable Visibility, named ownership, acceptance criteria, and source-data access as evaluation requirements.

Outcome: A new partnership structured around evidence, process, measurable deliverables, and explicit governance.