Keep a commercial rename understandable while search and AI systems catch up.
Verify Presence records legacy references, canonical evidence and answer drift without pretending every external system updates at once.
How the workflow works
The scope stays bounded from observation through remeasurement.
- Inventory old and new names and routes.
- Preserve necessary historical explanation.
- Measure branded and category questions separately.
- Track redirects, canonicals and answer changes over time.
What the customer receives
Every output remains attributable to its source and period.
- Rename register
- Legacy-domain route map
- Public evidence migration checklist
- Comparable transition measurements
Human-review boundary
Configured tools can support collection, comparison and drafting; controlled launch may use disclosed human assistance. Material facts, external publication and insufficiently evidenced changes remain human decisions.
- Confirm evidence before it informs diagnosis.
- Approve an exact version, not a moving draft.
- Revoke access or sharing when the authority ends.
Measurement limit
A correct redirect does not prove that search or AI systems have completed reprocessing.
- Small prompt sets are directional.
- AI answers can vary between runs.
- No ranking, recommendation or revenue guarantee.
What to know before you begin
What is fixed for comparison?
The prompt wording, target scope, measurement date, provider/model context and classification method are recorded. Material scope changes create a new version.
How is routine work delivered?
Configured tools can support scheduled collection, evidence matching, drafting and comparable remeasurement within configured permissions. Controlled launch may use disclosed human assistance, and sensitive changes retain human approval.
Does a better result prove the intervention caused it?
No. A measured difference is recorded with its limitations and does not automatically establish causation.