jacobmikkelsen0311

Varnild checks how well your pages are set up to be found, read, and understood by AI search and assistants. Every result is transparent and explainable: each score is simply “X of Y checks passed”, so you always know why a page scored the way it did.
What you get:
<ul>
<li>Deterministic, explainable checks across three areas (access, answerability, and technical basics).</li>
<li>Clear guidance on what to fix, shown only where a check fails.</li>
<li>A prioritized “Problems” view that lists the most widespread issues across your site first.</li>
<li>History, so you can see how a page develops over time.</li>
<li>Optional AI-generated suggestions (titles, descriptions, FAQ, structured data and more), drafted for you to review — never applied automatically.</li>
</ul>
Varnild measures readiness — how prepared a page is to be found by AI. It does not promise or guarantee that any page will be cited by an AI system.
Scan results — including the score, check details, and any AI analysis and suggestions — are stored in your own WordPress database so you can view history. Only the three most recent scans per URL are kept.
<h3>External services</h3>
This plugin connects to an external service to analyze your pages: the Varnild scanning service.
When you run a scan, the plugin sends the page’s URL to the Varnild service. The service retrieves that page, analyzes it, and returns the results (a score and the per-check details) to your site.
When you request AI suggestions for a page, the plugin sends the page’s URL together with the list of checks that failed for that page. The Varnild service then retrieves the page and sends relevant page content to Google’s Gemini API to generate the suggestions, which are returned to your site as drafts for you to review.
Data is sent to these services only when you actively start a scan or request AI suggestions — nothing is sent in the background.
The Varnild service processes the data only to generate the results and does not retain the URL or page content after returning the response.
The AI-suggestion feature is powered by Google’s Gemini API, so page content used for those suggestions is processed by Google. On Google’s free tier, submitted content may be used by Google to improve their services; see Google’s terms below.
Google Gemini API — Terms: https://ai.google.dev/gemini-api/terms — Privacy: https://policies.google.com/privacy

Varnild

See how ready your pages are to be found and understood by AI — with clear, explainable checks and optional AI suggestions.

Jonathan Horowitz

Content Visibility for Divi Builder allows Sections and Modules to be displayed/hidden based on the outcome of a PHP boolean expression.
This plugin is for both the standalone Divi theme (or child themes thereof) and the Divi Builder plugin, version 3 or higher!
<h3>Developer Filters</h3>
<h4>Expression Validation Filters</h4>
The following filters allow developers to customize expression validation behavior. Add these filters in your theme’s functions.php or in a custom plugin.
<code>content_visibility_for_divi_builder_blocked_functions</code>
Filter the array of blocked function names. Functions in this list will cause an expression to fail validation. All comparisons are case-insensitive.
Example – allow <code>file_get_contents</code> (blocked by default):
<pre><code>add_filter( 'content_visibility_for_divi_builder_blocked_functions', function( $functions ) {
 return array_diff( $functions, array( 'file_get_contents' ) );
} );
</code></pre>
Example – block an additional function:
<pre><code>add_filter( 'content_visibility_for_divi_builder_blocked_functions', function( $functions ) {
 $functions[] = 'my_dangerous_function';
 return $functions;
} );
</code></pre>
<code>content_visibility_for_divi_builder_allowed_tokens</code>
Filter the array of allowed PHP token types (T_* constants). Tokens not in this list will cause an expression to fail validation. This is an advanced filter – consult the PHP tokenizer documentation before modifying.
Example – allow the T_VARIABLE token type (blocked by default, use with caution):
<pre><code>add_filter( 'content_visibility_for_divi_builder_allowed_tokens', function( $tokens ) {
 $tokens[] = T_VARIABLE;
 return $tokens;
} );
</code></pre>
<code>content_visibility_for_divi_builder_allowed_chars</code>
Filter the array of allowed single-character tokens. Characters not in this list (such as <code>=</code>, <code>;</code>, <code>{</code>, <code>}</code>, <code>`</code>, <code>@</code>, <code>&</code>, <code>|</code>, <code>~</code>, <code>^</code>) will cause an expression to fail validation.
Example – allow the <code>&</code> character for bitwise operations:
<pre><code>add_filter( 'content_visibility_for_divi_builder_allowed_chars', function( $chars ) {
 $chars[] = '&';
 return $chars;
} );
</code></pre>
<code>content_visibility_for_divi_builder_allowed_callables</code>
Filter the array of callables (function names and <code>Class::method</code> static-method entries) the validator considers known-safe. Anything not on the allowlist (and not on the <code>blocked_functions</code> denylist) is treated as an “Unknown callable” error. Names are normalized (leading <code>\</code> stripped, <code>namespace\</code> keyword prefix stripped, lowercased) before comparison, so <code>\My\Namespace\Class::method</code>, <code>My\Namespace\Class::method</code>, and <code>namespace\My\Namespace\Class::method</code> all match the same allowlist entry. The default list ships with WordPress conditional tags (<code>is_user_logged_in</code>, <code>current_user_can</code>, <code>is_admin</code>, etc.). The Expression Validation tab’s content scanner generates a ready-to-paste snippet for this filter pre-populated with every custom callable currently in your content.
Example – allowlist a theme helper and a static service method:
<pre><code>add_filter( 'content_visibility_for_divi_builder_allowed_callables', function( $callables ) {
 $callables[] = 'mytheme_should_be_visible';
 $callables[] = 'MyTheme\Visibility\Service::checkUser';
 return $callables;
} );
</code></pre>

Content Visibility for Divi Builder

Thanks for maintaining this plugin. It works great. Some examples in the documentation would make the use at the beginning easier :)

Great PlugIn


I found this addon to be very useful in putting up content for a persons website. It allows you to create PHP functions or use inherent true/false functions that you can then control what content shows based on that. I find it useful in having one content being shown before a certain date and another block being set to show after a certain date. Allowing you to schedule content changes within the website.


Varnild vs Content Visibility for Divi Builder