Start with a real page and a clear purpose
Ask the supplier to show one page, the information visitors can read and the labels proposed for it. The labels should describe the page accurately. An organisation name or article author is useful only if it matches the real organisation or author.
For example, a practice that has moved should update its visible address and any stored address labels together. A technically valid label containing the old address still gives the wrong information.
Separate eligibility from a promise
Some supported types can make a page eligible for an enhanced Google result. Eligibility does not guarantee that Google will display it or improve the page's position. Ask which current Google feature the supplier means and whether this particular page meets its requirements.
Google says FAQ rich results stopped appearing on 7 May 2026. Useful questions and answers can remain on your website, but a proposal should not promise FAQ drop-down listings. Speakable labels are also not a universal route into voice assistants or AI answers.
Ask for evidence you can understand
- Which pages and facts will change?
- Which supported feature, if any, is relevant to this page?
- Does the published page pass the appropriate validation checks?
- Who updates the labels when our locations, services or authors change?
A test passing means the checked markup meets the test's requirements. It does not establish clinical accuracy, guarantee a special search appearance or show that an enquiry was generated.
Decide where this work belongs
Correct inaccurate labels and genuine implementation faults. Compare optional additions with more immediate problems such as an unclear service description or a broken contact route. Ask for a small, explained scope rather than a long list of schema types applied indiscriminately.
Sources and further reading
Choose a useful next step
If a proposal includes structured data, ask us to explain what it would change for your actual pages and how the work would be checked.
