FAQs and medical schema
Page patches preserve omitted FAQ and schema fields. Send only information supported by the visible page and the practice’s confirmed services.
Update FAQs
Section titled “Update FAQs”Set patch.faqs to the complete intended question-and-answer collection:
{ "expectedRevision": 3, "patch": { "faqs": [ { "question": "How do I arrange a consultation?", "answer": "Contact our office to discuss your goals and arrange a consultation." } ] }}This replaces the page’s FAQ collection. Include every question and complete
answer you want to retain. Use an empty array only when you intend to remove
the collection. Leaving faqs out keeps the existing collection.
The renderer derives FAQ structured data from the visible questions and answers
and removes stale retained FAQPage nodes. FAQ markup does not guarantee a
search enhancement.
Update medical page metadata
Section titled “Update medical page metadata”This patch changes the page type while preserving other schema fields:
{ "expectedRevision": 3, "patch": { "schema": { "pageType": "MedicalWebPage" } }}Supported schema fields
Section titled “Supported schema fields”| Field | Type | Meaning |
|---|---|---|
pageType |
String | WebPage, MedicalWebPage, AboutPage, ContactPage, CollectionPage, ProfilePage or ItemPage |
mainEntityId |
URL | Identifier for the page’s main entity |
service |
Boolean | Whether the page represents a service |
nodes |
Array | Supported structured entities associated with the page |
medicalClinic |
Object | medicalSpecialty, practitionerId and availableService |
Structured nodes require @type. Supported types are Service,
MedicalProcedure, SurgicalProcedure, MedicalTherapy, MedicalCondition,
Person, Organization, MedicalClinic, Physician, WebPage and
MedicalWebPage.
Optional node fields are @id, name, description, url, image,
medicalSpecialty, procedureType, bodyLocation, serviceType, areaServed,
provider, mainEntityOfPage and about. The last three are entity references
of the form {"@id":"https://example.com/#entity"}.
Supplied schema arrays, including nodes and availableService, replace their
complete arrays. Read the current page and carry forward the entries you need.
Unsupported fields fail validation instead of silently disappearing.
The main practice and practitioner identity remains managed by PulpSense. Preview the saved revision to check that its visible content and structured data stay consistent.