Inside a Coffee Shop Website Audit: What We Actually Look For

Thomas Garner

9 hours ago

11 min read

See the audit is the plain language overview of why Hillcane looks before it touches anything. This post is the deeper companion: the actual categories we open, in order plain enough that a careful owner can half audit themselves afterward. It is still not a shop by shop scorecard, and it still is not a promise that every café needs the same fixes.

The checklist is practical. Title, meta, and H1. Whether schema exists and is typed as a café. Google Business Profile categories, hours, photos, and address match. Whether any URL is location or neighborhood specific beyond a footer name, address, and phone block. How the shop performs in a search for its own name and city. Whether the page loads on a phone. Those are the doors we open on purpose.

The same gaps showed up across Hillcane's 2026 visibility research on 201 independent specialty cafés: 167 of 201 (83%) had a zero post blog, 63 of 201 (31%) had no café schema, and where live local packs were opened in 12 of 53 cities, Maps was functioning as the effective homepage. Owner language from Phase 1 support notes sounds like GBP, Maps, reviews, and not showing up, not content cluster. Keep that vocabulary in mind as you read. It is usually the right way into the technical list.

Title, meta description, and H1

We start where search engines start: what does the title tag say, what does the meta description claim, and what is the visible H1. On many independent café sites these fields were never rewritten after launch. They still say Home, or the brand name with no city, or a phrase so vague it could belong to any business.

This check is boring on purpose. It is also one of the highest leverage boring checks in the audit. If the homepage title does not name the café and the city, the page is withholding the two facts a local searcher is most likely using. Multipage sites get the same scrutiny page by page, because one good homepage title does not rescue a menu page still wearing a default.

Owners can do a light version of this check themselves by looking at browser tabs and search result snippets. The audit version is simply more complete, and it ties the title story to everything else that follows.

I also compare the title story to the visible H1. When those two fields disagree, the page is sending mixed signals about what it is. A title that names the cafe and city with an H1 that says Welcome is a small example of the larger pattern See is built to catch: the public facing story and the machine facing story are not lined up.

Whether café schema exists and is typed correctly

Next we look under the page for structured data. The question is not only whether any schema exists. It is whether the entity is typed as a café or local business rather than a generic Organization or WebSite package. In the 201 shop study, 63 cafés (31%) had no café schema, which is a different problem from schema that exists but says the wrong kind of business.

Correct type matters because Fix looks different in each case. Missing markup gets built. Generic markup gets corrected. Real café markup means we stop spending time here and look harder at profile, content, and branded search behavior instead.

This is one of the structural halves a weekend often cannot finish cleanly, even when an owner can spot that something is missing. It is also one of the reasons people still call after they half audit themselves.

A quick owner check is imperfect but useful: view the page source and search for schema.org or application/ld+json. If you find nothing, that is a clue. If you find Organization only, that is a different clue. Either way, you now have a more specific question for a first conversation than we are not showing up.

Google Business Profile categories, hours, photos, and address

The profile gets a full pass, not a glance. Categories should say coffee shop when that is what the place is. Hours should match the door. Photos should be current enough to show the real space. The address should match the site. Attributes that are true, outdoor seating, Wi Fi, and the rest, should be filled instead of left blank.

This matters because Maps is often the first door. In the research cities where we could open a live local pack, 12 of 53, the Maps listing was functioning as the effective homepage more than the café's own website. Auditing the site while ignoring the profile would miss the surface most searchers actually touch first.

We also look for quieter profile problems: a duplicate listing, an unclaimed shell, a category that technically fits but undersells the café. Owner language about Maps looking wrong is usually pointing at this cluster even when the owner does not have the vocabulary for it yet.

Photos deserve a second look because they age quietly. A profile still showing last year's remodel dust, or a menu that no longer exists, trains Maps visitors to distrust the listing. Updating photos is one of the few audit items an owner can often finish the same afternoon, and it still belongs on the formal checklist so it does not get skipped.

