Docs    Facebook    FAQs

Is the content of my feed crawlable by search engines and how does it help improve my SEO?

The Custom Facebook Feed renders server-side rather than in an iframe, so feed content is in your page HTML.

Would you like to know whether search engines can read the posts in your Facebook feed?

This guide explains how Facebook Feed adds your posts to a page and how to check it yourself. It also covers which parts of a feed load after the page opens.

It only describes what is in your page. It makes no promise about search rankings. What a search engine does with a page is up to the search engine.

Before you get started, make sure Facebook Feed is installed and set up on your WordPress site, with a feed on a page. Some settings below are part of Facebook Feed Pro, and each section says which.

How the Feed Is Added to Your Page

To get started, we’ll look at how your posts get into the page.

Facebook Feed builds your posts on your own server. When someone opens the page, WordPress runs the plugin. The plugin then prints the posts as HTML inside the page. The feed sits in a container with the id cff. The text of each post is in an element with the class cff-post-text.

The posts are not inside an iframe. An iframe is a box that loads a separate web page inside your page. Because the text is part of the page’s own HTML, any tool that reads that HTML can read it, including search engines. This guide does not cover what a search engine does with that text.

Next, you can check this on your own page.

Checking Your Page Source

View Page Source shows the HTML your server sent, before any script on the page has changed it. That makes it the right check here.

  1. In your browser, open the page that has your feed.
  2. Right-click an empty part of the page. Then, click View Page Source. A new tab opens with the HTML.
  3. To search the source, press Ctrl+F on Windows, or Cmd+F on a Mac. Then, search for a few plain words, with no apostrophes or quotation marks, from one of the posts you see when the page first opens. You can also search for cff-post-text.

If the search finds the words, the text of your post is in the page HTML. For this check, use View Page Source and not Inspect. Inspect shows the page after its scripts have run. It can show text that was not in the HTML your server sent.

If the search finds nothing, see When the Feed Loads Later.

Images in Your Feed

The text of a post is printed into the page. Images work differently. Where an image comes from depends on the Optimize Images setting and on which image it is.

Optimize Images is a plugin setting. To find it, go to Facebook Feed » Settings. Then click the Advanced tab and look for the Optimize Images box.

The setting is on by default in Facebook Feed Pro. When it is on, the plugin saves copies of your post images, in different sizes, in the uploads folder of your own site. They go in a folder named sb-facebook-feed-images. The feed then shows the smallest copy that fits its size.

The copies are made after the page loads. The page first prints each image with the address it got from Facebook. Then the plugin’s JavaScript asks your site to save a copy. It swaps the copy in when one exists.

With the GDPR setting on No, the plugin only asks for a copy of an image when the data from Facebook has no medium size. Medium means between 150 and 500 pixels wide. With it on Yes, the plugin asks for a copy of every image. Automatic, the default, works like Yes when one of the supported consent plugins is active, and like No when none is.

In short, the images come from these places.

  • A post image with a saved copy that is wide enough comes from your own site, from the uploads folder. For a wider space, the plugin can use a larger image from Facebook.
  • A post image with no saved copy yet comes from the address Facebook gave the plugin. So does every post image when Optimize Images is off.
  • The header avatar, the header cover and the small author picture next to each post use the address Facebook gave the plugin, with Optimize Images on or off. When the GDPR setting blocks Facebook’s servers, they show a placeholder instead.

In the free version, a photo or video post shows a link to view it on Facebook, in place of the image.

Because the copy is swapped in by JavaScript, View Page Source shows the Facebook address, not the copy. To see the copy, right-click the image and use your browser’s Inspect tool.

Wherever the image file comes from, the image tag and its alt text are part of the page HTML.

There is one more setting that changes what the page prints. In Facebook Feed Pro, the Advanced tab also has JavaScript Image Loading, which is off by default.

Its help text says “Load images on the client side with JS, instead of server side.” While it stays off, the page prints each image with its Facebook address, as described above. When it is on, the HTML holds the plugin’s placeholder image. JavaScript then puts the real image in after the page loads.

For how the GDPR setting changes images, and what it limits, see our GDPR guide. For how Optimize Images affects speed, see our guide to a slow feed page.

When the Feed Loads Later

The posts are in the page HTML in most setups. These are the main cases where some or all of the feed arrives after the page opens. Each of them can also make the source differ from what you expect.

  • A theme or plugin that loads page content with AJAX. AJAX brings in new content without reloading the whole page. The feed’s own script may not run on such a page. The AJAX theme loading fix on the Advanced tab adds the script to the feed so it runs. For the steps, see our guide to the AJAX theme loading fix.
  • The GDPR setting. When it is on Yes, or on Automatic with a supported consent plugin active, the plugin limits what loads before a visitor agrees. Its own list covers images, videos, the Load More button and the Like Box. See our GDPR guide.
  • Load More. In Facebook Feed Pro, the posts after the first set are not in the page when it opens. The plugin gets them with AJAX when a visitor clicks the button.
  • The Like Box and the video players of Facebook Feed Pro. Both are iframes. Text inside an iframe is not part of your page’s HTML.
  • Saved copies of your posts. Posts shown in the feed come from a saved copy. A page-caching plugin can also store the page HTML on top of that. New posts therefore show after both are updated.

The Caching box sets how long the plugin keeps its saved copy. In Facebook Feed Pro, go to Facebook Feed » Settings. Next, click the Feeds tab. Then choose a Caching update interval.

The default is Every 12 hours. In the free version, the box takes a number and a unit. The default is one hour.

For the full steps, see our guide to the caching settings. For a page-caching plugin, see our guide to a feed that stopped updating.

That’s it! You now know that Facebook Feed prints the text of your posts into your page HTML, and how to confirm it in View Page Source. To fix a feed that shows old posts, see why a feed stopped updating or is missing posts.

Frequently Asked Questions

Below, we’ve answered some of the most common questions about search engines and your feed.

Will a Facebook feed improve my search ranking?

We can’t promise that. The plugin puts the text of your posts into your page HTML. What a search engine does with that text is up to the search engine.

Is the feed added to my page with an iframe?

No. The plugin prints the posts as HTML in your page. Only the Like Box and the video players are iframes.

Does my feed need JavaScript to show its posts?

The text of the posts is printed by your server, so it is in the page without JavaScript. JavaScript is used for other parts, such as the Load More button, saved image copies and the Like Box. See When the Feed Loads Later.

Why can’t I find my post text in the page source?

The feed may be in content that a theme or plugin loads with AJAX after the page opens. A page-caching plugin may also be serving an older copy of the page. The post may also be one that only shows after a visitor clicks Load More. The cases in When the Feed Loads Later cover all three. The check also works only in View Page Source, not in Inspect.

Are my feed’s images stored on my site?

Some are. With Optimize Images on in Facebook Feed Pro, post images can have a saved copy in your uploads folder. The header avatar, the header cover and the author pictures come from Facebook, or show a placeholder when the GDPR setting blocks Facebook’s servers. See Images in Your Feed.

Will a new post show in my page right away?

Not always. The page shows the plugin’s saved copy of your posts. It can take until the next update for the new post to appear. A page-caching plugin can delay it further. See When the Feed Loads Later.

support

Couldn’t find your answer in the docs?

Contact Support