Sebastjan

Search is shifting from ten blue links to AI answers. When ChatGPT, Claude, 
Grok, Perplexity or Gemini crawl your site, a handful of signals decide whether 
they can read, understand and cite your content. NINJA AI SEO scores those 
signals and shows you exactly what to fix.
AI visibility (site-level):
<ul>
<li>AI crawler access — checks whether your robots.txt lets GPTBot, ClaudeBot, 
Google-Extended, PerplexityBot and Common Crawl in. Block them and you can 
never be quoted.</li>
<li>Structured data — emits schema.org JSON-LD (Article/WebPage) on every post 
and page, turning your prose into facts a model can extract and trust.</li>
<li>llms.txt — detects the site-root file that tells LLMs what your best 
content is (Pro generates it for you).</li>
<li>XML sitemap — confirms crawlers can discover every page.</li>
</ul>
On-page audit (per post/page, scored 0–100):
<ul>
<li>Meta description — the summary engines read first and often quote</li>
<li>SEO title length — how your page is titled and attributed</li>
<li>Image alt text — the only thing a text model “sees” in an image</li>
<li>Content length, subheadings, internal links</li>
</ul>
The Overview tab gives you a site SEO-health score, an AI-visibility panel, and 
your top opportunities. For every page you can set the SEO title and meta 
description by hand; NINJA AI SEO outputs them (and the JSON-LD) on the front 
end immediately. The free plugin is fully functional on its own and makes no 
external connections.
<h3>NINJA AI SEO Pro (optional add-on)</h3>
NINJA AI SEO Pro is a separate add-on (available from https://ninja.si — not from 
the WordPress.org directory) that adds a one-click auto-fix engine: it generates 
meta descriptions and SEO titles from each page’s own content and backfills 
missing image alt text, per page or across the whole site. Pro is the only part 
that connects to ninja.si, and only after you choose to activate it.
<h3>Privacy</h3>
The free plugin sends no data anywhere — all auditing happens locally in your 
WordPress install. (The optional Pro add-on contacts ninja.si only when you 
register it; see the Pro readme.)

NINJA AI SEO

Make your content visible to AI answer engines (ChatGPT, Claude, Perplexity, Gemini) and classic search. Audits SEO + AI signals, emits schema.

Ayuda WordPress

Fernando Tellado

