Why I Built A Blog Title & Post Optimizer WordPress Plugin to Manage A Content-Heavy Site

If you have ever run a content-heavy website, you know the specific frustration of sitting in front of a list of draft posts and spending forty minutes on titles.

Not writing. Not researching. Not publishing. Just titles.

Do they have the right keyword? Are they the right length for search snippets? Do they create enough pull to earn a click when they appear in a results page alongside eleven other options? Are the meta descriptions written or still blank? Has anyone checked keyword density on the body copy?

For a site like IdeasPlusBusiness.com (a digital media platform I have been running since 2015, with hundreds of published articles and a steady publishing cadence), that process was consuming more time than it deserved. Not because it was complicated. Because it was manual, repetitive, and scattered across tools that did not talk to each other.

The Blog Title and Post Optimizer plugin started as a direct response to that problem. It was not a market opportunity I identified from the outside. It was friction I was experiencing every week from the inside.

The Problem with WordPress Content Optimisation

WordPress is the publishing platform for a significant portion of the internet. It is also, by default, almost entirely indifferent to content quality.

The core WordPress editor gives you a text field and a publish button. Everything else (SEO, readability, keyword analysis, title scoring, etc.) comes from third-party plugins.

Some of those plugins are excellent. Yoast and Rank Math are the obvious names. But they are also broad tools designed to do many things for many types of users, and they approach content optimisation at the post level, one post at a time.

That is fine if you are publishing occasionally. It becomes a bottleneck when you are managing a site with a regular publishing schedule, a backlog of posts that need to be refreshed, and a content team or workflow that involves multiple pieces in various states of completion at any given time.

The specific gaps I kept running into:

No way to see the SEO health of multiple posts at once without opening each one individually. No tool that combined title scoring, meta description status, and keyword density into a single view.

No AI-assisted title generation that lived inside WordPress rather than requiring me to open a separate browser tab. No performance tracking that connected title and metadata choices to actual traffic outcomes over time.

These gaps were not hypothetical. They were things I was working around every week, manually, using a combination of spreadsheets, external tools, and judgment built from years of doing this work.

The plugin was built to close them.

What the Blog Title and Post Optimizer Does

The plugin lives inside the WordPress dashboard. It extends the editing and management experience rather than replacing it, which means it works alongside whatever theme or other plugins a site is already running.

The core features, developed across versions 2.5.4 through 2.5.7, cover four areas:

1\. Title optimisation and AI generation.

The plugin analyses existing post titles against SEO best practices (length, keyword placement, emotional pull, clarity) and scores them.

For titles that score poorly, it generates AI-assisted alternatives based on the post content, the target keyword, and the optimisation criteria that the analysis identified as weak.

Bulk title generation lets you process multiple posts in a single operation rather than working through them one at a time.

2\. Meta description management.

The plugin surfaces posts with missing or suboptimal meta descriptions and provides bulk generation for those gaps.

This was one of the most practically useful features to build. IdeasPlusBusiness.com had a significant backlog of posts published before meta descriptions were part of the standard workflow, and dealing with them individually would have taken weeks.

3\. Keyword density analysis.

The plugin analyses body copy for keyword density and flags posts where the target keyword is either absent, underused, or overused to a degree that risks appearing manipulative to search engines.

This is not a replacement for editorial judgment, but it is a reliable check that catches the obvious cases without requiring a manual read of every post.

4\. Performance tracking.

The plugin records title and metadata changes and tracks traffic data over time, creating a connection between optimisation decisions and outcomes.

This is the feature that is still most actively in development. The infrastructure works, but building a performance tracking system that is genuinely useful rather than just data-rich requires more iteration than the other features.

How I Built It and Why All Four Hard Parts Were Hard

I will be honest about this: the Blog Title and Post Optimizer has been one of the more demanding technical builds in my portfolio, precisely because it operates inside someone else’s system.

Most of the products I build are standalone. I control the architecture, the dependencies, and the deployment environment.

A WordPress plugin is different. It has to work inside WordPress (its hooks, its database structure, its admin interface conventions), and it has to work alongside whatever else is already installed on a given site. That constraint changes how you have to think about every technical decision.

1\. The AI generation and bulk optimisation

The AI title generation feature required connecting the plugin to an external AI API, processing the response, and presenting the output in a way that was useful rather than just technically present.

The bulk processing aspect was the harder part. Generating a title for one post is straightforward. Generating titles for thirty posts in a single operation (handling API rate limits, managing the queue, providing feedback to the user about progress, and handling failures gracefully without losing work) is a different problem.

I went through several versions of the bulk processing architecture before settling on an approach that was reliable under real-world conditions.

2\. The keyword density and SEO scoring logic

Keyword density sounds like a simple calculation until you think about what it actually requires.

You need to tokenise the body copy correctly, handling HTML markup, shortcodes, and embedded media. You need to handle keyword variations (singular and plural forms, common synonyms) in a way that reflects how search engines actually process content rather than applying a naive string match.

You need to set thresholds that reflect current SEO best practices, which change over time.

