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.

Storm Rockwell

Allows you to discourage search engines by url to prevent you from forgetting to turn off the “Search Engine Visibility” setting when going between development and live instances.
Features
<ol>
<li>A field to enter in as many domains as needed</li>
<li>An icon in the admin bar to display if the current page is indexable for convenience and debugging</li>
<li>A checkbox to hide the icon in the admin bar</li>
</ol>
Usage
<ol>
<li>Go to Settings > Reading</li>
<li>Make sure “Search Engine Visibility” is unchecked</li>
<li>Add your development environment URL(s) or any url you want to be not indexable. You can do partial urls such as “staging.” to cover all staging. subdomains.</li>
<li>Hover the eye icon in the admin bar to make sure it is set up correctly.</li>
</ol>
For Example: if my live site was google.com and my development site was dev.google.com I would enter dev.google.com in the field.

Discourage Search Engines by URL

Allows you to discourage search engines by url to prevent you from forgetting to turn the setting off when transfering databases between development a …

Varnild vs Discourage Search Engines by URL