Facebook Visibility Restrictions: How to Check Shadow Banning and Reach Drops

A Facebook shadow ban means an unnoticed reduction in content visibility that users detect through reach, recommendations, and search. The term is not the name of a single official Meta status. People often use it for several different situations: recommendation restrictions, reduced priority for a specific post, a page-level penalty, or an ordinary fluctuation in analytics. Start the diagnosis by checking the facts rather than deleting posts, and understand what a shadow ban is.
A sharp drop in Facebook reach does not prove that a restriction exists. The feed ranks content by its likely value to the audience, while separate rules apply to recommendations. Check three things: whether there is an official notice, whether people who do not follow the page can still see the content, and which metrics changed. A control profile is useful for an independent check, but anonymous Facebook viewing only shows public visibility and does not explain why reach declined.
Login problems are also easy to confuse with visibility restrictions. If Facebook requests another verification, fails to load the page, or ends the session, first rule out common Facebook login errors. An authentication failure is not evidence that the platform reduced post distribution. Base the check on data collected over several days, not guesses.
What do users mean by a Facebook shadow ban?
A Facebook shadow ban usually describes a situation where posts remain accessible but appear much less often in the feed, Reels, search results, or recommendations. The page owner can still publish and reply to comments, so the restriction may go unnoticed.
Visibility or distribution restriction is a more precise description. Meta separates at least three levels: allowed content, content that is ineligible for recommendations, and material that violates rules and may be removed. The Facebook recommendation guidelines explicitly allow content to remain on the platform without receiving broad reach among people who do not follow its creator.
For diagnosis, identify exactly what the restriction affects. It may apply to:
- one post
- a specific feature
- page recommendations
- monetization
- the entire profile Mixing these levels can lead to deleting good content when the actual problem concerns the recommendation status of one Reel.
There is another reason to avoid rushing to label the problem. Reach is the result of ranking, not a fixed quota. Two posts shown to the same number of followers can receive different impression counts because of:
- topic
- audience retention
- negative feedback
- competition in the feed on that day A drop of 20 or even 50 percent does not identify the cause on its own. The pattern matters: where impressions disappeared, which formats were affected, and which part of the audience stopped seeing the content.
A useful working model has three layers:
- accessibility: whether the content opens through its direct URL
- distribution: whether it receives impressions in feeds and recommendations
- engagement: what people do after seeing it
If the content opens and receives impressions but people quickly scroll past it, look at the content itself. If it remains accessible while non-follower impressions nearly disappear across several posts, check recommendation status.
How can you separate a recommendation restriction from analytics changes or login errors?
A recommendation restriction differs from an ordinary decline through a combination of signals. One weak post proves nothing. Look for changes in reach sources, visibility problems among non-followers, and ideally a notice in page status or the professional dashboard.
The most reliable approach resembles a small controlled study. Compare the latest seven posts of the same type with the median from the previous 28 days. Do not compare a short Reel with a long text post, or a weekday post with coverage of a major event. Format, publishing time, and audience should be reasonably similar.

One viral post can inflate the average several times over and make a normal result look like a failure. To find the median, sort reach values from low to high and take the middle value. If you have a large dataset, export it to a spreadsheet and separately calculate total reach, non-follower impressions, and interactions per 1,000 impressions.
For example, a page publishes four Reels per week. During the previous 28 days, median non-follower reach was 8,200, but it fell to 2,100 across the latest seven comparable videos. Follower reach remained close to its usual level. That gap justifies checking recommendation eligibility. If both segments declined equally, first check the topic, publishing frequency, and analytics accuracy. These figures illustrate the method; they are not a universal Meta threshold.
| Signal | Likely explanation | How to check | What not to do |
|---|---|---|---|
| reach fell for only one post | weak topic, early audience response, or poor publishing time | compare it with other posts in the same format | delete all page content |
| non-follower impressions fell | recommendation restriction or changing audience interest | check reach sources and recommendation status | rely only on the total reach figure |
| analytics are missing or delayed | analytics failure | compare the figures later and on another device | republish posts in bulk |
| login fails or the session repeatedly ends | security review or technical failure | check notices, email, and active sessions | treat it as a shadow ban |
| followers see the page but a new profile cannot find it | possible loss of recommendation or search visibility | run a control check from a non-follower profile | ask the whole team to search for the page |
The table does not produce an automatic diagnosis. It helps eliminate unlikely explanations. If follower reach remains stable while several content formats stop receiving recommendation views, check page status first. Do not rush to change the content plan.
How should you read metrics without inventing a threshold?
There is no universal percentage drop that proves a shadow ban. Tens of views can matter for a small page, while one popular Reel can distort a large page's weekly figures. Compare each metric primarily with the page's own previous performance.
Calculate non-follower reach as a share of total reach for every post. Then compare the median share from the latest seven posts with the previous period. Separately check video retention, shares, and post hides if those metrics are available. A sharp decline in recommendation traffic while retention remains stable is a stronger signal than fewer likes alone.
Keep absolute figures alongside percentages. The non-follower share can fall because impressions among loyal followers increased even when the absolute number of recommendations did not change. Conversely, a good percentage based on very low reach does not mean distribution recovered.

