We want to add Schema Markup (JSON-LD) to build a standardized, structured metadata API directly into our HTML <head> to give web crawlers a clean object model to parse.
Additionally, Voice assistants (Siri, Alexa, Google Assistant) rely heavily on structured Q&As, so a properly configured Answer.text property acts as a read-ready script.
Core Schema types we want for our help center:
  1. TechArticle (highest priority)
For individual help articles (e.g., "Send a Message", "Download Dialpad"). This is the most impactful schema for a help center.
Fields: headline, description, datePublished, dateModified, author, articleSection (maps to the category like "Calls & Messages")
  1. FAQPage
Many help articles are structured as question-and-answer content. Adding FAQPage with Question + Answer pairs can earn FAQ rich results directly in Google SERPs — high-value for support queries.
  1. HowTo
For step-by-step setup and configuration guides (e.g., "Set Call Routing Rules", "Set a Custom Ring Duration"). Enables rich result display with numbered steps.
  1. BreadcrumbList
The site has a clear hierarchy: Help Center → Category → Article. Breadcrumb schema improves navigation display in search results.
  1. WebSite + SearchAction (Sitelinks Search Box)
The homepage has a prominent search bar (CTRL + K). Adding SearchAction on the WebSite schema can surface a search box directly in Google results for the brand.
  1. VideoObject
The homepage and articles embed YouTube videos (e.g., tutorial videos). Marking these up can enable video rich results and carousels.
  1. Organization
On the homepage/footer to establish Dialpad's identity — name, logo, social profiles, contact URL. Supports knowledge panel accuracy.
  1. SoftwareApplication
For pages describing the Dialpad app itself (download page, feature pages)
·