You hit Post and Facebook throws it back at you: “Your content couldn’t be shared, because this link goes against our Community Standards.” Maybe it’s your shop, your booking page or your own blog, and you know there’s nothing wrong with it. The same thing can show up in Messenger as a message that won’t send, or as a post that quietly disappears from a group.
Take a breath. In most cases the block is automated, the cause can be found, and you can ask Meta for a human look. The order matters, though: if you request a review before fixing what tripped the filter, you’re very likely to get the same answer back. This guide walks you through a ten-minute diagnosis, each real cause and how to fix it, and then the review request.
The 10-minute diagnosis
1. Run your link through Meta’s Sharing Debugger (developers.facebook.com/tools/debug). Paste the exact URL you tried to share and click Debug. Then do the same with just your homepage. If the homepage fails with a message like “We can’t review this website because the content doesn’t meet our Community Standards”, the block is on your whole domain. If the homepage is fine and only one URL fails, the problem is that page or that link format.
2. Check your site on Google’s Safe Browsing site status page (transparencyreport.google.com/safe-browsing/search). If Google flags your site as dangerous or partly dangerous, your site has very likely been hacked, and that is almost certainly why Facebook is blocking it too.
3. Look at the link itself. Is it a shortened link (bit.ly-style), a free hosting subdomain, an affiliate tracking link, or a link that redirects somewhere else? Those are the usual suspects.
4. Think about how you posted it. Did you share the same link to lots of groups, pages or chats in a short burst, or schedule it from a tool that posts everywhere at once? That pattern alone can trigger a spam block.
Whatever you find, write it down. You’ll use it when you request the review.
Cause 1: your site has been hacked or is serving malware
How to recognise it: Safe Browsing shows a warning, visitors report pop-ups or being sent to strange sites, or your site looks normal to you but different on a phone or when someone arrives from a social link. Hacked WordPress sites often hide their redirects from logged-in admins, so you may never see the problem yourself.
The fix: clean the site properly. Update your CMS, themes and plugins, remove anything you don’t recognise, change every password (hosting, database, admin, FTP), and ask your host to scan for malware. If you use Google Search Console, the Security Issues report lists hacked content, malware and social engineering problems Google has found, and lets you request a review once everything is fixed. Google itself says these reviews can take several days or weeks, so start now.
Only ask Facebook to review your domain after the site is genuinely clean. Asking while malware is still on it is a wasted request.
Cause 2: you’re sharing a shortener or a shared domain
How to recognise it: the link starts with a URL shortener, or your site lives on a free subdomain of a big hosting or website-builder platform. Your own page may be perfectly fine, but you share the domain with thousands of other people, and some of them are spammers.
Meta doesn’t publish how it scores domains, but blocks clearly can apply to a whole domain. Shortener companies, link-in-bio services and web hosts all have help pages about Facebook blocking links on their shared domains, which tells you how often it happens. When a spammer abuses the same shortener or subdomain host, your link can get caught in the same net.
The fix: share the full, direct URL to your page instead of a shortened one. If you’re on a free subdomain, the long-term fix is your own domain, or at least a page on a well-established domain that doesn’t hand out anonymous throwaway links. If you need click tracking, use UTM parameters on your real URL rather than a shortener.
Cause 3: redirects, cloaking or a preview that doesn’t match
Meta’s spam policy specifically bans cloaking, which it describes as presenting different content to its integrity systems than to users. It also bans links that automatically redirect to a substantially different domain, landing pages that require an action like a captcha before the real page appears, and links that promise one type of content but deliver something substantially different.
How to recognise it: in the Sharing Debugger, look at the fetched URL, the redirect path and the Open Graph tags (og:title, og:description, og:image, og:url). If the debugger shows a different final URL from the one you pasted, a chain of redirects, or a title and image that don’t match the actual page, Facebook’s crawler is seeing something different from your visitors. That can happen by accident with security plugins, geo-redirects, “coming soon” modes, or a firewall that treats Meta’s crawler (facebookexternalhit) as a bot.
The fix: link straight to the final page, remove unnecessary redirects, make sure your firewall or bot protection lets Meta’s crawler fetch the page, and set Open Graph tags that honestly describe the page. Meta’s crawler documentation says your meta tags should appear within the first 1 MB of the page. After changes, click “Scrape Again” in the Sharing Debugger so Facebook fetches the fresh version.
One important limit: the Sharing Debugger fixes previews and refreshes Facebook’s copy of your page. It does not remove a Community Standards block on its own. Re-scraping a blocked domain will just show you the block again.
Cause 4: posting the same link too often, too fast
How to recognise it: your link worked fine yesterday, you then shared it to a lot of groups, pages or Messenger chats, and suddenly it’s refused. Or you got a warning about your account or a temporary limit on posting.
Meta’s spam policy covers posting, sharing or engaging with content “at very high frequencies”, whether manually or automatically. Copy-pasting one link into twenty groups in an hour looks like spam to an automated system, even if every word is true.
The fix: stop posting the link for now. When you resume, post it in fewer places, write a post that’s actually different each time, and spread it out. Put the link on your Page or profile and let people find it, rather than pushing it into every group you belong to. Avoid tools that blast the same link to many destinations at once.
Cause 5: your content falls under a restricted category
How to recognise it: your site sells or promotes things Meta restricts, such as regulated goods (for example weapons, drugs, alcohol or tobacco), adult content, gambling, or aggressive “get rich” affiliate offers. A site can also be blocked if it impersonates a well-known brand, for example a lookalike domain with a typo.
The fix: read the relevant section of Meta’s Community Standards at transparency.meta.com and be honest with yourself about whether your page fits. Some of these categories can’t be shared freely however you word the post. If your business is legitimate but sits close to a line, make your page clear and factual: real business details, contact information, clear pricing, no pop-ups, and no claims that sound too good to be true.
New domains with little history, almost no content and lots of outbound affiliate links tend to look worse to automated systems than an established site with a real About page, contact details and original content. Meta doesn’t publish its exact signals, but building up real, useful content never hurts.
Step by step: fix it, then request a review
1. Fix what you found: clean malware, remove shorteners and redirects, let Meta’s crawler in, correct your Open Graph tags, and pause any repeated posting.
2. Re-check Google Safe Browsing and, if needed, get Google’s own warning cleared through Search Console first.
3. Run the URL through the Sharing Debugger again and click Scrape Again.
4. Request the review. When a post is blocked, the error message usually includes a link along the lines of “If you think this doesn’t go against our Community Standards, let us know.” The Sharing Debugger shows a similar link on blocked domains. Use it. Keep your note short and specific: what your website is, who runs it, what you found and fixed (for example “removed a malicious redirect plugin, site is clean on Google Safe Browsing”), and that you’re sharing your own direct URL.
5. If one of your posts was taken down, you can also ask for that decision to be reviewed. Meta’s help centre explains that you open your profile, go to your profile or account status, open the message about the removed content and click Request review if the option is shown.
6. Be patient and don’t flood the form. Meta doesn’t publish how long domain reviews take, and there’s no guaranteed reply. One clear request after a real fix is better than ten angry ones. Keep checking your homepage in the Sharing Debugger; when the block is lifted, it will scrape normally again.
What not to do
Don’t swap in a different shortener, a redirect domain or a “link changer” to sneak past the block. That is exactly the cloaking and deceptive-URL behaviour Meta’s spam policy describes, and it can turn a link problem into an account problem.
Don’t keep reposting the blocked link to test whether it works yet. Each attempt adds to the pattern that caused the block. Use the Sharing Debugger to test instead.
Don’t ask friends to report or mass-share the link. It won’t speed up a review.
Preventing it next time
Most link blocks come from three habits: sharing through shortened or shared-reputation links, posting the same link in bulk, and not noticing when a site has been compromised. Fix those and you remove most of the risk.
A simple setup that helps: keep one stable page as your main link, on a reputable domain, and point everything else from there. For example, a link-in-bio page like onesol.io/yourname can hold your shop, booking form and socials in one place, so you share one clean, direct URL instead of a different shortener for every post. It won’t make a policy-breaking page acceptable, and no platform can promise Facebook will never block something, but it does keep you away from the throwaway links spammers rely on.
Finally, run your main links through the Sharing Debugger now and then, keep your site software updated, and you’ll usually catch a problem before your customers do.