WEBVTT 00:00:00.000 --> 00:00:01.860 Remember how we used to search for things? It 00:00:01.860 --> 00:00:04.500 was, well, it was rigid. Yeah, very robotic. 00:00:04.679 --> 00:00:06.620 You pull out your phone, you type pizza or mechanic, 00:00:06.960 --> 00:00:08.460 and you were basically just matching stickers. 00:00:08.660 --> 00:00:10.359 You put in a word, the machine gave you a list 00:00:10.359 --> 00:00:14.699 with that word. But that era is ending. I mean, 00:00:14.980 --> 00:00:16.579 fast. Now you can pick up your phone and say, 00:00:16.879 --> 00:00:19.339 I need a romantic date spot with vegan pasta 00:00:19.339 --> 00:00:21.600 that isn't too loud. And the crazy thing is, 00:00:21.719 --> 00:00:24.100 it understands vibe. It actually understands 00:00:24.100 --> 00:00:26.879 what romantic means. It's wild. It's a shift 00:00:26.879 --> 00:00:31.500 from just matching text to understanding reality. 00:00:31.899 --> 00:00:33.979 And for the businesses relying on those searches, 00:00:35.340 --> 00:00:37.759 it's absolutely terrifying if they aren't prepared 00:00:37.759 --> 00:00:40.359 for it. Welcome back to the Deep Dive. Today, 00:00:40.399 --> 00:00:44.039 we are unpacking a source titled Monetizing Gemini 00:00:44.039 --> 00:00:48.149 AI, the Google Maps business strategy. And look, 00:00:48.369 --> 00:00:50.670 I know business strategy can sound a little dry. 00:00:50.750 --> 00:00:52.729 A little, yeah. But this isn't just another tech 00:00:52.729 --> 00:00:55.310 update. This is about a fundamental shift in 00:00:55.310 --> 00:00:57.570 how we interact with the physical world. For 00:00:57.570 --> 00:01:00.390 local shops, this is about survival. It really 00:01:00.390 --> 00:01:03.149 is. Most people open Google Maps and just see 00:01:03.149 --> 00:01:05.689 it as a tool to get from point A to point B. 00:01:06.049 --> 00:01:11.790 But for a business owner, a cafe, a gym, a plumber... 00:01:11.819 --> 00:01:14.239 It is their lifeline. It's their front door. 00:01:14.620 --> 00:01:16.780 Exactly. And there's a massive change happening 00:01:16.780 --> 00:01:19.340 right now with Gemini AI getting integrated into 00:01:19.340 --> 00:01:21.900 Maps. Most businesses are completely missing 00:01:21.900 --> 00:01:24.819 it. They're still operating like it's 2015. But 00:01:24.819 --> 00:01:27.379 the opportunity is there. Oh, it's huge. For 00:01:27.379 --> 00:01:29.920 the people who get it, there's a massive opportunity 00:01:29.920 --> 00:01:32.680 to build a business just by fixing this one problem 00:01:32.680 --> 00:01:35.420 for them. So we have a clear roadmap for today. 00:01:35.439 --> 00:01:37.000 We're going to break down this technical shift, 00:01:37.299 --> 00:01:39.079 something the source calls grounding. Right. 00:01:39.140 --> 00:01:41.000 Then we'll look at the invisible business problem, 00:01:41.099 --> 00:01:43.629 which Sounds pretty ominous. And finally, we'll 00:01:43.629 --> 00:01:46.230 get into the toolkit, how you can actually optimize 00:01:46.230 --> 00:01:48.530 for this AI and the specific model for pitching 00:01:48.530 --> 00:01:50.989 this to clients. So the mechanics, the problem, 00:01:51.049 --> 00:01:53.230 and then the solution. Let's start with the shift 00:01:53.230 --> 00:01:55.469 itself. Source source describes this move from 00:01:55.469 --> 00:01:58.310 keywords to conversation. I touched on it, but 00:01:58.310 --> 00:01:59.750 walk us through what's actually happening under 00:01:59.750 --> 00:02:02.629 the hood. Sure. So in the old days, and by old 00:02:02.629 --> 00:02:05.129 days, I mean like a few years ago, search was 00:02:05.129 --> 00:02:09.409 literal. If you typed cafe and wifey, Google's 00:02:09.409 --> 00:02:11.370 algorithm was just looking for those text strings. 00:02:11.830 --> 00:02:14.590 A robot matching sticker. Exactly. If the website 00:02:14.590 --> 00:02:17.210 said wifey, boom, it was a match. That's old 00:02:17.210 --> 00:02:19.629 enough. But the new Google Maps update has put 00:02:19.629 --> 00:02:23.009 Gemini Google's smartest AI brain right inside 00:02:23.009 --> 00:02:25.689 the map. This allows for these conversational 00:02:25.689 --> 00:02:28.310 queries. The example the source uses is really 00:02:28.310 --> 00:02:31.229 good. Imagine asking, find me a quiet cafe with 00:02:31.229 --> 00:02:33.990 good wifey and oat milk. OK. That feels like 00:02:33.990 --> 00:02:37.409 a very human request, very 2026 request. It is. 00:02:37.650 --> 00:02:39.270 And the old system would struggle with a word 00:02:39.270 --> 00:02:42.150 like quiet. That's subjective, right? Right. 00:02:42.169 --> 00:02:44.150 How do you measure that? Well, Gemini reads reviews. 00:02:44.270 --> 00:02:46.110 It reads descriptions. It looks at photos. It 00:02:46.110 --> 00:02:47.449 doesn't just look for the word quiet. It looks 00:02:47.449 --> 00:02:49.830 for evidence. It reads a review from six months 00:02:49.830 --> 00:02:52.189 ago that says, great place to study, very peaceful. 00:02:52.650 --> 00:02:55.729 It synthesizes that context. It understands the 00:02:55.729 --> 00:02:59.770 vibe. Wow. It's reading between the lines. But 00:02:59.770 --> 00:03:02.360 the source... mentions a specific technical term 00:03:02.360 --> 00:03:05.960 that makes this work, grounding. Can we slow 00:03:05.960 --> 00:03:07.580 down and unpack that? Because usually when I 00:03:07.580 --> 00:03:10.400 hear about AI, I also hear about it hallucinating. 00:03:10.719 --> 00:03:13.000 That's the biggest risk. You ask it for a fact. 00:03:13.210 --> 00:03:16.449 and it just confidently makes something up. Grounding 00:03:16.449 --> 00:03:19.909 is Google's fix for that problem inside of Maps. 00:03:20.289 --> 00:03:23.009 Essentially, they are tethering the AI to the 00:03:23.009 --> 00:03:25.650 hard data of the real world. So it can't just 00:03:25.650 --> 00:03:27.930 dream up a coffee shop. Precisely. It connects 00:03:27.930 --> 00:03:30.430 Gemini's reasoning brain to the real addresses, 00:03:30.650 --> 00:03:33.490 the real opening hours, the real reviews of 250 00:03:33.490 --> 00:03:36.030 million places. It makes sure the AI doesn't 00:03:36.030 --> 00:03:38.189 recommend a place that doesn't exist or, say, 00:03:38.189 --> 00:03:40.629 a place is open when it's closed. It's a reality 00:03:40.629 --> 00:03:42.250 check. You know, when you stop and think about 00:03:42.250 --> 00:03:45.469 the sca - of that 250 million places and the 00:03:45.469 --> 00:03:48.590 AI is instantly cross -referencing a query about 00:03:48.590 --> 00:03:50.949 vegan pasta against all that data to make sure 00:03:50.949 --> 00:03:53.949 it's not lying to you whoa that is honestly it's 00:03:53.949 --> 00:03:56.069 kind of staggering it's an engineering marvel 00:03:56.069 --> 00:03:59.129 it's assessing the vibe based on evidence not 00:03:59.129 --> 00:04:03.259 just keywords so to put a fine point on it The 00:04:03.259 --> 00:04:06.419 AI isn't just matching words anymore. It's interpreting 00:04:06.419 --> 00:04:08.919 reality. That's the perfect way to put it. It's 00:04:08.919 --> 00:04:11.719 assessing reality based on the data businesses 00:04:11.719 --> 00:04:14.259 leave behind. Which brings us to the scary part 00:04:14.259 --> 00:04:17.300 for the business owners. The source calls this 00:04:17.300 --> 00:04:20.220 the invisible business problem. This is where 00:04:20.220 --> 00:04:23.040 the rubber meets the road. Most businesses have 00:04:23.040 --> 00:04:26.540 what the source calls dumb profiles dumb profiles. 00:04:26.540 --> 00:04:28.259 I like that What does that look like think of 00:04:28.259 --> 00:04:31.579 a local gym? Their Google profile probably lists 00:04:31.579 --> 00:04:33.920 the name address and maybe a description that 00:04:33.920 --> 00:04:36.800 says, you know, we are a gym We have weights 00:04:36.800 --> 00:04:39.720 their minimum Right. And before, that was fine. 00:04:39.779 --> 00:04:42.680 You search gym, they show up. But now, imagine 00:04:42.680 --> 00:04:46.019 a user asks Gemini, find me a beginner friendly 00:04:46.019 --> 00:04:49.139 gym with yoga classes after 6 p .m. Okay, that's 00:04:49.139 --> 00:04:52.139 a very specific conversational request. And it's 00:04:52.139 --> 00:04:54.439 how people actually talk now. So Gemini looks 00:04:54.439 --> 00:04:56.899 at that dumb profile. Does it say beginner friendly? 00:04:57.000 --> 00:04:59.980 No. Does it mention yoga classes after 6 p .m.? 00:04:59.980 --> 00:05:03.259 No. And the AI is grounded in facts, so it can't 00:05:03.259 --> 00:05:05.379 guess. It can't verify those things, so what 00:05:05.379 --> 00:05:07.829 does it do? I assume it just skips them. It skips 00:05:07.829 --> 00:05:10.589 them. The business becomes invisible. Because 00:05:10.589 --> 00:05:12.889 the profile wasn't optimized to answer those 00:05:12.889 --> 00:05:16.430 questions, the AI treats the answers as unknown 00:05:16.430 --> 00:05:18.990 and moves on. That is brutal. So you could have 00:05:18.990 --> 00:05:21.910 the best yoga class in town at 7 p .m., but if 00:05:21.910 --> 00:05:24.769 your profile just says, we have weights, you 00:05:24.769 --> 00:05:27.170 don't exist for that user. Exactly. Now contrast 00:05:27.170 --> 00:05:30.430 that with the detailed winner. This is the optimized 00:05:30.430 --> 00:05:33.600 profile. It says, Perfect for beginners, we offer 00:05:33.600 --> 00:05:37.060 relaxing yoga classes every weekday evening at 00:05:37.060 --> 00:05:40.519 7 p .m. So the AI runs its check, beginner friendly, 00:05:40.980 --> 00:05:44.399 yep, yoga, yep, time, yes. And boom, that gym 00:05:44.399 --> 00:05:46.870 gets the recommendation. It's like the AI is 00:05:46.870 --> 00:05:49.069 picking winners and losers based entirely on 00:05:49.069 --> 00:05:51.889 who gives it the best data to work with. So vague 00:05:51.889 --> 00:05:53.949 marketing copy isn't just bad style anymore. 00:05:54.149 --> 00:05:55.970 It's literally costing businesses customers. 00:05:56.230 --> 00:05:58.089 Yes. If you don't answer the specific questions 00:05:58.089 --> 00:06:00.250 in your profile, you don't exist to the search. 00:06:00.449 --> 00:06:02.709 That seems like a huge vulnerability, but also 00:06:02.709 --> 00:06:04.490 a huge opportunity if you know how to fix it. 00:06:04.589 --> 00:06:06.569 Which is exactly what this deep dive is all about. 00:06:06.750 --> 00:06:09.370 Right. So let's talk tools. The source gets into 00:06:09.370 --> 00:06:12.750 APIs in Google AI Studio. And I have to admit, 00:06:12.949 --> 00:06:16.050 when I see API, my brain usually shuts down a 00:06:16.050 --> 00:06:18.430 little bit. I feel like I need a computer science 00:06:18.430 --> 00:06:20.370 degree. You really don't. And the source makes 00:06:20.370 --> 00:06:24.209 a great analogy. Think of the API as a waiter 00:06:24.209 --> 00:06:27.449 in a restaurant. You're the customer or the developer. 00:06:28.029 --> 00:06:31.750 The kitchen is Google's massive database. The 00:06:31.750 --> 00:06:34.730 API is just the waiter. You tell the waiter what 00:06:34.730 --> 00:06:37.490 you want. Bring me info on dentists in Chicago. 00:06:37.970 --> 00:06:39.850 And the waiter goes to the kitchen, gets it, 00:06:39.949 --> 00:06:41.689 and brings it back. You don't need to know how 00:06:41.689 --> 00:06:43.709 to cook. You just need to know how to order. 00:06:43.810 --> 00:06:45.949 That makes it feel much more approachable. And 00:06:45.949 --> 00:06:48.529 the source mentions Google AI Studio as a place 00:06:48.529 --> 00:06:50.709 to practice ordering. Yep. It's a free playground. 00:06:50.790 --> 00:06:52.490 You can go in there right now and test prompts. 00:06:52.730 --> 00:06:55.009 You can literally type search for dentists in 00:06:55.009 --> 00:06:57.250 Seattle and tell me which ones have the best 00:06:57.250 --> 00:07:00.110 reviews for handling scared patients. Scared 00:07:00.110 --> 00:07:02.850 patients. That's such a human filter. It is. 00:07:03.050 --> 00:07:05.069 And the AI will read the reviews and give you 00:07:05.069 --> 00:07:07.750 an answer. This lets you find these hidden insights. 00:07:07.949 --> 00:07:10.410 But the source takes it a step further. It talks 00:07:10.410 --> 00:07:12.550 about building assistance. This is the chatbot 00:07:12.550 --> 00:07:14.689 part. Right. Because here's the other problem 00:07:14.689 --> 00:07:17.290 businesses face. The phone rings constantly. 00:07:17.589 --> 00:07:20.800 Are you open? Do you have parking? The same questions 00:07:20.800 --> 00:07:24.139 100 times a day. Exactly. So the opportunity 00:07:24.139 --> 00:07:26.699 is to build an AI chat bot for their website. 00:07:26.939 --> 00:07:29.779 But, and this is critical, you don't use a generic 00:07:29.779 --> 00:07:33.139 AI standard chat GPT for this. Why not? Because 00:07:33.139 --> 00:07:35.519 of that hallucination problem. A generic bot 00:07:35.519 --> 00:07:37.279 might guess. It might say, oh, yes, they have 00:07:37.279 --> 00:07:39.339 a huge parking lot just to be helpful when they 00:07:39.339 --> 00:07:40.920 only have street parking. And then the customer 00:07:40.920 --> 00:07:44.100 shows up, gets mad, and leaves. Exactly. But 00:07:44.100 --> 00:07:47.100 a chat bot connected to the Maps update using 00:07:47.100 --> 00:07:51.319 that API waiter pulls real verified info. It 00:07:51.319 --> 00:07:54.000 becomes an honest assistant. It only answers 00:07:54.000 --> 00:07:57.040 with what is actually in the grounded data. I 00:07:57.040 --> 00:07:59.300 have to say, even with the waiter analogy, the 00:07:59.300 --> 00:08:01.899 idea of setting up an API connection, it still 00:08:01.899 --> 00:08:03.740 sounds kind of heavy. I mean, I can write a script, 00:08:04.019 --> 00:08:06.339 but connecting databases. I get that. I really 00:08:06.339 --> 00:08:10.300 do. But the source emphasizes these no code tools. 00:08:11.000 --> 00:08:14.040 platforms like Zapier or Voice Flow. It's really 00:08:14.040 --> 00:08:16.180 like playing with Lego blocks. You grab a block 00:08:16.180 --> 00:08:18.620 that says Google Maps. You grab one that says 00:08:18.620 --> 00:08:20.879 Chatbot, and you just snap them together. You're 00:08:20.879 --> 00:08:23.420 connecting pipes, not writing code. You got it. 00:08:23.759 --> 00:08:25.959 So is this something you can actually sell to 00:08:25.959 --> 00:08:28.399 a normal shop owner? Will the guy running the 00:08:28.399 --> 00:08:30.699 pizza place get it? He will when you tell him 00:08:30.699 --> 00:08:32.559 it stops his phone from ringing with the same 00:08:32.559 --> 00:08:34.820 quarrel about gluten -free crust during the lunch 00:08:34.820 --> 00:08:37.559 rush. That's the selling point. It saves them 00:08:37.559 --> 00:08:39.799 time. Time and accuracy. Okay, so we have the 00:08:39.799 --> 00:08:41.799 tools. Now let's talk about the actual work. 00:08:42.960 --> 00:08:45.320 Optimization. Section 4 of The Source gets into 00:08:45.320 --> 00:08:48.059 the nitty -gritty of rewriting profiles. This 00:08:48.059 --> 00:08:50.779 is the low -hanging food. This is the $500 service 00:08:50.779 --> 00:08:52.340 you can sell tomorrow. The Source gives a great 00:08:52.340 --> 00:08:55.759 example of Joe's Pizza. The bad version is just 00:08:55.759 --> 00:08:58.279 best pizza in town. Which, honestly, is what 00:08:58.279 --> 00:09:02.059 90 % of places say. It's lazy. And the AI hates 00:09:02.059 --> 00:09:05.100 it because there's no data there. Best is an 00:09:05.100 --> 00:09:08.000 opinion, not a fact. So how do we optimize Joe's? 00:09:08.220 --> 00:09:10.860 You load it up with what the source calls hooks. 00:09:11.940 --> 00:09:15.129 Like... Joe's Pizza specializes in thin crust 00:09:15.129 --> 00:09:17.870 NY -style pizza. We're a family -friendly spot 00:09:17.870 --> 00:09:20.889 with large booths. We offer gluten -free crust 00:09:20.889 --> 00:09:23.789 options and we're open until 11 p .m. Okay, I 00:09:23.789 --> 00:09:25.509 see the difference immediately. Look at all those 00:09:25.509 --> 00:09:28.509 hooks. Thin crust, family -friendly, large booths, 00:09:28.570 --> 00:09:31.509 gluten -free, 11 p .m. Now when someone asks 00:09:31.509 --> 00:09:33.909 Gemini, where can I take my kids for late -night 00:09:33.909 --> 00:09:37.169 pizza with gluten -free options, Joe's is the 00:09:37.169 --> 00:09:39.669 only answer. You're giving the AI all these handles 00:09:39.669 --> 00:09:41.970 to grab onto. Exactly. And it applies to service 00:09:41.970 --> 00:09:44.350 menus, too. Don't just list oil change. List 00:09:44.350 --> 00:09:47.269 express oil change, 15 minutes with fluid top 00:09:47.269 --> 00:09:50.429 off. Give the AI context. Now, this leads into 00:09:50.429 --> 00:09:52.370 reviews. And this part really surprised me. The 00:09:52.370 --> 00:09:54.230 source says the way we think about reviews is 00:09:54.230 --> 00:09:56.309 totally outdated. Completely. We all thought 00:09:56.309 --> 00:09:58.549 a five -star rating was the gold standard. But 00:09:58.549 --> 00:10:01.590 a five -star review with no text? To Gemini, 00:10:01.710 --> 00:10:04.309 that's weak. It's almost useless. Because there's 00:10:04.309 --> 00:10:07.529 no semantic data, no information. Right. The 00:10:07.529 --> 00:10:10.470 AI reads reviews to learn facts. So the strategy 00:10:10.470 --> 00:10:12.990 now is to coach your clients to ask for specifics. 00:10:13.190 --> 00:10:15.409 How does that conversation even go? Instead of 00:10:15.409 --> 00:10:18.269 saying, please review us, you teach them to say, 00:10:18.769 --> 00:10:21.509 hey, could you please mention the outdoor seating 00:10:21.509 --> 00:10:24.149 or the tiramisu in your review? Oh, that's clever. 00:10:24.330 --> 00:10:26.850 You're prompting the customer. And when the customer 00:10:26.850 --> 00:10:29.570 writes, the outdoor seating was lovely and the 00:10:29.570 --> 00:10:32.389 tiramisu was great, the AI learns two new facts. 00:10:32.990 --> 00:10:35.169 This place has outdoor seating and the tiramisu 00:10:35.169 --> 00:10:38.419 is good. So we are basically training the customers 00:10:38.419 --> 00:10:42.220 to write code for the AI. In a way, yeah. Specific 00:10:42.220 --> 00:10:45.039 words and reviews become data points the AI treats 00:10:45.039 --> 00:10:47.679 as facts. It's a feedback loop that makes the 00:10:47.679 --> 00:10:50.100 business more and more visible. That's fascinating. 00:10:50.320 --> 00:10:52.299 It turns your customer base into a marketing 00:10:52.299 --> 00:10:55.779 team. Or a data entry team, really. So we understand 00:10:55.779 --> 00:10:58.039 the tech. We understand the optimization. Let's 00:10:58.039 --> 00:11:00.120 talk about the business model. How do we turn 00:11:00.120 --> 00:11:02.500 this knowledge into money? The source outlines 00:11:02.500 --> 00:11:05.139 a pitch strategy using a front door analogy. 00:11:05.340 --> 00:11:07.820 This is crucial. You can't walk into a bakery 00:11:07.820 --> 00:11:10.320 and start talking about APIs and large language 00:11:10.320 --> 00:11:12.799 models. Their eyes will just glaze over. Yeah, 00:11:12.919 --> 00:11:16.360 totally. The front door pitch is, hi, I noticed 00:11:16.360 --> 00:11:18.740 something. People are now asking their phones 00:11:18.740 --> 00:11:21.799 questions like, where is a quiet coffee shop? 00:11:22.279 --> 00:11:24.440 And because your profile doesn't answer that, 00:11:24.779 --> 00:11:27.059 the AI is effectively locking your front door. 00:11:27.279 --> 00:11:28.980 It's sending people to your competitor. That 00:11:28.980 --> 00:11:31.679 hits a nerve. The AI is skipping you. It creates 00:11:31.679 --> 00:11:35.080 immediate urgency. and then you back it up with 00:11:35.080 --> 00:11:37.539 a competitive audit. This is the competitor check 00:11:37.539 --> 00:11:40.379 from section B. Right. You run a report. You 00:11:40.379 --> 00:11:42.620 ask Gemini to compare the client to their biggest 00:11:42.620 --> 00:11:45.039 rival. The AI might come back and say, your competitor 00:11:45.039 --> 00:11:48.360 mentions 204 .7 availability clearly, and you 00:11:48.360 --> 00:11:50.759 don't. And you put that on a PDF and just slide 00:11:50.759 --> 00:11:52.759 it across the table. You are losing customers 00:11:52.759 --> 00:11:55.019 because you didn't write 24 .7. I can fix that 00:11:55.019 --> 00:11:57.419 for you. It's an easy yes. And then you move 00:11:57.419 --> 00:11:59.659 them up the offer ladder. Exactly. You start 00:11:59.659 --> 00:12:02.179 with a free audit, maybe a quick video. Then 00:12:02.179 --> 00:12:05.379 you sell the fix, the $500 rewrite of their description 00:12:05.379 --> 00:12:08.509 and services, and then the holy grail. The monthly 00:12:08.509 --> 00:12:10.830 retainer. This is the part I wanted to ask about. 00:12:11.350 --> 00:12:14.210 The source mentions charging like $300 a month. 00:12:14.669 --> 00:12:17.470 Why would a plumber pay a monthly fee for this 00:12:17.470 --> 00:12:20.460 once the description is written, isn't it? Done. 00:12:20.840 --> 00:12:23.240 That's a common misconception. The AI favors 00:12:23.240 --> 00:12:25.600 businesses that look alive. It wants to see recent 00:12:25.600 --> 00:12:28.320 activity. If a business hasn't replied to a review 00:12:28.320 --> 00:12:31.940 in six months, the AI might downgrade its relevance. 00:12:32.080 --> 00:12:35.340 Oh, OK. It's a signal of life. The monthly fee 00:12:35.340 --> 00:12:38.360 is for activity management. You're replying to 00:12:38.360 --> 00:12:40.559 reviews, posting updates, uploading new photos. 00:12:40.940 --> 00:12:42.899 You're signaling to Gemini that this business 00:12:42.899 --> 00:12:45.740 is open, active, and reliable. So you're paying 00:12:45.740 --> 00:12:47.980 to stay active. Yeah. Because the owner's too 00:12:47.980 --> 00:12:50.460 busy fixing pipes to reply to a review about 00:12:50.460 --> 00:12:53.440 a water heater. Exactly. It's an insurance policy 00:12:53.440 --> 00:12:55.899 against becoming invisible again. The source 00:12:55.899 --> 00:12:59.019 also lists specific industries to target. Restaurants, 00:12:59.059 --> 00:13:02.080 of course, but also trades, dentists, and gyms. 00:13:02.320 --> 00:13:04.639 These are all high intent, high trust categories. 00:13:04.779 --> 00:13:06.919 I mean, think about dentists. People are terrified 00:13:06.919 --> 00:13:09.480 of dentists. I am, yeah. Right. So people are 00:13:09.480 --> 00:13:12.360 searching for gentle dentists near me. or dentist 00:13:12.360 --> 00:13:15.779 for anxiety. If you optimize a dentist's profile 00:13:15.779 --> 00:13:20.220 for the words gentle and anxiety free, that is 00:13:20.220 --> 00:13:22.600 a gold mine. You're capturing the most motivated 00:13:22.600 --> 00:13:24.539 customers. It really highlights that this isn't 00:13:24.539 --> 00:13:27.139 just about keywords. It's about the psychology 00:13:27.139 --> 00:13:29.279 behind the search. It's about answering the human 00:13:29.279 --> 00:13:33.059 need. OK, we're back. We've covered a lot of 00:13:33.059 --> 00:13:36.240 ground, pun intended. Let's try to distill this. 00:13:36.570 --> 00:13:39.490 What is the big idea here? The big idea is that 00:13:39.490 --> 00:13:42.190 the world of local search has fundamentally shifted. 00:13:42.210 --> 00:13:44.710 It's moved from keyword stuffing, you know, pizza, 00:13:44.850 --> 00:13:48.330 pizza, pizza, to context and conversation. And 00:13:48.330 --> 00:13:51.049 Gemini is the new gatekeeper. It is. And the 00:13:51.049 --> 00:13:53.610 opportunity lies in the fact that 99 % of agencies 00:13:53.610 --> 00:13:55.629 are still doing it the old way. They're still 00:13:55.629 --> 00:13:58.370 buying backlinks and stuffing keywords. The big 00:13:58.370 --> 00:14:00.309 idea is that you can be the translator. You help 00:14:00.309 --> 00:14:03.029 businesses speak the language of the AI. That's 00:14:03.029 --> 00:14:05.190 it. So it's about... grounding, making sure the 00:14:05.190 --> 00:14:07.809 facts are there. It's about specificity, rewriting 00:14:07.809 --> 00:14:10.549 profiles to have those hooks. And it's about 00:14:10.549 --> 00:14:12.929 reviews, getting that descriptive fuel for the 00:14:12.929 --> 00:14:14.950 engine. You get those three things right. You 00:14:14.950 --> 00:14:16.889 don't just improve a listing. You could actually 00:14:16.889 --> 00:14:20.470 change the trajectory of a business. So for everyone 00:14:20.470 --> 00:14:23.289 listening who is thinking, this sounds cool, 00:14:23.289 --> 00:14:26.649 but what do I do right now? The source gives 00:14:26.649 --> 00:14:29.289 a very specific call to action. It does. And 00:14:29.289 --> 00:14:32.370 I love this plan because it requires zero money. 00:14:32.539 --> 00:14:35.899 to start. Go to Google AI Studio. Yes. Go to 00:14:35.899 --> 00:14:39.399 Google AI Studio, play with the map tools, but 00:14:39.399 --> 00:14:42.360 then pick a favorite local spot. Maybe it's that 00:14:42.360 --> 00:14:44.340 cafe you go to every morning. And look at their 00:14:44.340 --> 00:14:47.519 profile with fresh eyes. Audit them. Find three 00:14:47.519 --> 00:14:49.240 things they're missing. Do they mention they 00:14:49.240 --> 00:14:51.580 have oat milk? Do they mention the wifey speed? 00:14:51.940 --> 00:14:54.360 Is the menu updated? Write those three things 00:14:54.360 --> 00:14:57.360 down. I'm in. Walk in. buy a coffee and just 00:14:57.360 --> 00:14:59.539 tell the owner, hey, I noticed people are asking 00:14:59.539 --> 00:15:01.820 for oat milk on maps and you're missing out. 00:15:01.820 --> 00:15:04.500 I can fix that for you for free. Do it for free. 00:15:04.539 --> 00:15:07.320 Get your first case study, prove it works. Once 00:15:07.320 --> 00:15:09.440 you have that result, you can walk into the shop 00:15:09.440 --> 00:15:11.720 next door and charge them full price. I love 00:15:11.720 --> 00:15:15.379 that. It's low risk, high reward. It's the best 00:15:15.379 --> 00:15:17.720 way to learn. You know, the source ends with 00:15:17.720 --> 00:15:20.019 a thought that really stuck with me. It says 00:15:20.019 --> 00:15:23.860 we aren't selling magic. We are fixing invisible 00:15:23.860 --> 00:15:26.659 businesses. It's a powerful thought. It really 00:15:26.659 --> 00:15:29.539 is. Because in the modern economy, if the AI 00:15:29.539 --> 00:15:32.740 can't see you, if it can't understand your vibe 00:15:32.740 --> 00:15:37.100 and verify your facts, do you even exist? For 00:15:37.100 --> 00:15:39.000 a whole generation of customers, the answer is 00:15:39.000 --> 00:15:41.480 no. Something to think about next time you ask 00:15:41.480 --> 00:15:43.679 your phone for a recommendation. Thanks for diving 00:15:43.679 --> 00:15:45.620 in with us. Always a pleasure. We'll see you 00:15:45.620 --> 00:15:46.019 on the next one.