Related posts for your WordPress site with inbuilt caching. Supports blocks, shortcodes, widgets and custom post types!
Contextual Related Posts is a powerful WordPress plugin that helps you increase your site’s engagement by displaying a list of related posts that are relevant and interesting to your readers.
Contextual Related Posts uses a smart algorithm that analyzes the title and/or content of your posts to find the most related ones. This way, you can show your visitors more of your awesome content and keep them on your site longer.
Contextual Related Posts also comes with many features and options that let you customize the look and feel of the related posts list. You can choose between different styles, layouts, thumbnails, excerpts, and more. You can also use widgets, shortcodes, Gutenberg blocks, or REST API to display the related posts anywhere on your site or in your feed.
With Contextual Related Posts, you can easily boost your site’s traffic, reduce bounce rates, and refresh old entries. It’s fast, flexible, and easy to use. Try it today and see the difference for yourself!
[crp]
to display the related posts anywhere within the post content.contextual-related-posts/v1/posts/<id>/
. You can also use query parameters to filter or sort the results.CRP Pro enhances your experience with an advanced query block, offering more precise customisation options, additional shortcode functionalities, and enhanced meta box settings.
On activation, the plugin creates three mySQL FULLTEXT indices (or indexes) that are then used to find the related posts in the *_posts
. These are for post_content
, post_title
and (post_title,post_content)
. The Pro version also has an index for post_excerpt
.
If you’re running a multisite installation, then this is created for each of the blogs on activation. All these indices occupy space in your mySQL database but are essential for the plugin to run.
You have two sets of options in the settings page which allows you to remove these indices when you deactivate or delete the plugin. The latter is true by default.
If you do not wish to use these indices, you can disable contextual matching in the settings page. You will need to turn on related posts by category, tags and/or custom taxonomies.
Contextual Related Posts is GDPR compliant as it doesn’t collect any personal data about your visitors when installed out of the box. All posts are processed on your site and not sent to any external service.
YOU ARE RESPONSIBLE FOR ENSURING THAT ALL GDPR REQUIREMENTS ARE MET ON YOUR WEBSITE.
I spend a significant amount of my free time maintaining, updating and more importantly supporting this plugin. Those who have sought support in the support forums know that I have done my best to answer your question and solve your problem.
If you have been using this plugin and find this useful, do consider making a donation. This helps me pay for my hosting and domains.
Contextual Related Posts is also available on Github.
So, if you’ve got some cool feature that you’d like to implement into the plugin or a bug you’ve been able to fix, consider forking the project and sending me a pull request.
Bug reports are welcomed on GitHub. Please note GitHub is not a support forum and issues that aren’t properly qualified as bugs will be closed.
Contextual Related Posts is available for translation directly on WordPress.org. Check out the official Translator Handbook to contribute.
Contextual Related Posts is one of the many plugins developed by WebberZone. Check out our other plugins:
Navigate to Plugins within your WordPress Admin Area
Click “Add new” and in the search box enter “Contextual Related Posts”
Find the plugin in the list (usually the first result) and click “Install Now”
Download the plugin
Extract the contents of contextual-related-posts.zip to wp-content/plugins/ folder. You should get a folder called contextual-related-posts.
Activate the Plugin in WP-Admin under the Plugins screen
Check out the FAQ on the plugin page or the Knowledge Base.
If your question isn’t listed there, please create a new post at the WordPress.org support forum. It is the fastest way to get support as I monitor the forums regularly.
Support for products sold and distributed by WebberZone is only available for those who have an active, paid extension license. You can access our support form here.
Contextual Related Posts is highly customizable. There are several configurable options in the Settings page and you can use CSS to customize the outputs. Learn more by reading this article.
You can insert the related posts anywhere in your post using the [crp]
shortcode. View this article in the knowledge base for more details.
You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team help validate, triage and handle any security vulnerabilities. Report a security vulnerability.
If you enable thumbnails, the plugin will try to find the correct thumbnail in this order:
Post meta field: This is the meta field value you can use when editing your post. The default is post-image
. Change it in the Settings page
Post Thumbnail image: The image that you can set under Featured Image
First image in the post: The plugin will try to fetch the first image in the post. Toggle this in the Settings page
First child image attached to the post
Site Icon: this is typically set using Customizer
Default Thumbnail: If enabled, it will use the default thumbnail that you specify in the Settings page
Release post: https://webberzone.com/announcements/contextual-related-posts-v3-5-0/
Modifications:
Fixes:
manual_related
attribute in shortcoderelation
attribute is set for meta_query and tax_querypost_status
when using get_posts()
the_posts
filter in CRP_QueryModifications:
Bug fix:
Complete code rewrite using OOP, namespacing and autoloading. This will make it easier to maintain and extend the plugin in the future.
Features:
display_only_on_tax_ids
to display related posts only on specific taxonomy termsinclude_cat_ids
to include related posts from specific categories onlyEnhancements:
WP_Query
directly if crp_query
is set in the query argumentsBug fix:
trim_char
function returned a blank string instead of the original string if length was 0For the changelog of earlier versions, please refer to the separate changelog.txt file or the releases page on Github.