Editorial standard

How XScanHub checks product signals before making recommendations

This methodology exists so a tool page reads like a decision surface, not a directory card. We verify the highest-impact product signals, say where confidence is limited, and point out fields that can move faster than our last review.

Official-source checks firstUnknown beats guessedTradeoffs stated plainly

What we verify

  • Official site reachability, core product access, and whether the product still resolves as expected.
  • Pricing structure, real free-entry claims, and whether paid gating is obvious before signup.
  • API availability, docs quality, integration cues, and developer handoff readiness.
  • Region-specific access signals such as China availability, login friction, export options, and workflow constraints.

What changes fastest

  • Pricing tiers, credits, and plan packaging can move without much notice.
  • Regional availability, waitlists, and login requirements can change faster than feature descriptions.
  • API access, rate limits, and enterprise-only controls often change before marketing copy catches up.

How recommendation judgments are made

1. Verify the product signal

We start with the official site, visible pricing, documentation, and entry flow instead of relying on recycled summaries.

2. Score the decision pressure

We weigh the signals that matter most to a buyer: task fit, budget risk, onboarding friction, and workflow compatibility.

3. Publish the tradeoff, not just the pitch

If a tool is strong for one use case but weak on access, pricing clarity, or regional support, we say that directly.

How to treat unknown or stale fields

Unknown

Treat unknown fields as unresolved, not negative and not confirmed. We leave them open when we cannot verify them confidently.

Fast-changing

Re-check price, access, and API details before purchase, rollout, or migration. Those fields move the fastest.

Stale or mismatched

If a tool page conflicts with the official product page, trust the official source first and send us the mismatch.

How to report outdated information

Report broken pricing, access changes, removed APIs, or regional availability mismatches. We would rather mark a field unknown than leave a false signal live.