Improve your WordPress SEO: Write better content and have a fully optimized WordPress site using the Yoast SEO…
About Relevanssi – A Better Search
Relevanssi is a plugin for WordPress that improves the search functionality on your website. It provides better search results, customizable options, and features like fuzzy matching, phrase search, and highlighting of search terms. While the free version is available, there is also a premium version with additional features. However, using Relevanssi may require a large amount of database space, so it may not be recommended for hosting setups with limited space.Screenshots
Frequently asked questions
What is Relevanssi?
Relevanssi replaces the standard WordPress search with a better search engine, with lots of features and configurable options. You'll get better results, better presentation of results – your users will thank you.
Is there a premium version of Relevanssi?
Yes, there is a premium version of Relevanssi called Relevanssi Premium. It has added features.
Does using Relevanssi require a large amount of database space?
Yes, using Relevanssi may require large amounts (hundreds of megabytes) of database space. If your hosting setup has a limited amount of space for database tables, using Relevanssi may cause problems.
What are the key features of Relevanssi?
The key features of Relevanssi include: search results sorted in the order of relevance, fuzzy matching, search for phrases with quotes, create custom excerpts, highlight search terms, search comments, tags, categories, and custom fields, multisite friendly, bbPress support, and Gutenberg friendly.
What are the advanced features of Relevanssi?
The advanced features of Relevanssi include: adjust the weighting for titles, tags, and comments, log queries, restrict searches to categories and tags, index custom post types and custom taxonomies, index the contents of shortcodes, 'Did you mean?' suggestions, support for WPML multi-language plugin and Polylang, support for membership plugins, advanced filtering, search result throttling, and disable indexing of post content and post titles.
Changelog
4.24.3
- New feature: New filter hook
relevanssi_cached_post_objectcan be used to modify the cached post objects. - Minor fix: Relevanssi cache population now creates stdClass objects instead of WP_Post objects to avoid out of memory issues. If you need WP_Post objects, use the
relevanssi_cached_post_objectfilter hook to create them. - Minor fix: Avoid problems with object custom field values.
4.24.2
- Minor fix: Fix broken excerpts.
4.24.1
- Minor fix: Prevent database errors.
4.24.0
- Minor fix: SEO Framework local search exclude option description now tells what the option actually does.
- Minor fix: Relevanssi cache population now creates WP_Post objects instead of stdClass objects.
- Minor fix: SEOPress compatibility mode is enabled again.
- Minor fix: Avoid fatal errors in installation process with Polylang enabled.
- Minor fix: Update counts link had the wrong tab query parameter.
- Minor fix: Adjust post type parameter handling so that it doesn’t change the
post_typequery var.
4.23.1
- Security fix: Prevent an XSS attack by a malicious contributor.
4.23.0
- New feature: New filter hook
relevanssi_forbidden_post_typesfilters the list of post types excluded from Relevanssi indexing. - New feature: New filter hook
relevanssi_forbidden_taxonomiesfilters the list of taxonomies excluded from Relevanssi indexing. - New feature: New filter hook
relevanssi_show_password_protectedcontrols whether password protected posts are shown in the search results. - New feature: Support for
post_mime_typequery parameter. - New feature: Relevanssi settings tabs have more CSS ids to help hide individual settings.
- Changed behaviour: Password protected posts are excluded from the search results by default to protect their contents.
- Minor fix: In rare cases, the search results would not be in relevance order if the throttle wasn’t used.
- Minor fix: The settings tab query parameter was renamed to avoid collisions with other plugins.
- Minor fix: User searches page now uses
wp_print_inline_script_tag().
