Coffee Bag Product Pages: Title, Tasting Notes, Facts, Schema

Thomas Garner

Oct 7

11 min read

Open your own bag page right now. A name, a price, maybe a short line about the flavor. That is what most roaster sites give a search engine or an AI tool to work with, and it is not enough for either one to actually understand what the coffee is.

Short answer: a bag page is a set of facts first and copy second. The title states the coffee in plain terms, origin facts sit in a structured block a customer and a crawler can both read, tasting notes are a short honest line rather than a paragraph of poetry, and product structured data repeats what the page already says rather than inventing anything new. This post walks that anatomy with a worked example, the required and recommended properties as Google's documentation states them, and the differences across Shopify, Squarespace and Wix, so you can rebuild one bag page in a sitting and check it in a real testing tool.

This covers structure, not copywriting. If you are looking for guidance on writing tasting notes and origin copy that sells, that is a separate piece worth reading alongside this one. What follows here is specifically the anatomy: what facts go where, in what order, and how the schema underneath repeats what the page already says rather than inventing anything new of its own.

Title

A bag page title should state the coffee plainly: the origin or name, the process if it is a defining feature, and the word coffee itself, since a customer scanning a results page or an AI answer summarizing a search should not have to guess what kind of product this is. A title reading only as a farm or lot name, with nothing else, asks too much of an unfamiliar reader.

Worked example, using invented but realistic details: a washed process coffee from a fictional Ethiopian region, sold as a light roast, might carry the title Ethiopia Light Roast Washed Process Coffee. That title alone tells a reader the origin, the roast level, and the process, three facts a customer cares about, before they read a single word of description.

A second worked example, for contrast: a fictional house blend with no single traceable origin might carry the title House Blend Medium Roast Coffee, naming what it is, a blend, rather than borrowing the specificity of a single origin title it cannot honestly claim. The title's job is accuracy, not a marketing flourish, and a blend that is honestly titled as a blend reads as more trustworthy than one dressed up to sound more exotic than it is.

Keep the product name in the page's visible heading consistent with the title, rather than a shorter or differently worded version. A mismatch between the H1 a visitor sees and the title tag a search result shows creates a small, avoidable moment of confusion right when a visitor lands on the page, and it is one of the easiest inconsistencies to fix once you notice it.

Resist naming conventions that sound appealing internally but mean nothing to a first time visitor, an internal lot code, a playful nickname with no descriptive information attached. Those names can still appear on the page, in a smaller subtitle line beneath the main title if the roaster wants to keep them, but the title itself should lead with the facts a stranger needs to understand the product at a glance.

Tasting notes

Tasting notes belong on the page, and they should be short and honest rather than an extended piece of prose competing with the facts around them. Two to four descriptors, written plainly, do the job: something like bright citrus, honey, a light floral finish for the fictional washed Ethiopian example above. This is copy, not structured data, meant for a human reader deciding whether the flavor profile sounds appealing.

Keep tasting notes distinct from the facts block described next. Notes are a matter of judgment and description. Facts are verifiable. Blending the two, burying an actual origin detail inside a poetic tasting description, makes both harder to find for a reader skimming the page and for a crawler trying to extract either one cleanly.

A short worked example for the same fictional bag: Notes of bright citrus, honey and a light floral finish. That is a complete, honest tasting notes section for a bag page. It does not need to be longer to do its job well, and a shorter, specific line reads as more credible than an overwritten one reaching for language that does not describe the coffee.

It is worth naming a common trap here: borrowing language from a supplier's own sample description rather than describing what the roaster tastes in the finished, roasted coffee. A green coffee sample sheet and a finished retail bag do not always taste identical after roasting, and copying one onto the other without cupping the final product risks printing a description that does not match the coffee a customer opens. Tasting the actual finished product before writing its notes is worth the few extra minutes.

Facts

The facts block is where a bag page earns real trust, both from a customer and from anything reading the page automatically. Eight facts belong here where the roaster can honestly provide them: origin, process, variety, altitude, roast level, weight, roast date, and the tasting notes already covered above, restated briefly if useful.

