What it is
There is a particular kind of WordPress plugin we appreciate: one that does its job without trying to become the main character of the dashboard. The SEO Framework is a rather good example. We use it on Geekist.
A search engine doesn’t see a website quite the way a person does. Alongside the writing, images and links, it looks for signals explaining which page is which, what each page is about and how related pages fit together. The SEO Framework generates much of that information from WordPress itself: page titles and descriptions, canonical URLs, indexing instructions, social previews and structured data.
The appealing part is how little ceremony it demands. It starts with sensible defaults, gives each post or page its own controls when needed and shows a compact, colour-coded SEO Bar in WordPress’s content lists. No endless dashboard advertising, no theatrical promises that a particular keyword score will win Google over.
Geekist introduces a twist: our public website is a static export of WordPress. We edit on WordPress, use The SEO Framework to produce the right page metadata, then publish the rendered pages through Simply Static. Visitors don’t need to run WordPress or the SEO plugin to receive a title, canonical link, Open Graph tags or Schema.org JSON-LD. Those are already part of the exported HTML.
That distinction matters. A static export carries the output, not the running WordPress plugin. Something like a server-generated redirect, a dynamically produced sitemap or a search endpoint needs its own static-export or hosting treatment. We let the authoring system do what it does well, then verify what actually makes it to the public site.
What’s new
The 5.2 release, named “Complete”, arrived in October 2026 with changes that are especially useful for publishers.
Authors finally get their own SEO controls. Previously, many author-archive settings came from global defaults. Now authors can manage archive titles, descriptions, social images, canonical URLs, indexing preferences and redirects. The sitemap respects whether an author archive is actually meant to appear in search results.
Generated metadata is easier to edit. Rather than retyping the title or description that TSF proposes, editors can click into the generated text and change only what needs changing. Existing installations may need to enable this in their layout settings. That sounds small until you’ve edited several hundred articles.
More control over what search engines and social networks see. The release adds Fediverse creator attribution for services such as Mastodon, clearer breadcrumb controls across post types, and a stylesheet for sitemaps as browsers move away from XSLT rendering. These are the rather unglamorous details that make a publishing system easier to trust.
The subsequent 5.2.1 release in November concentrates on performance and polish: less work building the SEO Bar, faster title and description processing, improved keyboard operation and a fix for Twitter Card metadata on certain archives. The developers report sub-millisecond overhead on the public routes they benchmarked. That matters most on a dynamic WordPress site; on a static public site, visitors consume the generated output without executing TSF at request time.
What else is similar to it
Yoast SEO offers a broad toolkit with editorial analysis, search previews and a large ecosystem. For authors who want a running commentary on every paragraph they write, its guidance can be useful. The SEO Framework takes a quieter approach, relying more heavily on sensible automatic metadata and contextual controls.
Rank Math brings many SEO features into one plugin, including integrations and reporting. SEOPress is another established option for metadata, sitemaps and structured data, with free and paid features. They’re all viable ways to manage WordPress SEO; the difference is in how much interface, automation and additional tooling you want.
The SEO Framework’s free Extension Manager is part of that comparison. It offers optional features rather than packing everything into the core plugin. Articles enriches posts with structured data and a news sitemap; Focus gives keyword-oriented editorial guidance; Local adds business information; and the free Transport extension helps migrate metadata from other SEO plugins. Some extensions require a paid plan.
For a site like Geekist, which already has its own editorial and publishing machinery, the ability to choose only the extensions we need is considerably more appealing than installing a second content-management department inside WordPress.
Why it’s different
The philosophy is restrained: generate good metadata automatically, respect WordPress conventions and stay out of the writer’s way. The plugin doesn’t need to advertise itself across the dashboard to be useful. Its work turns up where it belongs — in the page’s HTML and the editor controls that affect it.
But there’s more depth here than the minimal interface suggests. The SEO Framework is designed to be extended. Its Extension Manager catalogue supplies ready-made modules for things like article markup, local businesses, keyword guidance and migrations. You can choose an established extension instead of maintaining a home-grown solution.
For developers, the more interesting door is the filter API and action hooks. There are hooks to adjust generated titles and descriptions, change indexing rules, add sitemap URLs, alter social-image selection and work with the SEO Bar. The structured-data API even exposes the_seo_framework_schema_graph_data, letting a small custom plugin modify the Schema.org graph before it is printed. The documentation gives a concrete example of attaching a VideoObject using a post’s custom fields.
That’s the route for making your own extensions. You don’t need to modify TSF’s core files or force a custom feature into the official Extension Manager catalogue. A conventional WordPress plugin or must-use plugin can register TSF’s documented filters and actions, read your own metadata and change the resulting SEO output. The official extension packages are useful examples of how the authors organise additional functionality, but the documented hooks are the simpler integration boundary for an independent project.
Our static setup makes that especially interesting. Imagine custom repository metadata, editorial series or rich-media details feeding the site’s Schema.org output. The integration runs inside WordPress while Simply Static renders the page; the resulting JSON-LD and social tags then travel with the exported HTML. Just make sure canonical URLs, image URLs and site references end up pointing at the public domain, rather than the private WordPress installation. Simply Static’s URL-replacement settings are part of that equation.
It’s a neat division of responsibility: WordPress remains the editorial workshop, The SEO Framework interprets the material, our own integrations can refine it, and the public website receives the finished artefact. Sometimes the cleverest architecture is deciding which machinery never needs to run in production.
How to get started
- You need a WordPress site where you can install plugins. Check your installed WordPress and PHP versions against The SEO Framework’s current requirements; the 5.2 line requires WordPress 7.0 or newer. If you’re exploring without a site, use its WordPress Playground demo.
- Think about the job you want the plugin to do. Basic page titles, descriptions and canonical URLs work with the core plugin. Structured data for articles, keyword guidance and migration tools are available through optional extensions.
- If you export a static website, know which address WordPress uses internally and which domain the public site serves. The final canonical URLs, Open Graph images and sitemap links need to refer to the public destination, not merely look correct in the private editor.
- In WordPress, go to Plugins → Add New Plugin, search for The SEO Framework, install and activate it. Its default settings already generate essential metadata. Browse the SEO settings once to understand the available controls.
- Edit an existing page or post. Find its SEO settings and compare the generated title and description with what the page actually says. Change a field if you can improve it, save the post and inspect the rendered page source for
<meta name="description">,rel="canonical"and Open Graph tags. - Want extra features? Install the separate, free Extension Manager, then explore Articles, Focus, Local or Transport depending on the site. Some features require a subscription; there’s no need to activate everything.
- Want to customise your own? Create a small custom WordPress plugin and start with a single documented filter, such as
the_seo_framework_title_from_generationfor generated titles, orthe_seo_framework_schema_graph_datafor JSON-LD. The structured-data guide includes an example adding video metadata from custom post fields. Keep the integration separate from TSF so it survives plugin updates. - For a static site, run your normal export after making a change. Compare the exported HTML with the WordPress-rendered page. Check that the public canonical URL, social images and structured-data references survived correctly.
- The SEO Framework generates a strange title or description? Check the post’s SEO fields, your global title settings and whether another plugin or theme is generating competing tags. TSF’s SEO Bar can help identify the page’s current state.
- Your custom hook changes the WordPress preview but not the published site? Static files won’t change until the content is exported and deployed again. Inspect the exported
<head>, not just what the WordPress editor displays. - Canonical links point to the internal WordPress host? Review Simply Static’s absolute URL replacement. Its guidance explicitly covers canonical and Open Graph URLs. Check the actual generated files rather than assuming all metadata has been rewritten.
- Custom schema duplicates what another extension already emits? Inspect the final JSON-LD graph and consider enriching an existing entity instead of adding a competing one. The structured-data reference describes the graph hooks and how entity references work.
- A sitemap or redirect works in WordPress but not on the static host? A dynamic endpoint or HTTP redirect isn’t automatically a static file or hosting rule. Ensure your export includes the intended sitemap and that redirects are configured at the public hosting layer where necessary.
Explore further: The SEO Framework source · Available extensions · Extension Manager source · Customisation filters · Extend the structured-data graph · Simply Static URL handling.
