SEO Clusters in WordPress: How Antradus AI Builds Topic Hubs

SEO clusters turn one topic into a connected set of articles, and Antradus AI handles the planning, writing, and linking inside WordPress. Based on the documentation at https://antradusai.com/docs/seo-clusters/, the feature builds one pillar page and several related articles so your coverage reads like a real subject hub instead of a single oversized post.

One page rarely carries a whole subject anymore. You need breadth, internal links, and clear article roles. That is exactly where Antradus AI steps in.

Antradus AI is a WordPress plugin built to create, organize, and publish AI-assisted content workflows. In its SEO cluster feature, one idea can become a full section of your site: a long overview article, multiple supporting pieces, and automatic linking after the writing is done.

What is an SEO cluster and why does it matter in 2026?

An SEO cluster is a structured group of articles built around one main topic, with a central overview page linking to narrower articles that each answer one specific question. In Antradus AI, that structure is the core of the feature, not an afterthought.

The documentation makes a sharp point: one giant guide is tempting, but a connected set of articles tends to perform better because each page can target its own search intent. That matters for search engines, and the source also says it matters even more for AI assistants, which are more likely to cite a linked body of coverage than a standalone post.

The shape is simple. The pillar article covers the topic at survey depth. The spoke articles go deep on separate questions. Each spoke links back to the pillar, and the pillar links out to all spokes. If two spoke topics genuinely overlap, they can link sideways too.

That structure solves a common publishing problem. Without a cluster, you either publish one article that tries to do everything, or you publish multiple posts that accidentally repeat each other. The Antradus AI workflow is designed to prevent both. The pillar is required, and every spoke is assigned a distinct role before anything is written.

As of August 7, 2026, the documentation for Antradus AI Pro v2.4.0 presents SEO clusters as part of its Bulk Publishing tools for WordPress. The value is not only speed. It is controlled coverage.

How do SEO clusters work inside Antradus AI?

SEO clusters in Antradus AI work through a four-step workflow inside WordPress: define the source, choose the cluster size, review the plan, and send the whole set to the publishing queue. The process is built into Bulk Publishing under the SEO Cluster option.

Step one is deciding where the subject comes from. You can start from an idea, from an existing article, or from a YouTube video. If you already know the topic, you can describe it in plain language. The documentation gives a spoken-style example: “home battery storage for UK households.” That matters because the tool is not asking for a stiff keyword formula first. It starts with the real subject.

You can also build SEO clusters from an article URL. Antradus AI reads the page before writing anything. And if the page turns out to be a menu, a login wall, or some other unusable source, the system tells you and stops. That check is a practical guardrail, especially for teams expanding competitor content or turning existing research into new article sets.

The third entry point is video. For that route, Antradus AI requires the free Antradus YT extension, which reads the transcript in your browser. That gives WordPress users a direct way to turn a recorded talk, tutorial, or explainer into a structured article cluster.

Then comes planning. You click the planning option, review the pillar and proposed supporting articles, and inspect the focus keyword assigned to each one. Nothing is written at this stage. You can untick topics, rename awkward titles, or fix a keyword before the system starts generating content.

That pause is important. A good cluster needs editorial judgment, not blind automation.

How many articles should an SEO cluster include?

An SEO cluster in Antradus AI should usually contain 8 to 12 supporting articles, because the documentation says that range is the sweet spot for real coverage without overlap. The tool lets you choose a fixed size or let the AI decide.

The available size options are specific. You can let the AI decide, or you can choose Small, Standard, or Large. Those fixed sizes correspond to exactly 6, 10, or 14 deep dives. The “AI decide” option produces between 6 and 14 deep dives depending on how much genuine scope the topic has.

The limits are not arbitrary. According to the documentation, fewer than 6 supporting pieces often do not provide enough breadth to read as subject authority. More than 14 creates the opposite problem: subtopics begin to overlap, and writing gets stretched to fill slots. That is where thin content starts creeping in.

So why not force a bigger cluster every time? Because a cluster is supposed to map the topic, not inflate it. If your subject only supports a handful of real questions, manufacturing extra posts will weaken the whole section.

The source is unusually direct here. If the AI can only find one angle worth covering, it refuses the cluster request and suggests writing a single article instead. That is a useful admission. Some topics are broad enough for a hub. Some simply are not.

For publishers working in WordPress, that kind of refusal is healthy. It saves budget, avoids filler, and keeps your content architecture honest.

What does Antradus AI write for the pillar and spoke articles?

Antradus AI writes different instructions for the pillar and the supporting articles so the SEO cluster does not collapse into repetition. The documentation gives clear word-count targets and clear editorial boundaries for each type.

The pillar article is assigned 2,500 to 3,500 words. Its job is to cover the whole topic at survey depth, not to exhaust every subtopic. It receives the list of all deep-dive articles and is told not to act like the final word on those narrower questions.

