Title: Feature request: support Block Visibility plugin
Last modified: February 18, 2025

---

# Feature request: support Block Visibility plugin

 *  Resolved [Ravi B](https://wordpress.org/support/users/ravibee/)
 * (@ravibee)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/feature-request-support-block-visibility-plugin/)
 * Hi Ernest, I use the [Block Visibility](https://blockvisibilitywp.com/) plugin
   to hide content in a post. It would be nice if ASL didn’t scan hidden content
   in its search. Currently, ASL ignores the “hidden” attribute and finds matches
   in hidden text thereby allowing the user to navigate to a page that could potentially
   only display an “Under Construction” message, because the found content is actually
   hidden and yet not ready for public consumption.
 * Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [Ernest Marcinko](https://wordpress.org/support/users/ernestmarcinko/)
 * (@ernestmarcinko)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/feature-request-support-block-visibility-plugin/#post-18313171)
 * Hi,
 * Thank you very much for your suggestion, but I’m not sure if this is technically
   possible. While the part of content is hidden when it’s rendered, it is still
   there in the database and at that point it’s not possible to differenciate (as
   it is only raw text content).
   I will surely take a look, but there is a very 
   good chance this is not possibe to achieve.
 * All the best,
   Ernest
 *  Thread Starter [Ravi B](https://wordpress.org/support/users/ravibee/)
 * (@ravibee)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/feature-request-support-block-visibility-plugin/#post-18314136)
 * Hi Ernest, I totally understand. I suggested it as a feature request because 
   of the popularity of [Block Visibility](https://blockvisibilitywp.com/). I realize
   it could increase ASL’s indexing time when a post is created or modified.
 * Perhaps a configuration flag for “Don’t search hidden content” may help? That
   would allow a graceful fallback to existing behavior if there are any issues 
   with the implementation. The default value of this flag could even be “False”.
 * Thanks.
 *  Plugin Support [Ernest Marcinko](https://wordpress.org/support/users/ernestmarcinko/)
 * (@ernestmarcinko)
 * [1 year, 3 months ago](https://wordpress.org/support/topic/feature-request-support-block-visibility-plugin/#post-18315427)
 * I will definitely take a look, but it’s unfortunately much more complicated than
   that. I’m not sure if it’s technically possible to exclude that content, as what
   the search plugin “sees” in the database vs what the user gets are very different.
 * All the best,
   Ernest

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Feature request: support Block Visibility plugin’ is closed to new replies.

 * ![](https://ps.w.org/ajax-search-lite/assets/icon-256x256.png?rev=3192672)
 * [Ajax Search Lite - Live Search & Filter](https://wordpress.org/plugins/ajax-search-lite/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ajax-search-lite/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ajax-search-lite/)
 * [Active Topics](https://wordpress.org/support/plugin/ajax-search-lite/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ajax-search-lite/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ajax-search-lite/reviews/)

## Tags

 * [hidden text](https://wordpress.org/support/topic-tag/hidden-text/)

 * 3 replies
 * 2 participants
 * Last reply from: [Ernest Marcinko](https://wordpress.org/support/users/ernestmarcinko/)
 * Last activity: [1 year, 3 months ago](https://wordpress.org/support/topic/feature-request-support-block-visibility-plugin/#post-18315427)
 * Status: resolved