plugin-icon

Visibility – Native SEO / AEO / GEO

מאת Fernando Tellado·
Visible to search. Visible to AI. Lightweight SEO, AEO & GEO on WordPress core: meta tags, schema, Open Graph, robots and native sitemap.
noindex
open graph
schema
דירוגים
הוסף חוות דעת
גרסה
1.5.0
התקנות פעילות
20
עודכן לאחרונה
Jun 22, 2026
Visibility – Native SEO / AEO / GEO

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 (wp_robots, wp_sitemaps_*, register_post_meta, 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:

  • Discover — meta tags, Open Graph, Twitter Cards and JSON-LD schema.
  • Indexing — robots directives (noindex / nofollow).
  • Sitemaps — native XML sitemap control.

Visibility replaces a full SEO suite, it does not run alongside one: two SEO plugins fight over the <head> and hurt your ranking. If you need keyword research, redirect managers or content scoring, keep your current suite; if you want the essentials, fast and native, this is for you. When it detects Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework or Slim SEO active, it warns you on the settings page so you run only one.

Switching from one of those, or from the legacy AyudaWP plugins (Native SEO Meta Tags, NoIndexer, Sitemap Customizer)? The Overview tab runs a one-click, non-destructive importer that brings your per-post, per-term and per-author values, plus each plugin's site-wide settings, into Visibility. See the migration FAQ below for the field-by-field detail.

The full feature list per module, the editor integration, the migration details and the recommended companion plugins are in the sections below.

Discover: meta tags and social cards

  • 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).
  • Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:site_name).
  • Twitter Card tags (summary_large_image when an image is available, summary otherwise).
  • Article + BreadcrumbList JSON-LD on posts and pages for Google rich results.
  • Person JSON-LD on author archives with sameAs from user profile social URLs (E-E-A-T).
  • Smart image detection for og:image: per-post override → featured image → WooCommerce gallery → first inline image in the content → fallback Open Graph image.
  • Customizable: max length of auto-generated descriptions, home description override, fallback Open Graph image, site-wide Twitter @username and Facebook App ID, publisher logo for Article schema.
  • Title separator — pick the character placed between the page title and the site name in the automatic document title, applied through the native document_title_separator filter. Per-post title overrides are used verbatim.
  • Schema @type per content type — choose the JSON-LD type emitted on each content type's singulars, from the Article family (Article, BlogPosting, NewsArticle…) or the page types (WebPage, AboutPage, CollectionPage…), with a per-entry override. Limited to types that fill from the post content; rich types (Recipe, Product, Event…) are left to the plugins that own that data.
  • Per-post overrides in the post sidebar: meta title (also replaces the document title), meta description, canonical URL, social title and social description (override og: / twitter: title and description), Open Graph image, and the schema @type for the entry.
  • Canonical URL override per post or page: replaces rel=canonical and og:url for that entry, for syndicated or duplicate content whose ranking signals should point elsewhere.
  • 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.
  • Author social URLs: fields added to the user profile (Twitter/X, LinkedIn, GitHub, Mastodon, Instagram, YouTube) used as sameAs in Person schema.

Indexing: robots directives (noindex / nofollow)

  • 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.
  • 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.
  • 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.
  • Individual noindex / nofollow — Set noindex or nofollow on specific posts or taxonomy terms without affecting the entire content type or taxonomy.
  • Instant search — Find content and terms quickly with a live search field in the settings page. Click to add, click to remove.
  • Link-level nofollow — A nofollow checkbox in the Classic Editor link popup lets you mark individual links with rel="nofollow" without leaving the editor. The Block Editor already exposes a native nofollow toggle in its link popover.
  • Quick Edit — Toggle noindex and nofollow directly from the post list table without opening the editor.
  • Bulk actions — Set or remove noindex and nofollow on multiple posts at once from the post list.
  • Robots column — Two color-coded icons in your content lists show the current index/follow state at a glance.
  • Search results noindex / nofollow — Prevent internal search result pages from being indexed and/or having their links followed.
  • 404 pages noindex / nofollow — Keep 404 error pages out of search indexes and stop crawlers from following dead-end links.
  • Date archives noindex / nofollow — Apply either or both directives to daily, monthly and yearly archive pages.
  • Paginated archives noindex / nofollow — Apply either or both directives to /page/2/, /page/3/ and beyond, including Query Loop block pagination on block themes.
  • Attachment pages noindex / nofollow — Apply either or both directives to media attachment pages.
  • Author archives noindex / nofollow — Apply either or both directives to author archive pages.
  • 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 X-Robots-Tag HTTP header since feeds are XML.
  • Remove the category base — Optionally strip the /category/ base (and WooCommerce's /product-category/) 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.
  • Attachment page redirects — Optionally 301-redirect attachment pages to their parent post via the core template_redirect 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.

Priority logic (applies independently to noindex and nofollow):

  1. Individual directive always applies.
  2. Post type / taxonomy bulk directive applies unless the post or term is specifically excluded.
  3. Exclusions override the bulk setting for specific posts or terms.

Sitemaps: native XML sitemap control

  • Exclude post types from the native wp-sitemap.xml.
  • Exclude taxonomies entirely from the sitemap.
  • User control — exclude specific user roles, individual users, or disable the entire users sitemap for single-author sites.
  • Flexible content exclusions — exclude posts and pages by ID or by slug patterns; exclude taxonomy terms by ID or by slug fragments.
  • 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).
  • 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.
  • Static sitemap detector — spots leftover sitemap.xml, sitemap_index.xml, news-sitemap.xml and similar files in your WordPress root that silently override the native sitemap, and helps you remove them.
  • Performance — customize the maximum number of URLs per sitemap (1–50,000).
  • 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.

Editor integration

Block Editor

A single sidebar panel in the Block Editor exposes everything you need per post:

  • Meta title (also replaces the document title).
  • Meta description.
  • Canonical URL.
  • Social title and social description (override og: / twitter: title and description).
  • Open Graph image (with media picker and live preview).
  • Schema @type for the entry.
  • noindex toggle.
  • nofollow toggle.

The panel is implemented as a PluginDocumentSettingPanel — fully compatible with WordPress collaborative editing.

Classic Editor

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.

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 @id references 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.txt directives 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 to https://www.gravatar.com/avatar/{hash}?d=404 via wp_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.5.0)

  • Download size: about 125 KB zipped.
  • Codebase: 31 PHP files, roughly 10,700 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 emitted, 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.

חינםבתוכניות בתשלום
להתחיל
בביצוע ההתקנה, אנחנו מקבלים את הסכמתך לתנאי השירות של WordPress.com ולתנאים של התוסף של הצד השלישי.
נבדקו עד
WordPress 7.0
תוסף זה זמין להורדה ולשימוש דרך שברשותך.
הורדה ושמירה