Visibility – Lightweight SEO, AEO and GEO for Search and AI icon
Actively maintained Tested with WP 7.1 #11 in ai seo

Visibility – Lightweight SEO, AEO and GEO for Search and AI

Lightweight Free WordPress SEO: meta tags, schema, Open Graph, redirects, robots, LLMS, MD, sitemap. No bloat, no tracking. Visible to search and AI.

Active installs700+100+ tier
Downloads · 30d4.5K▲ +2.7% vs prev. 30d
Rating5/57 reviews
Health score86/100Excellent
All-time downloads14.2KSince Jun 2026
Support resolved5 / 5100% in last 2 months
RequiresWP 6.1PHP 7.4+
Downloads · 7d664▼ -58.2% week over week
Our verdict

Safe pick

Yes — Visibility is a safe, well-maintained plugin to use in 2026. It runs on 700+ sites, is rated 5/5 and was last updated 21 hours ago, and scores 86/100 on our health check.

  • Actively developed — last update 21 hours ago
  • Tested with the latest WordPress (7.1)
  • Responsive support — 100% of recent threads resolved
  • Small user base (700+ active installs)

How does it stack up?

Side-by-side on installs, updates, ratings & support

Daily downloads

108217326Aug 20Oct 3Nov 17
Yesterday287
Daily average (1y)88
Peak day435Nov 9, 2026
Last 12 months14.4K

Download spikes usually follow a new release — each site that auto-updates counts as a download.

Rankings

Where Visibility stands today

WordPress.org search rankings

Live position in the plugin search, top 100
KeywordPositionCompeting pluginsCategory
ai seo #24 3,357 Best ai seo plugins →
noindex #11 961 Best noindex plugins →
redirects #63 8,122 Best redirects plugins →
schema #60 3,473 Best schema plugins →
sitemap #60 1,884 Best sitemap plugins →

Version adoption

Share of active sites per release.

  • 3.292.3%
  • Other7.7%

Rating breakdown

★★★★★★★★★★ 5 from 7 reviews

  • 5★100.0%
  • 4★0.00%
  • 3★0.00%
  • 2★0.00%
  • 1★0.00%

About Visibility

From the official readme · v3.2.5

Description

Visibility is the SEO essentials in one light plugin: meta tags, canonical URLs, Open Graph, schema, robots rules, redirects, a robots.txt editor, llms.txt, Markdown for AI agents and control of the native XML sitemap, in about 505 KB.

  • Free, all of it. No Pro version, no upsell banners, no account.
  • No tracking. Nothing phones home.
  • Light. Built on WordPress core APIs, with no database tables of its own and no cron jobs.
  • Easy to switch to. One-click import from Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, Slim SEO and SureRank.
  • Ready for AI search (AEO and GEO). Clean metadata, llms.txt and a Markdown version of every page, for ChatGPT, Perplexity, Gemini and other AI assistants to read and cite.

Four modules, switch on only what you need

Discover: meta tags, schema and AI discovery

  • Meta title and meta description, with templates and per-post and per-term overrides.
  • Canonical URLs on entries and on every listing.
  • Open Graph and Twitter Cards.
  • JSON-LD schema: Article, BreadcrumbList, Person, ProfilePage, FAQPage and Site Identity (Organization, LocalBusiness or Person). Choose the type per content type, or None to leave it to another plugin.
  • Author details (job title, topics and credentials), shown with the Author details block or the [visibility_author_details] shortcode. Each author can pick a page as their profile page.
  • AI discovery: llms.txt, llms-full.txt, a Markdown version of each page and a robots.txt editor with AI crawler rules.
  • Respect nosnippet: content set to nosnippet stays out of the llms.txt summaries, llms-full.txt, Markdown and FAQPage.
  • A filter for content that has not been updated in a while.

