“Possum” is the local SEO industry’s name for substantial changes noticed in Google local results around September 2016. Google did not publish a ranking system called Possum or disclose its filters. The useful history therefore begins by separating contemporary observations from current official guidance: local visibility mainly depends on relevance, distance and prominence, while the result shown can change with the searcher, query and competitive context.
Possum in six evidence-backed points
Possum is an industry nickname. Google did not document an official system with this name or publish a Possum score, filter list or recovery process.
Practitioners reported major local-result movement around 1 September 2016. Contemporary analysis described changes involving proximity, query wording, city borders and similar businesses.
Filtered did not mean removed. A profile absent for one category-and-location query could still appear for its name, another location, another wording or another result surface.
The historical address and category patterns were observations, not a published formula. Google has never supplied a universal radius, similarity threshold or rule that lets every same-building business appear together.
Current official guidance is more reliable than a 2016 nickname. Google says local results are mainly based on relevance, distance and prominence, with accurate and complete business information supporting eligibility and matching.
Diagnosis needs samples, not one screenshot. Record search location, wording, time, device and result surface, then connect visibility with profile actions and qualified enquiries.
September 2016
What the 2016 record supports
| Date | What was observed or documented | Safe conclusion |
|---|---|---|
| Before September 2016 | Local practitioners already knew that distance, business data and competition could make rankings vary, but common tracking still relied heavily on one city-centre search. | A single position was never a complete map of local visibility. |
| Around 1 September 2016 | Industry trackers and consultants reported substantial changes in Local Pack and Local Finder results. | The timing is an industry observation; Google did not publish a Possum launch announcement. |
| 6 September 2016 | Joy Hawkins documented stronger filtering among similar local businesses and explicitly noted that only Google knew whether this was a refresh or algorithm change. | The filter pattern was useful evidence, but its exact mechanism remained unconfirmed. |
| 21 September 2016 | A broader industry synthesis popularised the name Possum and grouped observations involving city limits, searcher location, query variations and address or category similarity. | These were observed result patterns—not Google-published ranking factors or fixed thresholds. |
| November 2016 study | A BrightLocal data set covering 1,307 businesses found change in 64% of the local SERPs examined. | This quantified one sample; it was not a universal Google impact figure for all countries, queries or businesses. |
| 2017 onward | Local search continued to change, including later proximity and profile-interface changes. Google’s current documentation still describes relevance, distance and prominence rather than Possum. | Do not turn a 2016 observation into a permanent modern threshold. |
Why local filtering was mistaken for disappearance
The name “Possum” came from a practical misunderstanding: businesses appeared to have disappeared from a local result when they were still present elsewhere in Google. The observed change looked more like result selection among similar eligible options than a universal removal of the underlying profile.
That distinction still matters. A profile can be verified and eligible yet fail to appear for one non-brand query because another result is judged more relevant, closer or more prominent for that search context. This is different from suspension, a duplicate-profile status, an ineligible business, a website indexing problem or a manual action.
Google also receives business information from profiles, public web content, licensed data, users and its own interactions. Local visibility is therefore not controlled by one field or one page. Correct profile governance, a trustworthy website, reviews, citations and real-world operations need to describe the same business without manipulation.
Observed patterns, evidence limits and current checks
Use the historical patterns as investigation prompts, not as a substitute for current documentation. Each row separates what an observation can reasonably support from what it cannot prove.
| Observed pattern | What it can support | What it cannot prove | Current diagnostic |
|---|---|---|---|
| Businesses outside a city boundary gained city-query visibility. | Administrative borders were not an absolute eligibility wall for every query. | Every nearby business can rank across the entire city. | Test real service relevance, representative search points, competition and landing-page usefulness. |
| Results changed with the searcher’s location. | Proximity and search context can materially change local results. | A public universal radius or exact distance weight. | Sample priority neighbourhoods and record the exact location used. |
| Small query-wording changes produced different packs. | Relevance matching and intent interpretation can vary by phrase. | Adding keywords to the business name is acceptable. | Track meaningful query groups and keep the real-world business name. |
| Similar businesses at one or nearby addresses were filtered differently. | Google may diversify or select among similar local options for a context. | A suite number, ownership change or fixed distance guarantees visibility. | Confirm each entity is genuinely distinct, independently eligible and accurately represented. |
| Local and organic results moved differently. | Local and web systems can weigh context and evidence differently. | Website quality no longer matters to local visibility. | Diagnose Profile visibility and website search performance as connected but separate layers. |
| One 1,307-business study found 64% of sampled SERPs changed. | The observed 2016 movement was substantial within that data set. | A universal impact rate, ranking uplift or probability of recovery. | Use the figure only with its sample, date and methodology context. |
The durable operational lesson
Possum made local rank reporting more honest. A business does not have one stable rank for an entire city: it has a distribution of visibility across locations, queries, times and result surfaces. Reports should show representative coverage and business outcomes, not one flattering screenshot.
It also reinforced entity discipline. One real business should normally have one accurate profile. Distinct departments, practitioners or co-located businesses need to meet current eligibility rules; different services alone do not justify duplicate profiles.
Finally, local SEO became less about changing fields until a map pin moves and more about building a consistent evidence system: eligible operations, correct categories, useful local pages, accurate contact data, genuine reviews, strong reputation and a service experience people choose.
Replace local-ranking shortcuts with valid diagnostics
| Earlier assumption | Durable lesson |
|---|---|
| One search shows the true local rank. | Sample representative locations and queries; treat visibility as a distribution. |
| A filtered result means a penalty. | First separate contextual result selection from suspension, duplication, ineligibility and indexing issues. |
| Service areas create extra ranking points. | Service areas describe where a business serves; they do not create branches or remove distance. |
| Create another profile for each service. | Use one profile per business unless a genuinely distinct entity meets current eligibility rules. |
| Add city and service keywords to the name. | Use the consistent real-world name and choose accurate categories. |
| Move the pin or use a virtual address for coverage. | Represent the real eligible location or hide the address for a qualifying service-area business. |
| A business outside city limits cannot appear. | Administrative boundaries are not absolute; relevance, distance, prominence and context still matter. |
| The 2016 filter threshold still defines today’s results. | Local systems keep changing; use current documentation and fresh representative tests. |
How to reason through common local scenarios
Two dentists in one medical building
Confirm that each practitioner or practice is independently eligible, uses its real name and has distinct operational evidence. Then test branded discovery and representative non-brand queries. Do not manufacture suite numbers or duplicate profiles simply to defeat filtering.
A plumber serving customers at their locations
Use one eligible service-area profile, hide a residential address when customers are not served there and define a realistic service area. The service-area field does not make the business locally present in every selected city.
A real multi-location business
Each location needs real staffing, customer access where claimed, distinct contact and location information, and ongoing management. Reusing one landing page or creating empty shells weakens users’ ability to understand the actual branch.
A specialist just outside the city boundary
Do not fake an inner-city address. Build relevance for the real service, document the areas genuinely served, earn local reputation and measure visibility from the neighbourhoods that can realistically become customers.
A profile missing even for its exact business name
This is not a normal “filtered for one generic query” pattern. Check profile status, verification, eligibility, duplicates, ownership, edits, policy notifications and public visibility before doing ranking work.
A practical local-visibility diagnosis
- Define the test. Record the exact query, location, date, time, device, language, signed-in state and whether the result came from Search, Maps, Local Pack or Local Finder.
- Check identity discovery. Search the exact real-world business name and confirm the public profile, website and primary details are present and consistent.
- Separate status from ranking. Review verification, suspension, eligibility, ownership and duplicate warnings before diagnosing competitive visibility.
- Sample representative places and phrases. Use priority neighbourhoods and meaningful brand, category, service and problem queries instead of scanning every possible grid point.
- Audit representation. Confirm one profile per business, the real-world name, the most specific correct primary category, legitimate additional categories and accurate address or service-area settings.
- Inspect local similarity. Note legitimate competitors with similar categories, addresses and offers, but do not assume a fixed radius or attempt to disable another eligible business.
- Audit the connected website. Check indexability, local landing-page purpose, contact consistency, service evidence, internal links, structured data and mobile conversion paths.
- Improve real evidence. Complete the profile, maintain hours, services and media, earn genuine reviews, build relevant citations and make the customer experience worth recommending.
- Log changes and retest consistently. Avoid simultaneous name, category, address and website changes that make cause and effect impossible to separate.
- Connect visibility to business outcomes. Measure calls, directions, website clicks and qualified enquiries, understanding that profile interactions are actions—not confirmed sales or visits.
Measure visibility without inventing one citywide rank
Use a small repeatable measurement set that reflects where customers actually search. Keep visibility, profile interactions, website behaviour and qualified outcomes as separate layers.
| Measure | Collection method | Decision it supports | Important limitation |
|---|---|---|---|
| Representative map coverage | Repeat the same query set from priority neighbourhoods at controlled intervals. | Shows where visibility is consistently weak, strong or volatile. | Rank grids are samples and may not reproduce every user’s personalised result. |
| Brand and non-brand query groups | Group exact-name, category, service, problem and location-modified searches. | Separates identity discovery from competitive discovery. | Different wording can carry different intent; do not average unlike queries. |
| Profile interactions | Review Business Profile calls, directions, website clicks, messages and other available interactions. | Shows which actions follow profile visibility. | Calls are button clicks and directions are requests; neither confirms a completed customer outcome. |
| Website local-search visits | Use tagged profile links and analyse landing pages, devices, locations and conversion events. | Connects profile discovery to website task completion. | Consent, attribution and cross-device behaviour create gaps. |
| Qualified local outcomes | Reconcile calls, forms, WhatsApp, bookings or CRM leads with service and location fit. | Shows whether visibility creates useful business demand. | Outcome quality needs human or CRM validation; analytics events alone are insufficient. |
| Change log | Record profile edits, website releases, review changes, incidents and major Google local events. | Supports before-and-after comparison without assuming causation. | Correlation around one date is not proof of a specific filter or update. |
Ten Possum myths and evidence limits
- Possum is not an official Google system name. Treat it as a historical industry label.
- The exact rollout and mechanism were not published. Contemporary dates and patterns came from practitioner observations.
- Filtering is not proof of a penalty or manual action. It can reflect which result Google selects for one context.
- A missing generic-query result does not prove the profile was removed. Test exact-name discovery and profile status separately.
- No public distance or similarity threshold exists. Do not present a fixed number of metres, suites or categories as a Google rule.
- Service areas do not create local branches. They communicate where a qualifying business serves customers.
- A suite number does not make a duplicate entity legitimate. Eligibility depends on the real business, not formatting.
- The 64% figure was one study sample. It is not a universal share of businesses affected or improved.
- Later local changes prevent permanent 2016 rules. Current tests and current Google guidance take priority.
- No diagnosis guarantees ranking. Accurate eligibility and useful evidence remove avoidable problems; Google still selects the results it judges best for each search.
Possum and local filtering questions, answered
Did Google officially confirm Possum?
No official ranking-system documentation or launch post named Possum. The name and detailed 2016 patterns came from industry reporting.
Was Possum a penalty?
Not as a documented penalty. A business filtered from one local result could remain eligible and visible in other searches. Check policy and profile status separately.
Why does my listing appear for its name but not “service near me”?
Identity discovery and competitive discovery are different tasks. Relevance, distance, prominence, competitors and the searcher’s context can change the generic result.
Can two businesses share one address?
Sometimes, if each is genuinely distinct, independently eligible and accurately represented under current guidelines. A shared address does not guarantee both will show for the same query.
Will adding a suite number fix filtering?
Not by itself. Use a real recognised suite only when it accurately describes the business. Do not invent address details to manipulate visibility.
Should I create another profile for another service?
Usually no. Google says different services do not justify separate profiles. Use categories and services on the profile for the one real business.
Do service areas expand rankings?
They describe where a qualifying service-area business operates; they do not create physical locations or remove the distance component.
How should local rankings be tracked?
Use a stable set of meaningful queries from representative customer locations, record the test context and connect visibility with profile interactions, website behaviour and qualified leads.
How do I recover from local filtering?
There is no Possum recovery switch. Confirm eligibility and status, correct representation, improve relevance and real-world prominence, strengthen the connected website, then retest consistently.
Is Possum still relevant today?
It remains useful history for understanding contextual local results and careful rank tracking. Its inferred 2016 mechanics should not be treated as a current fixed formula.
Primary and official references
- Google Business Profile: improve your local ranking
- Google Business Profile: representation guidelines
- Google Business Profile: manage categories
- Google Business Profile: service-area businesses
- Google Business Profile: resolve duplicate profiles
- Google Business Profile: performance and insights
- Google Business Profile: how Google sources business information
- Google Business Profile: eligibility and ownership
- How Google Search works
Historical reporting and supporting analysis
The following sources are historical industry reporting or supporting analysis, not official Google ranking-factor documentation.
- Joy Hawkins: local-result filtering observations, 6 September 2016
- Joy Hawkins: Possum analysis, 21 September 2016
- Joy Hawkins and BrightLocal: 1,307-business study
- Sterling Sky: later Vicinity local-search analysis
Build the supporting local SEO system
Continue the Google Algorithm History series
Review affected pages, queries, dates, releases, crawling, demand and conversions before choosing a fix.
How Google Ranking Evolved: From PageRank to Modern Search SystemsSeptember 2, 2026
Google AI Content and SEO: What Is Allowed, What Is Spam, and How to Publish SafelySeptember 2, 2026
Google Florida Update (2003): What We Know, What Remains TheorySeptember 2, 2026