The scoring logic for titles had similar complexity. Length scoring, keyword placement scoring, emotional pull scoring, and clarity scoring; each of those is a separate analysis with its own criteria, and combining them into a single score that is useful rather than misleading requires careful calibration.

3\. Making it work reliably inside WordPress

Plugin conflicts are the unglamorous reality of WordPress development.

Any WordPress site of meaningful age has accumulated plugins. Some of those plugins modify the admin interface. Some of them load JavaScript that conflicts with other JavaScript.

Some of them hook into the same WordPress filters and actions as each other, producing behaviour that is hard to debug because it only appears in specific combinations.

Building a plugin that works reliably across that diversity of environments required defensive coding, careful use of WordPress hooks, and a lot of testing across different configurations.

Every time I thought the compatibility issues were resolved, a new environment surfaced a new conflict. This is not a problem you solve completely. It is a problem you manage through careful architecture and thorough testing.

4\. The performance tracking system

The performance tracking feature is where I am most honest with myself about how much work remains.

The concept is straightforward: track when a title or meta description changes, record the traffic data before and after, and surface insights about which optimisation decisions produced measurable improvements.

That is a genuinely useful feature if it works well. It is a misleading feature if it works poorly; if it attributes traffic changes to title changes that were actually caused by seasonal trends, algorithm updates, or changes in the external link profile.

Building a performance tracking system that is statistically honest is harder than building one that just displays data.

I have the infrastructure in place. The tracking works. What is still in progress is the interpretation layer, making the insights trustworthy rather than just plausible.

The Monetisation Question

I will be direct about this: I do not yet have a monetisation model for the Blog Title and Post Optimizer that I am confident in.

That is an unusual thing to admit about a product I have invested significant development time in. But it reflects something I think is worth saying plainly: Not every product needs to have its business model figured out before it is worth building.

The plugin exists because it solved a real problem in my own publishing workflow.

The development of this plugin has produced a set of WordPress development capabilities (plugin architecture, AI API integration within WordPress, bulk processing systems, performance tracking infrastructure) that I apply in client work and in other builds. The process of building it taught me things I could not have learned any other way.

The most likely monetisation path is a freemium model: a free version available through the WordPress plugin directory with the core functionality, and a premium version with the AI features, bulk processing, and performance tracking behind a one-time or annual purchase.

That model works well for WordPress plugins because the free version drives discovery and the premium version captures value from the users who need the full capability.

But I have not shipped that version yet. What I have shipped is a functional plugin that runs on my own sites, has gone through multiple iterations of improvement, and demonstrates a specific set of capabilities in a specific and widely used platform context.

What This Project Demonstrates

The Blog Title and Post Optimizer is the product in my portfolio that most directly reflects the intersection of two things I do professionally: content strategy and technical product development.

It was not built for a client or for a market I observed from the outside. It was built because I manage a content site, I understood the workflow problem from daily experience, and I had the technical capability to build a solution rather than work around it.

That combination (domain expertise from being a practitioner, and technical capability from years of building) is what makes the plugin possible and what makes it useful.

I know what a content team actually needs from this kind of tool because I am part of a content team. I know what WordPress can and cannot do because I have been building on WordPress for years.

The versions that have shipped (2.5.4 through 2.5.7) represent a product that has gone through real iteration, real bug fixing, and real improvement based on actual use. It is not a proof of concept. It is a working tool that runs in a production environment.

What Is Next

The immediate next step is a public release. A free version on the WordPress plugin directory that makes the core functionality available to a wider audience and begins generating user feedback that will inform the premium version.

After that, the performance tracking feature needs another development cycle to reach the standard where I am comfortable calling it production-ready. The interpretation layer, the statistical honesty problem I described earlier, is the work that remains.

Long-term, the plugin is a foundation. The architecture that handles bulk AI processing, WordPress hook management, and performance tracking could support additional features like content readability scoring, internal linking suggestions, and image alt text auditing, which extend the same workflow improvement into other parts of the content publishing process.

There is a real category of WordPress-native content intelligence tools that does not yet exist at the quality level it should. The Blog Title and Post Optimizer is my first entry into that category. It will not be the last.

A Note on Building Tools You Actually Use

Every product in my portfolio was built to solve a problem.

The Blog Title and Post Optimizer is the one where the problem was most directly and continuously personal. Not a frustration I experienced once and decided to fix, but a recurring friction in the work I do every week.

That proximity to the problem is an advantage in product development. It means I cannot convince myself that something is good enough when it is not, because I am the one who has to use it.

It means the edge cases I find in testing are edge cases I found in real use, not edge cases I constructed hypothetically. And it means the next version of the plugin will be better because I will have spent more time running up against its limitations.

Building tools you actually use is slower than building tools for an abstract user. It is also more honest. And honestly, it is what produces products worth using.

Adeyemi Adetilewa is a product builder, content strategist, and SEO specialist. He has been running IdeasPlusBusiness.com since 2015 and building WordPress-based tools and products since 2016. You can read more about his work at adeyemiadetilewa.com.