Creator Assistant Categories

They are deleted, unless you protect them. After the tree is applied, the category structure belongs to the tree and every analyzed article is in one category of it. Categories that exist already with the same name are reused, so a hand-made "Travel" is kept if the analysis also finds a group named "Travel". Every other category is deleted, whether you made it by hand or a previous analysis created it. Articles the analysis does not cover (drafts, scheduled or private articles, and published ones not summarized yet) leave the deleted categories: they keep the categories that stay, or get the default category, and receive the category of the most similar article once they are published. Some categories are always kept: the default category, the protected ones, and a category you made by hand that also holds other kinds of content, such as pages or the items of another plugin, because this plugin would never give them a category back. A category that has a kept category below it is emptied but not deleted, so that no category moves to another level. The preview lists the categories that will be deleted, those that will be emptied but kept, and the protected ones: read it before you apply it.

Go to Posts > Categories, edit the category (or create it) and tick "Protect this category and its branch from Creator Assistant Categories". A protected category is never deleted, and its articles stay in it: they get their topic category in addition to it. Protected categories never move either: they keep their place, and a category with a protected one below it is not moved to another place in the tree (a new category is created there instead).

A new article receives the category of the most similar article already in the tree, as soon as its summary is ready. It is not a new analysis: to reorganize the tree, run the analysis again.

Each threshold is a number between 0 and 1: the closer two articles must be to share a category, the higher it is. A higher value gives more and smaller categories. The three values must increase from the first to the third. If the preview has a single main category that holds all your articles, the first threshold is too low: raise it and analyze again. The minimum number of articles per category makes smaller groups join the closest one.

The analysis relies on a clustering service and on a way to read the summaries that arrived with Hub 1.2.0. An older Hub does not have them, so the plugin cannot work with it.

Only where the topics changed. When you analyze again, the AI sees the categories the plugin created last time and keeps a category whose topic is the same, with its current name. Next to each category the preview says what happens to it:

• "existing category, stays where it is": nothing changes, the address included.
• "existing category, moved": the category moves under another one (the preview says where it was). It is the same category, so it keeps its description, its SEO data and its place in your menus, but its address changes, because the address of a subcategory contains the category above it.
• "new category": the category is created, with a new address.

No. A category that is moved or deleted when you apply a tree changes its address, and the plugin does not add a redirect. If your site is already well indexed, check the addresses of your main categories first.

A category is reused when its name matches an existing one, and the comparison follows the collation of your MySQL database, which usually ignores accents and case. Rename the category afterwards if you want the other spelling.

It keeps all the vectors in memory and compares every article with every other one, so it is meant for the articles of a blog, not for tens of thousands of them.