GBP & Local SEO Intent

What it is: the Google Business Profile taken from claimed to complete, with the search-intent map behind it - which query means what, which one the profile should answer, and what proves the answer is right.

Overview

Works out the smallest useful profile for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a profile. The GBP register - CSV, SQL DDL, JSON Schema, Notion mapping - is produced on request, from one field list so the four cannot drift apart.

Layer: Layer 3: Acquire. Fits: Starter stage. Table code: n/a.

The rule this table exists to enforce: five different things are recorded in one place and must not be confused - the profile itself, the services, the posts, the reviews, and the questions. A Row Type discriminator keeps them apart, because a profile update and a review reply are different actions with different owners, and merging them turns the register into a log nothing can be filtered out of.

The second rule: local rank is relevance, distance and prominence. A profile controls relevance directly and prominence partly. Nobody can buy a better local rank, and this skill never suggests otherwise.

When to Use This Skill

• Google Business Profile, Google My Business, GMB, GBP
• map pack, local pack, local SEO, "near me" searches
• "we do not appear on Google Maps"
• categories, services, products, attributes, business description
• GBP posts, updates, offers, events
• reviews, review replies, review strategy
• Bing Places, Apple Business Connect, and the other map surfaces
• local keyword and intent research

Do not use it for: the website's own page structure (business-website-setup), off-site directory citations (seo-directory-backlinks), or paid advertising - which buys clicks, not rank.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "set up" / "claim" / "we do not have one" -> artifacts wanted; go to Step 2.
• "we have one, it is not showing" -> something exists; capture the current state, then Step 2.
• "review" / "audit" / "what is wrong with it" -> a check, not a build.
• "which keywords" / "why do we not rank" -> an intent question, not a build.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: What is the business called, and what does one line of it actually do?

Step 2 - Ask only what is missing

Treat ambiguous replies as unanswered and ask which explicit option the user means. Record unknown values as Unknown; Unknown is not zero. A record must not be Done when a required check fails.

Skip anything already answered. Ask the rest one at a time, and stop as soon as the remaining answers would not change the profile spec.

• Location - Can customers visit a physical address, or is it a service-area business? / One location or several? / City, country, and the exact address as it should print?
• What it does - The full service list, in the words customers would use? / What does a new customer ask for first? / Is there a second, different kind of work?
• Current state - Is a profile already claimed and verified? / Who owns the login, and is it a personal account or a shared one? / What is the review count and average now?
• Proof - Can the premises be photographed, inside and out? / Is there a team, a process, stock or equipment worth showing? / Any seasonal or by-appointment behaviour?
• Engagement - Who reviews replies, and how fast? / Is anyone being asked for a review, and by what method? / Is there time to post weekly?

Never invent an answer. Address, phone, categories, services, review counts, ratings, keywords, opening hours and metrics the user has not supplied are Unknown. A review count is a measurement, never an estimate.

Step 3 - Hold the internal context

module: gbp-local-seo-intent
intent: null            # set up | fix | review | report | import
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Location": null
  "What It Does": null
  "Current State": null
  "Proof": null
  "Engagement": null
requested_outputs: []
confirmed_facts: []
open_questions: []

Step 4 - Recommend the smallest workflow

…