Preparing the sample workspace…
Product guides
Use these guides to move from account setup and a verified brand to a labelled benchmark, evidence review, remediation, follow-up, billing and data-rights support.
02 / Deliverables
A start-to-first-evidence orientation
A checklist for reading observations and coverage
A safe remediation and follow-up workflow
Clear account, billing, support and privacy destinations
03 / How it works
Create an account through the configured identity provider, complete the organisation setup, and invite only people who need access. Account security, sessions, members and invitations are managed from Settings.
Identity-provider verification, recovery and MFA must be completed with the configured provider; Ekvidu does not create a second password store.
Add the authorised website, record its market and competitors, and complete domain verification before treating it as an owned brand. The product will not let an operator silently mark a domain as verified.
Freeze the buyer questions and declared benchmark conditions before a collection run so later evidence and comparisons have an auditable denominator.
Start with coverage: planned, valid, invalid, retried, cancelled and not-run cells remain distinct. Then inspect the exact question, declared provider or model, acquisition method, answer excerpt, mention and cited source.
A mention is not automatically a citation. A citation is not automatically a visit, and a visit is not automatically a conversion.
Choose a recommendation only when its supporting evidence is visible. Record the intervention, affected surface and deployment proof, then wait for recrawl and run a fresh compatible follow-up.
Keep, revise, revert or stop the experiment based on the measured follow-up and its limitations. Never publish an unsupported causal claim.
Reports retain their frozen methodology, coverage and evidence lineage. Sharing is scoped and revocable; scheduled delivery is available only when the delivery process is configured.
Billing Settings shows the authoritative plan and subscription state for enabled environments. Use authenticated Support for product questions, and the data-rights workflow for access or deletion requests.
04 / Limitations
05 / Next step