adding-schema-markuplisted

# Adding Schema Markup ## Overview Schema is the language Google and LLMs use to understand a page. Crawlers extract entities, relationships, and facts from JSON-LD with much higher confidence than from raw HTML. In 2026 the Google rich-result surface has narrowed sharply (HowTo retired, FAQPage limited to gov/health authority sites) [1][2], but the AI-citation upside has grown: pages with well-formed structured data are cited 2.5–3.2× more often in ChatGPT, Perplexity, and AI Overviews than unstructured pages [3][4]. The job: pick the right type, populate the required + key recommended fields **from content that actually exists on the page**, validate, ship. ## When to Use - A new content page (article, product, itinerary) is going live - A page already has bootstrap-level `Organization` + `WebSite` schema and now needs page-specific markup - An audit flagged "no structured data" on important pages - A page is getting AI-search impressions but few citations — schema gap is a likely cause **Don't use for:** thin pages with no real content (Google penalizes schema-for-content-that-isn't-there [1]), legal/disclaimer/utility pages, or pages already covered by a route-level generator. --- ## Schema Type Decision Table | Page type | Schema type | Notes | |---|---|---| | Blog post / news article | `Article` or `BlogPosting` | Use `NewsArticle` for time-sensitive news only | | Long-form guide | `Article` + `BreadcrumbList` | Add `mainEntityOfPage` | | Product page | `Produc