When Facebook Page Widgets Give You A Visibility Warning

Jumping back into development during a staff member’s well-deserved vacation has its perks. I get to be more hands-on with the client communication & bug tracking, and there’s always something new to learn. Today I came across a situation where a Facebook Page Widget, which is normally very simple to handle, was not showing up when testing on Firefox.

When previewing the widget on the Facebook Page Widget generator, I saw an interesting warning that said ”

Warning: This Page is not accessible by everyone.

( This message is only visible on developers.facebook.com )

Screen Shot 2015-07-03 at 5.37.46 PM

Ryan Henry’s Real Estate Page gave a warning for visibility.

Scratching my head over the issue, because I had clearly published the page already and all, I was a little bit perplexed. Some snooping around, the some trial & error, quickly revealed the issue. If there are any visibility restrictions, the page will not be visible for everybody, or anybody that is not logged into Facebook on the browser they are on.

In our case, the Age Restriction was set by my client to be 21 and over. After removing that restriction, the problem was resolved; whether logged in or not, regardless of age/demographic, the page was visible.

Things that can affect the visibility of your Facebook Page Widget are:

  • Page Visibility (obviously)
  • Country Restrictions
  • Age Restrictions

Screen Shot 2015-07-03 at 5.44.31 PM

  • Dana Ž?avová

    Thanks for your advice. You helped me a lot.

  • Thanks for sharing this advice. After hours of pulling my hair out an age restriction was the causing my FB page plug-in not to show in some browsers and devices. Thank you!

  • Hi josh glad we could help 🙂 I love sharing these tips, I’ve personally saved hours thanks to people sharing their little tips after some struggle. It’s the collective intelligence at work to make all of us more and more efficient!

  • Dandelion

    Thank you so much for sharing this feedback! I’ve been having this problem and was completely stumped!

  • Sir. Felipe II

    Thanks.