Location or neighborhood specificity beyond the footer

A footer with name, address, and phone is not a location strategy. We ask whether any URL on the site is actually about a place: a neighborhood page, a location page for each address, or body copy that names real cross streets and landmarks a regular would recognize. Generic city mentions without place detail leave local search with little to match.

The zero post blog finding belongs here as a related signal. Across 167 of 201 cafés (83%), a blog slot existed in navigation with nothing published. That is not a scolding about posting cadence. It is evidence that many sites have no ongoing, place specific content for a search engine to index at all.

If the only place detail on the whole site is the footer, Build will eventually matter. See's job is to say that clearly before anyone writes a thin page that repeats the homepage with a new H1.

When a cafe has two or more addresses, this check gets stricter. Each location needs a URL that is truly about that room, not a copied page with the city name swapped. See flags that early because Build cannot honestly invent distinct location pages on top of a single shared stub.

Branded search for the shop's own name and city

We search the way a real person searches: shop name plus city. Does the right listing lead. Do hours look right. Is the link pointing at the live site. Or does an old directory page, a duplicate profile, or a stale aggregator result sit where the owner expects their own presence to be.

This is often the moment the rest of the audit becomes visible to an owner. Technical notes about schema can feel abstract until the branded search shows a wrong hours chip or a competitor directory above the real site. Owner phrases like not showing up usually map to something you can screenshot in this step.

We treat that screenshot as shared evidence, not as a scare prop. The goal is a short list of what is happening, in language that matches how the owner already describes the problem.

I also note whether review stars and hours chips look current. Owners often describe the problem as people say they cannot find us. Sometimes the shop is findable and the data beside the name is wrong. Branded search is where that distinction becomes visible without any jargon.

Whether the page loads on a phone

A café site that is slow, broken, or awkward on a phone fights every other fix. We check basic mobile load and usability because so much local search happens on a handset between parking and the door. This is not a lab full of invented performance scores. It is a practical look at whether the page is usable where customers actually are.

Mobile problems also interact with Maps. If the profile is doing the first introduction and the site collapses when someone taps through, the shop loses the handoff. Fixing titles and schema while leaving a painful mobile page in place leaves a hole in the middle of the path.

Owners can spot obvious mobile pain themselves. The audit simply refuses to ignore it because it is less glamorous than content ideas.

Heavy homepage videos, popups that cover the menu, and buttons that are hard to tap with a thumb all show up here. None of those require a full redesign to name. They require honesty about whether a traveler standing on a sidewalk can use the page in thirty seconds.

What you can half audit yourself, and what still needs a call

After this post, a careful owner can check titles, scan for obvious schema blocks, open the Google Business Profile, search their own name, look for any real location URL, and load the site on a phone. That half audit is useful. It turns a vague worry into a first list.

The people who still call are usually the ones without time, or the ones who hit the structural half a weekend cannot finish: schema typed correctly, unique location URLs, crawl hygiene, duplicate profile cleanup. Those are not moral failings. They are specialized work.

Hillcane's job, when you do call, is not to redo the owner doable list for theater. It is to finish the structural half and then keep the foundation from drifting. Inside the audit is the map. The relationship after the audit is how the map stays true.

If your half audit turns up only small profile and title fixes, that is useful information too. It may mean you do not need a deep engagement yet. See is allowed to return a short list. The point was never to invent work. The point was to find the real gaps.

How this stays honest in public

We will cite the aggregate research numbers that are already locked: the 201 shop set, the schema split, the zero post blog count, the 12 of 53 cities where live packs were opened. We will not publish a public ranking of named shops, and we will not recycle a false claim that every audited Asheville shop scored 16 of 40 or worse.

We also will not treat AI Overview behavior as a live, verified finding in this essay. Where research is still unverified, it stays out of the body. The audit categories above do not depend on that unresolved layer.

If you want the shorter overview, read see the audit. If you want the order justification, read why we audit first. This piece is the inside view of the checklist itself.