Indexing: noindex and clean URLs

  • noindex, nofollow, noimageindex and nosnippet, in bulk by content type and taxonomy or one by one.
  • Rules for search results, 404, date, paginated, attachment and author archives, and for RSS feeds.
  • Keep part of a page out of Google’s snippets with data-nosnippet, from the block editor or the classic editor.
  • Remove the base of any taxonomy, choose a WooCommerce product URL structure and redirect attachment pages to their parent, with 301 redirects from the old URLs.
  • Quick Edit, bulk actions and a Visibility column on your post and term lists.

Sitemaps: control of the native XML sitemap

  • Works on the sitemap WordPress already generates, instead of adding a second one.
  • Exclude post types, taxonomies, users, posts and terms. Noindexed content stays out automatically, and so does content whose canonical URL points to another address.
  • Add URLs of pages served outside WordPress.
  • lastmod dates, and 301 redirects from the sitemap URLs of your previous SEO plugin.
  • Keeps /wp-sitemap.xml answering 200 on a site with no blog posts, which older WordPress versions got wrong.

Redirects: 301, 302, 307 and 410

  • Managed from the admin: no .htaccess editing, no custom table, no 404 log.
  • CSV import and export.
  • A suggested redirect when you delete a post.
  • Take over the redirects WordPress creates when a slug changes.
  • Redirect chains answered in one hop, and loops refused.

Good to know

  • Per-post controls live in the Block Editor sidebar and in a Classic Editor meta box, with a live preview of your Google result, your social card and an AI answer.
  • The Tools tab groups the importers and exports your configuration as JSON for another site.
  • AI agents can read and edit the SEO of your posts and terms through the WordPress Abilities API, with the WordPress MCP Adapter, Novamira or any other client. EMCP Tools exposes the same fields over MCP while you edit a page in Elementor.
  • Multilingual: works with WPML and Polylang, with a folder or a domain per language.
  • Visibility replaces a full SEO plugin instead of running next to one, and warns you if another one is active.

Perfect companions

Visibility works on its own. These plugins pair well with it:

  • VigIA: see which AI crawlers visit your site. Both plugins share the Site Identity schema without duplicating it.
  • Share Buttons & AI-powered Summaries: share buttons for social networks and AI assistants.
  • AI Content Signals: tell AI systems how they may use your content (training, search or both) through robots.txt.
  • Vigilante: all-in-one WordPress security: firewall, login protection, security headers, 2FA and file integrity monitoring.

External services

This plugin connects to Gravatar (operated by Automattic Inc.) to check whether an author has a public avatar, so it can be used in Open Graph (og:image) and in Person schema (image).

  • What is sent: an MD5 hash of the author email, in a HEAD request to https://www.gravatar.com/avatar/{hash}?d=404. The email address itself is never sent.
  • When: on a single post or page with Open Graph on and no other image available (social image, featured image, WooCommerce gallery image or image in the content), and on an author archive with Person schema on.
  • How often: the result is cached for 24 hours, so later page loads do not contact Gravatar again.

It is the same lookup WordPress uses for comment avatars. 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 (3.0.0)

  • Download size: about 505 KB zipped.
  • Codebase: 51 PHP files, roughly 39,700 lines of PHP, plus 3,400 lines of JavaScript and 2,600 of CSS, loaded only where they are used.
  • On a page view: 26 PHP files, and no database query added to a post, a page or the home page of a default install.
  • No custom database tables. One option for the settings and native WordPress meta for per-post, per-term and per-author values.
  • No cron jobs.
  • No external HTTP calls, except the cached Gravatar check described above.
  • Built on WordPress core APIs (wp_robots, wp_sitemaps_*, register_post_meta, get_canonical_url, the Block Editor).

Measured against other SEO plugins

