Your Google Business Profile name still reads 'John Doe Miami Luxury Realtor'. That stopped ranking in December 2021.
- ✓ The Vicinity Update significantly increased user-proximity weight in the local pack and significantly decreased the ranking power of city and service tokens packed into the business name.
- ✓ NAR SOP 12-9 requires the brokerage firm name on every advertising surface. State commissions require the brokerage in clear hierarchy. The stuffing violates both regardless of the update.
- ✓ Post-Vicinity, the local pack rewards GBP categories, areaServed schema, RealEstateAgent entity architecture, and proximity. Name-stuffing inverts the risk-to-reward ratio entirely.
The four shifts the Vicinity Update made in the local pack and what each shift means for a real estate practice's GBP.
The December 2021 Vicinity Update was Google's largest local-algorithm rebalance since the 2016 Possum update. For real estate, the algorithm pre-Vicinity rewarded packing city and service tokens into the GBP business name so heavily that the SEO-versus-compliance trade-off was empirically winnable on the SEO side. NAR SOP 12-9 firm-name disclosure violations and state-commission advertising-rule violations were the cost of doing local SEO. Post-Vicinity, the trade-off inverted: the compliance violations persist and the rank they used to buy no longer does. The post-update local pack rewards proximity, GBP category fit, areaServed schema, and RealEstateAgent entity architecture nested correctly under the brokerage's parentOrganization. That architecture is what real estate SEO services shifted toward after December 2021, and what compliant practices were doing anyway.
User proximity weighting increased significantly.
Pre-Vicinity, the local pack could surface a business several miles from the searcher's location if the business-name token match was strong enough. Post-Vicinity, the algorithm tightened the proximity weighting: physical distance from the searcher to the listed business address became a much larger relative factor in pack ranking. For a real estate agent's GBP, this means the address Google has on file (which is typically the brokerage's office address) governs the search-centroid radius the agent can rank in. The shift compresses the geographic surface a single GBP can defensibly cover and elevates the importance of accurate areaServed schema on the website and accurate GBP service-area configuration.
Business-name token-match ranking power decreased significantly.
The pre-Vicinity pattern of stuffing the GBP business name with city, niche, or service tokens (the canonical example: 'John Doe - Miami Luxury Realtor' rather than the agent's legal practice name) was rewarded by the algorithm with substantial uplift on city-plus-niche queries. The pattern was already in violation of Google's own GBP guidelines on name spam, NAR SOP 12-9 firm-name disclosure requirements, and state license-law advertising rules. Post-Vicinity, the ranking power of the stuffing collapsed. The compliance violation persists. The rank it used to buy does not. The risk-to-reward ratio inverted, and the post-Vicinity pattern is to file the GBP under the agent's legal practice name with the brokerage firm name carried in the secondary surface per Google's guidelines and per SOP 12-9.
Same-address filtering interacts with proximity differently post-Vicinity.
Google's local algorithm has always filtered competing GBPs at the same physical address: when fifty agents at one brokerage share the office address, the pack diversity filter suppresses most agents' profiles for any given query. The Vicinity Update's proximity weighting amplified this dynamic. With proximity carrying more weight and the brokerage address being the only address available for most agents, the algorithm's filtering decision compresses onto remaining signals: GBP primary and secondary categories, review counts and recency, inbound link profile, profile completeness. Stuffing the business name was the workaround agents reached for, and it no longer works.
The post-Vicinity local pattern runs on GBP categories, areaServed, schema, and proximity.
The local-pack signals that actually rank post-Vicinity are the GBP primary category (Real estate agent, Real estate broker, Real estate agency, Commercial real estate agency, picked to match the entity's actual operating type), secondary categories that disambiguate specialization, accurate areaServed schema on the website's RealEstateAgent node (AdministrativeArea, GeoShape, or Place to match the actual served geography), and the proximity tied to the physical address. RealEstateAgent nested under the brokerage's RealEstateAgency via parentOrganization satisfies the SOP 12-9 affiliation requirement at the schema layer. Service and Person entity authority on the website lifts the GBP's authority signal. The stack works together. Each piece compensates for the loss of business-name stuffing as a ranking lever.
What agents ask about the Vicinity Update when their GBP rankings drop and the old playbook stops working.
[ 01 ] What did the December 2021 Vicinity Update actually change in the local pack? +
[ 02 ] If I still stuff my GBP name with city tokens, does it help at all post-Vicinity? +
[ 03 ] How does the Vicinity Update interact with the same-address agent filter? +
[ 04 ] If business-name stuffing is dead, what actually ranks in the local pack now? +
If your Google Business Profile is still named for the city you serve, the SOP 12-9 violation is live and the ranking lift it used to buy is gone. Book a diagnostic.
We read your current GBP configuration against the post-Vicinity local-pack signal set (primary and secondary categories, areaServed alignment between website and GBP, RealEstateAgent schema nesting, same-address filter exposure) and against NAR SOP 12-9 firm-name disclosure plus the relevant state commission's advertising rules. Diagnostic comes back inside two weeks with the GBP cleanup plan and the entity-architecture rebuild that replaces the business-name stuffing pattern.