What this site is
Coffee drinkers and roasters ask "what makes Yirgacheffe taste floral" or "what altitude does this varietal need." This encyclopedia answers with altitude bands, varietal facts, and flavor-family context, staying a shared reference layer distinct from any single roaster's bag-copy marketing claims.
How the catalog is organized
Facets cover country, altitude band, and dominant varietal (Bourbon, Typica, Geisha); altitude and typical yield stay numeric fields when regional co-ops or exporters publish them. A light optional map can show the growing region, since origin is genuinely geographic here, unlike a general cultivar entry.
Why roasters and coffee publishers pitch this niche
Origin-region facts are exactly what specialty-coffee shoppers search before buying, and consistent structured data beats inconsistent roaster marketing copy for AI citation. Roasters use the encyclopedia as a trust layer that sits beside, not inside, their commerce pages, and agencies resell the format across other origin categories.
Related surfaces
Complements hvce site wine grape cultivar encyclopedia and hvce site cheese aoc pdo reference for a full food-and-drink origin-authority cluster on one domain. Affiliate roaster hubs can cross-link for monetization without duplicating the same reference copy across every roaster's own site.
What ships with every page
Every reference profile is crawlable HTML with its own metadata, answer-first framing, structured data aligned to visible facts, and a clean text twin for answer engines—so authority bases stay trustworthy for learners and citable for search and AI systems.
Metrics
| Typical Catalog Size | 90 entities |
|---|---|
| Profile Depth Score | 4 |
| Facet Dimensions | 5 |
Descriptors
| Primary Monetization | affiliate |
|---|---|
| Discovery Surfaces | seo-aeo |
| Map Suitability | optional |
| Compare Suitability | optional |
| Delivery Mode | either |
| Buyer Persona | affiliate |
| Overlap Cluster | food-drink |
Frequently asked questions
Is this a roaster storefront?
No. It is an origin-region reference; roasters link out via CTAs to their own commerce pages.
Should altitude be a strict number?
Use a sourced band from a co-op or exporter; avoid inventing precise figures without a citation.
Why enable a map here?
Origin is genuinely geographic for coffee regions, so a light optional map adds real context.
Can multiple roasters use the same entity?
Yes—origin facts are shared reference data; each roaster's specific lot notes stay on their own pages.
How does this differ from a wine cultivar entry?
Same authority pattern, different commodity—altitude and varietal replace climate-affinity and color class as core facets.