The same clean WordPress, the same theme and the same 30 posts, with one SEO plugin active at a time on its default settings. Each figure is what that plugin adds to WordPress with no SEO plugin. Measured in October 2026 on the current release of each one, on a single machine: what carries over to your site is the order, not the exact figure.

  • PHP files loaded on every page view: 26. SureRank 122, SEOPress 134, Rank Math 267, All in One SEO 303, Yoast SEO 588.
  • Database queries added to a post: none. SEOPress 1, Yoast SEO 3, SureRank 7, Rank Math 16, All in One SEO 32.
  • Server time added to every page view: about 2 ms. Yoast SEO 7, SEOPress 8, Rank Math 11, SureRank 12, All in One SEO 17.
  • JavaScript loaded in the editor: 41 KB. SEOPress 89 KB, Rank Math 1.4 MB, SureRank 1.9 MB, Yoast SEO 3.5 MB.
  • Download size: about 505 KB. SEOPress 2.8 MB, Rank Math 3.6 MB, Yoast SEO 4.9 MB, SureRank 6 MB, All in One SEO 7.3 MB.
  • Custom database tables and cron jobs: none. SureRank 0 and 1, SEOPress 1 and 0, Rank Math 6 and 4, Yoast SEO 6 and 6, All in One SEO 13 and 1.

Security

  • Every release passes a security audit of the changed code before it ships.
  • Small attack surface: no custom tables, no unauthenticated endpoints, escaped output, validated input and prepared database queries.
  • No telemetry and no data collection.

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.

Installation

  1. Upload the native-aeo-pack folder to /wp-content/plugins/ or install through the Plugins screen.
  2. Activate the plugin.
  3. Open Visibility in the admin sidebar to review the active modules and tune the defaults.
  4. Done. Meta tags, robots directives and sitemap filters are applied automatically based on your settings.

Changelog

Title templates reach the page title on sites built with Divi, and inline code in the Markdown version of a page keeps Polish, Cyrillic, Arabic, Japanese and emoji characters whole.

3.2.5

Title templates reach the page title on sites built with Divi, and inline code in the Markdown version of a page keeps Polish, Cyrillic, Arabic, Japanese and emoji characters whole.

  • Fix: Title templates did not reach the page title on sites built with Divi, which writes a title of its own even with its custom titles off. Where a template applies, a Divi site gets the same title as with any other theme, with the separator set in Visibility, and a title typed in Divi is kept. Reported by xavichamorro.
  • Fix: Characters whose UTF-8 encoding ends in the byte 0x85 (Polish ą, Cyrillic х, Arabic م, many Japanese characters, emoji such as ✅) were split inside inline code in the Markdown version of a page, which then was not valid UTF-8.
  • Fix: The help of the JSON-LD: FAQPage setting and the FAQ said Google retired FAQ rich results in 2023, when it only limited them to government and health sites. Google no longer shows them at all.

3.2.4

