The Related Posts feature scans all of your posts’ contents, analyzes it, and uses that to display contextual posts your visitors might be interested in reading after they’re finished with the current post.
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 many plugins like YARPP or Similar Posts are often banned by web hosts, but Jetpack Related Posts are allowed.)
Note: this page describes how to use Related Posts when using the Classic Editor plugin or a Classic block. You can find instructions on adding a Related Posts Block block here.
To start using Related Posts, go to Jetpack → Settings → Traffic page and activate “Show related content after posts”.
Related Posts in the Classic Editor
If you’re using the Classic Editor, Related Posts will display after your post content.
You can opt to display a “Related” header to better separate the section from the end of your post — just activate the “Highlight related content with a heading” option.
You can also choose whether you’d like to include the thumbnail or not. If you’d prefer to display only links, you can disable “Show a thumbnail image where available”.
For further customization options, please read the Customize Related Posts page.
- 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.
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, provided it includes
heightparameters that can inform Jetpack about the image size. (If no such parameters exist, Jetpack has no way of knowing if the images will be big enough, and thus they are ignored.)
- 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 deactivated 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.