The Related Posts feature scans all of your post content, analyzes it, and uses the results to display additional posts your visitors might be interested in reading after they’re finished with the current post.
Note: This page describes how to use Related Posts when using the Block Editor. You can find instructions for using Related Posts with the Classic Editor here.
Most sites that activate this see an increase in traffic. Unlike many other related post plugins, we do all the analysis, processing, and serving from our cloud, so there is no additional load on your server. That’s why Jetpack Related Posts are allowed on web hosts even when similar plugins are banned.
To start using Related Posts, go to Jetpack → Settings → Traffic page and activate the “Show related content after posts” toggle.
Adding Related Posts
To add Related Posts, add a new block either with the in-post block selector or using the block selector in the post toolbar. You can add this block anywhere in the post content.
It is only possible to add one Related Posts block to each post.
See the Jetpack Blocks page for more detailed information on adding Jetpack blocks.
After adding the block, you’ll see any relevant posts showing up, otherwise, you’ll see a message saying ‘Preview: Not enough related posts found’.
Click on the block to display the block toolbar. The Related Posts block offers the following options in its toolbar:
As with the image block, the Related Posts block can be set by clicking the wide width or full-width icons.
The Grid View option in the toolbar displays posts side-by-side while the List View displays them horizontally in a list format.
In the Block sidebar, you can choose to Display thumbnails, Display date, and Display context.
You can also use the slider to change the number of related posts to display. The maximum number that can be displayed is 6.
You can customize the background color and text color for the block. The background color has two options: solid and gradient:
You can configure your Typography size using pre-selected default size or custom size.
- Related content will not appear unless we think we can show at least 3 good results (to avoid simply cross-linking posts with one another).
- Related content is automatically generated based on the content of the post and any tags or categories if they exist.
- This feature uses the WordPress.com infrastructure and mirrors your content there for indexing. If you see intermittent issues only affecting certain posts, you can request a reindex of your site by clicking on initiate a sync manually under Data synchronization, at the bottom of your WordPress.com Settings → General → Manage connection page.
- Related Posts for a given article are cached for 12 hours.
- The maximum number of related posts you can display is 6.
Details on Related Post Thumbnails
- A post’s featured image will appear as the thumbnail. If you haven’t set a featured image for the post, we will look for slideshows and galleries, and then for any images that may be attached to the post. If we don’t find any image attached to that post, we’ll look for single images you may have inserted in the post. If you’ve inserted an image that is hosted on another site, we can use it too.
- Thumbnails are resized and cropped automatically using the Jetpack image CDN to be 350px wide by 200px tall (1.75:1 ratio) to allow for a consistent visual display. Since this is done automatically, there’s no way to fine-tune where the image is cropped. However, you can change the size of the cropped image by using the jetpack_relatedposts_filter_thumbnail_size filter.
This feature is deactivated by default. It can be activated at any time by toggling the Show related content after posts setting in the Related posts section from Jetpack → Settings → Traffic in your dashboard.
|Site Owners / Users
In order to generate related posts, the following information is used: WordPress.com-connected site ID, local site ID, and the post IDs of the current post and any posts determined to be related. Moreover, related posts are determined by running the post content through Elasticsearch on WordPress.com servers.Additionally, for activity tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.
|Site Owners / Users
We track when, and by which user, the feature is activated and deactivated. We also track when, and which, configuration settings are modified.
|Data Synced (Read More)|
|Site Owners / Users
We sync options that identify whether or not the feature is activated and how its available settings are configured.