After the visual check, record the date, post format, follower reach, non-follower reach, and whether any notices appeared. Five to seven rows are often enough to show whether the problem is systematic. A screenshot of one chart without context cannot do that.
Add any control event that may have changed the data: a new format, a sudden increase in publishing frequency, an administrator change, a controversial topic, or the connection of an automation service. Do not try to prove causation immediately. First mark the timing. Then change only one factor, or you will not know what affected the results.
Which official statuses and notices should you check?
Official statuses are more reliable than third-party "shadowban checker" services. Check the professional dashboard, page and recommendation status, support messages, and notices tied to individual items. Menu names can vary by profile type and available features.
If professional mode is active, first determine whether the issue concerns recommendations, monetization, or community rules. These are different restriction types. A separate guide to Facebook professional mode can help you find the right tools without confusing a personal profile with a creator page.
Run the check in a consistent order. This reduces the chance of missing a notice that already contains the reason and a review button.
- open the profile or page with an administrator role
- go to the professional dashboard or status section
- check violations attached to specific posts
- review page and content recommendation eligibility
- open the support inbox
- save a screenshot, date, exact reason, and available actions
Read the wording closely. "Content is not recommended" does not mean "account disabled." "Feature temporarily restricted" also does not prove that organic reach fell across every post. This is where many false diagnoses begin.

If the status is green but reach keeps falling, check content analytics, post visibility, and the technical log. The absence of a restriction notice does not guarantee stable impressions.
For pages with several administrators, check whether every role sees the same status. Some tools may be unavailable to an editor or analyst. Do not share a password for this check. Use built-in roles and record which administrator profile captured the screenshot.
Check the decision date separately. An old violation may remain in history even though the current decline started much later. A thematic connection without a matching date is weak evidence. If a notice appeared on the same day that non-follower impressions stopped, add it to the review request as primary evidence.
How can you test post visibility without drawing false conclusions?
A visibility test works only when the control profile does not follow the page and has no recent interaction history with it. Otherwise, feed personalization distorts the result. Incognito mode removes local browser history but does not reproduce the experience of a signed-in Facebook user.
Run a short test on two or three recent posts. Do not involve dozens of colleagues; synchronized searches, reactions, and comments can distort the check.
- copy the direct URLs of two recent posts
- open each URL from a control profile that does not follow the page
- find the page through Facebook's internal search
- check whether the posts appear on the page profile
- compare comment order and availability
- repeat the test after 24 hours without additional reactions
If a direct link works but the post does not appear in recommendations, the content is not hidden from everyone. Distribution is the more likely issue. If the URL returns an unavailable message, check the post audience, age or geographic restrictions, and whether it was removed.
For external search, use an exact phrase from the post in English quotation marks, but treat the result carefully. Facebook does not have to expose every post to search engines. Absence from Google is a supporting signal, not proof of a shadow ban.

Another useful test concerns comments. Open the discussion from the control profile and change sorting if the interface allows it. A comment hidden under "Most relevant" may appear when all comments are shown. That indicates discussion ranking, not necessarily a restriction on the author's entire profile.
Do not rely on colleagues' reactions. They may already be connected to the page through shared groups or previous interactions. Repeat the check a day later from one control profile that has never interacted with the page.
Which factors most often reduce Facebook reach?
Check four possible causes of declining reach: recommendation rules, content quality and originality, behavioral signals, and technical session problems. Each requires a separate test, so advice to "take a break for a few days" is not always useful.
How do recommendation rules affect allowed content?
Facebook may decline to recommend content that remains accessible. Low-quality, sensitive, misleading, or reused material can become ineligible for recommendations even when it does not lead to a full page restriction. Check the status of the specific post and do not apply that conclusion to the whole account without evidence.
How do repetition and weak originality change distribution?
A series of nearly identical Reels, reuploads of other people's videos, or minimal edits to previously distributed material can reduce recommendation eligibility. The practical response is simple: keep source files, scripts, and publishing dates to prove where the material came from. When reusing content, add original analysis or editing that genuinely changes its value.
Do not edit the entire archive at once. Choose two new pieces created from scratch and compare them with two reused posts in the same format. If the difference appears consistently, the team has a working hypothesis. That is more useful than randomly deleting dozens of old posts.
What does behavioral spam look like to the platform?
Identical comments, bulk invitations, sudden bursts of actions, and synchronized activity across several profiles can look coordinated. Analyze the pace and sequence of actions. Do not try to "restore reach" with even more reactions. Stop the automation, inspect the action log, and return to a normal work pace.
How does an unstable session create a separate problem?
Frequent logins from different countries, switching devices during an active session, or repeated code requests can trigger a security check. This is different from a reduction in content ranking. If a team manages the page, record access roles, devices, and time zones. For new work profiles, do not replace this discipline with artificial Facebook account warming; activity should reflect real work, not an imitation script.
Keep the content log separate from the access log. In the first, record URLs, formats, dates, and metrics. In the second, record the administrator, device, login country, and security notices. When both datasets are mixed into one log, a technical review can turn into unsupported assumptions about the recommendation algorithm.

