See: The Audit Hillcane Runs Before It Touches Anything

Thomas Garner

6 hours ago

11 min read

Updated: 3 hours ago

Before Hillcane changes a single word on a café's website or touches a Google Business Profile, we run See. It's the first of three steps, See, Fix, Build, and it's the only one that isn't optional or skippable, because everything that comes after it depends on knowing, specifically and honestly, what's actually there right now. Not what an owner assumes is there. Not what a template promised when the site was built. What a search engine, a map, and an AI answer can actually read today.

That distinction matters more than it sounds like it should. A lot of marketing work starts with a pitch, here's what we'd build, here's what we'd write, here's the plan, before anyone has actually looked closely at the site or profile that plan is supposed to improve. See is the opposite of that. It's a look first, a plan second, and it's the reason Hillcane can tell an owner honestly what's actually broken instead of guessing.

This post walks through what the See step actually covers, in plain language, without turning it into a technical manual. If you want the deeper, more technical version of the same walkthrough, that's a separate post; this one is meant to answer the question most owners actually have, which is simply: what would you even be looking at?

The title, the meta description, and the H1 nobody ever changed

The first thing See looks at is embarrassingly basic, and it's also one of the most common gaps we find: what does the page's title tag, meta description, and main heading actually say? On a lot of independent café sites, these were never touched after the site was first built, they're still the CMS default, a generic placeholder, or something so vague it could belong to any small business in any city. A search engine reads these fields specifically to understand what a page is about and where it applies. If the title tag doesn't say the café's name and its city, that's not a stylistic nitpick, it's a page telling Google less than it needs to know to show that page to the right person.

This is one of the most common gaps we find precisely because it's invisible to a human visitor. Nobody browsing a café's homepage sees the title tag; it lives in a part of the page a customer never looks at. That's exactly why it goes unnoticed for years even at genuinely excellent cafés, the coffee is right, the room is right, and the one field a search engine actually reads first has never been touched since launch.

See also looks at how these fields behave across every page a site has, not just the homepage, a location page, an about page, and a menu page each need their own accurate title and heading, not a copy-pasted version of whatever the homepage says. A site where every page shares the same generic title is telling a search engine that every page is interchangeable, which is the opposite of what an owner actually wants when someone searches for a specific neighborhood or a specific menu item.

How the site is actually built, underneath the design

See also checks the more mechanical side of a site's construction: whether pages load in a reasonable time, whether a sitemap exists and is current, whether old URLs redirect properly instead of dead-ending, and whether anything on the site is accidentally telling search engines not to index a page that should be public. None of this requires touching how a site looks. A site can be visually polished, warm, and on-brand, and still have a technical layer underneath that's quietly working against it, a sitemap that hasn't been updated since a platform migration, a canonical tag pointed at the wrong URL, a handful of pages blocked from indexing by an old setting nobody remembers turning on.

These are exactly the kind of details that don't show up from the customer's chair and don't show up in a purely craft-focused review of a café's brand and content either, they only surface when someone is specifically looking for them from a technical angle, which is why they can sit unnoticed for years even on a site an owner is otherwise proud of.

Whether real, correctly typed schema exists at all

Underneath the visible page, there's a layer most café owners have never heard of: structured data, sometimes called schema, which is a standardized way of telling a search engine exactly what kind of business a page belongs to, along with its hours, address, and category, in a format a machine can read directly instead of guessing from prose. Hillcane's 2026 visibility research looked at 201 independent specialty cafés and found this layer missing or wrong far more often than it was right: 63 of the 201 (31%) had no café-specific schema at all, 68 (34%) had only generic Organization or WebSite markup that doesn't say "this is a coffee shop" to anything reading it, and just 60 (30%) carried real, correctly typed café or local-business schema.

See checks which of those three buckets a café's site actually falls into, because the fix looks completely different depending on the answer. A site with no schema at all needs it built from scratch. A site with generic Organization markup needs that markup corrected to the right business type. A site that already has real, correct schema needs something else entirely, which is itself useful information, because it means the visibility gap, if one exists, is coming from somewhere other than this layer.

