Separate signal from finding
A detected condition enters review without being treated as a confirmed defect.
Operating System // Human Quality Control Protocol
Detection is not diagnosis.
HQCP is Raptor's Human Quality Control Protocol. It determines whether a technical finding has enough direct inspection, reproducibility, corroboration, and business context to support action.
RAPTOR // FINDING VERIFICATIONV2 // REPRODUCED
DETECTED CONDITIONConflicting canonical signal on priority service templateSource // automated crawl report
V0DetectedComplete
V1InspectedComplete
V2ReproducedActive
V3CorroboratedPending
V4VerifiedPending
DECISION STATUSNot ready for remediation until the evidence supports the diagnosis.
Purpose // Control False Certainty
Tools surface signals. People determine meaning.
A crawler can report a redirect, duplicate title, canonical difference, missing field, or slow lab score. It cannot automatically determine the business context, affected scope, root cause, implementation risk, or whether the condition should be changed.
Require direct inspection
A person examines the page, source, template, configuration, or behavior involved.
Test the explanation
The suspected issue must be reproducible and supported beyond the original alert.
Define the action boundary
Verification records what the evidence supports and what remains uncertain.
Verification Ladder // V0 Through V4
Confidence increases one controlled step at a time.
The ladder records how far a possible finding has progressed. Higher levels require stronger evidence. A finding can pause, return for more inspection, or be rejected if the original signal does not survive review.
V0DETECTED
A possible condition enters the record.
A tool, report, stakeholder, or operator has surfaced a signal. At this level, the condition is neither accepted nor rejected.
REQUIRED // Source, affected location, detection date, and initial evidence.V1INSPECTED
A person reviews the actual system.
The affected URL, template, source, report, configuration, or behavior is examined directly instead of relying on the alert alone.
REQUIRED // Human inspection notes and observed condition.V2REPRODUCED
The condition can be observed again.
A defined test, path, query, device, user state, or technical method reproduces the issue and narrows the suspected cause.
REQUIRED // Reproduction method, result, scope, and exceptions.V3CORROBORATED
Independent evidence supports the finding.
A second tool, source, dataset, platform record, or technical observation supports the interpretation without merely repeating the original report.
REQUIRED // Independent source and agreement or conflict notes.V4VERIFIED
The finding is ready for a decision.
The evidence, business context, affected scope, and limits of the conclusion are strong enough to support prioritization and action planning.
REQUIRED // Verification notes, confidence, affected scope, and action boundary.Evidence // Corroboration Without Duplication
A second report is useful only if it adds independent support.
Running the same crawler twice does not automatically corroborate a finding. V3 should add a different observation, source, dataset, or method that can confirm, challenge, or narrow the interpretation.
Conflicting evidence is recorded. It is not hidden to protect the original assumption.
01Direct InspectionRendered page, source, headers, configuration, or system state.
02Independent ToolA separate crawler, validator, performance test, or platform diagnostic.
03First-Party DataSearch Console, analytics, server records, CMS data, or business records.
04Manual ReproductionA documented test path that produces the same condition.
Method Boundary // What HQCP Decides
Verification answers whether the finding is trustworthy.
HQCP does not decide business priority, implementation order, ownership, budget, or deployment timing by itself.
Once a finding reaches the required verification level, it moves into the Raptor Priority Model. Impact, confidence, effort, dependencies, risk, and logical order then shape the remediation sequence.
01
↓HQCPHuman Quality Control Protocol
Is the finding trustworthy enough to act on?02
↓Priority ModelHow important is the verified finding?
03
↓Implementation AssessmentWhat effort, dependencies, and risks shape the sequence?
04
Remediation RoadmapWho will do the work, when, and how will completion be verified?
Operating Artifact // ROA-SEO-001
The Workbook carries the verification record.
The Raptor Master Blueprint defines the methodology. The Technical SEO System Audit Workbook is the execution layer used to record findings, evidence, HQCP level, impact, priority, remediation ownership, and post-fix verification.
FIELD // 01Detection Source
FIELD // 02Evidence
FIELD // 03HQCP Level
FIELD // 04Verification Notes
FIELD // 05Confidence
FIELD // 06Post-Fix Verification
Applied Through // Audit and Evidence
Use the method where a wrong diagnosis carries cost.
HQCP is applied through technical SEO audits, search architecture work, structured data review, performance diagnosis, migrations, and evidence-based case records.
Raptor // Verify Before Action
Have an audit full of warnings but no trustworthy diagnosis?
Call or email Raptor directly. We can start with the reported conditions, inspect the affected system, and determine which findings are ready to support action.