How I Built an AI pSEO Glossary Builder Automation

This week’s post shares how I built an AI automation which can make a niche glossary on your WordPress site. I spent time making it as generic, (but still high quality), as possible, so I can apply it to almost any niche WordPress website.

This one’s a simple part of the bigger AI Marketing plan for my AI biz challenge.

Making an AI pSEO Bot Part 2:

Building a Niche Glossary with AI

Over the years I’ve built all kinds of microsites, (or hub pages), designed to catch long-tail search engine traffic.

I’ve seen this produce best results when the individual pages are super niche. E.g. “Auto mechanics specialising in alloy repairs in town X”.

I want my programmatic SEO bot to be able to do all that niche goodness. But to get started, I’ve built something that covers the basics: Glossary.

How I Made my AI pSEO Glossary

So we’re on the same page, you might want to read my Anatomy of a pSEO page that ranks post, which details the page-specific must-haves for generating legit pSEO pages.

This automation ended up being two different workflows, and a WordPress plugin.

1. Generate the terms list & create a hub page.
2. Create the sub pages.

… the WordPress plugin basically shows a list of child-pages in a ‘Glossary’ style.

AI Automation 1: Generate Terms & Hub Page

Here’s a look at the final workflow I have running on Make.com:

This automation is pretty simple. Once I had the page generation stuff & WordPress connection written, it really was just connecting the pipes. Here’s what it does:

1. Retrieve projectFile (read project memory – basic stuff like keywords, domain etc.)
2. Generate a list of terms suitable for this glossary
3. Save the list against projectFile
4. Generate ‘Hub’ page content (all of this good stuff)
5. Create a new page on remote WordPress install
6. Update the projectFile to log the page details

… I made steps 4 & 6 generic, so I can pass all manner of prompt tweaks and data to create all kinds of pSEO pages – all of which will match my high standard requirement. It also means I can remotely add images and posts, pages etc. to a WordPress install (see side-benefits below).

Next I created another workflow to generate a page for each glossary term.

Note: These could be the same workflow, really, but because I was running tests on the first, working on the second synchronously was quicker.

AI Automation 2: Generate Sub Pages

Why have I been using Groq to parse JSON this whole time? Anyway, out with that and in with Make’s default JSON parser.

Here’s the routine for generating sub pages:

1. Retrieve projectFile
2. Iterate through the pseo_glossary_terms list
   • Check if already processed this page
   • Generate single glossary page
   • Create a new child-page on WordPress
   • Update the projectFile to log the page details

… and it just works.

… after the 5,000 times I had to run & re-run it to get it producing the pages I actually wanted.

Workflow Side-Benefits: Sub-Flows

As with a lot of ProfitSwarm stuff, I’ve front-loaded this project with a load of requirements which I know I’ll need repeatedly for the AI Marketing Agent. This makes things take a bit longer, but it is increasingly building up a toolkit.

Here’s what this pSEO glossary bot needed, which I now have as generically reusable endpoints in my business API:

Remote Posting to WordPress

I use WordPress for most marketing sites because it’s familiar to most of us who’ve been doing online business.

WordPress already has a great REST API built into it, so by writing wrappers I can post data straight into the CMS.

Yes yes, I could have used the Make/n8n WordPress connector, but this way I’m keeping all credentials on my server, (and can do things like auto-optimise images before they get uploaded).

• Upload images (so they’re naturally hosted on the domain in question)
• Add/Edit Posts, Pages including AIOSEO data and Meta fields

Generic Page Generation

I now have a chunk of solid code sitting behind my business API which can reliably generate pSEO pages which I’m confident will rank well.

This uses many prompts to generate all of the associated content and images.

I’ve so far tried it on as disparate niches as here on ProfitSwarm and on my Home Ed mobile app site.

It’s smooth.

It sits behind 1 endpoint.

Nice.

Image Generation, Sizing & Lossless Compression

These image generation endpoints are getting easier to make each month. My latest one for this project wraps in keyword-filenames, resizing & kraken compression to make optimal use of AI & automations.

Example AI-Built Glossary

If you want to take a look at an example, head on over to the ProfitSwarm AI Automation Glossary.

This glossary took about 30 minutes (AI time) to make, cost about $5 in OpenAI credit. It took maybe 4 minutes of my focus to check things over and regenerate 2 images.

Reading through the terms, I even learned stuff!

Thoughts on Making this AI pSEO Bot

Slowly slowly catchy monkey.

This one took longer than it needed to, but it’s totally laying the groundwork for bigger programmatic SEO projects.

I have my doubts about the internet staying the same as it is for entrepreneurs in the mid-long term. With projects like this becoming increasingly accessible, it’s likely to get washed out; will we be wading through a swamp of slop by 2026?

We’ll see.

Still, all we can do is build the best, most generically re-usable modules into our toolkits and be ready to capitalise wherever we can.

What are you Automating this week?

What’s getting automated or prompt-engineered for you this week? Are you building pSEO or AI marketing tools? Let me know in the comments!