Once the causes are separated, each tool's role becomes clearer. The content editor can fix originality and presentation. The administrator checks roles and notices. A technical specialist handles sessions. None of them should credit their part of the process for the entire outcome.
How should you document the problem and request a review?
A review request should be short, specific, and tied to the platform's decision. Prepare the following for support:
- content identifier
- date
- status screenshot
- explanation of why the content complies with the rules
An emotional message about a "shadow ban" is harder to investigate because it does not name a specific system action.
A good request takes about half a minute to read. For example:
"On October 12, the page received a notice that video ID 123 was ineligible for recommendations because of unoriginal content. Our team created the video from a source file recorded on October 10. Please review the decision; we have attached the status screenshot and proof of authorship."
This request avoids assumptions about the platform's motives. It states the decision, date, and evidence.
If the interface gives a different reason, do not use a universal template:
- an authorship explanation will not help with a dispute about sensitive material
- an audience description does not resolve a licensing violation
Respond to the exact point named in the notice.
Create an incident log before editing or deleting material. A basic spreadsheet can contain:
- date and time when the decline was first noticed
- post URL and identifier
- content type and audience settings
- follower and non-follower reach
- exact notice text
- page status screenshot
- submission date and case number
This log preserves the sequence of events. Without it, a week later it is hard to remember whether the status changed after an appeal, a description edit, or a new administrator login.

The submission path depends on which button the interface shows. The general sequence stays the same.
- open the notice for the specific decision
- read the named policy section
- save a screenshot before making any edits
- request a review if the option is available
- explain the context in two or three sentences
- attach proof of authorship or licensing when originality is disputed
- record the case number and submission date
Do not submit several identical requests in a row. That does not speed up the review and makes the incident log harder to follow. If no button is available, preserve the evidence and check Support Inbox. A fully disabled profile requires the separate Meta account recovery process, not a reach diagnosis.
How can you separate work sessions without blaming the browser for reach changes?
A browser profile can isolate cookies, local storage, fingerprint data, and a proxy, but it does not control Facebook's recommendation algorithm. It cannot restore reach, reverse a violation, or make weak content popular. Its narrower role is to reduce confusion between work sessions and give the team a stable environment for signing in.
This is especially useful for an agency where one specialist checks analytics, another publishes content, and a third responds to messages. If everyone uses the same ordinary browser, it becomes harder to identify who changed a setting, which session ended, or where an unusual login came from.
| Tool | What it actually controls | What it does not control |
|---|---|---|
| Facebook professional dashboard | statuses, analytics, and available decision reviews | external isolation of browser sessions |
| content log | dates, formats, authorship, changes, and metrics | recommendation system decisions |
| separate browser profile | cookies, storage, fingerprint, proxy, and login history | reach, content quality, and appeal result |
| Facebook control profile | public visibility for another user | the exact internal reason for a restriction |
In Afina, each work account can stay in a separate browser profile with its own cookies, local storage, fingerprint, and proxy. This simplifies session management and separates work environments for different clients. A stable technical session is only one part of the process: the team must still follow Meta's rules, check statuses, and keep a change log. This material is provided for informational and educational purposes only.
Work in sequence: identify where visibility fell, check the official status, and only then change the content or access settings. If everything changes at once, finding the cause becomes difficult.
DownloadFAQ — Frequently Asked Questions
What is a Facebook shadow ban?
It is an unofficial term for an unnoticed reduction in content visibility. The cause may be a recommendation restriction, the ranking of one post, or another platform action.
How can I check whether Facebook restricted my reach?
Check page status, recommendation eligibility, and reach sources. Then compare two or three posts from a control profile that does not follow the page.
Why did Facebook reach suddenly drop without violations?
Audience interest may have changed, analytics may be delayed, or the post may have received weaker early signals. A green status does not require the algorithm to preserve earlier impression levels.
How long does a Facebook shadow ban last?
There is no universal duration because Meta does not describe one official status by that name. The timing depends on the specific restriction and review outcome.
Does deleting posts restore Facebook reach?
Mass deletion is not a reliable way to restore reach. Delete or edit content only when the status identifies a specific problem.
Where can I request a review of a Facebook decision?
The option appears next to the specific decision in page status or Support Inbox when review is available. Save a screenshot and the exact reason before submitting.
Can a login error mean a shadow ban?
No. Login errors usually concern authentication, security, or a technical failure, so check them separately from content distribution analytics.
Does an antidetect browser restore Facebook reach?
No. A browser does not control recommendations or reverse platform actions; it can only separate work sessions and their technical data.
