Visibility – Lightweight SEO for Search and AI
Active Installs
30+
Last Updated
June 29, 2026
First Released
June 8, 2026
Download History (Last one month)
Visibility is the SEO essentials without the suite. It covers what most sites actually need (meta titles and descriptions, canonical URLs, Open Graph and Twitter Cards, JSON-LD schema, robots directives, redirects, AI Discovery with llms.txt and Markdown for Agents, robots.txt editor and native XML sitemap customization) in about 192 KB, with no Pro tier, no upsell banners and nothing phoning home. It is built on WordPress core APIs (wp_robots, wp_sitemaps_*, register_post_meta, the Block Editor), so most of the work is the platform’s, already optimized.
Coming from Yoast, Rank Math, All in One SEO or SEOPress? Visibility imports your titles, descriptions, robots, Open Graph, schema and redirects in one click. And the clean metadata it outputs is what search engines and AI assistants (ChatGPT, Perplexity, Gemini) read to understand and cite you: the AEO/GEO angle, without the bloat.
Four modules you toggle independently from the Overview tab:
- Discover — meta title and description, Open Graph and Twitter Cards, Article/BreadcrumbList/Person JSON-LD with a selectable schema type per content type, and Site Identity, plus AI discovery: llms.txt, Markdown for agents and a robots.txt editor. Per-post and per-term overrides for title, description, canonical, schema type, social title and description, and image.
- Indexing — bulk or per-item noindex / nofollow by post type and taxonomy, with smart exclusions and rules for search, 404, date, paginated, attachment and author archives plus RSS feeds. Optionally remove the category base from your URLs (with 301s) and redirect attachment pages to their parent. Quick Edit, Bulk actions and a Robots column on your lists.
- Sitemaps — control over the native XML sitemap: exclude post types, taxonomies, users, posts and terms; lastmod dates; 301s from old sitemap URLs; and anything noindexed is kept out automatically.
- Redirects — a lightweight 301 / 302 / 307 / 410 manager resolved in PHP (no .htaccess, no custom table, no 404 log), with CSV import / export, suggested redirects when you delete a post, and the WordPress slug-change redirects surfaced to manage.
Per-post controls live in the Block Editor panel and a matching Classic Editor meta box.
Visibility replaces a full SEO suite rather than running alongside one (two would fight over the <head>), so it warns you if it detects another SEO plugin active. Footprint, migration detail and companion plugins are below.
Perfect companions
Visibility is fully independent — these plugins aren’t required — but they pair really well with it:
- VigIA — AI visibility, crawler analytics, Site Identity JSON-LD on the home page. Visibility coordinates
@idreferences with VigIA so both can add schema without duplicating the Organization or WebSite nodes. - AI Share & Summarize — share buttons for social networks and AI assistants. Helps your content reach both audiences and language models.
- AI Content Signals — control how AI systems can use your content (training, search, both) through
robots.txtdirectives endorsed by Cloudflare. - Vigilante — all-in-one WordPress security: firewall, login protection, security headers, 2FA, file integrity monitoring.
External services
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 (og:image) and in Person JSON-LD (image) for E-E-A-T.
What data is sent and when:
- When a singular view is rendered and the Open Graph module is active, and no other image source exists (per-post
og:image, featured image, WooCommerce gallery image, inline content image), the plugin sends an MD5 hash of the lowercased and trimmed author email tohttps://www.gravatar.com/avatar/{hash}?d=404viawp_remote_head()(HEAD request, no body). - When an author archive is rendered and the Person schema module is active, the same probe is performed for that author.
- The original email address is never sent — only an MD5 hash, which is the standard Gravatar lookup mechanism.
- The result (found / not found) is cached for 24 hours in a transient so subsequent page loads do not hit Gravatar again.
This is the same mechanism WordPress itself uses to display Gravatar avatars in comments. Gravatar’s privacy policy: https://automattic.com/privacy/
Performance and security
“Lightweight” should be a measurement, not a slogan. These are the real numbers for this release, refreshed on every update.
Footprint (1.8.0)
- Download size: about 192 KB zipped.
- Codebase: 36 PHP files, roughly 16,350 lines of PHP.
- Zero custom database tables. Settings live in a single autoloaded option; per-post, per-term and per-author values use native WordPress meta that is already in the object cache.
- Zero cron jobs and no scheduled background processes.
- Zero external HTTP calls, with a single exception: a cached Gravatar HEAD probe (24-hour TTL) that exposes the author avatar for E-E-A-T, the same lookup WordPress already performs for comment avatars.
- Built on WordPress core APIs (
wp_robots,wp_sitemaps_*,register_post_meta,get_canonical_url, the Block Editor), not private reimplementations, so most of the work is the platform’s and already optimized.
Security
- Every release passes a security audit of the changed code (sanitization, escaping, nonces, capabilities, SQL) before it ships. It is a release gate, not an afterthought.
- Minimal attack surface by design: no custom tables, no unauthenticated endpoints, output escaped where it is printed, input validated against allowlists, and prepared statements for every database query.
- No premium tier, no telemetry, no data collection. Nothing phones home.
A smaller surface is a smaller target.
Support
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 contact me and tell me what you need.
Need help or have suggestions?
Love the plugin? Please leave us a 5-star review and help spread the word!
About AyudaWP
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.
- Upload the
native-aeo-packfolder to/wp-content/plugins/or install through the Plugins screen. - Activate the plugin.
- Open Visibility in the admin sidebar to review the active modules and tune the defaults.
- Done. Meta tags, robots directives and sitemap filters are applied automatically based on your settings.
Screenshot Gallery
For most sites, yes. Visibility covers what 90% of sites actually need: titles, meta descriptions, canonical URLs, Open Graph, schema, robots directives, redirect management and sitemap control — and it imports your per-post data from those plugins in one click. It does not include keyword analysis or content scoring. If you don’t need those, Visibility is a much lighter alternative. If you do, stick with your current SEO plugin — Visibility isn’t meant to run alongside.
Install and activate Visibility. If data from any of those plugins exists in your database (the suite can be active or already deactivated), the Overview tab shows an import card with a per-field breakdown: titles, meta descriptions and robots overrides on posts and on taxonomy terms, plus canonical URLs, Open Graph images, social titles and descriptions, the default social image and the per-content-type schema type. Your existing 301, 302, 307 and 410 redirects come over too, from Rank Math, All in One SEO and SEOPress. One click copies it all into Visibility without touching the source plugin, skipping anything you already set here and any value built from the suite’s template variables (%%title%%, %title%, #post_title) — Visibility generates those from your real content. From its free version, All in One SEO stores fewer fields (no Open Graph images and no per-term SEO, which are AIOSEO Pro features); Yoast and Rank Math import the full list, taxonomy terms included. The per-field breakdown always shows exactly what was found before you import, and the import is non-destructive and idempotent: your existing Visibility values win and re-running never duplicates. Review a few entries, then deactivate the suite. Old sitemap URLs (sitemap.xml, post-sitemap.xml…) keep working through a 301 redirect to the native /wp-sitemap.xml.
Install and activate Visibility. If it finds data from any of those plugins, the Overview tab shows an import card with a per-plugin breakdown and an “Import now” button. The import is non-destructive (it copies, never deletes) and your existing Visibility values win on any conflict, so you can run it safely. Once you’ve imported and checked everything, deactivate the old plugins.
No. Visibility stores its settings in a single WordPress option and uses native post, term and user meta tables for per-content overrides. Deleting the plugin removes the option; per-content overrides remain so reinstalling does not lose your work.
Yes. The Overview tab lets you toggle Discover (meta tags), Indexing (robots), Sitemaps and Redirects independently. You can run only what you need.
It emits the signals AI search and assistants can read about your site: Site Identity JSON-LD (who is behind it), llms.txt and llms-full.txt (a Markdown index of your content, with taxonomy sections and WooCommerce-aware data), a clean Markdown version of every page at its .md URL, and a robots.txt editor to allow or block AI crawlers by name. No plugin can guarantee a citation, but Visibility makes your content easy for AI systems to find, read and attribute, and these are served on the fly with no extra files or cron. The companion plugin VigIA can then measure which AI crawlers actually visit.
Yes. All public post types and taxonomies are supported — including WooCommerce product categories, tags and attributes (the latter requires “Enable Archives?” in the WooCommerce attribute settings).
In the Block Editor, open the Visibility panel in the post sidebar and tick the noindex toggle. In the Classic Editor, the same toggle is in the Visibility meta box. You can also use Quick Edit or Bulk Actions from the post list.
Yes, and this is an SEO safeguard worth knowing about. WordPress only serves its virtual /robots.txt on root installs once the rewrite rules have been flushed; on a subdirectory install, or when the rules go stale, /robots.txt can return a 404 while the same directives still answer at /?robots=1 — so crawlers asking for the canonical /robots.txt get nothing. Visibility takes ownership of the endpoint: it serves /robots.txt itself when there is no physical file (independent of the rewrite rules, so it works on any install), and when another plugin writes a physical robots.txt that the web server would serve instead, it merges its own directives into that file in a BEGIN/END block, leaving every other block untouched, so its rules prevail there too. It also 301-redirects WordPress’s internal /?robots=1 to /robots.txt. The result is a single canonical /robots.txt that always loads your AI-crawler and indexing rules, even behind a static file.
In standard WordPress post meta (_native_aeo_pack_* keys). Term overrides go to term meta, user social URLs to user meta. Nothing leaves the standard WordPress tables.
Public helper class methods are available for third-party integrations. Documentation will be expanded as the public API stabilizes.
Changelog
1.8.0
- New: Your site structure in llms.txt. Add taxonomy archive sections — the categories, tags or custom taxonomies you choose — to /llms.txt, each listing its terms with their archive URL and entry count, so AI agents see how your content is organized, not just the individual entries.
- New: WooCommerce product details in Markdown. The .md version of a product now carries its SKU, price, currency, stock status and rating in the YAML frontmatter, next to its product categories and tags.
- Improved: llms.txt and Markdown now share their content rules. A post you keep out of llms.txt, with the per-post exclude flag or a URL pattern, is also withheld from its .md, so both AI surfaces stay consistent.
- Improved: Richer Markdown frontmatter. Every .md now lists its categories and tags by name and sends an X-Markdown-Tokens header with an estimated token count, so agents can size the read before fetching it.
- Improved: llms.txt lists everything. The per-type entry cap is gone — the index now includes every published entry of each selected type. You can also include whole taxonomies at once, not only individual terms.
- Improved: Your robots.txt always prevails. Visibility now references your llms.txt from robots.txt, and when another plugin writes a physical robots.txt that the web server would serve instead, it merges its own directives into that file in a BEGIN/END block, leaving every other block untouched, so your AI-crawler rules always reach crawlers.
- Improved: Your llms.txt always prevails. While llms.txt is enabled, Visibility’s index is what gets served: if another plugin leaves a physical llms.txt that would shadow the dynamic one, Visibility replaces it (and llms-full.txt when that is enabled). Turning the endpoint on in Visibility is taken as your decision to let it manage the file, so an incomplete llms.txt from another llms or SEO plugin cannot take over.
- Fix: Saving the Discover settings now applies the physical llms.txt / robots.txt change from the values you just saved, not the previous ones, so toggling the physical-file mode takes effect on the same save instead of the next page load.
- Fix: Visibility no longer triggers WordPress 6.7+’s “translation loading was triggered too early” notice for the native-aeo-pack text domain. Its default settings were built on the plugins_loaded hook from an AI-crawler catalogue that carried translated labels, so a string was translated before the init action; the catalogue’s data and its labels are now kept apart and nothing loads translations early. The notice surfaced on sites whose language has the plugin’s translations installed with WP_DEBUG enabled.
For older changelog entries, please check the changelog.txt file.
" width="120" height="120">