Worked example continued: Origin, a fictional Ethiopian region. Process, washed. Variety, heirloom. Altitude, a fictional but realistic range such as 1,900 to 2,100 meters. Roast level, light. Weight, 12 ounces. Roast date, filled in accurately per batch rather than left as a placeholder. Laid out as a short labeled list rather than folded into a paragraph, this block is fast for a customer to scan and clean for a crawler to parse.

Notice what this block deliberately leaves out: no adjectives, no marketing language, no claims about how the coffee will make anyone feel. That kind of language belongs in the tasting notes section covered above, or in the shop's own about page describing its general approach to sourcing. The facts block earns its keep specifically by staying plain, since a reader who wants marketing language has plenty of other places on the page to find it, but a reader who wants the actual origin altitude has only this one place to look.

It is fine, and honest, to leave a fact out entirely when it genuinely is not known or does not apply, rather than inventing a plausible sounding number. A roaster who does not track altitude precisely should say so or omit the field, not guess at a range that sounds right. The value of this block depends entirely on every line in it being true.

This is also the place to be careful about claims beyond what can be proven. A certification, a specific sourcing relationship, a direct trade claim, only belongs here if the roaster can genuinely stand behind it, since an unverifiable claim printed as fact undermines the credibility of every other honest line on the page.

Batch specific facts, roast date in particular, are worth automating if the platform allows it rather than updating by hand on every page every time a new batch goes out. A roast date left stale for months is arguably worse than no roast date at all, since it actively misleads a customer checking freshness rather than simply leaving a gap. If automation is not available on your platform, build a simple recurring reminder into whatever schedule already governs restocking.

Schema

Google's structured data documentation for products centers on the Product type, generally paired with an Offer for price and availability, and a review or aggregate rating if genuine reviews exist. For a coffee bag specifically, the properties worth filling in include name, description, image, and brand at minimum, with offers carrying price, priceCurrency and availability. None of the origin facts above, process, altitude, roast date, have a dedicated schema property of their own, so they typically live in the description field or as additionalProperty entries rather than a purpose built field.

Whether a platform outputs this automatically differs meaningfully. Shopify generates Product schema by default on most themes, covering the core fields, though origin specific facts like process or altitude still need to be added manually, usually through the description or a metafield depending on the theme. Squarespace's product pages carry basic Product markup on many templates as well, with similar gaps around coffee specific facts. Wix requires either the Advanced SEO panel's structured data field or a custom code embed to add Product markup, since it is not guaranteed to be present by default on every store template.

None of these platform differences should be treated as a reason to switch platforms over this one issue alone. In every case described here, the gap is the same: a working starting block that still needs the coffee specific facts added by hand. That is a manageable, one time task per product template, not a reason to rebuild an entire store.

After publishing or editing a bag page's schema, run it through Google's Rich Results Test and the Schema Markup Validator, checking both for hard errors and for warnings. A warning about a missing recommended property, such as a rating with no actual reviews behind it, is worth reading carefully rather than dismissing, since it often points to a genuine gap in what the block currently describes.

A note on the aggregateRating property specifically, since it is tempting to fill in even when reviews are thin. Only include it when there are genuine, real reviews behind the number, never a placeholder or an estimated figure meant to make the product look more established than it is. A fabricated or inflated rating is exactly the kind of claim this project's own evidence rules exist to prevent, and the same standard applies to a roaster's own product pages.

It is worth being direct about what this markup does and does not do. Structured data helps a search engine and an AI tool understand a page more clearly. It is not a guarantee of a rich result appearing in search, and it does not by itself move a product page higher in results or increase how often it sells. Treat it as a foundation that makes the honest facts already on the page easier for a machine to read accurately, nothing more and nothing less.

Reviews themselves connect back to this same block once they exist, since a real Review or aggregateRating property should describe actual customer feedback, collected honestly and never invented or edited to look more favorable. Collecting and displaying reviews for coffee bags is its own larger topic, and once your shop has genuine reviews worth showing, that same aggregateRating property is the natural place they connect to the Product schema described here.

Frequently Asked Questions

What should a coffee bag product page include?

