Structured data is a machine-readable description of page entities and content. It should mirror visible, supportable information. It is not a substitute for useful content, and adding markup does not guarantee rankings, rich results, local visibility, or inclusion in Google AI Overviews or other Google AI features.
1. LocalBusiness + ProfessionalService
Evidence required: the generated markup, the visible contact and practice information, and the source-of-truth business records. Pass: the type and properties accurately describe the real practice or practitioner context. Fail: the markup invents a location, service, credential, review, or relationship. Severity: high for false professional claims, otherwise medium. Owner: developer and practice reviewer. Corrective action: remove unsupported properties. Validation: inspect the rendered source and re-test the deployed page.
<script type="application/ld+json">
{ "@context": "https://schema.org", "@type": "ProfessionalService", "name": "Your Practice Name", "address": { "@type": "PostalAddress", "streetAddress": "123 Main St", "addressLocality": "Portland", "addressRegion": "OR", "postalCode": "97201" }, "telephone": "+15035551234", "areaServed": "Portland, OR", "credential": "Licensed Clinical Psychologist, Oregon Board #12345", "availableService": "Anxiety Therapy, Trauma Therapy, Depression Treatment"
}
</script>
2. FAQ Schema
If a page visibly answers 4-6 useful reader questions, the content itself may be valuable. Evidence required: visible questions and answers plus any corresponding markup. Pass: the markup matches the visible text and current structured-data guidance. Fail: hidden, contradictory, or unsupported FAQ content is marked up. Severity: low to medium. Owner: developer and editor. Corrective action: align or remove the markup. Validation: compare rendered copy with JSON-LD. FAQ content may help readers, but do not claim FAQPage markup can earn a Google FAQ rich result.
3. Review/AggregateRating Schema
Evidence required: the exact visible review content, rating source, eligibility under current search documentation, and corresponding markup. Pass: a responsible implementer has confirmed that the page and entity qualify and that every marked-up value is visible and supportable. Fail: ratings are copied from another platform without an appropriate basis, self-serving review markup is used where not eligible, or the values do not match visible content. Severity: medium to high. Owner: SEO implementer and reviewer. Corrective action: remove unsupported review properties. Validation: test the final page and inspect any search enhancement separately from ranking performance.
Implementation: If code is managed directly, add JSON-LD only after the source facts are approved. If a plugin such as Yoast SEO or Rank Math generates markup, inspect its output rather than assuming defaults are correct. Use Google's Rich Results Test where applicable for syntax and eligibility checks, while remembering that a passing test is not a visibility guarantee.