The spoke articles are shorter and tighter. Each one is assigned 900 to 1,400 words and focuses on one question only. Each spoke also receives the titles of its sibling articles and is told not to re-cover their ground. That is one of the smartest parts of the system, because article clusters often fail when every page starts restating the same background section.

The plugin also blocks sloppy linking behavior during drafting. Neither the pillar nor the spokes are allowed to write placeholder language such as “see our other article,” and they are not allowed to invent links. Instead, the linking is added afterward by the plugin in a separate pass.

That separation matters. Writing and linking are related, but they are not the same task. By handling them in sequence, Antradus AI reduces the mess that comes from AI-generated posts guessing URLs or forcing awkward anchor text into paragraphs.

“The pillar is required — it’s what everything else links to.”

Antradus AI documentation, SEO Clusters page

For WordPress users trying to build a topic section instead of a random stack of posts, that requirement creates discipline. You are building a hub, not just uploading ten articles.

How does linking work in an SEO cluster?

SEO clusters in Antradus AI are linked automatically after all articles are written, using a hub-and-spoke structure where every supporting post links to the pillar and the pillar links to every supporting post. That linking phase is automatic and mandatory for the cluster feature.

The documentation is explicit: linked relationships are not an optional checkbox here. Without those links, a cluster is just a batch of articles. So the plugin waits until the final article is complete, then runs a dedicated linking pass.

The pattern works like this:

• Every spoke links up to the pillar.
• The pillar links down to every spoke.
• Spokes link sideways only where there is a real overlap.

That last point deserves attention. Sideways linking is not sprayed everywhere. It appears only where the content genuinely intersects. That helps preserve article boundaries and avoids turning every post into a knot of unnecessary internal links.

The source also notes that links are wrapped around words already present in the text. That means Antradus AI is not stuffing random anchors into the draft after the fact. It is applying links to language already in place, which usually produces cleaner reading.

And because the work happens inside WordPress, the cluster joins the normal publishing queue. You keep the usual progress view, failure retries, and scheduling controls. You can publish as drafts, push posts live immediately, or drip them over time.

For editorial teams, that queue integration is not a small detail. It means SEO clusters are not a separate experiment bolted on the side. They sit inside the same operational flow as the rest of Bulk Publishing.

What are the costs, limits, and trade-offs of SEO clusters?

SEO clusters cost more than a single article because each cluster is effectively N+1 posts, plus planning and linking requests, and they take longer to process if you do not keep the queue active in WordPress. The documentation is clear about both the cost logic and the operational trade-offs.

If you create a 10-spoke cluster, you are not buying 10 articles. You are buying roughly 11, because the set includes the pillar page too. On top of that, Antradus AI makes one small request for planning and another for linking. The documentation does not list a currency price on the page, but it does explain the request structure plainly.

Featured images are switched off by default for SEO clusters. The reason is practical: a cluster with 11 posts would also trigger 11 separate paid image-generation requests. If you need those images, you can account for them. But the default keeps the content build from quietly getting more expensive than expected.

Time has a similar trade-off. If you keep the Queue tab open, the system runs at full speed. If you close it, WordPress’s own scheduler takes over. That is slower, and it depends on your site being visited to continue processing tasks. For site owners who have used WordPress cron before, that warning will sound familiar.

There is also an editorial limit, and it is a healthy one. Some topics do not deserve a cluster. Antradus AI says so when it cannot find enough distinct angles. That refusal protects you from padded content and protects the site structure from weak sections that only look impressive from a distance.

So the trade-off is simple. SEO clusters give you breadth, stronger internal architecture, and cleaner subject coverage. In return, you spend more requests, more review time, and more planning attention than you would on one ordinary post.

What should you do with SEO clusters on your WordPress site?

You should use SEO clusters when a subject naturally breaks into several distinct reader questions, and you should skip the format when the topic only supports one solid article. That is the practical lesson from the Antradus AI documentation.

Start with topics that already show branching intent. A good candidate is a subject where readers ask for setup, cost, comparisons, mistakes, tools, and step-by-step help as separate searches. In that case, the pillar can introduce the field while the spokes handle the narrower needs properly.

Use the planning stage seriously. Review every proposed spoke. Rename titles that sound mechanical. Fix focus keywords that feel too broad. And cut any article that does not earn its place. The tool gives you automation, but it also gives you a moment to act like an editor.

If you work in WordPress and want a faster route to topic hubs, Antradus AI is built for that exact job. The SEO cluster feature documented at https://antradusai.com/docs/seo-clusters/ is not just a writing shortcut. It is a way to build a section that reads coherently, links properly, and covers a subject without repeating itself.

Pick one topic that has real depth. Plan the cluster. Trim the weak angles. Then let the queue run.