A site name of its own, apart from Site Identity, and WebSite markup on the home page even with Site Identity off. Redirects say who made them, follow your trailing slash and flag two hops. One rule for who counts as an author.

  • Improved: The site name has a field of its own, in a new Site name section of the Discover tab, apart from the name of the organization, business or person in Site Identity. It goes into the WebSite markup, into og:site_name on every page and into the titles of llms.txt and of the Markdown version of the blog. Left empty, it is the name of the organization or business, or the site title, never the name of a person. The title of the home page does not change.
  • Improved: The WebSite markup is written on the home page with Site Identity off too, since that is where Google reads the site name from, so sites without Site Identity get it after the update. It has its own switch for a theme or another plugin that already writes one. With VigIA, Visibility leaves it to VigIA only while its own Site Identity is off and VigIA writes one on the home page. When no page writes it, posts and author pages carry a minimal one.
  • Improved: Alternate names and site search are in the Site name section. The alternate names go on the organization as well when it has the same name as the site, never on a person.
  • Improved: For a person, the WebSite and llms.txt take the site tagline as their description, not the biography.
  • Improved: The import brings the site name and the alternate names from Yoast, AIOSEO and SEOPress, and the alternate names from Rank Math. The Website Name of Rank Math is named on the import card instead, because Rank Math copies the site title when it is installed. The identity of AIOSEO (organization or person, contact details, logo and profiles) is imported too.
  • Improved: Every redirect Visibility makes on the front end says so in an X-Redirect-By: Visibility header: the Redirects tab, old sitemap addresses, removed taxonomy bases, product URLs, Markdown, robots.txt and attachment pages. The hop WordPress adds says WordPress, so a chain shows who makes each hop.
  • Improved: Redirect targets get the trailing slash of the permalink structure when they are served, before any ? or #, and lose it when the structure has none. That covers redirects saved before, imported from a CSV or taken over from WordPress. External targets and files are left as they are.
  • Improved: A redirect whose target is an old address of an entry, which WordPress sends on with a second hop, has a mark in the list and a Convert button that takes over that WordPress redirect, so visitors get there in one hop. The mark appears too when the slug of the entry changes after the redirect was saved.
  • Improved: One rule for who counts as an author: anyone who can write posts or pages, or has a published post. The profile fields used to ask for the first and the author archive for the second. A former contributor whose posts are still published keeps their details on their archive and on their profile page, and can still edit them. To take them out of the structured data, empty the fields or reassign the posts. A role that only writes pages counts too.
  • Improved: The author profile warns when the job title, topics, credentials or profiles are in the structured data but have not been seen on the author archive or the profile page for 30 days, since Google asks that markup describe what readers can see. Only real views count, crawlers included, with at most one write a day.
  • Improved: Author details on profile pages, a new option in Discover, adds the Author details at the end of the profile page an author picked, unless the page already has the block or the shortcode. Off by default.
  • Fix: The WebSite markup took the name of the Site Identity entity, so a site whose identity is a person, often imported from Yoast, was named after them.
  • Fix: An address of the site itself in the Website field of a profile (the home page or an about page, with or without www) was given in sameAs as another profile of the person. It is left out, of the Author details as well.
  • Fix: A user created, or made an author, with a biography in the same save had no modified date on their profile page until the next change.

3.2.3

Import notices no longer come back after an import, and can be hidden card by card on the Tools tab. llms-full.txt and the Markdown versions leave forms out, indent nested lists and no longer drop text in brackets.

  • Improved: Import cards on the Tools tab can be hidden one by one. A hidden card folds into one line that still opens its list and its Import button, and the Overview notice follows the same choice. It comes back only when there is something new to import.
  • Improved: The Overview notice about SEO data you can import names what is left for each plugin, and points to Tools to import it or hide it.
  • Improved: The Tools tab shows what SEO plugins that are no longer running left in the options table, how much of it WordPress loads on every page view, and recommends removing it by hand after a backup. Visibility never deletes another plugin’s data.
  • Improved: Nested lists keep their levels in llms-full.txt, two spaces further in for each one, as in the Markdown version. Reported by Emilio Calvo.
  • Fix: Import notices came back after any import in which you later changed or cleared an imported value, because that value counts as pending again. They now show only what goes beyond what was offered when you imported or hid it. Reported by willtm.
  • Fix: Forms no longer reach llms-full.txt, the summaries of llms.txt or the Markdown versions. A contact form put its privacy notice, its consent label, its Send button and its success and error messages into them. Reported by Emilio Calvo.
  • Fix: Text in square brackets with an equals sign or a link inside, such as [Note that 2+2=4], was taken for a page builder leftover and removed from llms-full.txt and the Markdown versions.
  • Fix: A copy of llms.txt or llms-full.txt built while a change was emptying it holds the content from before that change, and a cache in front of the site could keep it for an hour. That copy now goes out with no-store.
  • Fix: Empty lock files of llms.txt and llms-full.txt that nothing uses any more, like those left by versions before 3.2.1, are removed from the uploads folder after a week.

3.2.2

