What an SEO Guy Notices That a Coffee Guy Never Would

Jacob can tell you in a few minutes whether a café website sounds like the room. My half of the same look is less romantic and just as decisive: whether the technical layer underneath that room is quietly telling search engines the wrong story, or no story at all. Craft focused owners rarely think to check these fields, because none of them show up from the customer's chair.

The list is specific. A canonical pointed at the wrong URL. A duplicate or unclaimed Google Business Profile sitting beside the real one. A sitemap that has been stale since a platform move. Schema that is present but typed as Organization or WebSite instead of a café or local business entity. Title tags still sitting on the commerce platform default. Each one is invisible until someone opens the right panel on purpose.

This post is the technical companion to what a coffee guy notices, and the other half of how we split the work. It uses the same 201 shop research Hillcane already published in plain language elsewhere, without turning your café into a public scorecard. The point is to make the invisible gaps nameable before anyone proposes a fix.

Schema that exists but still says the wrong thing

Structured data is the machine readable layer that tells a search engine what kind of business a page belongs to. A lot of café sites either skip it or install a generic package and assume the job is done. In Hillcane's 2026 visibility research across 201 independent specialty cafés in 53 Southeast secondary cities, 63 shops (31%) had no café schema at all, 68 (34%) carried only Organization or WebSite markup, and 60 (30%) had a real café entity.

Those three buckets need three different fixes. Missing schema needs to be built. Generic Organization markup needs to be corrected to the right business type. Real café schema means the visibility gap, if one exists, is coming from somewhere else. A craft walkthrough will not surface that distinction, because the markup never appears on the visible page.

I check this early in See because it changes everything that follows. Writing a beautiful neighborhood page on top of generic Organization markup is still leaving the crawler without a clear café entity. The craft can be perfect and the machine still guesses.

Owners sometimes tell me they already added schema because a plugin or a theme claimed to handle it. That claim is where a lot of the generic Organization markup comes from. The theme did add something. It just did not add the something that says this page belongs to a coffee shop. Checking the type is the whole point of the notice.

Title tags stuck on the platform default

Titles are one of the first fields a search engine reads, and on café sites they are often still whatever the platform wrote at launch. Home, Welcome, or a store name with no city. Visitors never see the title tag in the page body, which is exactly why it can sit untouched for years while the coffee and the room get better every season.

Platform mix helps explain why this is so common. Of the 201 cafés in that same research set, 148 (74%) run Squarespace, Shopify, Square Online, or Wix. Those tools are good at commerce and design. They do not automatically write a host forward, city specific title for every page. That work still belongs to someone, and on most independent shops that someone has never been assigned.

I also check whether every important page has its own accurate title, not a copy paste of the homepage. A menu page, a location page, and an about page that all share one generic title are telling a search engine the pages are interchangeable.

A useful owner test is to Google the cafe name and city and look at the blue link text that appears. If that text still says Home or Welcome, the title tag is doing almost no local work. Fixing it does not require a redesign. It requires deciding what the page is actually about and writing that into the field the platform already provides.

Canonicals, sitemaps, and the quiet crawl problems

A canonical tag pointed at the wrong URL can send ranking signals to a page the owner is not even trying to rank. A sitemap that froze during a platform migration can leave new pages undiscovered while old URLs linger. Redirects that dead end waste both crawl attention and human patience. None of this requires the site to look broken.

These are the problems a craft focused owner would not think to check, not because they are careless, but because the tools for checking them live outside the normal owner workflow. You do not see a stale sitemap while pouring a cortado. You see it when someone opens Search Console, the sitemap file, and the live HTML head on purpose.

See exists to open those panels before Hillcane proposes new content. Building pages on top of crawl debt is how shops end up with good writing that still does not move.

Platform moves are a common trigger. A cafe migrates from one builder to another, the visible pages look fine, and the sitemap or canonical map quietly points at the old world. Months later the owner wonders why new location pages never seem to land. The answer is often sitting in a file nobody opened after the migration day.