Visibility brings together everything a WordPress site needs for technical SEO without installing a heavyweight all-in-one plugin. It is built around WordPress native features (<code>wp_robots</code>, <code>wp_sitemaps_*</code>, <code>register_post_meta</code>, the Block Editor sidebar) and stays out of your way: no custom database tables, no cron jobs, no third-party calls beyond a cached Gravatar lookup.
The clean metadata, Open Graph and JSON-LD structured data it generates don’t only help classic search engines (SEO) — they are also what answer engines (AEO) and generative AI assistants and LLMs (GEO) read to understand, summarize and cite your content.
Three modules you toggle independently from the Overview tab:
<ul>
<li>Discover — meta tags, Open Graph, Twitter Cards and JSON-LD schema.</li>
<li>Indexing — robots directives (noindex / nofollow).</li>
<li>Sitemaps — native XML sitemap control.</li>
</ul>
<h4>Built on WordPress core</h4>
Visibility is “native” in the literal sense: every feature is a thin layer over a WordPress core API, not a reimplementation. When the platform already does something, Visibility configures it instead of shipping its own engine.
<ul>
<li>Robots directives ride on the core <code>wp_robots</code> filter, plus the <code>X-Robots-Tag</code> HTTP header for feeds (which are XML and have no <code><head></code>).</li>
<li>The document title is composed by core: Visibility only sets the per-post title through <code>pre_get_document_title</code> and the separator through the native <code>document_title_separator</code> filter.</li>
<li>Canonical URLs go through core’s <code>get_canonical_url</code>, so <code>rel=canonical</code> and <code>og:url</code> always match.</li>
<li>The XML sitemap is core’s own <code>wp-sitemap.xml</code>; Visibility filters the <code>wp_sitemaps_*</code> hooks to shape it and never generates a sitemap of its own.</li>
<li>Per-post, per-term and per-author values are stored in standard post, term and user meta via <code>register_post_meta</code>, and exposed to the Block Editor over the REST API.</li>
<li>Removing the <code>/category/</code> base (and WooCommerce’s <code>/product-category/</code>) uses the core rewrite API and the <code>term_link</code> filter, with 301 redirects on <code>template_redirect</code>; deactivating the plugin restores the default URLs.</li>
<li>Attachment-page redirects use <code>template_redirect</code> and <code>wp_safe_redirect</code>.</li>
<li>The per-post UI is the native Block Editor panel (<code>PluginDocumentSettingPanel</code>) and a Classic Editor meta box, alongside core Quick Edit and Bulk Actions.</li>
<li>Schema coordination references VigIA’s <code>@id</code> nodes instead of duplicating the Organization and WebSite graph.</li>
</ul>
The result is the lightweight footprint described under “Zero database tables” below: no custom tables, no cron jobs, no build step, no external services beyond a cached Gravatar probe.
<h4>Discover: meta tags and social cards</h4>
<ul>
<li>Document title and meta description on home, singulars, taxonomy archives and author archives, auto-generated from the content you already have (post title, excerpt, term description, user biographical info).</li>
<li>Open Graph tags (<code>og:title</code>, <code>og:description</code>, <code>og:image</code>, <code>og:url</code>, <code>og:type</code>, <code>og:site_name</code>).</li>
<li>Twitter Card tags (<code>summary_large_image</code> when an image is available, <code>summary</code> otherwise).</li>
<li>Article + BreadcrumbList JSON-LD on posts and pages for Google rich results.</li>
<li>Person JSON-LD on author archives with <code>sameAs</code> from user profile social URLs (E-E-A-T).</li>
<li>Smart image detection for <code>og:image</code>: per-post override → featured image → WooCommerce gallery → first inline image in the content → fallback Open Graph image.</li>
<li>Customizable: max length of auto-generated descriptions, home description override, fallback Open Graph image, site-wide Twitter <code>@username</code> and Facebook App ID, publisher logo for Article schema.</li>
<li>Title separator — pick the character placed between the page title and the site name in the automatic document title, applied through the native <code>document_title_separator</code> filter. Per-post title overrides are used verbatim.</li>
<li>Per-post overrides in the post sidebar: meta title (also replaces the document title), meta description, canonical URL, Open Graph image.</li>
<li>Canonical URL override per post or page: replaces <code>rel=canonical</code> and <code>og:url</code> for that entry, for syndicated or duplicate content whose ranking signals should point elsewhere.</li>
<li>Per-term overrides on the term edit screen: meta title and meta description for category, tag and custom taxonomy archives, with the term name and term description as fallbacks.</li>
<li>Author social URLs: fields added to the user profile (Twitter/X, LinkedIn, GitHub, Mastodon, Instagram, YouTube) used as <code>sameAs</code> in Person schema.</li>
</ul>
<h4>Indexing: robots directives (noindex / nofollow)</h4>
<ul>
<li>Bulk noindex / nofollow by post type — Set entire post types (pages, posts, products, etc.) as noindex, nofollow or both with a single checkbox per directive.</li>
<li>Bulk noindex / nofollow by taxonomy — Set entire taxonomy archives (categories, tags, product attributes, etc.) as noindex, nofollow or both. Works with all public taxonomies, including WooCommerce product categories, tags and attributes.</li>
<li>Smart exclusions — When a post type or taxonomy is set to noindex or nofollow, exclude specific posts or terms that should keep the default behavior. Exclusions work independently per directive.</li>
<li>Individual noindex / nofollow — Set noindex or nofollow on specific posts or taxonomy terms without affecting the entire content type or taxonomy.</li>
<li>Instant search — Find content and terms quickly with a live search field in the settings page. Click to add, click to remove.</li>
<li>Link-level nofollow — A nofollow checkbox in the Classic Editor link popup lets you mark individual links with <code>rel="nofollow"</code> without leaving the editor. The Block Editor already exposes a native nofollow toggle in its link popover.</li>
<li>Quick Edit — Toggle noindex and nofollow directly from the post list table without opening the editor.</li>
<li>Bulk actions — Set or remove noindex and nofollow on multiple posts at once from the post list.</li>
<li>Robots column — Two color-coded icons in your content lists show the current index/follow state at a glance.</li>
<li>Search results noindex / nofollow — Prevent internal search result pages from being indexed and/or having their links followed.</li>
<li>404 pages noindex / nofollow — Keep 404 error pages out of search indexes and stop crawlers from following dead-end links.</li>
<li>Date archives noindex / nofollow — Apply either or both directives to daily, monthly and yearly archive pages.</li>
<li>Paginated archives noindex / nofollow — Apply either or both directives to <code>/page/2/</code>, <code>/page/3/</code> and beyond, including Query Loop block pagination on block themes.</li>
<li>Attachment pages noindex / nofollow — Apply either or both directives to media attachment pages.</li>
<li>Author archives noindex / nofollow — Apply either or both directives to author archive pages.</li>
<li>RSS feeds noindex / nofollow — Granular control to noindex and/or nofollow RSS feeds by type: main feed, taxonomy feeds, author feeds, site comments feed and per-post comments feeds. Works via the <code>X-Robots-Tag</code> HTTP header since feeds are XML.</li>
<li>Remove the category base — Optionally strip the <code>/category/</code> base (and WooCommerce’s <code>/product-category/</code>) from category URLs, built on the core rewrite API, with automatic 301 redirects from the old URLs so nothing already indexed breaks. Off by default; deactivating the plugin restores the default URLs.</li>
<li>Attachment page redirects — Optionally 301-redirect attachment pages to their parent post via the core <code>template_redirect</code> hook. Only the attachment page is redirected; the media file itself keeps working. Since WordPress 6.4 new sites disable attachment pages and no longer link to them, so this mainly helps older sites that still use them; on a modern site you can simply noindex them instead. Off by default.</li>
</ul>
Priority logic (applies independently to noindex and nofollow):
<ol>
<li>Individual directive always applies.</li>
<li>Post type / taxonomy bulk directive applies unless the post or term is specifically excluded.</li>
<li>Exclusions override the bulk setting for specific posts or terms.</li>
</ol>
<h4>Sitemaps: native XML sitemap control</h4>
<ul>
<li>Exclude post types from the native <code>wp-sitemap.xml</code>.</li>
<li>Exclude taxonomies entirely from the sitemap.</li>
<li>User control — exclude specific user roles, individual users, or disable the entire users sitemap for single-author sites.</li>
<li>Flexible content exclusions — exclude posts and pages by ID or by slug patterns; exclude taxonomy terms by ID or by slug fragments.</li>
<li>Lastmod dates — adds last-modification dates to every URL in the sitemap and to every entry in the sitemap index (Google’s most used optional field).</li>
<li>Smart redirects — automatically redirect old sitemap URLs left over by other SEO and sitemap plugins (Yoast, Rank Math, AIOSEO, SEOPress, Google XML Sitemaps, Jetpack and others) to the native WordPress sitemap (301), so you don’t lose crawl signals when switching.</li>
<li>Static sitemap detector — spots leftover <code>sitemap.xml</code>, <code>sitemap_index.xml</code>, <code>news-sitemap.xml</code> and similar files in your WordPress root that silently override the native sitemap, and helps you remove them.</li>
<li>Performance — customize the maximum number of URLs per sitemap (1–50,000).</li>
<li>Noindex-aware — content marked as noindex by the Indexing module is automatically excluded from the sitemap, so search engines won’t even find it there.</li>
</ul>
<h4>Coming from Yoast SEO, Rank Math or All in One SEO?</h4>
Visibility imports your SEO data from the big suites in one click: meta titles, meta descriptions and noindex / nofollow overrides — on posts, pages and custom post types, and also on taxonomy terms (categories, tags, custom taxonomies) — plus per-post canonical URLs and Open Graph images. When it finds suite data that is not in Visibility yet, the Overview tab shows an import card with a per-plugin, per-field breakdown. The suite can be active or already deactivated — leftover data in the database is enough.
A note on All in One SEO for transparency: from its free version the import covers meta titles, meta descriptions, canonical URLs and noindex / nofollow, but not Open Graph images or per-term SEO (taxonomy SEO is an AIOSEO Pro feature, so the free version does not store it). Yoast and Rank Math import the full list above, taxonomy terms and Open Graph images included. The per-plugin breakdown on the import card always shows exactly what was found, so you can see this per field before importing.
The import is non-destructive (it copies, never deletes or changes the source), idempotent (re-running never duplicates), and your existing Visibility values always win. Titles and descriptions made from the suite’s template variables (<code>%%title%%</code>, <code>%title%</code>, <code>#post_title</code>) are skipped on purpose: Visibility already generates those from your real content. After importing, review a few entries and deactivate the suite — Visibility never deactivates another plugin for you.
Most site-wide suite settings (search appearance rules, social defaults) are not imported, so review the Discover, Indexing and Sitemaps tabs once and you are set. The exceptions are three parity options Visibility also offers — removing the category base, redirecting attachment pages and the title separator — which are brought over when the suite had them set. Your old sitemap entry points are covered too — legacy sitemap URLs get a 301 redirect to the native <code>/wp-sitemap.xml</code>.
<h4>Coming from Native SEO Meta Tags, NoIndexer or Sitemap Customizer?</h4>
Visibility unifies those three AyudaWP plugins. When it detects their data, the Overview tab offers a one-click importer that copies your per-post, per-term and per-author values, plus the site-wide configuration of each plugin, into Visibility — with a per-plugin summary of exactly what was detected and imported. It is non-destructive: your existing Visibility values are kept, lists are merged, and nothing is removed from the old plugins.
<h4>Block Editor integrated</h4>
A single sidebar panel in the Block Editor exposes everything you need per post:
<ul>
<li>Meta title (also replaces the document title).</li>
<li>Meta description.</li>
<li>Canonical URL.</li>
<li>Open Graph image (with media picker and live preview).</li>
<li><code>noindex</code> toggle.</li>
<li><code>nofollow</code> toggle.</li>
</ul>
The panel is implemented as a <code>PluginDocumentSettingPanel</code> — fully compatible with WordPress collaborative editing.
<h4>Classic Editor compatible</h4>
When the Block Editor is disabled for a post type, all the per-post controls are exposed as a single Classic Editor meta box with the same fields. Quick Edit and Bulk Actions on the post list provide the noindex/nofollow toggles without opening the editor.
<h4>Zero database tables</h4>
Visibility uses standard WordPress options and post/term/user meta tables. No custom tables, no cron jobs, no scheduled background processes, no external API calls beyond a cached Gravatar avatar probe (24h TTL) for E-E-A-T author images.
<h4>Replaces full SEO plugins, doesn’t coexist with them</h4>
Visibility is not designed to run alongside Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework or Slim SEO. Running two SEO plugins generates duplicate <code><head></code> tags and hurts your SEO. If Visibility detects one of these active it will warn you on the settings page — you should keep one and deactivate the other.
If you want full keyword analysis, redirect managers, content scoring and dozens more features, stick with your current SEO suite. If you want the essentials, fast and native, Visibility is for you.
<h4>Perfect companions</h4>
Visibility is fully independent — these plugins aren’t required — but they pair really well with it:
<ul>
<li><a href="https://wordpress.org/plugins/vigia/" rel="ugc">VigIA</a> — AI visibility, crawler analytics, Site Identity JSON-LD on the home page. Visibility coordinates <code>@id</code> references with VigIA so both can add schema without duplicating the Organization or WebSite nodes.</li>
<li><a href="https://wordpress.org/plugins/ai-share-summarize/" rel="ugc">AI Share & Summarize</a> — share buttons for social networks and AI assistants. Helps your content reach both audiences and language models.</li>
<li><a href="https://wordpress.org/plugins/ai-content-signals/" rel="ugc">AI Content Signals</a> — control how AI systems can use your content (training, search, both) through <code>robots.txt</code> directives endorsed by Cloudflare.</li>
<li><a href="https://wordpress.org/plugins/vigilante/" rel="ugc">Vigilante</a> — all-in-one WordPress security: firewall, login protection, security headers, 2FA, file integrity monitoring.</li>
</ul>
<h3>External services</h3>
This plugin connects to Gravatar (operated by Automattic Inc.) to check whether the post or page author has a public Gravatar avatar, so it can be exposed in Open Graph tags (<code>og:image</code>) and in Person JSON-LD (<code>image</code>) for E-E-A-T.
What data is sent and when:
<ul>
<li>When a singular view is rendered and the Open Graph module is active, and no other image source exists (per-post <code>og:image</code>, featured image, WooCommerce gallery image, inline content image), the plugin sends an MD5 hash of the lowercased and trimmed author email to <code>https://www.gravatar.com/avatar/{hash}?d=404</code> via <code>wp_remote_head()</code> (HEAD request, no body).</li>
<li>When an author archive is rendered and the Person schema module is active, the same probe is performed for that author.</li>
<li>The original email address is never sent — only an MD5 hash, which is the standard Gravatar lookup mechanism.</li>
<li>The result (found / not found) is cached for 24 hours in a transient so subsequent page loads do not hit Gravatar again.</li>
</ul>
This is the same mechanism WordPress itself uses to display Gravatar avatars in comments. Gravatar’s privacy policy: https://automattic.com/privacy/
<h3>Support</h3>
Need private support or custom development?
Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just <a href="mailto:native-aeo-pack@ayudawp.com" rel="nofollow ugc">contact me</a> and tell me what you need.
Need help or have suggestions?
<ul>
<li><a href="https://visibility.quest" rel="nofollow ugc">Official website</a></li>
<li><a href="https://wordpress.org/support/plugin/native-aeo-pack/" rel="ugc">WordPress support forum</a></li>
<li><a href="https://www.youtube.com/AyudaWordPressES" rel="nofollow ugc">YouTube channel</a></li>
<li><a href="https://ayudawp.com" rel="nofollow ugc">Documentation and tutorials</a></li>
</ul>
Love the plugin? Please leave us a 5-star review and help spread the word!
<h3>About AyudaWP</h3>
We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.

Visibility – Native SEO / AEO / GEO

Visible to search. Visible to AI. Lightweight SEO, AEO & GEO on WordPress core: meta tags, schema, Open Graph, robots and native sitemap.

NINJA AI SEO vs Visibility – Native SEO / AEO / GEO