4 people reported

All time, since Aug 7.

Meta crawler gets 403 errors

“Hi, Meta's Sharing Debugger consistently returns 403 for https://www.michaelfx-community.co.uk with the "could be due to a robots.txt block" message.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/vercel/issues/9046/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 2 a week at the late-September peak.

Meta crawler gets 403 on some projects despite allow rules. Sharing Debugger reports 403 while browsers and curl get 200; Bot Protection off and firewall bypass rules have no effect.

Is this your bug?

File my report
Where
Firewall
How bad
Breaks a normal workflow.

Original reports4, newest first

  1. 403 problem with meta ads (instagram)#49990
  2. Facebook crawler gets 403 on new projects while control project returns 206#49963
  3. facebookexternalhit gets a persistent 403 on our custom domain — every other crawler gets 200#49028
  4. Meta Sharing Debugger receives 403 while Facebook crawler gets 200#47350

Do you work on Vercel?

Claim its RAP Sheet to see what your users report and answer them in one place.