Name the product and the intended audience
Ask the supplier to demonstrate the particular question and experience they mean. A patient comparing local clinics has a different task from a student researching a condition. Your practice needs relevant service enquiries, not visibility for every health-related question.
Keep the question, date, product and observed answer together. If the report changes products or questions later, it should explain the change before comparing results.
Inspect the work being proposed
The practical work might include correcting conflicting service facts, improving a useful page or resolving an access problem. Ask which public pages will change, which facts your team must approve and what completion evidence you receive.
Do not assume that a package name means a separate set of website changes is required. Compare it with the work your current SEO or website supplier already undertakes.
Avoid a guaranteed citation
Google's guidance for AI features in Search explains eligibility and existing SEO practices. It should not be stretched into a promise that the Gemini app will recommend a particular clinic. Ask the supplier for current documentation supporting any specific technical claim.
A single successful demonstration may show that an answer appeared once. It does not establish consistent visibility for prospective patients.
Judge progress by useful outcomes
Correct factual errors because they matter to readers. Monitor relevant referral activity and enquiries where measurable. Keep observed mentions separate from visits, bookings and clinical suitability. A modest, explained test is easier to assess than a claim to dominate Gemini.
Sources and further reading
Choose a useful next step
Bring a proposed scope or sample report. We can help you identify the practical work and the claims that need evidence.
