Hello!
Good to hear from you again — it has been a while. Thank you for sharing your honest take.
I get what you mean. Compared with some SEO plugins, TSF can look quiet, maybe even dull. That is intentional, but quiet should not feel abandoned.
About Twitter/X: you are right that “Twitter” feels outdated in everyday language. We already refer to the platform as X where that makes sense. The catch is technical: Twitter Card is still the name of the metadata protocol. That is not homage for Twitter; it is the protocol name. X, Discord, and LinkedIn still read meta tags such as twitter:card, twitter:title, and twitter:image. Renaming the setting itself to X would make it less accurate and harder to recognize for people looking for the actual protocol. X also recently overhauled its developer documentation and removed many old references, which made this more confusing, so I wrote a clearer Twitter Cards and X sharing article about this.
About Focus: I do not plan to move Focus into the free core plugin. Focus is a writing assistant, not basic SEO infrastructure. The free plugin already handles the SEO output itself — titles, descriptions, canonical URLs, robots directives, Open Graph, Twitter Cards, structured data, sitemaps, breadcrumbs, and many safeguards — without ads, tracking, branding, or nags. Focus is useful for people who want keyword and synonym guidance, but it is not required for correct SEO output. Paid extensions also fund the continued maintenance of the free plugin; I will not pretend otherwise.
On the dated feeling: some of that is WordPress. WordPress is simple and durable, but its admin UI is not modern, and WordPress 7.0 will, unfortunately, worsen that (in my opinion). TSF deliberately blends into WordPress rather than building a separate, flashier app-like interface around it. That may hurt us in screenshot comparisons. It also keeps TSF predictable, accessible, unbranded, and usable on professional sites where the dashboard should not become our sales funnel.
SEO itself also has not moved nearly as far as SEO plugin marketing pretends. Search engines still need the boring fundamentals done correctly: titles, descriptions, canonical URLs, robots directives, crawlable URLs, structured data, sitemaps, performance, and sane defaults. Many modern-looking plugin features are packaging: scores, dashboards, prompts, reports, alerts, and AI suggestions. Some may be useful, but many mostly look busy. TSF is built around what works, not what helps sell the upgrade. This also goes for AI (GEO/AIO) — the landscape hasn’t changed a bit.
That does not mean TSF is standing still. Our WordPress.org plugin’s “last updated” date only changes when we publish a plugin release. Since 5.1.4, I have been working on 5.1.5 / 5.2.0. I also refreshed the website style (new buttons, sidebars, footer, etc.), and rebuilt the documentation and release notes. Last year, I built a state-of-the-art update service around Troy Client, so fixes can still be delivered reliably even if the Extension Manager itself has an issue.
Much of my best work is intentionally hard to see: security hardening, compatibility, safe defaults, reliable updates, privacy, accessibility, strict canonical handling, and safeguards against SEO attacks.
The WordPress plugin ecosystem, including SEO plugins, regularly experiences security issues. The SEO Framework still has none of that. It’s because I would rather spend engineering time preventing those than chasing a dashboard trend. That is not flashy, but it is the side I want TSF to be strongest on.
So yes, there is UI and workflow work I can improve. I won’t dismiss that. But TSF’s direction will remain users and professional sites first, sales second. If you have one or two concrete friction points from daily use, please share them. I cannot promise every feature will move into the free plugin, but I can take specific pain points seriously and improve the core where it makes sense.
Thank you again for sharing your thoughts. I hope this gives you a better idea of where I am coming from and where TSF is going. I am always open to feedback, and I want to make sure TSF continues to serve you well.
