User-feedback methodology

Reviews generate verification questions, not failure rates

Public reviews are self-selected, can be invited or incentivized, may describe different products and dates, and can be manipulated. Web Host Lens does not convert them into a provider reliability score.

No star average as quality proofRecent themes separatedPlan context requiredPolicy cross-check before conclusion

Collection protocol

  1. 01

    Define the sample

    Record platform, visible date range, visible sample size, sorting/filtering and whether reviews appear invited or organic.

  2. 02

    Remove unusable records

    Exclude duplicates, content without a hosting experience, undisclosed incentives, obvious spam and reviews of unrelated products.

  3. 03

    Code themes

    Separate billing, renewal, cancellation, support access, resolution, migration, uptime, performance, email and account-security reports.

  4. 04

    Preserve context

    Record provider product, plan, country, date and outcome when the reviewer supplies them; mark missing context.

  5. 05

    Cross-check

    Compare recurring claims with official policy, status history and reproducible independent evidence.

  6. 06

    Publish boundaries

    Describe themes and example verification questions without claiming population prevalence or a causal rate.

Provider feedback files

Theme-led, not score-led

Each page identifies what feedback can help verify and what it cannot establish.

User-feedback research

Hostinger

Recurring purchase, operation and exit themes translated into pre-sales questions.

Open feedback file →User-feedback research

Namecheap

Recurring purchase, operation and exit themes translated into pre-sales questions.

Open feedback file →User-feedback research

DreamHost

Recurring purchase, operation and exit themes translated into pre-sales questions.

Open feedback file →User-feedback research

SiteGround

Recurring purchase, operation and exit themes translated into pre-sales questions.

Open feedback file →User-feedback research

IONOS

Recurring purchase, operation and exit themes translated into pre-sales questions.

Open feedback file →User-feedback research

Cloudways

Recurring purchase, operation and exit themes translated into pre-sales questions.

Open feedback file →User-feedback research

Kinsta

Recurring purchase, operation and exit themes translated into pre-sales questions.

Open feedback file →User-feedback research

WP Engine

Recurring purchase, operation and exit themes translated into pre-sales questions.

Open feedback file →User-feedback research

Bluehost

Recurring purchase, operation and exit themes translated into pre-sales questions.

Open feedback file →User-feedback research

GoDaddy

Recurring purchase, operation and exit themes translated into pre-sales questions.

Open feedback file →User-feedback research

HostGator

Recurring purchase, operation and exit themes translated into pre-sales questions.

Open feedback file →

Regulatory and platform boundaries

FTC Consumer Reviews Rule Q&A

Fake, purchased, insider and suppressed review risks.

Open source ↗UK CMA fake-review guidance

Business duties concerning fake and concealed incentivized reviews.

Open source ↗Trustpilot platform

Open review platform; collection and sample composition must still be recorded.

Open platform ↗