Fixes llms-full.txt on sites built with Divi 5, which listed their pages with no text, and stops caches in front of the site from showing the Markdown version of a page to visitors.

  • Fix: llms-full.txt listed the pages built with Divi 5 with their title and address but no text, and their summary in llms.txt and the description of their Markdown version were empty. Divi 5 keeps the text of each module in the settings of its block, where only a render finds it, so Visibility now renders those pages, as it already did for the shortcodes of other page builders and for the Markdown version, and with the same rules: the cart, the checkout and My Account are never rendered, and for a visitor with cookies the document is built for that visitor alone. The same goes for the blocks of any builder that renders its own. Reported by alfonsobb.
  • Fix: When rendering a page gives no text, llms.txt and llms-full.txt are no longer built again for every request with cookies or with extra parameters in the address, as if the page had been rendered.
  • Fix: The Markdown version that an AI agent gets at the address of a page itself, by asking for text/markdown, went out as public for an hour. A cache in front of the site that does not keep apart what each request accepts (the dynamic cache of SiteGround, Cloudflare) kept it and showed it to the people who opened the page next. It now goes out as private, for the agent alone. The .md addresses and llms.txt stay public: they answer with nothing else. VigIA gets the same fix.
  • Fix: With Polylang, every language in its folder and the default language not hidden, /index.md at the site root, and the Markdown version of the posts page asked for without its language, answer in the language of the visitor’s cookie or browser, as llms.txt does, and now say so in a Vary header, so a cache keeps one copy per language.

3.2.1

Fixes llms-full.txt on sites built with page builders, adds the llms.txt exclusion to the editors, refreshes the AI documents when the URL format changes and warns when the server sends llms.txt without UTF-8. Your robots.txt rules now come first.

  • Improved: The llms.txt exclusion of an entry is now a checkbox in the editors too, in the Visibility box of the classic editor and in the Indexing tab of the block editor panel. It keeps the entry out of llms.txt and llms-full.txt and serves no Markdown version of it, as the list on the settings screen does. Ticking it takes the entry off the list of entries always included. Suggested by Emilio Calvo.
  • Improved: robots.txt shows Visibility’s rules before those of WordPress and other plugins, in the file it serves, in the physical file and in the preview. Crawlers read it the same way: it is only easier to see what the site decided. Suggested by Emilio Calvo.
  • Improved: With WPML or Polylang, the URL patterns kept out of llms.txt can be translated, so each language has its own list. Suggested by Emilio Calvo.
  • Improved: With the physical llms.txt option on, the settings screen warns when the web server sends the file without saying it is UTF-8, which makes browsers and some AI tools show accented letters as odd symbols although the file is correct. Visibility asks the server once for each new copy of the file.
  • Improved: The note that Site Identity is off, under the import table, also says that its name and description are already the title and summary of llms.txt and of the Markdown version of the blog.
  • Fix: llms-full.txt listed the pages built with the shortcodes of a page builder (Avada, WPBakery and the like) with their title and address but no text, and their summary in llms.txt was empty. When taking the shortcodes out leaves nothing, Visibility now renders the page, as it already did for its Markdown version. The cart, the checkout and My Account are never rendered. When a page has to be rendered for a visitor with cookies, logged in or with extra parameters in the address, the document is built for that visitor alone and not stored, and a request that does not just read it (a form sent to it) gets a 405, as with the Markdown versions. Reported by Emilio Calvo.
  • Fix: The tags of a page builder whose shortcodes are not loaded when llms-full.txt is built (Divi’s builder) appeared around the text. They are taken out and the text stays. The Markdown versions, which already did this, no longer take out a note in brackets that starts with a word.
  • Fix: llms.txt, llms-full.txt and the Markdown versions kept the old addresses for up to 12 hours after a change of the permalink structure, the category or tag base, the WooCommerce product base, or the URL format of WPML or Polylang (folders, domains, the default language). They are emptied when any of those changes. With the Markdown versions off, changing the posts page did not refresh llms.txt either. Reported by Andrés, from WPML.
  • Fix: In llms-full.txt and in the summaries of llms.txt, a heading or a paragraph right after loose text was glued to it (Price: 20 €Shipping). A list item that wraps its text in a paragraph keeps its bullet.
  • Fix: On a multisite network with folders, a site with a domain of its own could be served the physical robots.txt and llms.txt of the main site. Visibility no longer writes those files on such a network. On a network, turning the physical files on or off, and changing the robots.txt rules while there is a physical robots.txt, now take a network administrator, since those files sit in the folder every site shares.
  • Fix: When another plugin had already set a cookie in the response, a shared cache could keep llms.txt, llms-full.txt or a Markdown version together with that cookie. They now go out as private in that case.
  • Fix: With Polylang and every language in its folder, /llms.txt answers in the language of the visitor’s cookie or browser, and now says so in a Vary header, so a cache keeps one copy per language.
  • Fix: Unticking the llms.txt exclusion through an import of the Tools tab left an empty value that still kept the entry out of llms.txt and llms-full.txt. The update clears those values once.
  • Fix: Deleting the plugin left its block in a physical robots.txt or .htaccess saved with Windows line endings, and taking the block out of robots.txt could join the lines around it.
  • Fix: The copies of llms.txt and llms-full.txt under uploads are handled more safely: a copy that could not be deleted no longer passes for current, one built during a change no longer survives it, two installs that share the uploads folder no longer share copies, and the copy in the site root is taken away when a change arrives while it is being written. Importing many strings in WPML String Translation empties the documents once, not once per string.

