Switching to Visibility from Other WordPress SEO Plugins

When you switch SEO plugins in WordPress, you need to move settings such as page titles, descriptions, and canonical URLs. A canonical URL tells search engines which version of a page to treat as the main one. Indexing rules tell search engines whether to include a page in search results. Visibility, the WordPress.org plugin listed as “Visibility – Lightweight SEO, AEO and GEO for Search and AI,” can import data from several other SEO plugins. After importing, check what moved and what visitors and search engines see.

To switch safely, back up your site first. Then review the importer’s results and compare important pages before and after the switch. Check redirects and sitemap behavior before you deactivate the old plugin. Visibility covers core SEO settings, but it does not include keyword analysis or content scoring. Its AI-related files have no established benefit for rankings or citations.

Check whether Visibility fits your needs

Visibility’s importer supports Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, Slim SEO, and SureRank. It can find and import titles, meta descriptions, canonical URLs, indexing rules, social metadata, some schema types, and title templates. Meta descriptions summarize a page for search results. Social metadata supplies information about a page to social platforms. The plugin listing names the supported plugins and the kinds of data the importer can transfer.

The importer does not transfer every feature of every plugin. Visibility says it does not provide keyword analysis or content scoring, so sites that rely on those tools need a replacement editorial workflow or a reason to keep using their current plugin. Visibility is not intended to run alongside another SEO plugin.

Check schema needs as well. Structured data is code that describes page content to search engines. Visibility lists support for Article, BreadcrumbList, Person/ProfilePage, FAQPage, WebSite, and Site Identity schema. It does not add Recipe, Product, Event, or HowTo schema; the plugin says WooCommerce supplies Product schema. If your old plugin outputs a specialized schema type, identify which plugin or feature will provide it after the switch.

Move the data, then check the live pages

Start with a site and database backup. Then record a few representative URLs so you can compare their output before and after the switch: the homepage and a post with custom SEO fields. Add an archive page. Include a page with a custom canonical and one that should not appear in search results.

Install and activate Visibility, open Tools, and review the values the importer found before you import them. If you have installed or configured several SEO plugins, check which plugin’s values Visibility will use. Visibility says it prioritizes the active plugin. Next in the order is an installed plugin, followed by the plugin set up last. Check the imported values, especially on pages with custom settings. The importer leaves the old plugin’s data in place and is described as safe to run again. Keep a backup in case your site behaves differently than expected.

For each sample URL, inspect the fields in the WordPress editor and the output sent to browsers and search crawlers. Check the title and description, canonical URL, and indexing instructions such as noindex. Also inspect social metadata and structured data. If both plugins are active during testing, look for tags that appear twice or conflict. After you review the output, deactivate the old SEO plugin. Visibility says it is not designed to run alongside another SEO plugin.

Treat redirects and sitemaps as separate checks

A redirect sends a visitor or crawler from one URL to another. Visibility lists redirect imports from Rank Math, All in One SEO, SEOPress, and the separate Redirection plugin. It does not list every supported SEO plugin as a redirect source, so check your existing redirect rules rather than assuming they came across with your metadata.

Pay particular attention to permanent redirects for URLs that have moved. Google’s technical SEO guidance distinguishes permanent moves from temporary ones and recommends redirects when a page has permanently changed address. After switching, test important old URLs and confirm they reach the intended live pages.

An XML sitemap is a file that lists URLs on your site. Visibility says it manages WordPress’s native XML sitemap instead of adding a second sitemap. Its listing also describes redirects from sitemap URLs used by previous SEO plugins. After switching, open your site’s sitemap and check that important pages appear and excluded pages do not. Also check the sitemap reference in robots.txt. A sitemap helps Google discover and prioritize URLs, but Google can crawl URLs that the sitemap does not list.

Set realistic expectations for AI features

Visibility creates llms.txt, llms-full.txt, and Markdown versions of pages. It also offers settings for AI crawlers in robots.txt. These files and pages present site content in formats that software can read. The plugin calls llms.txt a proposed convention and says Google ignores it. It also notes that no major AI vendor has confirmed support. The plugin also says no SEO plugin can promise an AI citation.

Treat these files as optional. They are not a proven way to improve rankings or make an AI service more likely to cite your site. During the switch, keep useful page content, correct canonical URLs and indexing settings, working redirects, and a functioning sitemap.

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