How the Google Business Profile is actually set up

A café's Google Business Profile does more real-world work than most owners realize, and See treats it as its own full check, not an afterthought to the website. We look at the categories chosen (is it actually marked as a coffee shop, or something more generic), whether the hours match what's posted on the door, whether the photos are current and show the real space, and whether the profile's attributes, outdoor seating, Wi-Fi, whatever genuinely applies, are filled in accurately rather than left blank.

This matters because, in the research we conducted, wherever we could open a live local Google Maps pack for a café's own name, the Maps listing was functioning as the effective homepage more than the café's own website was. That's not a knock on any individual café's site, it's a description of how people actually search and how Google actually answers that search. A profile with stale hours or a wrong category is losing ground in the one place a lot of first-time searchers land before they ever click through to a website at all.

See also checks for the quieter problems that don't show up unless someone is specifically looking: a duplicate or unclaimed listing sitting next to the real one, a category that technically applies but undersells what the café actually is, an address that doesn't quite match what's printed on the site. None of these are visible to a customer walking in the door. All of them are visible to Google, and all of them are exactly the kind of gap See is built to surface.

Whether the site says anything specific to a real place at all

A surprising number of café websites could belong to almost any café, in almost any city, with the name swapped out. See asks a specific question: does this site describe the actual neighborhood it sits in, the real cross streets, the specific block regulars would recognize, or does it stay at the level of generic language that never gets more specific than the city name, if that? In Hillcane's research, 167 of the 201 cafés studied (83%) were running a blog section with zero posts published, a slot that exists in the site's navigation and says nothing, which is one of the clearest signs a site has no ongoing, location-specific content for a search engine to index at all.

This isn't really a writing problem, even though it looks like one on the surface. It's a visibility problem wearing a writing problem's clothes. A page that never names the neighborhood it's in gives a search engine nothing to match against a search that includes that neighborhood, and See is the step that identifies exactly where that specificity is missing, before anyone starts writing a single new page to fix it.

How the café actually performs in a plain search for its own name

The last thing See checks is the simplest and, for a lot of owners, the most revealing: what actually happens when someone searches for the café by its own name and city, the way a real person would? Does the right listing come up first, or does a review-aggregator page or an old, outdated directory listing outrank it? Are the search results showing accurate hours and a working link to the actual site, or is something stale sitting at the top instead? This is the plainest possible test of visibility, and it's often the moment an owner sees, in their own search results, the exact gap the rest of the audit has been describing.

Owners tend to describe this problem in specific, consistent language before they ever talk to us, not "I need a content strategy," but "we're just not showing up," or a question about why their Google listing looks wrong. See exists to take that plain, honest description and turn it into a specific, checkable list of what's actually happening underneath it, instead of leaving it as a vague feeling that something's off. We'd rather hand an owner a short, concrete list of what's actually happening than a longer report full of jargon that doesn't tell them anything they can act on.

Why this always comes before anything else

See isn't a formality before the "real" work starts, it is the real work, in the sense that everything Hillcane proposes afterward is built on what See actually finds, not on a generic template of fixes applied to every café the same way. A café with real schema and a broken Google Business Profile needs a completely different next step than a café with no schema and a strong profile. Skipping straight to fixes without See means guessing at that difference, which is exactly the kind of guessing this whole process is built to avoid.

That's also why See always comes before Fix, and Fix always comes before Build. You can't correct a schema problem you haven't identified, and there's little point building a new neighborhood page on top of a foundation that's still structurally broken, a well-written page sitting on missing schema and a stale Business Profile is still fighting the same underlying gap the rest of this post describes, no matter how good the writing is. See is what makes Fix and Build worth doing at all, because it's what tells us, specifically, what actually needs fixing and building in the first place.