3.2.0

Works with WPML and Polylang, with a folder or a domain per language: SEO fields and settings translate, each language gets its own llms.txt, Markdown and og:locale, and the sitemap covers every language. With a folder per language, a redirect now applies only to its own language.

  • New: Compatibility with WPML and Polylang, through a wpml-config.xml that Polylang reads too. The Meta title, Meta description, social title and social description of each entry are translated with it. The robots, sitemap and llms.txt choices are shared by every translation of an entry, and the Canonical URL is not, so each translation keeps its own address. The title templates, the home page description and the Site Identity texts are translated in WPML String Translation or in Polylang Strings translations, and the page chosen for the identity, the fallback social image and the logo follow their translations.
  • New: The sitemap of the default language lists the sub-sitemaps of every language when WPML uses a folder per language, as Polylang already did, so the address in robots.txt covers them all. With one domain per language, each domain keeps its own sitemap and robots.txt. There is no hreflang in the sitemap: WPML and Polylang print it in the page head.
  • Improved: Each language gets its own llms.txt, llms-full.txt and Markdown versions, in its language and with its links, at /en/llms.txt or on its own domain. With the physical file option on, the llms.txt in the site root is the default language’s.
  • Improved: og:locale, inLanguage and the lang of the Markdown versions follow the language of the page.
  • Improved: The description of llms-full.txt in the Optional section of llms.txt and the title of llms-full.txt are translatable.
  • Fix: With WPML, the title templates, the home page description and the Site Identity texts translated in String Translation were not used, and every language showed the default language’s. The settings were read before WPML could translate them.
  • Fix: With WPML and a folder per language, a redirect for /old-page also fired on /en/old-page and sent the visitor to the default language’s target, and a redirect written as /en/old-page never matched. A redirect now applies to the exact path it is written for: add one per language. With one domain per language a redirect holds for every domain, and a relative target goes to the domain asked for.
  • Fix: With WPML or Polylang and the category base removed, the categories of the languages other than the one that rebuilt the permalinks answered 404 at their address without the base.
  • Fix: With Polylang, /en/llms.txt, /en/llms-full.txt and /en/index.md answered 404, and the canonical, the Markdown link and the llms.txt link of the other languages’ home pages pointed to the default language. With one domain per language, the Markdown version of each entry, its link in llms.txt and a relative redirect pointed to the default domain.
  • Fix: The Markdown version of the blog was kept once for every language, so /en/index.md could answer with the default language’s listing.
  • Fix: With Polylang, the sitemap index entries of each language had no lastmod, and the additional URLs were listed once per language.
  • Fix: With a persistent object cache (Redis, Memcached) on a site with several languages, the lists of what stays out of the sitemap were kept without their language: the first language requested gave its list to the others, and what had been left out there could come back.
  • Fix: og:locale was a bare language on some sites (es on Spanish ones), which Open Graph does not accept. It is now language and territory (es_ES).
  • Fix: The Markdown version of an entry whose address has accents in its base (/artículos/) answered 404, and an address that matches nothing was looked up twice.
  • Fix: On a site installed in a subfolder, the address of the Markdown versions in the page head and in llms.txt repeated the folder (/blog/blog/post.md).
  • Fix: Turning off “Write to the physical robots.txt” did not remove the robots.txt Visibility had created in the site root: it kept writing its rules into it, and deactivating the plugin left the rest of the file behind. The server kept serving that file instead of the virtual robots.txt, and with one domain per language every domain got the Sitemap line of one of them. Visibility now deletes the file it created, as long as nothing else was added to it. A file created by an earlier version is not recognised: delete it by hand.
  • Fix: In a physical robots.txt with Windows line endings, Visibility added its block a second time instead of updating it, and could not remove it on deactivation. The file is now written with Unix line endings.
  • Fix: With WPML or Polylang, saving the translation of the site title, the tagline or a Visibility text did not refresh llms.txt, llms-full.txt or the Markdown version of the blog, which kept the old text for up to 12 hours.
  • Fix: With WPML, a robots, sitemap or llms.txt choice of an entry set in the block editor, in Visibility’s lists, with a bulk action or through the Abilities stayed on that one language, and one changed on a translation in the classic editor was undone on saving, because WPML copies these choices only from the original and only when it is saved. A choice now applies to every translation of the entry, whichever language it was made in, as it already did with Polylang. Saving an entry in the editor or Quick Edit shares only what changed in that save, so choices that already differ between languages stay as they are until changed.