Duplicate or unclaimed Google Business Profiles

The Google Business Profile is often doing more first contact work than the website. When I open Maps beside the site, I am looking for whether the real listing is claimed, whether a second listing is competing with it, and whether categories, hours, photos, and address match what the site and the door say.

A duplicate or unclaimed profile beside the real one is easy to miss if you only search the way a regular searches. Regulars type the name they already know and click the familiar card. A new searcher can land on the wrong hours, the wrong photos, or a shell listing that was never finished. That is not a branding problem. It is a local search hygiene problem.

Jacob will notice if the photos on the profile feel fake. I notice if there are two profiles, or if the category undersells a coffee shop as something vaguer. Both notices belong in the same audit.

Hours mismatches between the profile and the door deserve their own callout. Leaf season, campus calendars, and holiday weeks change faster than most owners update Maps. From the customer's chair that looks like the shop is unreliable. From the audit chair it looks like a field that never got an owner.

Why these gaps stay invisible from the customer's chair

Everything in this post can be wrong while the café looks beautiful on a phone browser. That is the trap. Owners judge the site the way a guest judges it: does it look like us, does the menu load, do the photos feel right. Search engines judge a different layer. If nobody on the team is assigned to that layer, the layer drifts.

This is also why Hillcane will not print a public 0 to 40 scorecard of named shops. The research numbers above are aggregate findings from the 201 shop study. Your café gets a specific list in private, not a public ranking. The useful output of an SEO notice is a short, checkable set of structural facts, not a dunk.

If your site already has real café schema, clean titles, a healthy profile, and a current sitemap, my list can be short. That is a good outcome. It means any remaining problem is more likely sitting in content specificity or craft voice, which is Jacob's half.

That invisibility is also why craft only agencies miss this half. They review the site the way a guest would. Hillcane exists because that guest view is necessary and incomplete. Somebody still has to open the panels.

How this pairs with the coffee culture check

I do not write café voice copy, and Jacob does not ship schema alone. The split only works if both of us name what we see without pretending the other half is optional. A technically clean site with stock photos and template About copy still fails. A gorgeous craft site with Organization only markup and a duplicate Maps listing still fails.

On a live project, See is usually where my list appears first. Fix corrects the structural debt. Build adds location and neighborhood pages once the foundation can hold them. Jacob is in the loop wherever language changes, because a corrected title still has to sound like the shop.

If you want the craft companion, read what a coffee guy notices. If you want the process shape, read how we split the work and see the audit. This essay stays on the invisible technical half on purpose.

When both halves agree, the work gets simpler. Jacob can say the About page needs a true sourcing story, and I can say the same page also needs a title and schema that name the cafe as a cafe in this city. One page, two notices, one Fix list.

What I will not claim from these notices

I will not turn a schema gap into a guaranteed ranking timeline. I will not invent Keyword Planner volumes to scare an owner into urgency. I will not dunk on named shops as negative examples, and I will not publish a week one hit list. The research supports plain aggregate claims. It does not support theater.

What I will claim is narrower and more useful: these fields are checkable, they are commonly wrong in the 201 shop set, and they are the kind of wrong that craft alone cannot see. That is enough to justify looking before building.

If that matches the vague sense that you are not showing up the way you should, bring the live site and the live profile to a call. We will translate owner language into a specific structural list, then decide what Fix actually needs to touch.

If you want the craft companion essay, read what a coffee guy notices. If you want the process shape, read how we split the work. If you want the audit checklist itself, read inside the audit. This piece stays on the invisible technical notices on purpose.

What a first pass of these notices usually produces

A first pass rarely produces a novel. It produces a short list: schema type, title debt, profile hygiene, sitemap freshness, maybe a canonical pointed the wrong way. That list is the whole point. Owners do not need a hundred page PDF. They need to know which invisible fields are actually wrong on their cafe.

The list also decides the order of Fix. If the profile is the main door and the schema is generic, those come before a neighborhood page. If titles are default and the sitemap is stale, those come before a blog calendar. See is what makes that order honest instead of fashionable.

