Migrating to the Visibility SEO WordPress Plugin

When you switch WordPress plugins for search engine optimization (SEO), you move settings that tell search engines and social networks how to interpret your pages. Visibility – Lightweight SEO, AEO and GEO for Search and AI imports many settings from supported plugins, but you still need to check the pages and search-related files visitors and crawlers receive.

Visibility also includes answer-engine optimization (AEO) and generative-engine optimization (GEO), features that help answer-generating tools interpret site information. Those features do not guarantee search rankings or AI citations. During the migration, keep one plugin responsible for search-related output. Check that the imported settings work on the live site, then monitor whether search engines index your pages. Visibility’s WordPress.org listing documents the supported imports and their limits.

Prepare the site before importing

First, make a backup you can restore. Then record the current settings for sample content from each type on your site: posts, pages, categories or tags, and products if the site uses WooCommerce. For each sample, note its title, meta description, canonical URL, indexing directives, social preview image, and any custom schema or title template.

A canonical URL tells search engines which address to treat as the preferred version of a page when similar versions exist. An indexing directive such as noindex tells search engines not to show a page in results. Open Graph metadata supplies information that social networks use to build link previews. These values can look correct in a plugin dashboard even when the page’s HTML, the code delivered to visitors and search crawlers, says something different. Save a copy of the page source for important URLs if you can.

Also record the sitemap URL, which points to a file listing pages on your site. Record important robots.txt rules and redirects too. A redirect sends a visitor or crawler from one URL to another. Changing SEO plugins does not by itself change page URLs or make the transition a site move. If you are changing URL structures at the same time, test those redirects and canonical URLs as a separate migration task.

Import the settings into Visibility

Install and activate Visibility, then open its Tools tab and review the import card before starting. The documented import sources are Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, Slim SEO, and SureRank. Visibility also supports redirect imports from Rank Math, All in One SEO, SEOPress, and the Redirection plugin.

The importer covers many common settings, including page titles and category or tag titles, descriptions, canonical URLs, robots rules, social metadata, schema types, verification codes, and title templates. It also imports some details about the site’s identity, such as its organization or business type, name, logo, and social profiles. The exact fields available depend on the source plugin.

If more than one SEO plugin has stored data, Visibility says it selects the active plugin first, then an installed plugin, then the plugin configured most recently. Review the import card’s summary of each setting so you know which source plugin supplied it. Keep the previous plugin installed while you inspect and import its data. Visibility says repeat imports preserve existing Visibility values and avoid duplicate imports, and that the importer does not delete data from the source plugin.

Check the live output before deactivating the old plugin

After importing, compare the saved settings with what Visibility shows for each sample page. Then view the page as a logged-out visitor and inspect its HTML. Confirm that the title, description, canonical URL, indexing directives, social metadata, and structured data match your intended settings. Structured data, also called schema, is machine-readable information about a page or organization.

Check at least one page from each content type that uses different SEO settings. Pay particular attention to title templates: Visibility converts supported variables, but variables that depend on custom fields or dates remain unchanged. If a title shows a variable as text instead of a finished value, edit the template or set the title directly.

Look for duplicate metadata and schema as well. Visibility is designed to replace a full SEO plugin, so do not run it alongside another full SEO plugin. A theme, page builder, or another plugin can also add tags, so inspect the page source before deciding which component produced duplicates. Once representative pages show the intended output, deactivate the previous SEO plugin and check the same pages again.

Then verify the live sitemap, robots.txt, and important redirects. Visibility describes its sitemap feature as a customization of WordPress’s native sitemap. Check the live sitemap URL and the pages it lists. Do not assume the old plugin’s sitemap URL still applies. Also confirm that no robots.txt rule blocks a page that relies on noindex: Google needs to crawl a page to see that directive, as its documentation on robots meta tags explains.

Check feature gaps and AI-search claims

The importer transfers settings it supports, but it does not transfer every feature or way of working from the previous plugin. Visibility does not provide keyword analysis or content scoring. Its documentation also identifies limits for template variables that rely on custom fields or dates. Before switching, list any other features you use in the old plugin and confirm that Visibility or another tool covers them.

Visibility offers AI-discovery features, including controls for named AI crawlers. It also provides llms.txt and Markdown versions of pages. These outputs are optional, and their availability does not establish that an AI service will crawl or cite a site. Google says its existing SEO guidance applies to AI features in Search and that site owners do not need special AI files or schema for eligibility. Google also says eligibility does not guarantee that it will crawl, index, or show a page in an AI feature, according to its guidance for AI features.

Treat those features as additional ways to publish site information, not as a substitute for accurate content, accessible pages, and sound technical SEO. Likewise, the performance comparisons on the plugin listing are developer-reported results from a specific test setup. They do not establish the speed change your site will experience.

Monitor indexing after the switch

Use Google Search Console to review sitemap reporting and indexing for important pages after the change. If a page disappears from search or has an unexpected indexing status, check its live canonical URL and robots directives. Also check the redirect destination and sitemap entry. Google’s site-move guidance covers URL changes. A plugin switch with unchanged URLs does not automatically call for a site-move procedure. The checks remain useful if the switch changes search-related output.

Visibility’s importer does not remove the old plugin’s stored data. Deactivation stops that plugin from running, but it does not mean its settings have been erased. Keep the backup until you have verified the live output and indexing. Remove leftover data only after confirming what it belongs to and preserving a restorable copy.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com