For older changelog entries, please check the changelog.txt file

Full changelog on WordPress.org →

Screenshots

Overview tab — the four modules, on or off.
Overview tab — the four modules, on or off.
Discover tab — meta tags, Open Graph and schema, with the section navigation of the tab on the left.
Discover tab — meta tags, Open Graph and schema, with the section navigation of the tab…
Indexing tab — noindex and nofollow in bulk, by content type and taxonomy.
Indexing tab — noindex and nofollow in bulk, by content type and taxonomy.
Sitemaps tab — what goes into the sitemap and what stays out.
Sitemaps tab — what goes into the sitemap and what stays out.
Post list — the Visibility column and Quick Edit.
Post list — the Visibility column and Quick Edit.
Redirects tab — 301, 302, 307 and 410, with CSV import and export.
Redirects tab — 301, 302, 307 and 410, with CSV import and export.
Editor — the entry as a Google result, a social card and an AI Overview, live as you type.
Editor — the entry as a Google result, a social card and an AI Overview, live as you type.
Tools tab — importers from other SEO plugins, and configuration export.
Tools tab — importers from other SEO plugins, and configuration export.

For developers

Is this your plugin? Show off the numbers.

Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.

Active installs badge Rating badge Health score badge

Best Visibility alternatives

All ai seo plugins →
Alternatives
Rank Plugin Active installs Rating Updated Health
1 SEOPress – AI SEO Plugin & On-site SEO SEOPress – AI SEO Plugin & On-site SEO WordPress SEO plugin with AI SEO metadata, schema, XML sitemap, redirections & Search… by Benjamin Denis 300K+ ★★★★★★★★★★ 4.8 (1.3K) 3 weeks ago 96
2 GetGenie – AI SEO Assistant & Content Writer with Keyword Research, AEO & GEO GetGenie AI powered SEO assistant & content writer with 40+ templates, chatbot, NLP keyword… by Roxnor 70K+ ★★★★★★★★★★ 4.8 (120) 2 months ago 90
3 CrawlWP SEO – Complete WordPress SEO Plugin with AI, Indexing & Search Performance CrawlWP SEO Complete WordPress SEO: meta titles, schema, redirects and sitemaps, plus instant indexing… by properfraction 30K+ ★★★★★★★★★★ 4.7 (62) 1 month ago 90
4 BeyondSEO – AI SEO to Improve Rankings, Listings & Online Visibility BeyondSEO Grow your traffic with AI-powered SEO, local listings, review management, social media &… by rankingCoach 20K+ ★★★★★★★★★★ 4 (4) 1 week ago 66
5 ThinkRank SEO – AI SEO Plugin for SEO & Google Search Console ThinkRank SEO AI SEO plugin for WordPress SEO: AI SEO tools, Google Search Console, meta descriptions… by WPDeveloper 20K+ ★★★★★★★★★★ 4.9 (38) 3 days ago 94
6 Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibility Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibility AI powered meta, clustering, content, schema & rank tracking, plus an AI website builder -… by Xagio SEO 10K+ ★★★★★★★★★★ 4.9 (51) 23 hours ago 90
7 Search Atlas SEO – OTTO AI SEO Automation for WordPress Search Atlas SEO – OTTO AI SEO Automation for WordPress AI-powered SEO & GEO for WordPress: OTTO auto-optimizes meta, schema & content, and helps… by Search Atlas Group 6K+ ★★★★★★★★★★ 3.3 (24) 17 hours ago 81
8 WPBot – AI ChatBot for WordPress & Growth Suite: SEO, AI Writer, Email Marketing, Social Media WPBot AI ChatBot for Support, Leads and Sales, with AI SEO, AI Writer, Email Marketing, Social… by QuantumCloud 5K+ ★★★★★★★★★★ 4.7 (124) 20 hours ago 92
9 LovedByAI – AI SEO, GEO & AEO for ChatGPT and AI Search, Agentic WooCommerce (ACP, UCP) & WebMCP LovedByAI Get cited by ChatGPT, Perplexity, Gemini and AI Overviews. Schema, FAQs, llms.txt, AI… by LovedByAI 1K+ ★★★★★★★★★★ 4.4 (5) 1 day ago 84
10 LLM Bot Tracker – AI Crawler Detection & Analytics LLM Bot Tracker – AI Crawler Detection & Analytics Automatically track ChatGPT, Claude, Perplexity & 56 AI bots crawling your WordPress site… by Hueston 1K+ ★★★★★★★★★★ 3 (2) 1 year ago 26

