Categories, description, and website URL on GBP feed both Maps and answer retrieval. What to align with your schema.
Google Business Profile (GBP) is not only a Maps listing. Categories, description, website URL, and NAP feed the same local graph that answer surfaces and assistants consult when someone asks who to call, where to go, or which brand matches a place.
If your schema says one category and GBP says another, you taught a conflict. Align them on purpose.
What GBP contributes to answer readiness
| GBP field | Why it matters for AEO / local answers | Align with |
|---|---|---|
| Business name | Entity label | Site H1, schema name |
| Primary category | Type disambiguation | Real-world category; schema @type / additional types |
| Description | Short definitional copy | Meta description voice; About blurb |
| Website URL | Canonical site link | Prefer https canonical host |
| Address / service area | Place resolution | On-site NAP, schema address |
| Phone | Contact fact | Footer + schema telephone |
| Hours | Operational truth | On-site hours if published |
| Products / services | Offer clarity | Site service pages |
GBP will not replace a clear About page. It reinforces the same story in Google's local inventory.
Primary category and schema
Pick the most specific accurate primary category. Do not choose a trendier category you do not fulfill — short-term discovery games become long-term wrong answers.
| Business reality | GBP primary category (illustrative) | Schema leaning |
|---|---|---|
| Single retail storefront | Store subtype that fits | LocalBusiness subtype |
| Clinic with appointments | Medical / dental appropriate type | Relevant subtype + physician pages if needed |
| B2B office, rare visits | Company HQ / office style | Often Organization on site; GBP only if you truly want the place public |
| Service-area plumber | Service-area business settings | LocalBusiness without fake storefront pin |
When in doubt on types, read Organization vs LocalBusiness.
Description: write a definition, not a brochure
Same advice as meta descriptions assistants reuse: lead with who you are and who you serve. Skip hype words. Hypothetical Northstar Analytics storefront (they mostly should not force a GBP if they are pure SaaS — this is illustrative for a regional analytics consultancy arm):
Northstar Analytics Consulting is a product analytics consultancy in Austin serving mid-market SaaS teams. We help clients instrument activation events and build retention dashboards.
Mirror the nouns on your website. Do not invent a second brand voice for Maps.
Website URL and UTM hygiene
| Practice | Do | Avoid |
|---|---|---|
| URL | Canonical https host that 200s | Tracking redirects that strip path |
| Landing | Homepage or true location page | Random campaign LP that 404s next month |
| Parameters | Clean URL in GBP | Forever UTMs that create duplicate indexed junk |
If apex and www both work, fix canonicalization first so GBP and schema point at one.
Step-by-step alignment
- Export or screenshot GBP name, category, description, URL, NAP, hours.
- Open your LocalBusiness/Organization JSON-LD and footer; paste into a comparison table.
- Resolve mismatches toward the canonical NAP doc from your NAP checklist.
- Update GBP fields that are wrong (name changes have rules — do not game renames).
- Update site schema and visible contact blocks the same day.
- Confirm the website URL in GBP returns 200 to normal and AI-friendly fetches (no accidental Bot Fight on the homepage).
- Add photos and services only if true; outdated menus become hallucinated facts.
Reviews and Q&A (honest ceiling)
Reviews influence trust for humans and often appear in local packs and summaries. You cannot fake your way into durable trust. Respond factually. Fix operations that cause one-star themes. Astroturfing backfires when assistants cite the thread that calls it out.
Q&A on GBP should match pricing and policy pages. If GBP says walk-ins welcome and the site says appointments only, expect confused answers.
Mistakes
- Stuffing keywords into the business name
- Using a personal cell that changes every quarter as the GBP phone
- Listing a coworking address you do not control as a storefront
- Letting an ex-employee remain an owner on the profile
- Ignoring GBP while investing only in schema — local retrieval still leans on the profile
How to verify
| Check | Pass |
|---|---|
| Name vs site vs schema | Same core string |
| Category vs real services | Accurate |
| Website link | 200, canonical host |
| NAP | Matches checklist |
| Description | Definitional, current |
BrandKnown scans your website for access and identity readiness (~60-second scan; Agency plan $49/mo for teams managing multiple brands). It does not replace walking through the GBP UI — do both when local matters.
Treat GBP as part of the entity record, not a side marketing chore. Categories, description, and URL should tell the same story your schema already claims.
Products, services, and attributes
If GBP lets you list services or products, copy names from the website — same spelling as pricing and schema offers. Inventing a "Premium AI Audit Plus" only on Maps guarantees someone will ask your sales team for a SKU that does not exist.
Attributes (women-owned, LGBTQ+ friendly, wheelchair accessible, and similar) should be true. False attributes are not a growth hack; they are a trust failure waiting to be screenshotted.
Owner and agent hygiene
| Role issue | Fix |
|---|---|
| Ex-employee still owner | Transfer ownership; remove managers |
| Agency left as primary owner | Keep agency as manager if useful; brand retains ownership |
| Unclaimed duplicate listing | Claim/request access; consolidate |
| Personal Gmail as only owner | Add a shared company-owned recovery path |
Document who owns GBP in the same runbook as DNS and the domain registrar. Local entity work dies when the only owner left the company.
A clean GBP will not overcome a blocked homepage fetch. If Cloudflare or middleware 403s the site linked from the profile, fix bot access in parallel. Profile and website have to agree and load.