A One Page Cafe Schema Checklist You Can Print and Run
You have been told schema matters. Nobody has shown you what done actually looks like. This post fixes that with one printable page, grouped into four sections, scored on a simple 0 to 2 scale, ending with the three fixes that carry the most weight.
Short answer: most cafe sites need a small number of correct things, not thirty scattered worries. Basics first, name, address, hours, phone, type of place. Advanced items second, menu, events, FAQ content, only if you have that content to mark up. Testing third, because markup nobody has checked is markup nobody can trust. Ongoing fourth, because a site changes and schema needs to change with it. Run the whole page in about twenty minutes and you will know exactly where to start.
This is not the complete guide to schema for coffee shops, which explains the topic in full elsewhere. This is the run sheet. Print it, work through it, and stop as soon as you know your next move.
Basics: The Items Nearly Every Cafe Site Needs
Score each item 0, 1, or 2. A 0 means the item is missing entirely. A 1 means it exists but is incomplete or generic. A 2 means it is present, specific, and correct.
1. Place type marked up as a real business type, not a generic placeholder. Google's Local Business structured data documentation names the required and recommended properties for this, and schema.org's own CafeOrCoffeeShop type exists specifically so a coffee shop can identify itself as exactly that, not a generic store or restaurant. 2. Business name matching what appears everywhere else, your Google Business Profile, your sign, your own header text. 3. Street address, complete and exact, matching your Google Business Profile down to the unit number. 4. Hours, in a structured format a machine can parse, not only a sentence buried in a paragraph. 5. Phone number in a consistent, clickable format. 6. Website URL pointing to the correct canonical page, not a redirect chain.
Score these six items honestly. A shop scoring a 2 on all six has the actual floor most cafe sites should be standing on, and nothing more advanced than this. If you score a 0 or 1 on more than two of these six, stop here. This is your starting point, and nothing later on this page matters until these six are solid.
This group alone accounts for most of what the Southeast audit vintage flagged as a real gap. Among the 201 shops audited in 53 Southeast cities, score bands broke down as Invisible 21, Brochure 67, Trying 12, and Methodical under 1 percent, with a blog zero rate of 83 percent and a platform stat of 148 of 201, or 74 percent, tied to how the underlying platform handles markup by default. That vintage is quoted here exactly as it appears in the live audit posts, and it should not be mixed with the newer 40 point census scores used elsewhere in this checklist.
It is worth understanding why these six items get so much weight rather than treating the weighting as arbitrary. Every other property on this checklist, menu items, event dates, FAQ answers, sits inside the same overall block as these six. If the place type itself is wrong or missing, a validator has no reliable container to attach the rest to, which means a perfectly written menu block can still fail to validate cleanly because the foundation underneath it is broken. Fixing the basics first is not a stylistic preference. It is the order the underlying technology requires.
Advanced: Only If You Actually Have the Content
This group is conditional. Do not mark up something you do not have. A menu block with no real menu behind it, or an event block for an event that does not exist, is worse than no markup at all, because it tells a validator and potentially a search feature something false.
7. Menu items, if you maintain an online menu, marked up with real names and categories rather than a scanned image. 8. Event markup, if you host a recurring open mic, a cupping, a roastery tour, or any other real, scheduled event, with a real date and location. 9. FAQ content, if you have a genuine set of questions customers ask, wifi, parking, dietary options, not invented questions stuffed in purely for markup's sake. 10. Aggregate review markup, only if you have a real, current review count you are allowed to display this way, and only pulled from a source that permits it.
Score these the same 0 to 2 way, but treat a 0 here differently than a 0 in the basics group. A missing menu block is a missed opportunity. A missing place type in the basics group is a foundational gap. Weight your attention accordingly: fix every basics item before spending a minute on this group.
A common mistake worth naming directly: copying a generic FAQ template from a guide like this one instead of writing your own actual questions. A generic FAQ block with questions no customer of yours has ever asked reads as filler to anyone checking closely, human or machine, and it can do more harm than leaving the FAQ property out entirely. If you cannot think of at least three real questions your own customers ask at the counter, skip this item for now rather than inventing content to fill it.
Testing: Confirming the Markup Actually Works
Markup you have not tested is markup you are only hoping works. Two free tools exist specifically for this. Google's Rich Results Test checks whether your structured data is eligible for the rich result types Google currently supports, and flags errors and warnings by name. The Schema Markup Validator checks your markup against the schema.org vocabulary more broadly, independent of whether Google currently surfaces a rich result for that type.
11. Run your homepage through the Rich Results Test and record what comes back, pass, warning, or error, with the date you ran it. 12. Run the same page through the Schema Markup Validator and do the same. 13. If either tool flags an error, not a warning, fix it before moving on, since an error generally means the markup is broken in a way that could prevent any of it from being read correctly. 14. If a warning appears for an optional property you have not filled in, note it and decide deliberately whether it is worth adding, rather than leaving it as an unexamined gap.
Score this group pass or fail rather than 0 to 2, since testing is binary in a way the content groups are not. Either your markup validates cleanly or it does not, and either way you now know instead of guessing. Save a screenshot or a note with the date every time you run this, since schema can break silently after an unrelated site update, and a dated record is the only way to know when something changed.
Understand the difference between the two tools before you rely on either one alone. The Rich Results Test is Google specific, checking your eligibility for the particular rich result types Google currently supports, which means it can pass cleanly while still missing a property another tool would flag as incomplete. The Schema Markup Validator checks against the broader schema.org vocabulary itself, independent of any one search engine's current feature set. Running both gives you a fuller picture than running either alone, and neither substitutes for the other.
Ongoing: What Keeps This From Going Stale
A schema block is not a one time task. It goes stale the same way a Google Business Profile goes stale, quietly, while nobody is watching. This group is about catching that before a customer or a machine reads something false.
15. Check your hours markup again any time your actual hours change, seasonal, holiday, or permanent. 16. Check your menu markup again any time you meaningfully change what you serve. 17. Run the Rich Results Test again after any site redesign or platform migration, since a new template can silently drop markup a previous one carried. 18. Set a recurring reminder, quarterly is reasonable for a small shop, to run through this entire one page checklist again from the top.
This group has no score, only a date. Write the date you last ran the full checklist directly on your printed copy, and compare it to today's date before deciding you are done for the year. A checklist run once and never again slowly turns back into the same gap it was meant to close.
Tie this reminder to something you already do on a schedule, rather than trusting yourself to remember a standalone quarterly task. Many small shops already do a seasonal menu refresh, a slow season review, or a quarterly bookkeeping pass. Running this checklist alongside one of those existing habits, rather than as its own separate thing to forget, is a small practical shift that makes it far more likely to happen.
Scoring the Whole Page and Your Three First Fixes
Add up your basics score out of 12, your advanced score out of 8 if applicable, and note your testing pass or fail. A basics score of 10 or higher with a testing pass means you are in solid shape and can move to the advanced group at leisure. A basics score under 8 means stop and fix basics first, full stop, before touching anything else on this page.
If you only fix three things today, fix these, in this order. First, place type: make sure your markup identifies you as a real business type, not a generic placeholder, since this is the single item every other property depends on. Second, hours in a structured, machine readable format, since stale or unstructured hours is one of the most common single points of failure on a small business site. Third, run the Rich Results Test once, today, so you know for certain whether what you believe is on your site is there and valid, rather than assumed.
None of this is a promise of a rich result appearing in search, and this checklist will not pretend otherwise. Correct markup is a documented best practice, not a guarantee. What it does guarantee is that you know, with a dated test result in hand, exactly what state your site is in, instead of trusting a guess.
Keep the printed page somewhere you will see it again, taped inside a supply closet door, clipped to a clipboard by the register, wherever you already glance at paper during a normal week. A checklist that lives only in a browser tab you closed months ago accomplishes nothing beyond the day you first ran it. A checklist you can see again next quarter is the one that keeps your markup honest over time. If you want a second pair of eyes on your results, Hillcane can walk through this checklist with you. Reach out at hillcane.co/contact or call (256) 384-2449.
Related Reading
More from Hillcane on this topic, plus the pages on the site that sit next to the work.
Frequently Asked Questions
What is the fastest way to use this checklist?
Print it, work through the basics group first, all six items scored 0 to 2, and stop there if your score is under 8 out of 12. Fixing the basics before touching menu, event, or FAQ markup is the single most efficient order, since every advanced property depends on the place type and core fields being correct first.
Which schema type should a coffee shop use?
Schema.org publishes a CafeOrCoffeeShop type specifically for this purpose, sitting under the broader LocalBusiness type. Using the specific type rather than a generic Store or Restaurant type is one of the six basics items on this checklist, and it is the first thing worth checking if your markup currently identifies you as something more generic.
Do I need menu or event schema if I do not host events?
No. The advanced group on this checklist, items 7 through 10, is conditional, so skip menu and event markup unless the content behind it is real. An event block needs a real date and location for a recurring open mic, cupping, or roastery tour. Marking up an event that does not exist, or a menu with nothing behind it, presents something false to a validator rather than something merely incomplete, which is worse than leaving the property out.
What tools test whether my schema works?
Two free tools do the job: Google's Rich Results Test and the Schema Markup Validator. The first checks eligibility for the rich result types Google currently supports and flags errors and warnings by name. The second checks your markup against the broader schema.org vocabulary, whether or not Google surfaces a result for that type. Items 11 and 12 on the sheet ask you to run both on your homepage, record pass, warning, or error with the date, and fix any error before moving on.
How often should I run this checklist again?
Run it quarterly, plus any time your hours, menu, or site template changes. Item 18 on the sheet sets that quarterly reminder, and item 17 calls for a fresh Rich Results Test after any redesign or platform migration, because a new template can silently drop markup the old one carried. Pairing the run with a habit you already keep, such as a seasonal menu refresh or a quarterly bookkeeping pass, makes it far more likely to happen. Write the date on your printed copy each time.
What do the Southeast audit numbers on this checklist mean?
They come from the Southeast vintage audit of 201 shops across 53 cities, quoted exactly as worded in the live audit posts: score bands of Invisible 21, Brochure 67, Trying 12, and Methodical under 1 percent, a blog zero rate of 83 percent, and a platform stat of 148 of 201 shops, or 74 percent. These numbers describe that specific audit and are never mixed with the newer 40 point census scores.
Does correct schema guarantee a rich result in Google?
No, and this checklist does not claim otherwise. Correct, validated markup is a documented best practice that makes your content eligible for certain rich result types. Whether a rich result actually appears depends on factors outside any single site owner's control. Treat validation as confirmation your markup is correct, not as a guarantee of appearance.
What does a score of 0 versus 1 versus 2 mean on this checklist?
A 0 means the item is missing entirely, a 1 means it exists but is incomplete, generic, or inconsistent with your other listings, and a 2 means it is present, specific, and matches your current facts. The six basics items add up to 12 points and the four advanced items to 8. Testing is scored pass or fail instead, since markup either validates cleanly or it does not. Scoring honestly, rather than optimistically, is what makes the total a useful starting point.
What are the three fixes that matter most if I am short on time?
Fix three things in this order. First, correct place type using the specific CafeOrCoffeeShop schema rather than a generic placeholder, since every other property depends on it. Second, hours in a structured, machine readable format rather than a sentence buried in a paragraph, because stale hours are a common single point of failure. Third, one full run of Google's Rich Results Test today, so you hold a dated result showing what is on your site. A basics score under 8 out of 12 means stop there.
Where can I find a deeper explanation of schema for coffee shops?
The complete guide to schema markup for coffee shops explains the topic in full; this page is only the run sheet. For reference reading, Google publishes structured data documentation for local businesses that lists required and recommended properties, and schema.org keeps a page for each of two types, CafeOrCoffeeShop and LocalBusiness. The Rich Results Test and Schema Markup Validator each document their own checks too. Sibling posts cover breadcrumb schema, testing methods, and BlogPosting fields for anyone going further on a single item.
Work with Hillcane
You have been told schema matters and never shown what done actually looks like. Here is one printable page, scored, that ends with the three fixes worth doing first.
Want a second pair of eyes on your schema results? Reach Hillcane at hillcane.co/contact or call (256) 384-2449.
Comments