Title: Modern SEO Plugin ? Last modified: July 21, 2026 --- # Modern SEO Plugin ? * Resolved [akgt](https://wordpress.org/support/users/akgt/) * (@akgt) * [2 weeks, 6 days ago](https://wordpress.org/support/topic/modern-seo-plugin/) * Hi Fernando, * Your ecosystem (Visibility, VigIA, and VulgatAI) offers one of the cleanest technical architectures in WordPress. Splitting front-end emission (Visibility) from admin observation (VigIA) and AI generation (VulgatAI) is brilliant—it proves sites can handle modern SEO and AI discovery (`llms.txt`, `.md` endpoints) without custom database tables or background CRON bloat. * I would like to completely replace Rank Math Pro across my client sites, but I’ve encountered a major real-world hurdle: **non-technical authors and clients panic when drafting content without visual editor guardrails and automated safety checks.** * Visibility handles front-end execution flawlessly, but authors work blind inside the editor. To make your stack the undisputed replacement for Rank Math Pro, we don’t need gamified “0–100 scores.” We need **local browser guardrails** and** one-click auto-improvements** that prevent client errors before publishing. * **My Question:** * Is expanding client-side JavaScript guardrails and automated workflow helpers across your 3-plugin roadmap something you would consider? * By combining pure browser JS in the editor with native WP hooks, you can offer 100% editor confidence with **0% server tax and 0% database bloat**: * **1. Visibility (Real-Time Editor Panel & Media Automation)** - **Visual Pixel & Character Counters:** Live character counts and pixel-width warning bars directly on Meta Title/Description inputs to prevent search truncation. - **Social Snippet Card Preview:** A pure DOM preview box rendering Facebook and X cards live in the editor before publishing. - **Auto-Healing Image Alt Tags:** A lightweight front-end HTML filter that injects fallback alt attributes on render using dynamic pattern tags (`%title%- Image %count%`) if an author forgets them. - **Media Attachment Auto-Naming:** Automatically cleaning camera filenames ( e.g., `IMG_9941.jpg`) into clean titles/captions upon upload. - **Global Dynamic Snippet Patterns:** Simple variables (`%title% %sep% %sitename%`) for fast catalog metadata processing. - **Automated 301 Redirects on Slug Change:** Automatically capturing changed URLs and writing native redirect rules in Visibility so traffic never hits broken links. - **Custom Canonical URL Override:** An explicit meta input allowing authors to override canonical tags for syndicated/cross-posted content. - **Instant IndexNow Hook:** A lightweight `transition_post_status` hook pinging Bing and Yandex queues when content goes live. * **2. VigIA (Admin Observation, Audits & Safety Control Tower)** Instead of post- publication audits, run a client-side JS panel inside the editor checking: - **Structural Hierarchy Guardrail:** Verifying a single H1 and proper heading nesting (H1 -> H2 -> H3). - **Alt Text & Media Counter:** Flagging images inserted into the draft that lack alt text. - **Isolated 404 Diagnostics & 1-Click Fix:** Filtering 404 dead link events into a clean view with a 1-click button to create redirect rules. - **Orphan Content Detector:** An audit filter flagging published posts with zero internal incoming links. - **Universal Builder Support:** Enqueuing standard `add_meta_box` views so Classic Editor, Elementor, and Divi users get the exact same visual guardrails. * **3. VulgatAI (Content Intelligence & AI Automation)** - **AI Image Alt Generator:** Reading draft context and uploaded images to generate descriptive, accessibility-compliant alt text in 1 click. - **Auto-Schema Extractor:** Parsing raw draft text to automatically build complex JSON-LD structured data (combining Article + FAQPage + HowTo + Product) without manual coding. - **Contextual Internal Link Assistant:** An on-demand button querying local WP REST API endpoints (`/wp/v2/posts`) to suggest 3–4 older relevant articles and semantic anchor text to link to. - **Bulk Meta Assistant:** Generating optimized meta titles and descriptions in bulk across published catalog posts via a clean admin interface. * Bringing this browser-side UI, automated media handling, and GEO/AEO intelligence into your ecosystem would make it the undisputed, zero-bloat alternative to Rank Math Pro for creators and agencies alike! * I’d love to know if browser-side editor guardrails and these auto-improvement features align with your long-term vision for these plugins. * Best regards, Viewing 1 replies (of 1 total) * Plugin Author [Fernando Tellado](https://wordpress.org/support/users/fernandot/) * (@fernandot) * [2 weeks, 6 days ago](https://wordpress.org/support/topic/modern-seo-plugin/#post-18970793) * Hi again [@akgt](https://wordpress.org/support/users/akgt/)! * This is one of the most well-thought-out comments I’ve received about my plugins, and it’s clear that it stems from having used these plugins on real client websites. Thank you—that’s the kind of comment that deserves a detailed response. * You’re right that gamified scores from 0 to 100 aren’t the solution. Let me take this a step further, because it touches on the entire design philosophy: traffic- light-style safety barriers and warning bars are the same mechanism, just with less detail. A red or green bar is a score, and a warning like “fix this” is the plugin deciding what “better” means. * That’s what has taught a generation of writers to stretch a sentence to 155 characters or repeat an exact keyword to get the green light—text that’s harder for people to read and that, for AI-based response engines, doesn’t help at all. What actually correlates with citations is timeliness, the author’s verifiable E-E-A-T, and a genuine question-and-answer structure—not writing to please a tool. * That’s why Visibility shows you the truth and doesn’t get involved in grading your writing. (The only score I track—VigIA’s AI-powered visibility check—evaluates objective site data—is there a llms.txt file? Is the identity schema present?— just like Core’s “Site Health,” never the writing itself.) * The “0% server tax” also comes with a hidden cost: real-time content analysis is precisely what causes large suites to balloon in size (Yoast has about 87,000 lines of code, Rank Math about 51,000). The browser’s pure JavaScript still needs to be created, maintained, and kept from becoming obsolete, and the moment you launch a content evaluator, the one thing that sets this stack apart (small, no upsells, minimal attack surface) will disappear. * Several of your ideas are already shipping, which tells me we think alike: - **Live SERP, social-card and AI-Overview previews** in both editors (1.9.0)— deliberately with no score and no traffic lights, just an honest render of what gets emitted. - **Per-post canonical override** since 1.2.0. - **A 301 manager that captures slug changes** and offers a redirect when you trash a post (1.6.0) — without a 404-logging table. * On putting the editor audits inside VigIA, that’s the one place I’d gently push back. VigIA watches and controls AI crawlers — who’s hitting you, and blocking the ones that ignore your rules — it doesn’t grade the draft. * H1 nesting, alt coverage and orphan-page detection are the content-scoring layer I keep out of the _whole_ suite. * The 404 idea is the good exception: VigIA already sees the 404s crawlers hit, so the right move is to surface those and hand them to Visibility’s redirect manager, not build a second 404 tool. * One thing worth clearing up: VulgatAI isn’t the SEO “content intelligence” engine the website may have suggested. It’s an **AI translator and autoposter** — it translates your content (keeping block structure, images, alt text, captions, taxonomies and your SEO metadata, Visibility’s included) into another language, and it can also pull posts from external sites over the REST API or RSS, translate them on the way in and publish them. It runs on the native AI connectors in WordPress 7.0, so no API key of its own. * So the alt generator, the schema extractor, the internal-link assistant and the bulk meta writer aren’t a VulgatAI fit — and they’re the one kind of AI I’ve chosen to keep out of the whole stack. Not for lack of ideas: writing your meta, inventing your schema or auto-generating alt text is the generative-SEO lane where the quality evidence is thin and you end up in the credit-metered content- mill business, which isn’t mine. * Where AI genuinely earns its place here is translating and importing (VulgatAI), not opining on your SEO. On the schema point specifically: stitching Article + FAQ + HowTo + Product into one blob is the “schema everything” approach the 2026 evidence shows doesn’t move citations, and emitting rich types without their required properties just throws Search Console errors — so Visibility emits what the content can back (Article family, FAQ from native blocks) and leaves the rich types to the plugin that owns the data (WooCommerce, etc.). * ```wp-block-code You clearly got curious about VulgatAI from the site, so — if you run any multilingual client sites, or any that syndicate content — I'd be glad to set you up with a free, no-strings test account and let you see what it actually does. Just send me a quick email from vulgatai.com website early access button and I'll get you access. ``` * None of this lands in a void, though: I’ve logged the whole list, and the pieces that fit the philosophy are already on the plugins’ roadmaps, credited to this thread — the neutral character counter under the title and description fields, a compatibility pass for Elementor and Divi, the standing interest in IndexNow, and the crawler-404 → redirect handoff between VigIA and Visibility. Between those and the parts already shipping, a good chunk of your list is either done or now on the plan; the rest helped me sharpen exactly where the line sits, which is just as valuable. * Really, thank you for taking the stack this seriously. That’s how the next versions get better 🙂 * Hugs, * Fernando Viewing 1 replies (of 1 total) You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fmodern-seo-plugin%2F%3Foutput_format%3Dmd&locale=en_US) to reply to this topic. * ![](https://ps.w.org/native-aeo-pack/assets/icon-256x256.png?rev=3583628) * [Visibility - Lightweight SEO, AEO and GEO for Search and AI](https://wordpress.org/plugins/native-aeo-pack/) * [Frequently Asked Questions](https://wordpress.org/plugins/native-aeo-pack/#faq) * [Support Threads](https://wordpress.org/support/plugin/native-aeo-pack/) * [Active Topics](https://wordpress.org/support/plugin/native-aeo-pack/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/native-aeo-pack/unresolved/) * [Reviews](https://wordpress.org/support/plugin/native-aeo-pack/reviews/) * 1 reply * 2 participants * Last reply from: [Fernando Tellado](https://wordpress.org/support/users/fernandot/) * Last activity: [2 weeks, 6 days ago](https://wordpress.org/support/topic/modern-seo-plugin/#post-18970793) * Status: resolved