Modern SEO Plugin ?

Hi again @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.).

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