Once the list is clear, Jacob and I can talk about voice and structure in the same conversation. The owner hears one plan, not two agencies arguing about which half matters more. That is the practical reason these notices live beside the coffee culture ones instead of replacing them.

Related Reading

Three other Hillcane notes that sit next to this one — same studio, same problem, different door in.

• The Kind of Client Relationship We're Actually Building

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

• Your Google Business Profile Is Doing More Work Than Your Website

Frequently Asked Questions

What technical things does an SEO guy check that a craft review misses?

Canonical tags pointed at the wrong URL, duplicate or unclaimed Google Business Profiles, sitemaps stale since a platform move, and schema typed as Organization or WebSite instead of a café or local business. Title tags left on commerce platform defaults belong on that list too. None of those show up from the customer's chair. That working checklist is what keeps See from becoming a vague marketing conversation. Each category either clears or becomes a concrete Fix item.

How common is missing or generic café schema?

In Hillcane's 2026 visibility research of 201 independent specialty cafés across 53 Southeast secondary cities, 63 shops (31%) had no café schema, 68 (34%) had Organization or WebSite only, and 60 (30%) had a real café entity. Those three states need three different fixes, which is why See checks the type instead of assuming schema is either present or absent.

Why do title tags stay wrong for so long?

Because visitors never see them in the page body, and because many shops launch on a platform default and then move on to the work that is visible. Of the 201 cafés in the research set, 148 (74%) run Squarespace, Shopify, Square Online, or Wix. Those platforms do not automatically write city specific titles for every page.

Can I see these problems myself without an agency?

Some of them, yes. You can search your own name and city, open your Google Business Profile, and view page source for obvious schema blocks. Canonicals, sitemap freshness, and quiet crawl issues usually need a more careful pass. The weekend fixes post covers the owner doable list; structural debt is the half an afternoon rarely finishes.

Does finding these gaps mean I need a new website?

Usually no. Most of this work corrects the site and profile you already have. A wrong canonical, a stale sitemap, or generic schema can be fixed without a redesign. Hillcane's default is repair the foundation, then build on it, not rip and replace for its own sake. A wrong canonical, a stale sitemap, or generic schema can be corrected on the site you already run. Hillcane's default is repair the foundation, then build on it.

Why check the Google Business Profile during a website audit?

Because local searchers often meet the Maps listing before they meet the site. A duplicate listing, wrong hours, or a vague category can undo good website work. Ignoring the profile would mean auditing half the door. 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.

Will Hillcane publish a score for my shop?

No. Aggregate research numbers are public. Shop by shop scorecards are not. Your audit findings stay specific to your site and shared with you, not ranked against named neighbors in a blog post. 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.

How does this relate to what Jacob notices?

Jacob catches voice, sourcing language, and whether photos show the real bar. I catch crawl and entity problems a craft eye would miss. Both halves fail often, and both halves usually get handled by nobody until a two person pass is designed on purpose. Both halves fail often on independent specialty cafes, and both halves usually get handled by nobody until a two person pass is designed on purpose. That is the practical reason Hillcane is built as a split.

What happens after you list the technical gaps?

See's list becomes the basis for Fix, where structural problems get corrected, almost always on the platform the shop already runs. Build comes after Fix, once location and neighborhood pages have a foundation that can actually support them. Build comes after Fix, once location and neighborhood pages have a foundation that can actually support them. Skipping that order is how good writing lands on a still broken base.

How do I start if I only know we are not showing up?

That owner language is enough. Bring the live site and the live Maps listing to a first conversation and we will turn the vague sense into a checkable list. Start at hillcane.co/contact or call (256) 384-2449. 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

Most craft focused cafe owners never open the panels where visibility actually breaks. The gaps are technical, quiet, and fixable once someone is looking for them.

If you want the structural half named in plain language, reach Hillcane at hillcane.co/contact or call (256) 384-2449.

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