MOONRAKER: SCHEMA DRAFTING PROMPT
Future Proof Your Practice, Part 3
Updated 16 September 2026

Use this prompt with your web team. Replace the brief with confirmed, public
practice information. Review the draft before adding it to a website.

PROMPT

Prepare appropriate JSON-LD structured data for this page.

Approved visible page copy: [paste]
Canonical page URL: [supply]
Practice name and website: [supply]
Relevant clinicians, qualifications and public verification links: [supply]
Services and confirmed service areas: [supply]
Actual office/contact details, if relevant to this page: [supply]
Existing site markup and entity @id values: [paste or say unknown]
Other confirmed public facts: [supply]

Requirements
- Read the page and choose appropriate schema.org types. Explain the choice.
- Use https://schema.org as @context and reuse existing entity identifiers.
- Include only facts represented accurately on the visible page.
- Use properties appropriate to each type. A Person or Service does not need
  every LocalBusiness property. Do not force an address or coordinates where
  they do not belong.
- Do not invent addresses, license numbers, NPI numbers, prices, hours,
  coordinates, ratings, profile URLs or clinical qualifications.
- If a needed fact is missing, ask or list it outside the draft. Omit
  unresolved values from the proposed JSON-LD.
- Do not automatically add rating or review markup.
- FAQPage is optional and must describe visible questions and answers.
  Do not promise Google FAQ rich results; that feature was retired in May 2026.
- Output a JSON-LD draft wrapped in a script tag with type application/ld+json,
  plus open questions and validation instructions. Do not modify or publish a site.
- Report validation honestly: name the actual tool and findings if you ran it;
  otherwise say "not yet validated". A model's review is not a validator run.

HUMAN REVIEW

Confirm the facts and relevance of the chosen types. Check for duplicate or
conflicting entity records. Validate vocabulary with https://validator.schema.org/
and check supported Google features with https://search.google.com/test/rich-results.
After implementation, inspect the served page and its visible information.
Update both the markup and the page when the practice changes.

Structured data describes information. It does not independently verify a
credential, guarantee a rich result or ensure a recommendation by an AI system.

REFERENCES
https://developers.google.com/search/docs/appearance/structured-data/sd-policies
https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
https://developers.google.com/search/updates#may-2026