Four things: a title stating the coffee plainly, origin, process and roast level if relevant, a short honest tasting notes line separate from the facts, a facts block covering origin, process, variety, altitude, roast level, weight and roast date where known, and Product structured data repeating those same facts for a crawler to read accurately.

What is the difference between tasting notes and the facts block on a bag page?

Tasting notes are judgment, two to four plain descriptors such as bright citrus, honey, and a light floral finish, written for a person deciding whether the flavor appeals. The facts block is verifiable: origin, process, variety, altitude, roast level, weight, and roast date, laid out as a short labeled list. Keeping them apart makes each easier to find for a reader skimming and for a crawler extracting either one cleanly. Burying an altitude inside poetic copy hides it from both.

Does Shopify add Product schema automatically to coffee bag pages?

Shopify generates Product schema by default on most themes, covering core fields such as name, description, image, and an Offer with price, priceCurrency, and availability. Coffee specific facts such as process, altitude, or roast date are not in that automatic output. Add them manually through the product description or a metafield, depending on your theme, then check the result in Google's Rich Results Test and the Schema Markup Validator for errors and warnings.

Does Wix add structured data to product pages automatically?

Not on every Wix store template. Wix offers a structured data field in its Advanced SEO panel that accepts a Product block without custom code, or a custom code embed for more control. Either way, the block should carry name, description, image, brand, and an Offer with price, priceCurrency, and availability, with origin facts in the description or additionalProperty entries. Check it afterward in Google's Rich Results Test and the Schema Markup Validator to confirm it validates.

What facts should a coffee bag product page always include?

Where known, list origin, process, variety, altitude, roast level, weight, and roast date. For the fictional washed Ethiopian example that means an origin region, washed, heirloom, 1,900 to 2,100 meters, light, 12 ounces, and a roast date filled in per batch rather than left as a placeholder. Omitting a fact the roaster does not track is honest; inventing a plausible number is not, because the block's value depends on every line being true.

Will adding schema markup to my coffee bag pages help them rank or sell better?

This post makes no such promise. Product structured data helps a search engine or an AI tool read the facts already on the page more accurately, such as name, price, priceCurrency, and availability. Google's Rich Results Test can confirm the markup validates, but a valid block is not a guarantee of a rich result appearing, and it does not by itself move a page higher or increase sales. Treat it as a foundation, nothing more.

Should a coffee bag title include the roast level?

It is often worth including when the roast level is a defining feature of the coffee, alongside the origin or name and the word coffee itself. A title stating origin, roast level and process together, such as Ethiopia Light Roast Washed Process Coffee, tells a reader three useful facts before they read any further copy.

Can a roaster claim a certification or direct trade relationship on a bag page?

Only if it can be proven and stood behind. A certification, a specific sourcing relationship, or a direct trade claim belongs in the facts block beside origin, process, and altitude only when the roaster can document it. This post does not endorse claims beyond what is true, because one unverifiable line printed as fact undermines every honest line around it. The same standard covers aggregateRating, which should never hold a placeholder or estimated figure.

How do I test whether my coffee bag page's schema is set up correctly?

Run the page through Google's Rich Results Test and the Schema Markup Validator, both free, after any edit to the page or the platform's settings. Read the warnings as well as the errors, since a warning about a missing recommended property, such as a rating with no real reviews behind it, often points to a genuine gap. On Shopify, Squarespace, and Wix alike, the usual gap is the coffee specific facts that still need adding by hand.

Can Hillcane help build or fix coffee bag product pages for a roaster?

Yes. Hillcane works through this anatomy with roasters: a plain title naming origin, roast level, and process, a labeled facts block, a short tasting notes line, and Product schema with an Offer that repeats what the page says. The result gets checked in Google's Rich Results Test and the Schema Markup Validator, with platform specific steps for Shopify, Squarespace, or Wix. Reach out at hillcane.co/contact or call (256) 384-2449 to talk through your bag pages.

Work with Hillcane

Open your own coffee bag page right now. A name, a price, one short line. That is not enough for a search engine or an AI tool to actually understand the coffee.

If you want help rebuilding your coffee bag pages with a real facts block and working schema, reach Hillcane at hillcane.co/contact or call (256) 384-2449.