FAQ

Visibility: quick answers

Straight answers, pulled from live WordPress.org data.

Live data from WordPress.org · checked Nov 18, 2026

Is Visibility free?

Yes. Visibility is free to download and use from the official WordPress.org plugin directory.

Is Visibility safe to use in 2026?

Yes — Visibility is a safe, well-maintained plugin to use in 2026. It runs on 700+ sites, is rated 5/5 and was last updated 21 hours ago, and scores 86/100 on our health check.

How many websites use Visibility?

Visibility is active on 700+ WordPress websites and has been downloaded 14,233 times since it launched in June 2026. It was downloaded 4,520 times in the last 30 days.

Does Visibility work with WordPress 7.1?

Yes. The developer has tested Visibility up to WordPress 7.1.4, the latest release. It requires WordPress 6.1 or newer.

What PHP version does Visibility need?

Visibility requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.

When was Visibility last updated?

The latest version, 3.2.5, was released on November 17, 2026 (21 hours ago).

Who makes Visibility?

Visibility is developed and maintained by Fernando Tellado.

What are the best alternatives to Visibility?

The most popular alternatives to Visibility are SEOPress (300K+ installs), GetGenie (70K+ installs) and CrawlWP SEO (30K+ installs).

Powered by PageForge

Want thousands of pages that rank like these? Build them in an afternoon.

This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.

  • CSV, Google Sheets & API data sources
  • AI content, schema & internal links per page
  • Works with Elementor, Gutenberg, Yoast & Rank Math
  • Free on WordPress.org — no credit card
Sarah is here to help!
Hi there! 👋 Need help finding what you're looking for?
Sarah
Sarah
Online & Ready to Help
Hi there! 👋 Need help finding what you're looking for?

We'll use this to continue our conversation

Just now ✓ Verified

Join 500+ SEO Pros Scaling Their Strategy

Get exclusive programmatic SEO tactics, AI content workflows, and the latest PageForge updates delivered straight to your inbox. Stay ahead of the algorithm.

We care about your data in our privacy policy.