How we verify and publish profiles

We do not publish a profile just because we scraped something from HTML. Our standard requires verifiable facts, clear structure, and a trust/provenance layer.

Required baseline

• Official site or another clear official source.
• Basic identity, contacts, and geography.
• Clear description of services and specialization.
• Separation of confirmed facts from unknown claims.

Quality statuses

• ready: profile passes quality gate and can be delivered/published.
• needs_review: profile can be improved but is not safe for automatic paid delivery.
• blocked: profile lacks critical quality signals and requires manual intervention.

Control Room and enterprise flow

For ongoing monitoring we use the Control Room to track source evidence, crawler access, freshness, conflicts and owner-review tasks. Enterprise work can add a structured questionnaire, fit/not-fit constraints, stronger official routes and custom review logic. This is quality control, not just adding more text.

Related guide: Extended profile questionnaire.