VisibleGen SEO, GEO & AEO

Сүрөттөө

Search is changing. People still find you on Google, but more and more of them ask AI assistants like ChatGPT, Claude, Gemini and Perplexity. VisibleGen helps your WordPress site do well in all of them: classic search engine optimization (SEO), generative engine optimization (GEO) for AI assistants, and answer engine optimization (AEO) for direct answers, featured snippets and AI Overviews.

Every feature below is free, runs on your own site and works on unlimited pages.

GEO: get found and cited by AI assistants

• llms.txt generator: an automatic, always-current /llms.txt that lists your key pages for AI systems, with noindexed content left out
• AI crawler control: allow or block each AI bot (OpenAI, Anthropic, Google, Perplexity, Apple, Meta and more), with one-click presets such as “allow AI search, block AI training”
• GEO content checks: live advice in the editor on what makes content easy for AI assistants to quote: a direct answer at the top, question-style headings, a Key Takeaways summary, specific facts and figures, and lists or tables

On-page SEO

• SEO title and meta description per post, page and product
• Title templates with variables (%title%, %sitename%, %tagline%, %sep%, %page%)
• Canonical URL and index / noindex per post, plus noindex per post type
• Advanced robots per post: nofollow, noarchive, nosnippet, noimageindex, indexifembedded and max-snippet
• CSV bulk edit: export SEO fields, edit them in a spreadsheet, import with a preview of every change
• Table of contents block: automatic jump links from your headings (H2 to H4), numbered or bulleted, optionally collapsible
• Live content analysis with a focus keyword, plural-aware matching and a score

Structured data (schema)

• Organization or Person, WebSite, WebPage and BreadcrumbList
• Article for posts
• FAQ block with FAQPage schema
• WooCommerce Product schema with price, availability, SKU, GTIN, brand and reviews

Social

• Open Graph and X (Twitter) card tags with image fallbacks
• Custom social image per page

Sitemaps

• Extends the WordPress XML sitemap: leaves out noindexed content, adds last-modified dates, removes thin author sitemaps
• /sitemap.xml redirects to the sitemap index
• Leave out single pages, whole content types or taxonomies

Technical SEO

• robots.txt editor with checks before saving and a “test a URL” tool
• Custom 404 page that keeps a real 404 status
• Site health checks: real 404 status, HTTPS, one site address (www or not), trailing slashes, robots.txt and sitemap
• Optional redirect of uppercase URLs to lowercase
• Header and body code (analytics, tag managers, verification tags) with a check that blocks broken tags

AI agents (MCP)

• Optional: lets AI assistants read and update SEO fields, find pages needing work, manage redirects, review 404s and run site health, through the WordPress Abilities API and the MCP Adapter plugin. Agents can only do what the WordPress user they sign in as may do.

Redirects and 404 monitoring

• 301, 302, 307, 308 and 410 redirects, for exact addresses or regex patterns (with $1 replacements)
• Patterns must pass a test before saving, including a check that they don’t catch your existing pages
• Optional active dates: start or stop a redirect on a schedule
• No chains or loops: redirects always point straight to the final page
• 404 log with suggested matching pages and one-click redirects
• Link scan: update links that point to redirected addresses, and find broken internal links
• Automatic redirect when you change a published post’s URL

Switch from another SEO plugin

• Import titles, descriptions, canonical URLs, index settings and focus keywords from Yoast SEO, Rank Math and All in One SEO
• The other plugin’s data is never changed, so you can switch back at any time
• While another SEO plugin is active, VisibleGen outputs nothing in the page head and leaves llms.txt to that plugin, to avoid duplicates

External services

