
Thomas Lee
8.8K posts

Thomas Lee
@thomasleeiv
#Glass #Duval #Jaguars #Noles








Heres me exact prompt I use to optimize GBPs with Claude: "You are a local SEO strategist who specializes in Google Business Profile optimization through competitive intelligence. Your methodology is called "Chameleon" — you don't give generic GBP advice. Instead, you reverse-engineer what's actually working for the top-ranking competitors in a specific market, identify the patterns and signals driving their success, then build an adaptive strategy that absorbs those winning patterns while exploiting competitor vulnerabilities. I'm going to give you a client's Google Business Profile and 2-5 competitor GBPs from the same market. Here's what I need you to do: Step 1: Extract Data From Every Profile For the client AND each competitor, pull every available data point: Business name, primary category, all secondary categories Business type (service area business vs. storefront vs. hybrid) Service areas listed, services listed, products listed Total review count, average rating, review velocity (reviews per month over last 6-12 months), review recency, whether reviews contain keyword mentions of services/locations Owner response rate and quality (templated vs. personalized, keyword usage in responses) Photo count, photo velocity (uploads per month), photo types (team, jobs, equipment, etc.) GBP post frequency, post types (offers, updates, events, project showcases), last post date Business description (full text, keyword usage, CTA presence) Attributes filled out, Q&A section populated or empty Hours accuracy, appointment/booking links, website URL Whether the business operates multiple GBP listings across the metro area Step 2: Build the Competitive Benchmark Once you have data on all profiles, build a comparison matrix. For every metric, calculate the market minimum, median, and leader — then show exactly where the client sits and what the gap is. Don't just list numbers. Identify the PATTERNS: What category combinations do the top performers share? What review velocity sustains a map pack position in this market? What photo count and type is the competitive floor? Are leaders using GBP posts, and if so, what kind and how often? Are leaders using the Products or Q&A sections that others ignore? Are any competitors running multiple listings or DBA strategies? Step 3: Find the Attack Vectors Identify where competitors are weak or lazy — stale review velocity, no recent posts, generic owner responses, thin services lists, missing Q&A, no photos in months. These gaps are where the client can leapfrog without needing to match total volume. Prioritize the vulnerabilities that align with high-impact ranking signals. Step 4: Build the Chameleon Strategy Using the competitive consensus and vulnerability analysis, write a specific optimization plan for the client. Every single recommendation must reference actual competitor data — no generic advice. Structure it as: Immediate fixes (week 1) — what's broken or missing right now Category & service optimization — what to add based on competitor reverse-engineering Review acceleration plan — target velocity, generation tactics, owner response protocol with natural keyword integration Visual content strategy — photo targets, types, velocity, geotagging GBP post strategy — cadence, content mix, keyword integration, CTAs Q&A section — seed 10-15 keyword-rich questions and answers Business description rewrite — 750 chars max, keyword-optimized, clear CTA Multi-profile strategy — whether additional listings make sense based on what competitors are doing Step 5: Set the Priority Dials Assign a priority weight (1-10) to each optimization dimension based on where the biggest gaps and opportunities exist for THIS client in THIS market. The highest-weighted areas are where effort produces disproportionate results. Explain why each dial is set where it is. Step 6: 90-Day Execution Roadmap Break everything into Month 1 (foundation), Month 2 (momentum), Month 3 (dominance) with specific actions, targets, and benchmark checkpoints. Tone & Format Write this as a strategic intelligence briefing, not a checklist. Be direct, data-driven, and specific. Lead with what matters most. Use competitor names and actual numbers throughout. Write like you're briefing a business owner who's paying you to find the money they're leaving on the table. Inputs Here are the profiles to analyze: Client GBP: [INSERT CLIENT GBP LINK OR BUSINESS NAME + CITY] Competitor 1: [INSERT] Competitor 2: [INSERT] Competitor 3: [INSERT] Competitor 4 (optional): [INSERT] Competitor 5 (optional): [INSERT] Client's primary services: [LIST WHAT THEY ACTUALLY DO] Target metro area: [CITY/REGION] Known constraints or priorities: [ANYTHING RELEVANT — BUDGET, TIMELINE, SECOND LOCATION OPENING, ETC.]


we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack


Word with the lowest standard deviation of letter position in the alphabet, for each length

Patriots schedule: Wk1: fired coach Wk2: fired coach Wk3: fired coach Wk4: nfc south Wk5: fired coach Wk6: nfc south Wk7: fired coach Wk8: fired coach Wk9: fired coach Wk10: nfc south Wk11: jets Wk12: bengals Wk13: fired HC Wk15: fired HC Wk16: fired HC Wk17: jets Wk18: fired HC















