🌟 In today’s Issue
This weekly dispatch is specifically designed for restaurant and small business owners who are trapped in the daily grind and ready to move from "struggling artist" to strategic operator.
One note first. Last week I promised you The Golden Hour. It ships next Tuesday. This one could not wait, and you will want the seven days.
The Review Gap... The restaurants AI names most, and the ones it names once, are a tenth of a star apart. Something else is separating them...

Strategic Marketing:
Four Point Six Versus Four Point Five... That is the entire rating gap between the most-recommended restaurants and the also-rans [1]. The review count gap is 2,559 against 1,178…
You Have Two Scoreboards and They Do Not Agree... Humans buy on the rating. Machines barely look at it. One star is worth 5 to 9% of revenue to an independent [5]. To an assistant it is worth almost nothing…
Google Has Written Down What It Reads... "Places, reviews, photos, addresses, opening hours" [3]. That is Google's own documentation, current last week. And Ask Maps landed in Australia on 7 August [4]…
Practical AI Implementation:
The Review Rate Audit... Not how many you have. How many you earn per hundred covers, which is the only number you control…
The Photo Gap Audit... The most-named restaurants carry a median 3,979 photos. The named-once carry about a thousand [1]…
The Recency Ledger... Three quarters of Australians say reviews from the last three months are crucial to their decision [7]…
Actionable Growth Tactic:
The Hundred-Cover Count... Four weeks, one number, and you will know whether your review problem is a rating problem or an arithmetic one…
The Savvy Operator Mindset:
From Polishing the Score to Building the Record... A rating is an opinion about you. A review count is evidence that you exist…
The Tenth of a Point.
You are at 4.6.
It took three years. It took answering the bad ones at eleven at night. It took the week you changed the coffee because two people in a row said the same thing.
The place four doors down is at 4.5.
You won. On the one number you have been watching, you won.
Now ask an assistant where to eat around here on Saturday. They get named. You do not.
For scale: the average restaurant brand is recommended by ChatGPT 5.3% of the time, by Gemini 7.1% and by Perplexity 7.6% [11]. Nobody is being named often. Somebody is being named more than you.
That is not bad luck and it is not a conspiracy. It is that you have been playing the scoreboard humans use, and the machine is reading a different one.
Both scoreboards are real. Both matter. They are not the same scoreboard.
First, The Number I Nearly Gave You.
Last week I told you this issue was coming, and I described it wrong.
I wrote that restaurant brands turn up in AI recommendations far more often when their review base looks a particular way, and that "the gap between the top and the bottom is not small." I had a figure in mind: 1% at one end, 53.5% at the other.
That figure is real. It is from Seer Interactive, published 14 May 2026, built on 804,491 AI responses across four assistants [2].
Three things are wrong with the way I put it.
One. 53.5% is not the top. It is near the bottom. It is the second-lowest of four tiers. The top tier is about 75%. The jump from nothing to 53.5% happens when a brand goes from no review profile at all to as few as one to thirteen reviews.
That is a better finding than the one I described. The money is at the very bottom of the ladder, not the top.
Two. It is not about restaurants. Eight verticals were studied. Money, shopping, travel, home services, health, education, electronics, business services. The word restaurant does not appear in it.
Three. It does not measure being recommended. It measures how often a brand turned up alongside a citation of one particular review platform. Close to what you want to know. Not the same thing.
So I am not building this issue on it. I am telling you it exists, what it actually says, and why it is not yours.
This took me one afternoon to check. It is the difference between a newsletter and a newsletter you can act on.
The Two Scoreboards.
Here is the study that is actually about us.
Pluspoint published it on 24 August 2026 [1]. They asked ChatGPT, Gemini and Perplexity eight standard restaurant questions, twice each, across twelve cities. 551 answers. 1,917 different restaurants named.
Then they took the 36 restaurants named most often, and the 34 named exactly once, and looked at what was different.
Named most | Named once | |
|---|---|---|
Star rating | 4.6 | 4.5 |
Google reviews (median) | 2,559 | 1,178 |
Photos (median) | 3,979 | 1,044 |
Listing attributes | 50 | 47 |
Has a reservation link | 67% | 47% |
Has a menu link | 86% | 76% |
Claimed listing | 97% | 97% |
Under 1,000 reviews | 11% | 47% |
Read that top row again.
A tenth of a star. That is the whole rating difference between the restaurants the machines cannot stop naming and the ones they mention once and forget.
Now read the bottom row. Among the most-named, one in nine had under a thousand reviews. Among the named-once, nearly half did.
The rating is flat. The volume is not.
Two things before you act on that
It is American and it is small. Twelve US cities, 551 answers. Australia was not in it. Nobody has published an Australian version, and I looked.
It is a correlation and the authors say so themselves. Their words: the study "cannot say whether the photos caused it" or whether both follow from being popular. I would rather hand you an honest correlation than a confident invention.
And it is vendor research. Pluspoint sells review and listing management to restaurants. The study's conclusion is, conveniently, the product.
I am using it because it is the only dataset that is actually about restaurants. Not because the people who published it have no stake in the answer.
The scoreboard humans use
Now the other one, and this is where the rating earns its keep.
Michael Luca at Harvard Business School matched Yelp ratings against actual state revenue records for 3,582 restaurants. A one-star increase raised revenue between 5 and 9% [5].
And the detail everyone leaves out. That effect held for independent restaurants only. For chains it was statistically indistinguishable from zero.
The work is old — Seattle, 2003 to 2009 — and it is Yelp, not Google. It is a working paper, not a journal publication, and I am not going to dress it up as one.
It is also causal by design, and about exactly the venue you run.
So: the star rating is worth real money with humans and almost nothing with machines. The review count is close to the reverse.
You do not get to pick one. You have been running hard at one of them and calling it the whole job.
One honest caveat on all of this
The evidence here is unsettled and I am not going to pretend otherwise.
Uberall, published 10 September 2026, found the same thing Pluspoint did — review volume predicts AI mentions better than rating does [6]. That is the newest large dataset available.
Yext, from December 2025, measured something adjacent and found reviews falling as a share of the sources AI cites [6].
Those two are not a straight contradiction. One is about who gets named. The other is about what gets quoted. A thing can matter more and be cited less at the same time.
But all of it is vendor research. Pluspoint, Uberall and Yext all sell something that gets easier to sell depending on the answer.
What I can tell you is this. The one study that is actually about restaurants and the largest multi-location dataset point the same way. The largest dataset of all points the same way again, and is not about restaurants. One vendor points elsewhere, at a different question.
Anyone selling you certainty on this has not read all four.
What Google Has Actually Written Down.
Everything above is somebody measuring from the outside.
Here is Google describing its own plumbing.
In the documentation for grounding Gemini in Google Maps, current as of 23 September 2026, Google states the service queries Maps for "places, reviews, photos, addresses, opening hours" across more than 250 million places [3].
Reviews. Photos. In a list of what the machine goes and fetches. Written by Google, not inferred by an agency.
And it is live here. Ask Maps — conversational search inside Google Maps, running on Gemini — rolled out in Australia on 7 August 2026 [4]. Google's own example in the Australian announcement is looking for a restaurant where you can hear each other talk.
That is nearly two months ago. Most operators I speak to have not registered it.
Put the two together. A diner in your suburb can now ask Maps a question in plain English, and the thing answering reaches for reviews and photos to build the answer.
Your review base stopped being a reputation asset. It became an input.
The Brutal Math.
I am not going to hand you a target of 2,559 reviews. That number came from big-name restaurants in American cities and it would be a lie to put it in front of a forty-seat venue in Sydney.
Here is the only review number you control. Not the total. The rate.
Say you do 300 covers a week. That is 15,600 a year.
At one review per 200 covers, you earn 78 a year. At one per 50, you earn 312 a year.
Same room. Same food. Same rating. The only thing that changed is whether anybody asked.
Over three years that is 234 reviews against 936. One of those venues has a thin record. The other has a thick one. Neither of them got there by being better.
Label on that, stated plainly: the covers and the ratios are an illustration, not a measurement. Run it on your own numbers. The first prompt below does it properly.
And the reason it matters, in the one place it is measured: among the restaurants AI named most often, 11% had under a thousand reviews. Among the ones named once, 47% did [1].
Thin records lose. Not to worse food. To less evidence.
What a Photograph Is Now Worth.
The photo gap in that study is the widest of the raw-count gaps. 3,979 against 1,044. Nearly four to one, and a wider separation than the review count.
Before you go and upload two hundred plating shots, two things.
One. A lot of those photos are not the venue's. Customers upload to a busy listing constantly. You cannot upload your way to 3,979 on your own — you can only be the kind of place people photograph.
Two. There is better evidence than a correlation, and it says something more interesting.
Zhang and Luo published in Management Science in 2023, working from 755,758 customer photos and 1.1 million reviews across 17,719 restaurants [8]. They found customer-posted photos predict whether a restaurant survives — beyond what the reviews alone explain.
Food photos carried the strongest signal. Then exteriors. Then interiors.
Read that as what it is. Photos are not a marketing lever you pull. They are a reading you take. A room people photograph is a room people are having something in.
One number to delete from your head
You have probably seen this: businesses with photos get 42% more direction requests and 35% more website clicks. It is on hundreds of agency pages, usually attributed to "a study by Google and Ipsos."
I went looking for that study. It is not on Google's own help page, it is not in the Ipsos local search work it is credited to, and no version of it names a sample, a date or a market.
It appears to have escaped from a sales deck around 2016 and been copied ever since [10].
Delete it. The Management Science paper does the same job and it is real.
Practical AI Implementation: The Review Desk
Three prompts. All three are new ground — nothing in the fifty-one from last week's Special Edition covers rate, photos or recency.
If you want the ones that already exist, run them alongside: The Review Gold Miner and The Human Reply Desk from #39, and The Sentiment Scanner from #49. Those handle mining, replying and root cause. These three handle arithmetic.
Set up the project. Call it The Review Desk. Upload: your last 90 days of covers by week from your POS; your Google review export; a screenshot or count of the photos on your listing; your brand notes; your house rules for replies.
🤖 AI PROMPT #1: The Review Rate Audit
Stop counting reviews. Start counting the rate.
This one turns your covers and your reviews into a single number — how many reviews you earn per hundred people through the door. Then it tells you where in your service the ask is going missing.
You need: ninety days of covers from your POS, and your Google review export.
You get back: a week-by-week table, and what your current rate adds up to over a year. Then three moments in your service where an ask could sit, ranked by how little they would cost your team.
Run this one first. It is the one that tells you whether you have a problem at all.
[TASK TITLE/GOAL] Work out my true review rate and what would move it.
1. Role & Expertise (Function): You are a hospitality data analyst who works on guest feedback volume for small venues. You deal in rates per hundred covers, never in totals, because a total tells an owner nothing they can act on. You never recommend buying, incentivising or gating reviews…
2. Context & Background (Pre-loaded / Specific to task): My venue: [type, seats, suburb, trading days]… My covers: my POS export for the last 90 days is in this project, by week… My reviews: my Google review export is in this project, with dates… What I currently do to ask for reviews: [describe it honestly, including "nothing"]… Where in the service the guest last sees a staff member: [the pass, the counter, the terminal, the door]…
3. Task Description & Output Requirements (Function & Modifiers): Your task is to calculate my review rate per 100 covers, weekly, for the last 90 days, and tell me what is actually limiting it. The output must be one markdown table with four columns: week, covers, new reviews, reviews per 100 covers. Below it, name the three moments in my service where an ask could sit, ranked by how little they would cost my team. Under 500 words. End by naming the single moment to start with this week and the exact words to use…
4. Work Order: First, calculate the rate per 100 covers for each week and the 90-day average… Then, flag any week that sits more than 40% below that average and say what was different about it… Next, work out what my annual review count would be at my current rate, and at double it… Finally, rank the ask moments by staff effort, not by expected yield, because the one my team will actually do is the one that works…
5. Examples: 1,240 covers in a week and 4 new reviews… Useful finding: 0.32 per 100 covers. At that rate you add about 160 a year. The ask is not happening at the terminal, which is where 90% of your guests have their last conversation…
6. Warnings/What to Avoid (Modifiers): Do not tell me to offer a discount, a free item, a prize draw or an entry to anything in exchange for a review — under Australian law an incentive must be offered regardless of what the review says, and disclosed… Do not tell me to ask only the happy ones… Do not invent a benchmark for my suburb — no published Australian figure exists, so compare me only against myself… Do not estimate a cover count that is in my export…🤖 AI PROMPT #2: The Photo Gap Audit
Your listing has photos on it. This works out what they add up to.
Not whether they are nice photos. Whether a machine reading your listing would find anything missing. And whether a diner who has never walked in could tell what walking in feels like.
You need: a count of the photos on your listing and who posted them, plus the totals for the two nearest comparable venues. Ten minutes of counting.
You get back: a breakdown across food, room, street and the practical shots people check before booking. Five shots to take this week. And one change to the room that would get guests photographing it themselves.
The cheapest of the three. Most of what it finds you can fix on a Tuesday afternoon with your phone.
[TASK TITLE/GOAL] Find out what my listing looks like to a machine.
1. Role & Expertise (Function): You are a local listings analyst who reads a Google Business Profile the way an assistant reads it — as a pile of evidence rather than a shopfront. You know the difference between what an owner uploads and what a customer uploads, and you know which one carries more weight…
2. Context & Background (Pre-loaded / Specific to task): My venue: [name, type, suburb]… My listing: I have counted the photos and noted who posted them — [owner photos: N, customer photos: N, total: N]… My two nearest comparable venues and their counts: [name, total photos] and [name, total photos]… What my photos currently show: [describe the mix — food, room, exterior, team, events]… The three dishes I most want to sell: [list them]…
3. Task Description & Output Requirements (Function & Modifiers): Your task is to tell me where my photo record is thin and what to do about it. The output must be one markdown table with three columns: category, what I have, what is missing. Categories are food, interior, exterior, and the practical shots a diner checks before booking. Below it, give me five specific shots to take this week and one change to the room or the service that would make guests photograph it themselves. Under 450 words. End by naming the one missing shot that costs me the most…
4. Work Order: First, compare my total against the two neighbours and say plainly whether I am ahead or behind… Then, identify which of the four categories is thinnest relative to the others… Next, check whether my three priority dishes appear in the photos at all… Finally, separate what I must shoot myself from what only a guest can produce…
5. Examples: 340 photos, 290 of them food, 12 of the room, none of the street frontage… Useful finding: a diner who has never been cannot tell what walking in feels like. The street shot and two room shots are the gap, and they take ten minutes…
6. Warnings/What to Avoid (Modifiers): Do not tell me to buy stock photography or use an image that is not my venue… Do not suggest uploading the same dish repeatedly to raise a count… Do not invent what my competitors' photos show — work only from the counts I gave you… Do not promise that photos will raise my ranking; the published evidence is correlation, and say so if I ask…🤖 AI PROMPT #3: The Recency Ledger
Your all-time rating is an average of everything you have ever been.
This one shows you what you are now. It ages your review base and reads it the way a stranger reads it. A stranger is asking whether the place is still good, not whether it was ever good.
You need: your Google review export with dates.
You get back: your reviews sorted into four age bands, with your last-ninety-days rating sitting next to your all-time rating. Plus the one thing a guest reading only your recent reviews would wrongly believe about you today.
The uncomfortable one. Run it when you have twenty minutes and nobody needs you.
[TASK TITLE/GOAL] Show me how old my review base actually is.
1. Role & Expertise (Function): You are a reputation analyst who treats a review as a perishable item. You know that a guest reading reviews is asking "is this place still good", not "was this place ever good", and you read a review base the way that guest does…
2. Context & Background (Pre-loaded / Specific to task): My venue: [name, type, suburb]… My Google review export with dates is in this project… Anything that changed in the venue in the last year: [new chef, new menu, renovation, price change, new hours, nothing]… The complaint I am most tired of seeing: [name it]…
3. Task Description & Output Requirements (Function & Modifiers): Your task is to age my review base and tell me what a new guest sees. The output must be one markdown table with three columns: age band, number of reviews, share of total. Bands are last 30 days, 31 to 90 days, 4 to 12 months, over a year. Below it, tell me in plain English what story the last 90 days tells on its own, separately from the all-time rating. Under 450 words. End by naming the one thing a guest reading only my recent reviews would wrongly believe about my venue today…
4. Work Order: First, sort every review into the four bands and calculate the share… Then, calculate the average rating for the last 90 days alone and compare it to my all-time rating… Next, check whether anything I told you changed in the venue is reflected in the recent reviews at all… Finally, identify any complaint that has stopped appearing, because a fixed problem that still dominates the recent record is a communication job, not a kitchen job…
5. Examples: 640 reviews all time at 4.6, but only 9 in the last 90 days and those average 4.1… Useful finding: your visible rating and your live rating have come apart. A guest reading the top of the page is reading last spring…
6. Warnings/What to Avoid (Modifiers): Do not tell me to have old negative reviews removed — under Australian law suppressing or editing genuine negative reviews is itself a breach, and platforms remove them only for policy violations… Do not invent a review or a date that is not in my export… Do not tell me what my competitors' recency looks like unless I give you the data… Do not soften the finding to make me feel better…Pro Tip. Take the output and argue with it. If it names an ask moment your floor staff will never do at eight on a Friday, say so and get the next one. The model does the arithmetic. You know the room.
Actionable Growth Tactic: The Hundred-Cover Count
The ACT Model. Four weeks, one number.
Here's how it works:
Activation — twenty minutes, once.
Open a note. Two columns: covers, and new reviews. Fill in this week from your POS and your listing.
That is it. That is the whole measurement.
Do it at the same time every week. Sunday night, before you close the laptop.
Collaboration — fifteen minutes, with your team.
One pre-shift huddle. Tell them the number. Not a target — the number.
Then one question: where in the night does a happy guest have their last proper conversation with one of us?
Whatever they say, that is where the ask goes. Not where you think it should go. Where they say it already happens.
Then agree on the words, out loud, once. Under thirty seconds, no discount, no pressure, no mention of stars. Google's own rules prohibit offering anything in exchange, and prohibit asking only your happy guests [9].
Transformation — four weeks later.
Run The Review Rate Audit against the four weeks.
If the rate moved, you have found your lever and it costs nothing to keep pulling.
If it did not move, the ask is in the wrong place in the service. And you now know that for a fact rather than a feeling.
Why four weeks and not one. One week is weather. Four weeks is a pattern. And if you change the ask halfway through, you start the four weeks again.
Savvy Operator Mindset: From Listing Keeper to Evidence Builder.
The struggling artist polishes the score. They check it every morning. They get to 4.5, defend 4.5, and panic at 4.3. They answer the bad ones at eleven at night and they take it personally. Ask them how many reviews came in last month and they will not know, because nobody ever told them that was a number.
That training was correct, and it is still correct for the human reading your page and deciding where to take his in-laws. It is close to useless for the thing now standing between him and you.
The Savvy Operator builds the record. Not by buying anything. By asking, on purpose, at the moment the guest is already happy, week after week, until there is enough there to be worth reading.
Here is the whole thing in a line.
A rating is an opinion about you. A record is evidence that you exist.
Two weeks ago it was a machine cannot book a table that exists only in your head. This is the same sentence from the other side. A machine cannot recommend a venue it can find nothing to say about.
You are not being marked down. You are being skipped for lack of material.
The Rating Polisher. | The Record Builder. |
|---|---|
Checks the rating every morning. | Counts the reviews every Sunday. |
Panics at 4.3. | Panics at nine reviews in ninety days. |
Asks the guests who look pleased. | Asks at the same moment, every service. |
Thinks a thin record is bad luck. | Knows a thin record is arithmetic. |
Knows the all-time score by heart. | Knows what the last ninety days say on their own. |
Waits to be recommended. | Leaves something to recommend with. |
One more thing, and then I will let you get back to it.
There is no Australian benchmark anywhere in this issue, and that is not an oversight.
I went looking for the average review count and the average rating for an Australian restaurant. Every figure I found was either unsourced, or attributed to the company publishing it with no sample and no method.
So there is nothing honest to hand you. The only review benchmark that exists for your venue is your own last ninety days. That is why every prompt above compares you against yourself and against nothing else.
Somebody should build the Australian one. It might end up being me.
Your Next Move: Three Questions
Open your POS. Open your listing. Write down two numbers: covers last week, and reviews last week.
That is the whole first step and it takes four minutes.
How We Can Work Together
Here is the honest problem with everything above. It is another job.
You already run a kitchen, a roster, a supplier list and a family. Nobody needs a fourteenth tab open.
So do not run it yourself. Set your AI up as a second brain for the business and let it hold the detail.
Not a toy. Not a chatbot you poke when you remember it exists.
A working folder that knows your menu, your prices, your hours, your reviews and your suburb. And the twenty questions your team answers on the phone every week.
Feed it those things once and it stops handing you ideas. It starts handing you a scoreboard.
That is why I built Strategic AI Marketing. We set your AI up properly, on your real numbers, so it thinks with your business instead of guessing at it.
You do the cooking. It does the remembering.
Two ways to start this week.
One, and it is free. Get your AI Visibility Snapshot. Four assistants, twelve questions about your venue, written down and dated. You will know exactly where you stand by the end of the week. It is at strategicai.marketing/free-ai-marketing-snapshot.
Two, if you want to know where your gap actually is. Reply to this email with one word: GAP, and tell me your venue name and suburb.
I will send back three numbers: your review count and photo count, and the same two for the two nearest comparable venues. Plus which of the three prompts above to run first, and why.
No pitch deck. No discovery call unless you ask for one. One reply, one useful answer.
Next Week on The Savvy Operator: Somebody Else Is Uploading Photos To Your Listing. In September, scammers were caught putting AI-generated images carrying fraudulent phone numbers onto business profiles through Google's own contributor programme. Google also started emailing owners when it detects a spike in spam reviews [12]. Two changes, one month, and what to check on your own listing tonight.
Until then, remember. The rating is what people think of you. The record is whether the machine can find anything to say. Serve your community. Be the operator.
Talk soon,
Rowan Shead
The Editor
The Savvy Operator
Owner of Strategic Ai Marketing
PS. Know an operator who checks their rating every morning and has never once counted their reviews per hundred covers? Forward this. It takes four seconds and it might change what they watch. |
PPS. The part of this I keep coming back to is the tenth of a point. Three years of work separating 4.6 from 4.5, and it turns out to be the least load-bearing number on the page. That is not an argument for caring less about the food. It is an argument for knowing which number is doing which job. And for checking rather than assuming, which is the whole reason this newsletter exists.l change. The feeling of captaining a ship that takes on water faster than you can bail. |
If you're tired of fighting the digital war alone |
The Savvy Operator
References
[1] Pluspoint. The 2026 Restaurant AI Visibility Study: 551 Answers From ChatGPT, Gemini and Perplexity, Dmytro Semonov, 24/08/2026. 551 AI answers (ChatGPT 189, Perplexity 192, Gemini 170) to eight standardised questions asked twice per engine per city, across twelve United States cities; 1,917 distinct restaurants named; data collected 30/07–03/08/2026. Comparison is the 36 most-named restaurants against the 34 named exactly once. United States data. Australia was not sampled and no Australian equivalent has been published. The authors state the study "cannot say whether the photos caused it" — it is correlation, and is presented here as correlation.
[2] Seer Interactive. Study of 800K AI Responses: How Review Profiles Shape Brand Presence in AI Search, Nick Haigler, 14/05/2026, in partnership with Trustpilot. 804,491 AI responses, 1,926 brands, 15,783 prompts, four platforms (ChatGPT, Google AI Mode, Gemini, Perplexity), data window March 2026. Eight verticals — none of them hospitality; the word "restaurant" does not appear in the study. Tier 0 (no verified profile) median citation rate 1%; Tier 1 (1–13 reviews) 53.5%; top tier approximately 75%. The metric is co-occurrence with a Trustpilot citation, not being recommended. Star rating, review recency and response rate were not tested as variables. Geography is not stated in the published write-up. Cited here to correct the description given in Issue #55, not as evidence about restaurants.
[3] Google. Grounding with Google Maps, Google AI for Developers documentation, current as at 23/09/2026. States the service queries Google Maps for relevant information including places, reviews, photos, addresses and opening hours, across more than 250 million places. Google's own technical documentation.
[4] Google Australia. Ask Maps, blog.google, 07/08/2026. Gemini-powered conversational search inside Google Maps, live in Australia in English. Note: the Australian announcement does not itself name reviews as an input — the reviews-and-photos list comes from the developer documentation at [3].
[5] Luca, Michael. Reviews, Reputation, and Revenue: The Case of Yelp.com, Harvard Business School Working Paper 12-016, 2011, revised 2016. Regression discontinuity on Yelp's half-star rounding, 3,582 restaurants, revenue from Washington State Department of Revenue records. A one-star increase raised revenue 5–9%. The effect was statistically indistinguishable from zero for chain restaurants (coefficient 0.005, standard error 0.025). United States (Seattle), 2003–2009, and Yelp rather than Google. An unpublished working paper — first issued 2011, revised March 2016, never published in a peer-reviewed journal. Causal in design (regression discontinuity) and specifically about independents, which is why it is here — but it is a working paper and is labelled as one.
[6] Uberall, reported by Search Engine Journal, 10/09/2026: 120,000+ AI mentions across 3,793 locations and five models, United States; review volume predicted AI mentions better than star rating. Vendor research, labelled sponsored by the publisher, and drawn from multi-location brands rather than independents. Yext, reported by iPullRank, 16/12/2025: 6.9 million citations across 1.6 million questions; review and social citations declining as a share of AI sources. Also vendor research, with no geography or period disclosed. The two disagree and both are named here for that reason.
[7] The Insiders. People trust People: How Online Reviews shape Consumer Choices in Australia, May 2023. 300+ Australian consumers; 75% consider reviews from the past three months crucial. Australian, but a small vendor whitepaper, three years old and retail-skewed rather than hospitality. Independently echoed in a different market by BrightLocal's Local Consumer Review Survey 2026 (11/02/2026, 1,002 United States adults), where 74% wanted reviews from the last three months.
[8] Zhang, Mengxia and Luo, Lan. Can Consumer-Posted Photos Serve as a Leading Indicator of Restaurant Survival? Evidence from Yelp, Management Science 69(1), 2023. 755,758 consumer photos, 1,121,069 reviews, 17,719 United States restaurants. Consumer-posted photos predict restaurant survival beyond what reviews explain; food photos carry the strongest signal, then exteriors, then interiors. Peer-reviewed, and explicitly predictive rather than causal.
[9] Google. Maps User Generated Content Policy — prohibited and restricted content. Merchants must not offer incentives such as payment, discounts or free goods in exchange for a review, must not discourage or prohibit negative reviews, and must not selectively solicit positive reviews. Australian position: the ACCC's guidance on online reviews, last updated 15/07/2026, states it is against the law to create fake or misleading reviews, that incentives must be offered regardless of what the review says and must be disclosed, and that suppressing or editing genuine negative reviews may itself breach the law. Recent Australian enforcement: PhotobookShop paid $39,600 in penalties on 24/03/2026 over 107 occasions of undisclosed influencer reviews and the editing of a review to remove negative comments.
[10] Claim checked and rejected: "businesses with photos receive 42% more direction requests and 35% more website clicks," widely attributed to a Google and Ipsos study. No primary source found. It is absent from Google's own Business Profile photo help documentation and from the Ipsos local search research it is credited to, and no version of it states a sample, date or market. Not used in this issue.
[11] SOCi. 2026 Local Visibility Index, restaurant breakout published 17/08/2026, as cited in Issue #54. The average restaurant brand appears in Google's local 3-Pack 24.3% of the time, and is recommended by ChatGPT 5.3%, Gemini 7.1% and Perplexity 7.6%. Restaurant-specific figures; SOCi's widely quoted cross-industry numbers are different.
[12] Search Engine Roundtable, 10/09/2026 (updated 11/09): a Google Maps contributor account was found uploading 150+ AI-generated photos carrying a fraudulent phone number across unrelated business profiles; the contributor was removed about a day after disclosure. Search Engine Roundtable, 22/09/2026: Google has begun emailing owners to say it has detected a spike in spam reviews on their Business Profile and removed them. Practitioner trade reporting, dated, not a Google announcement.
Strategic AI Marketing's own citation record — 0/12 on 26/05/2026 and every reading since — is published at strategicai.marketing/we-did-this/.
