Stuffing your business name with city names stopped working in December 2021.
Google's Vicinity Update rebalanced the local algorithm: proximity weight up, business-name query weight down. · Same-address brokerage filter suppresses competing agent profiles at one physical address. · areaServed schema carries the geographic relevance that the business name used to.
Local SEO for real estate has four post-Vicinity facts that govern whether you show up in the 3-pack.
The local algorithm changed in December 2021. The patterns that ran the local play through 2020 stopped working. NAR SOP 12-9 was always going to flag the business-name stuffing pattern anyway. The post-Vicinity surface runs on proximity, categories, areaServed schema, and entity architecture.
Vicinity Update killed the city-name-in-business-name play. Pre-Vicinity, agents stuffed their Google Business Profile names with city tokens to win the 3-pack. Google's December 2021 Vicinity Update increased proximity weight significantly and decreased business-name query weight significantly. The risk-reward inverted: the SOP 12-9 violation risk stayed the same, the ranking benefit collapsed. Post-Vicinity, categories plus areaServed schema do the work.
Same-address Google Business Profile diversity filter. Google allows individual agents to have their own profiles at the same physical address as the brokerage's RealEstateAgency profile. The local algorithm's diversity filter then suppresses competing agent profiles at the same address for the same query. Solo agents compete against the brokerage and against colleagues for one slot. The route-around is distinct categories, areaServed schema that doesn't collide with sibling agents, and entity architecture the algorithm can disambiguate.
areaServed schema replaces the city-name-in-business-name pattern. address tells Google where your office is. areaServed tells Google where your service is offered. Post-Vicinity, local pack relevance runs on proximity plus the geographic surface the algorithm believes you serve. areaServed (accepting AdministrativeArea, GeoShape, or Place) carries the licensed surface in a structured-data signal. This is what does the work the business-name stuffing used to.
NAP consistency across the 50+ real estate directory ecosystem. Real estate operators have citation surfaces across Zillow profiles, Realtor.com profiles, brokerage networks, state and local association directories, and chamber listings. Inconsistencies suppress citation quality, which is a foundational local ranking signal. A brokerage rebrand or office move that propagates inconsistently across directories degrades local pack visibility for months. The cleanup is mechanical and worth the cost.
From local audit to post-Vicinity surface in four weeks. Then proximity and schema compound.
- WEEK 0
Local diagnostic
Google Business Profile audit (categories, address, business-name pattern, same-address filter risk against sibling agents at the brokerage). NAP audit across the 50+ real estate directory ecosystem. Schema audit on areaServed coverage. Local pack ranking review per ZIP for the priority queries. Output names the post-Vicinity gaps and the entity-architecture repair scope.
- WEEK 1
Google Business Profile reset
Categories corrected per the Real estate agent / Real estate agency / Real estate broker / Commercial real estate agency model. Business name reset to comply with SOP 12-9 and avoid post-Vicinity penalty surfaces. Service areas mapped. Photos and review-response cadence tightened. Profile is reset to the post-Vicinity pattern.
- WEEK 2-3
Schema and citations
areaServed schema built per the licensed geographic surface, using GeoShape where granular polygons matter, AdministrativeArea where county or city is sufficient. RealEstateAgent nested under the brokerage's RealEstateAgency. NAP consistency cleanup across priority directories. Citation surfaces that match the Google Business Profile data.
- ONGOING
Retainer cadence
Monthly review of local pack movement per priority ZIP. Quarterly citation audit against directory drift. Annual schema audit against algorithm updates. Same-address filter monitoring as sibling agents at the brokerage shift their profiles, which can change the suppression pattern at any time.
Named-client testimonials surface here as engagements ship.
Operators who shipped post-Vicinity local pack visibility.
Five hyperlocal content patterns that compound over the citation graph and the GBP work.
Local-pack ranking responds to proximity and citation consistency. The organic-search surface around local-pack queries responds to the content the site ships about the geography itself. The patterns below convert local-pack inputs into organic-search visibility on the queries that buyers actually run.
- 01
Neighborhood landing pages built on the SOP 10-2 safe-harbor pattern.
A standalone page per neighborhood the practice serves, structured around factual third-party-attributed data: Census Bureau demographics, standardized walkability scores, factual school district boundaries with no subjective quality ratings, transit accessibility metrics. The content survives Fair Housing review and ranks for the neighborhood-name queries the buyer actually runs.
- 02
Long-tail neighborhood-specific query coverage.
"Three-bedroom homes in [neighborhood]", "condos near [landmark]", "Victorian houses in [historic district]", "homes near [school district boundary]". Each long-tail query has a low absolute search volume and a high commercial intent. The pages do not need to be long; they need to be specific. Five paragraphs of substantive content per page outperforms three hundred words of generic copy.
- 03
Hyperlocal market data published on a monthly cadence.
Median sale price trend for the past 12 months in the specific neighborhood. Days-on-market changes. Inventory shifts. Days-from-listing-to-pending changes. The reports earn editorial mentions in hyperlocal blogs and community publications (which is the local-link-acquisition surface) while also ranking on their own for the neighborhood-name plus "market report" query.
- 04
Practice-area pages mapped to the actual geographic operating surface.
"Luxury real estate agent in [neighborhood]", "first-time buyer agent in [neighborhood]", "investment property agent in [neighborhood]". The practice-area-plus-geography query family is where the agent profile can win against the brokerage profile under the same-address filter. The pages require knowsAbout schema populated for the practice area and areaServed schema mapped to the geography.
- 05
Internal-link graph routes practice-relevant traffic to the right capability page.
A neighborhood page that links to the luxury capability page sends a stronger signal for luxury queries in that neighborhood than a neighborhood page that links to a generic services page. The internal-link graph is one of the strongest signals Google uses to understand topical relationships across the site graph. The discipline is per-link intentionality rather than blanket sitewide navigation.
The local-pack-specific work (GBP architecture, citation consistency, same-address filter workaround) is covered above in the operations section and at the Google Business Profile article and the local citations article.
What operators ask about local SEO post-Vicinity.
-
Does stuffing my Google Business Profile name with city tokens still work?
No. Google's December 2021 Vicinity Update rebalanced the local algorithm: user proximity weight increased significantly, business-name query weight decreased significantly. The risk-to-reward ratio inverted. State license law has always required clear brokerage disclosure in advertising, and NAR SOP 12-9 enforces firm-name disclosure on every surface. The post-Vicinity local pack rewards categories, areaServed schema, and proximity. Business-name stuffing now risks the SOP violation without delivering the rank. -
Which Google Business Profile category should an agent pick?
The options are Real estate agent, Real estate agency, Real estate broker, and Commercial real estate agency. The right pick depends on what the entity actually is. A solo agent under a brokerage picks Real estate agent. The brokerage itself picks Real estate agency or Real estate broker per state license. A commercial specialist picks Commercial real estate agency. Picking the wrong category triggers the same-address filter conflicts more aggressively because the algorithm can't disambiguate the entity from the brokerage. -
How important is NAP consistency across directories?
NAP (Name, Address, Phone) consistency is foundational for local ranking signals. Real estate has 50+ relevant directories including Zillow profiles, Realtor.com profiles, brokerage networks, state and local association directories, and chamber listings. Inconsistencies suppress citation quality. A brokerage rebrand or office move that propagates inconsistently across directories will degrade local pack visibility for months while the algorithm reconciles the entity. The cleanup is mechanical and worth the cost. -
How does areaServed schema show up in local SEO?
areaServed on the RealEstateAgent or RealEstateAgency node defines the geographic surface where the service is offered. The schema accepts AdministrativeArea (a county or city), GeoShape (a polygon), or Place (a named location). Post-Vicinity, local pack relevance leans on proximity plus the geographic surface the algorithm believes the entity serves. areaServed is the structured-data signal that carries that relevance, and it's what replaces the city-name-in-business-name stuffing pattern that used to run the local play.
Stop pretending the city-name-in-business-name play still works. Run post-Vicinity local SEO on proximity, categories, areaServed schema, and entity architecture. Book a diagnostic.
We read your Google Business Profile, your local pack ranking per priority ZIP, your areaServed schema, your NAP consistency across the directory ecosystem, and your same-address filter risk against sibling agents at the brokerage. Diagnostic comes back inside two weeks with the post-Vicinity repair scope.