Stuffing your Google Business Profile name with city tokens stopped working in December 2021.
- ✓ Google's Vicinity Update rebalanced the local algorithm: proximity weight up, business-name query weight down.
- ✓ The same-address filter suppresses competing agent profiles at the brokerage's shared physical address.
- ✓ Entity architecture (categories, areaServed, Person / Service nodes) replaces the business-name stuffing pattern that the algorithm now demotes.
Local SEO for real estate has three structural facts that govern whether the local pack returns your profile.
Real estate search intent bifurcates into explicit local queries (Miami real estate agent) and implicit local queries (real estate agent near me). Google serves both primarily through the Local 3-pack, which leans on proximity, NAP (Name, Address, Phone) consistency, and citation quality. The Vicinity Update of December 2021 increased the weight of user proximity and decreased the ranking power of business-name query tokens, which inverted the risk-to-reward ratio on the long-running pattern of stuffing the GBP business name with city tokens. The work that ranks now sits at the entity-architecture layer, where real estate SEO services built around RealEstateAgent schema, areaServed coverage, and same-address-filter work-arounds replace the business-name stuffing pattern.
The Vicinity Update inverted the GBP business-name calculus.
Before December 2021, putting John Doe - Miami Luxury Realtor in the GBP business-name field paid off in the local pack. The Vicinity Update rebalanced the algorithm: proximity weight went up, business-name query-token weight went down. State license law has always required clear brokerage disclosure under NAR SOP 12-9, which the city-stuffed business name violated. Post-Vicinity, the SOP violation persists without the ranking payoff. The pattern that ranks now uses categories, areaServed schema, and proximity-weighted entity signals rather than the business-name field.
The same-address filter suppresses competing agent profiles at one brokerage.
Google's local pack runs a diversity filter against multiple Google Business Profiles at the same physical address. When fifty agents share a brokerage's address, the algorithm surfaces a small number per query and filters the rest. The work-around is entity architecture: each agent's primary category fits their actual practice area (commercial real estate agency for the commercial agent, real estate broker for the broker, real estate consultant for the relocation specialist), each agent's areaServed schema maps to their actual licensed geography without identical claims across colleagues, and the Person / Service nodes carry the differentiating signals the algorithm reads.
areaServed schema is the structured-data replacement for city-name stuffing.
RealEstateAgent and RealEstateAgency nodes both carry an areaServed property. The schema accepts AdministrativeArea (a county, city, township, school district, MSA), GeoShape (a polygon for a coastline, corridor, or relocation coverage), or Place (a named locality below jurisdiction level: West Village, Buckhead, Wicker Park). Post-Vicinity, the local pack's geographic relevance signal leans on the schema-side coverage claim plus the GBP service-area configuration. The schema layer and the GBP service-area configuration should mirror each other. Misaligned signals (GBP service areas covering five counties, schema areaServed covering one city) muddy the relevance and weaken local-pack visibility.
NAP consistency across the 50+ real-estate directories is foundational citation signal.
Real estate carries an unusually long directory list: Zillow profiles, Realtor.com profiles, brokerage networks, state and local Realtor association directories, MLS member directories, chamber listings, and the standard general-purpose directories. Inconsistent Name, Address, Phone across these directories suppresses citation quality and degrades local-pack visibility for months while the algorithm reconciles the entity. A brokerage rebrand or office move that propagates inconsistently across the directory set is the most-common cause of local-pack rank loss. The cleanup is mechanical and worth the cost.
From local-pack diagnostic to live entity architecture in four weeks. Then the citation work runs as a retainer.
Local-pack diagnostic
Audit the Google Business Profile (business name, primary and secondary categories, service-area configuration, review profile, profile completeness), the RealEstateAgent and RealEstateAgency schema on the site, the NAR SOP 12-9 firm-name disclosure pattern across listing pages and footer, and the same-address overlap with colleagues at the brokerage. Output names the entity-architecture gaps and the citation gaps the algorithm is reading.
GBP and schema rebuild
Business-name field rewritten to the SOP 12-9-compliant form (agent name plus brokerage where state license law requires it). Primary category fit to actual practice area. Service-area configuration mapped to actual licensed geography. RealEstateAgent schema with parentOrganization linking to the brokerage's RealEstateAgency node. areaServed mapped to the same geography the GBP claims. Service and Person nodes added where the same-address filter is suppressing profile visibility.
NAP and citation reconciliation
NAP sweep across the 50+ real-estate directories. Inconsistencies (variant brokerage names, old phone numbers, prior addresses, missing license-number disclosures) fixed at the directory layer where the operator has access, queued for vendor support where the directory locks edits behind the platform. Sitewide footer block normalized so every page ships the canonical NAP plus license disclosure.
Retainer cadence
Monthly cadence on content the diagnostic surfaced (neighborhood pages on the SOP 10-2 safe-harbor pattern, areaServed expansion as the practice's geographic surface grows). Quarterly review on local-pack visibility against the GBP Insights data, the RealEstateAgent schema validation, and the directory consistency. Annual review against algorithm updates.
What agents and brokerages ask about local SEO before they book a diagnostic.
[ 01 ] Does stuffing my Google Business Profile name with city tokens still work? +
[ 02 ] Which Google Business Profile category should an agent pick? +
[ 03 ] How important is NAP consistency across directories? +
[ 04 ] How does areaServed schema show up in local SEO? +
Rebuild the entity layer for the post-Vicinity local pack. Map areaServed to your actual licensed geography. Reconcile NAP across the directories that feed the local algorithm. Book a diagnostic.
We read your Google Business Profile, your RealEstateAgent and RealEstateAgency schema, your sitewide NAP consistency, and your same-address overlap with colleagues at the brokerage. Diagnostic comes back inside two weeks with the entity-architecture rebuild scope, the GBP and schema reconfiguration, and the directory-cleanup ledger.