It's worth being clear about what See is not, too. It isn't a sales pitch dressed up as a diagnostic, and it isn't a scare tactic meant to manufacture urgency around problems that don't actually matter for a given café. Some shops come through See with a shorter list than they expected, a Business Profile that's mostly in good shape, a handful of small fixes rather than a structural overhaul, and that's a genuinely good outcome, not a wasted look. The point of See was never to find the maximum number of problems; it was to find the real ones, honestly, whatever that list turns out to be.

That honesty is also why we won't compress See into a five-minute glance and call it done. A real look at title tags, schema, Google Business Profile settings, location-specific language, and how a café actually shows up in a plain search for its own name takes real time, done properly, and it's the only way Fix and Build end up correcting the problems that actually exist, instead of guessing at them from the outside.

Frequently Asked Questions

How long does the See step take?

It depends on how much there is to look at, a single-location café's website, schema, and Google Business Profile can usually be reviewed thoroughly without an extended engagement, while a multi-location café takes longer simply because there's more to check across each address. Either way, See happens before any fix work starts, not alongside it.

Does See require changing anything on my website?

No. See is purely a look, at the site's title tags and structure, whether real schema exists, how the Google Business Profile is set up, and how the café performs in a plain search for its own name. Nothing gets changed during this step; it exists specifically to figure out what, if anything, actually needs changing.

What if See finds that my site is already in good shape?

That's a genuinely useful outcome, not a wasted step. If a café already has real schema, an accurate Business Profile, and location-specific content, See tells us that clearly and quickly, and it means whatever visibility gap exists, if one does, is coming from somewhere else entirely, which changes what Fix and Build should actually focus on next, rather than duplicating work that's already solid.

Why do you check my Google Business Profile instead of just my website?

Because in a lot of real searches, the Google Business Profile and the Maps listing are doing more of the actual work than the website is. Where we could open a live local pack during our research, Maps was functioning as the effective front door for a café more often than its own site. Ignoring the profile would mean auditing half the picture.

What is schema, in plain terms?

Schema is a standardized way of telling a search engine exactly what a business is, a coffee shop, its hours, its address, its category, in a format the search engine can read directly rather than inferring from ordinary page text. A page can look completely normal to a human visitor and still be missing this layer entirely, or have it typed incorrectly.

Did your research actually check real coffee shop websites, or is this a general estimate?

It's from Hillcane's own 2026 visibility research: 201 independent specialty cafés across 53 Southeast secondary cities, checked directly for schema type, blog activity, and overall site structure, one shop at a time. The 31% no-schema, 34% generic-only, and 30% real-café-schema figures all come from that same sample, not from an industry-wide estimate or a secondhand source someone else compiled.

My website looks fine to me. Why would it still need an audit?

Because the things See checks mostly aren't visible to a human visitor at all. A title tag, a schema type, a Google Business Profile category, none of these show up when you look at your own site the way a customer would. A site can look completely fine and still be missing the layer that tells a search engine what it actually is.

Is See the same thing as a general marketing audit?

No. A general marketing audit often covers branding, design, and messaging broadly, across whatever the agency happens to specialize in. See is specifically about whether modern search, Google, Maps, and AI-generated answers, can correctly read what a café actually is and where it's located. It's narrower and more technical by design, not a rebrand exercise.

What happens after See is done?

See's findings become the basis for Fix, the step where the actual structural problems get corrected, almost always without changing the platform the site already runs on. Build, the third step, comes after Fix, once the foundation underneath a café's site and profile is solid enough to actually support new location and neighborhood pages built on top of it.

Do I need to already suspect something is wrong to start with See?

Not at all. A lot of owners come to us with only a vague sense that something isn't working, they're not showing up the way they expect to, or a Google listing looks off. See exists to turn that vague sense into a specific, checkable list, whether or not you can already name what's wrong.

Work with Hillcane

Most agencies pitch a fix before they've looked closely at what's actually broken on your café's site. Hillcane looks first, then talks.

See is the first real conversation about your café's search visibility, not a sales pitch. Call (256) 384-2449 or start at hillcane.co/contact to find out what's actually there.

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