wSEO Technical Assessment Methodology

Scope and responsibility

The methodology covers technical SEO, indexability, delivery, performance and semantic HTML checks. An automated result is evidence for review, not a guarantee of rankings, traffic or revenue.

Automated and manual checks

Automated checks retrieve public URLs and inspect response chains, headers, HTML and detectable browser behavior. Manual review compares the result with the rendered page, templates, official documentation and the site’s intended behavior.

Tools may include browser developer tools, command-line HTTP clients, validators, Lighthouse and Search Console when access is provided. Tool name, version and test conditions are recorded when a quantitative claim is published.

Error and severity criteria

An issue is recorded only when observed evidence conflicts with a documented requirement or the agreed behavior. Severity reflects reach, impact, reproducibility and recovery cost; color is never the only severity label.

Evidence and false positives

Evidence may include response headers, reduced HTML extracts, screenshots and exported reports. Secrets and client data are removed. Ambiguous results are marked for manual review, and known tool limitations are recorded instead of being presented as confirmed errors.

Repeat verification and limits

After a fix, the same URL and relevant test conditions are checked again. Lab measurements, CrUX field data, user telemetry and single runs are identified separately. External systems, personalization, geography and cache state can limit reproducibility.

Measurement passport

A quantitative case records the measured URL; before/after date and time; device and viewport; browser and version; location and connection; cache and authentication state; tool and version; run count; median, p75 or single-run status; exact before/after values; implemented changes; source report; and limitations. If a historical report did not preserve a condition, the omission is stated explicitly rather than reconstructed.

Case evidence and privacy

Level A means public primary evidence and a client review; B means the source reports are available to the editorial team; C means the work and review are confirmed but complete analytics are unavailable; D is a demonstration and is not presented as a client case. Publication requires client permission and a separate privacy check for credentials, personal data, revenue figures and private projects.

Editorial responsibility

The author prepares the material and primary sources, the technical reviewer repeats key checks and validates conclusions, and the editor checks language, RU/EN meaning and unsupported guarantees. Publication, substantive review and evidence-review dates are stored separately from technical database timestamps.

Review cycle and corrections

Fast-changing guidance is reviewed every 3–6 months and stable technical guidance every 6–12 months. Version changes only when assessment rules materially change. Report a possible error to info@wseo.pw.