The companion essays matter for context. See the audit explains why the look comes first. What an SEO guy notices goes deeper on the technical half. What a coffee guy notices covers the craft half. This post stays on the checklist so an owner can leave with a map, not just a mood.

Frequently Asked Questions

What categories does Hillcane actually check in an audit?

Title, meta, and H1; whether schema exists and is typed as a café; Google Business Profile categories, hours, photos, and address match; whether any URL is location or neighborhood specific beyond a footer NAP; branded search for the shop name and city; and whether the page loads on a phone. That is the working checklist behind See.

Can I half audit my café myself after reading this?

Yes, for the owner doable half: titles, profile accuracy, branded search, obvious mobile pain, and whether any page is truly about a place. The structural half, especially correct café schema and unique location URLs, is where many owners still want help because a weekend rarely finishes it cleanly. The owner doable half still helps, because it turns a vague worry into a first list before any studio call. The structural half is where many shops still want a careful second set of eyes.

What did the 201 shop research find about blogs and schema?

167 of 201 cafés (83%) had a zero post blog slot, and 63 of 201 (31%) had no café schema. Those are aggregate findings from Hillcane's 2026 visibility research, not a public scorecard of named shops. Missing markup, generic Organization markup, and real cafe markup each point to a different Fix path, which is why the type matters as much as the presence. The check is quick to describe and slow to fake.

Why does the audit spend so much time on Google Business Profile?

Because in the 12 of 53 research cities where live local packs were opened, Maps was functioning as the effective homepage more often than the café's own site. Categories, hours, photos, and address match are first door issues, not afterthoughts. Categories, hours, photos, and address match are first door issues for local search. Ignoring the profile would mean auditing only half of what a searcher actually sees.

What owner language usually shows up before an audit?

Phase 1 support notes point to GBP, Maps, reviews, and not showing up. Owners rarely arrive talking about a content cluster. The audit's job is to translate that plain language into a checkable structural list. That check sits beside the rest of See so the findings stay concrete. Owners leave with a short list of what is actually happening, not a vague sense that something is off.

Is this the same as see the audit?

See the audit is the overview of why the look comes first. This post is the deeper companion that names the categories in more detail. Read both if you want the why and the what. Read both if you want the why and the what. Neither one invents a ranking timeline or a public scorecard for named shops.

Will you score my shop publicly?

No. Aggregate numbers can appear in essays. Shop by shop scorecards do not. Your findings stay private to the conversation about your site. Aggregate research numbers can appear in essays. Shop by shop scorecards do not. Your findings stay private to the conversation about your site and profile. We would rather hand you that list than a longer report full of jargon that does not change what happens next.

Does a zero post blog mean I need to publish every week?

Not as a guilt calendar. In the research it was a signal that many sites have no place specific content indexable at all. The fix might be real location and neighborhood pages, not a forced posting grind. In the research it was a signal that many sites have no place specific content indexable at all. The fix might be real location and neighborhood pages, not a forced posting grind.

What if my site already passes most of this checklist?

Then See should say that plainly. A short findings list is a good outcome. It changes what Fix and Build should focus on, instead of inventing work where the foundation is already solid. A short findings list is a good outcome. It changes what Fix and Build should focus on, instead of inventing work where the foundation is already solid.

How do I get this audit on my café?

Start at hillcane.co/contact or call (256) 384-2449. Bring the live site and the live profile. We will walk the checklist against what is actually there, then talk about what is owner doable versus structural. Bring the live site and the live Maps listing. We translate owner language into a checkable list, then decide what is owner doable versus structural.

Work with Hillcane

A real cafe audit is a short list of checkable doors, not a vibe check. Titles, schema, Maps, place pages, branded search, and mobile load are the doors that matter.

If you want that checklist run against your live site and profile, reach Hillcane at hillcane.co/contact or call (256) 384-2449.

Reach out at hillcane.co or (256) 384-2449.