This plugin can optionally connect to the VisibleGen service (https://wp.visiblegen.com, API at https://wp-api.visiblegen.com), run by One Network Solutions Limited. Connecting is only needed for account features such as AI tools, keyword data, rank tracking, Google Search Console and Google Analytics. All other features work without it. VisibleGen terms: https://visiblegen.com/terms · Privacy policy: https://visiblegen.com/privacy

Nothing is sent to VisibleGen until an administrator clicks “Connect to VisibleGen” on the VisibleGen > Account screen.

• When you connect: the site address, site name, WordPress version and plugin version are sent to VisibleGen to create the connection.
• While connected: when an administrator opens the VisibleGen > Account screen, the plugin checks the connection status and credit balance with VisibleGen. When a post editor opens, it loads the current AI tool prices (at most once an hour).
• When you use a VisibleGen AI tool (Optimize, FAQ, Key takeaways or Social posts): the post’s title, text and focus keyword (and, for Optimize, its SEO title and meta description) are sent to VisibleGen. VisibleGen uses Anthropic’s Claude (https://www.anthropic.com/) to generate suggestions and does not use your content to train models. Anthropic terms: https://www.anthropic.com/legal/commercial-terms · Privacy: https://www.anthropic.com/legal/privacy
• When you connect Google Search Console (optional, from the VisibleGen dashboard): you sign in with Google and allow read-only access to Search Console data. The Google authorization is stored encrypted by VisibleGen, not on your site. VisibleGen reads clicks, impressions, average position and top queries and pages for your site and shows them on the VisibleGen dashboard; it never changes anything in Search Console. Disconnecting revokes the access and deletes it from VisibleGen. Google privacy policy: https://policies.google.com/privacy
• When you click “Keyword data” in the VisibleGen Analysis box: the focus keyword and your chosen keyword market (country and language) are sent to VisibleGen, which gets search volume, keyword difficulty, CPC, search intent and related keywords from DataForSEO (https://dataforseo.com/). Results may be cached by VisibleGen for up to 30 days. DataForSEO privacy policy: https://dataforseo.com/privacy-policy
• When you track keywords (VisibleGen > Rank Tracker, paid plans): each tracked keyword, its device, tag and target page, your keyword market and your site address are sent to VisibleGen, which checks Google results (including AI Overviews) for them once a week through DataForSEO and stores the position history for your site.
• When you use “Discover keywords” or auto-sync: your site address and keyword market are sent to VisibleGen, which reads your site’s top search queries from Google Search Console (if you connected it) and keywords your site ranks for from DataForSEO.
• When you connect Google Analytics (VisibleGen dashboard, optional): you sign in with Google and allow read-only access to Google Analytics. VisibleGen stores the access tokens encrypted and reads a 28-day summary of the matching GA4 property (sessions, users, engagement, key events, top pages, traffic sources including AI assistants). The summary is cached by VisibleGen for up to 6 hours and on your site for up to 3 hours. Disconnecting deletes the tokens. Google privacy policy: https://policies.google.com/privacy
• Key renewal (every 12 hours while connected): the plugin asks VisibleGen for a one-time value and serves it at your site’s REST API path /visiblegen/v1/challenge; VisibleGen fetches it from your site’s address to confirm the site still controls that address, then issues a new access key. No content is sent.
• Once a day while connected: the names and versions of the VisibleGen plugins active on the site, and the WordPress version.
• AI Troubleshooter (VisibleGen > Support): your questions and the conversation so far are sent to VisibleGen, which uses Anthropic’s Claude to answer. Only if you tick “Share diagnostics”, the plugin also sends: WordPress, PHP and theme versions, site language, whether it is a multisite, the names and versions of active plugins, VisibleGen plugin versions, the connection status and recent VisibleGen connection errors. With diagnostics shared, the assistant can also run read-only checks on your site (connection and key status, whether the key renewal path is reachable, scheduled tasks, search engine visibility, permalinks and whether the sitemap, robots.txt and llms.txt load); their results are sent to VisibleGen and Anthropic in the same way. It can propose fixes from a fixed list (such as re-creating scheduled tasks or refreshing permalinks), which only run when an administrator clicks Apply and are recorded on the Support screen. VisibleGen does not store the conversation text.
• Support tickets (VisibleGen > Support): your email address, subject, messages and the plugin concerned (and the diagnostics above, only if you tick the box) are stored by VisibleGen. Our support team answers in the ticket, which you read and reply to on the same screen; VisibleGen emails you a short note when there is a reply. The plugin loads your site’s tickets from VisibleGen when you open the Support screen. To translate messages between your language and our team’s, and to help our team find the cause of a problem, VisibleGen may send your ticket messages, together with facts about your site’s connection to VisibleGen (such as connection status, plugin versions and recent errors), to Anthropic’s Claude.
• Moving a site from another VisibleGen account: when you connect a site that another VisibleGen account already uses, VisibleGen emails that account’s owner to approve the move, without telling them who asked.
• When you disconnect: the plugin asks VisibleGen to revoke the site’s access key, then deletes it from your site.

The access key is stored encrypted in your WordPress database.

Terms of service: https://visiblegen.com/terms
Privacy policy: https://visiblegen.com/privacy

Privacy

VisibleGen does not track users. It only contacts an external service if you choose to connect a VisibleGen account (see External services above). The 404 log stores the requested path and referring URL of missing pages on your own server; it does not store IP addresses. AI crawler rules are written to your site’s robots.txt.