Answer first
ModelBreeder.com uses metadata to make the page purpose unambiguous. Metadata is treated as a compact summary of the page, not a separate persuasion layer. The generated coverage file lists route titles, descriptions, sections, source counts, schema profile, and whether the page has a visible answer-first heading.
Coverage goals
- Every public guide should have one clear topic.
- Every guide should have a readable title and useful description.
- Every guide should expose an updated UTC date.
- Important guides should point to source reports.
- Structured data should describe only content visible on the page.
- Search and generative discovery files should point back to canonical human pages.
Metadata surfaces
| Surface | Implementation |
|---|---|
<title> | Uses meta_title when present, otherwise the guide title plus site name. |
| Description | Comes from front matter and is visible in cards, search results, route inventory, and Open Graph. |
| Canonical | Generated from the configured production origin and current route. |
| Article data | TechArticle JSON-LD includes headline, description, author, review context, date, section, level, and tags. |
| Breadcrumbs | BreadcrumbList JSON-LD follows the visible section breadcrumb. |
| Source support | Guide source reports are shown in the page source panel and counted in the generated route inventory. |
Generated evidence
Use @@MBTOKEN0@@ to inspect the current coverage record. It is generated from the same file-backed content that renders the public site.
Source reports used for this guide
These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.