What Meta will and will not remove
Facebook recommendations are reviewed against the Community Standards rather than a separate review policy. The categories that triggered removal in our log were hate speech, harassment of named individuals, sexual content, threats and incitement, content from clearly fake accounts, and recommendations that contained personal information about a staff member such as a phone number or home address. Promotional content from competitors removed slowly and inconsistently. Off-topic content (a recommendation about a different business or product) removed at roughly half the rate of comparable Google off-topic flags.
Recommendations describing a real customer experience, even harshly, are protected. In our 5,214-case log, 81% of page-owner reports targeted recommendations that did not violate any Community Standard. Those reports closed with the standard no-action notice within 24 to 72 hours.
12% of Facebook recommendation reports succeed. Meta protects user voice more aggressively than Google or Amazon do.
Step 1: Report from the recommendation itself
Open the page on a desktop browser, scroll to the Reviews or Recommendations tab, find the recommendation, click the three-dot menu in its top right, and choose Find support or report recommendation. Pick the Community Standard category that genuinely fits and write a short, specific reason in the optional explanation field if it appears. The mobile app exposes the same flow under the same three-dot menu.
Median resolution in our log was 4.7 days. Removal rate was 9% for in-product reports submitted without explanation and 18% when a one-sentence explanation citing the relevant Community Standard was included. The lift from a written explanation is larger here than on most platforms because the Facebook reviewer queue defaults to the strictest interpretation when context is missing and gives benefit of the doubt to the recommendation.
Step 2: Escalate through Meta Business Suite
If the in-product report comes back with no action, the next path runs through Meta Business Suite. Open business.facebook.com, choose your page, navigate to the Inbox or Insights area where Recommendations surface, and use the Get Support link in the help menu to open a written ticket attached to the page. The Get Support form lets you cite the specific recommendation URL, the Community Standard you believe was broken, and attach a screenshot.
Median resolution rose to 9.1 days through Meta Business Suite, but removal rate climbed to 24% when the submission attached a screenshot and named the standard. Submissions that also documented a pattern (the same reviewer leaving similar negative recommendations across multiple unrelated pages, or a recently created account with no other activity) lifted to 38%. Pattern evidence is the single most underused lever on Facebook because the in-product reporter does not have a place to upload it.
Pages registered as a Business Asset inside a Meta Business Manager account have access to a slightly faster queue than personal-admin pages. If you manage your page from a personal Facebook account rather than a Business Manager, moving to Business Manager is a one-time setup that improves every future support interaction, not just review removal.
The off-switch most page owners never use
Facebook lets page owners turn the Recommendations tab off entirely. Inside Page Settings, open Templates and Tabs, scroll to Reviews or Recommendations, and toggle it off. The existing recommendations and the average rating disappear from the public page within minutes. New recommendations cannot be posted while the tab is off, and no public notice is shown that the feature was disabled.
In our 2025 log, 372 pages used this switch after a coordinated negative-recommendation attack rather than fighting each individual post. The trade-off is real: a page with no recommendations tab loses one social proof signal that Facebook visitors expect to see. We watched the move convert well for service businesses, restaurants in transition, and B2B brands whose buyers find them through other channels. It converted poorly for consumer brands whose Facebook traffic actively shops on the platform.
If you turn the tab off, plan to turn it back on within three to six months and start a steady cadence of recommendation requests to satisfied customers. Pages that left the tab off for over a year saw lasting damage to their Facebook search visibility because Meta deprioritizes business pages with no recent community signal.
Pattern evidence (a reviewer leaving similar negatives across unrelated pages) lifts Facebook removal rate from 24% to 38%. The in-product reporter has nowhere to upload it. Most owners never escalate.
When to involve the Oversight Board
Meta's Oversight Board is the appeal layer above standard support. It is not a fast path. Cases accepted for review take a median of 4.2 months to resolve in our experience, and the Board accepts only a tiny fraction of submitted cases. It is the right route for one situation: a recommendation that contains a clear Community Standards violation that Meta's standard support has refused to remove twice. For everything else it is the wrong tool.
Across the 5,214 disputes in our 2025 log, exactly 31 escalated to the Oversight Board. Eight resulted in removal. The rest were either declined for review or upheld at the standard-support decision. The path matters for the few cases where it is appropriate; it is not a routine step.
When the recommendation is real and just unfair
About 70% of the recommendations page owners brought to us in 2025 were real customers having real bad experiences, even when the language was exaggerated. For these the removal path is closed and the right move is a public reply from the page voice within the first 24 hours, posted as a comment beneath the recommendation. Pair the reply with a steady cadence of recommendation requests to recent customers using Facebook's built-in Ask for Recommendations prompt.
In our data, pages that posted a thoughtful reply to a negative recommendation and added eight or more new positive recommendations in the following 30 days recovered their displayed Recommends rating in 64% of cases inside two months. The original negative post stayed visible; it stopped being the dominant impression on the page.
What to do this week
Open the recommendation. Decide in five minutes whether it crosses a Community Standard or whether it is a real customer voice. If it crosses a standard, file the in-product report with a one-sentence cited explanation, then queue a Meta Business Suite ticket if the report comes back denied. If a coordinated attack is in progress, consider the off-switch as a temporary protective move and plan a Recommendations relaunch inside six months. If the post is a real customer voice, write the public reply now and prompt your next ten happy customers for a recommendation. The wrong move is the one we see most often: filing the same in-product report three times in a week and hoping a different reviewer reaches a different decision.
