Short answer: the Pro plan of AI Blog Autopilot costs 99 euros a month and lists 70 articles, 5 websites, all 60 social networks, all 25 languages, evergreen reshares and a Search Console topic import. It suits a business or small group that runs several sites or languages and has enough review capacity to match. Choose it for the combination of volume and reach, not for the number alone.
Pro sits between Growth, which lists 30 articles, 2 websites and 3 languages, and Agency, which lists 200 articles and 20 websites. It is the first plan that lists all 25 languages and the first with the Search Console topic import. For a company with several brands, several markets or a serious content programme, it is often the natural working plan.
This guide explains what Pro lists, four situations where it fits, how to share 70 articles sensibly, what two of its exclusive features mean in practice and what to watch as volume grows. All limits come from the product’s pricing and home pages, which you should check for current details.
What Pro lists
The pricing page shows Pro at 99 euros a month, with yearly billing shown at 20 percent lower. It lists 70 articles a month, 5 websites, all 60 social networks, all 25 languages, evergreen reshares and the Search Console topic import. As elsewhere, articles can be up to 3,000 words, credits are monthly and do not roll over, the first three articles are free, VAT is added at checkout and you can cancel at any time.
Two things distinguish it from Growth: the number of websites and the languages. Five websites let a small group of brands or sites each have its own blog. All 25 languages open markets that three languages cannot. The Search Console topic import appears first at this level, and is described below.
Agency adds team and client approval and API and white-label reports, which matter mainly for firms handling clients’ sites. If you run only your own sites, Pro lists everything you are likely to need. The article on choosing an AI Blog Autopilot plan compares the plans.
Situation one: several brands
A company with several brands, each with its own website, can give each site a blog. With 70 articles and 5 websites, an even split is 14 articles per site, or about three a week each. A more realistic plan gives the main brand 25, others 15 or 10, depending on commercial priority.
Each brand needs its own brief. Different audiences, tones and keywords prevent the sites from competing with one another. Resist the temptation to reuse an article across brands, since duplicates can harm all sites involved. Keep a shared list of topics already used, with the site and main phrase, so that overlaps are visible.
Assign an owner to each brand. Even with automation, someone must check facts and answer comments. The article on managing several blogs offers a routine for people who run more than one.
Situation two: an international business
All 25 languages make Pro attractive for an exporter or an international service. The home page says each article is written directly in its language, not translated from English. That is different from a translation workflow, where an English article is converted, and it suits markets that expect local expressions.
Decide your languages by customers and capacity. For each language, you need someone able to review a sample and to answer enquiries. A language without either is a risk. Start with the two or three markets that matter most, and add others as you learn. The article on blogging in 25 languages covers the wider strategy.
Think about site structure. Languages may live on one site with a switcher, on separate sites or on subfolders. Plan this before you publish, since the choice affects the number of websites you use, and therefore the plan. The article on country domains, subfolders or subdomains for other languages compares the options.
Situation three: a content-led business
Some businesses live on content: a comparison site, a guide publisher, a training provider or a software company that wants thorough documentation and tutorials. For them, 70 articles a month builds a large library quickly. It makes sense when the business has editors or subject experts who can review at pace.
Plan clusters, not scattered topics. Group articles around main subjects, give each cluster a pillar and supporting pieces, and make sure the pieces link to each other. The article on topical authority explains why depth matters.
Keep quality at the front. A large number of weak articles does more harm than good. If review capacity is the limit, publish fewer articles and improve them. The article on quality control at volume describes routines that scale.
Situation four: a freelancer with several clients
A freelancer or very small agency with a handful of clients might use Pro for up to five sites. If you need team and client approval, or white-label reports, Agency is the plan that lists them. If you do not, Pro may suffice. Check what you promise clients, and make sure the plan supports it.
Be clear about who owns each website connection, and what happens if you stop working with a client. The article on handing over a blog lists the points to settle in advance. Also be clear in contracts about what is automated and what is reviewed, since clients are paying for your judgement.
If you grow beyond five clients, you will need Agency, which lists 20 websites. Plan the move before you are at the limit, so that you do not have to refuse work.
Sharing 70 articles
Whatever the situation, 70 articles are a pool to divide. Start from priorities. List each site or language with a business value and a review owner. Allocate articles in proportion to value, but never beyond what the owner can check. A site with no available reviewer should get fewer articles, however valuable.
Write the split down at the start of each month. Credits are monthly and do not roll over, so unused articles are lost. If a site has a quiet month, move its credits to another. The article on planning your monthly credits explains how.
Use the content map to see the whole pattern: a calendar for when, and a network matrix for where, with each cell linking to the live post. Check that the calendar is balanced across sites and that no network has gone silent.
A worked example shows the idea. A company with three sites and one language might give 30 articles to its main shop, 25 to an advice site and 15 to a small niche site, leaving none unused. Another, with one site in five languages, might give 25 to the home language, 15 to the second market and 10 each to the others. Both plans use all 70 credits, both assign a reviewer to each stream and both can change the split next month if results suggest it. The exact numbers matter less than having a written plan that someone checks.
Review capacity is the true limit, so estimate it honestly. If a reviewer can give 15 minutes to each article, 70 articles need more than 17 hours a month, which is a significant part of someone’s time. If that is not available, lower the number you use, or review in samples on topics that carry little risk. Unused credits are cheaper than a wrong article published under your name.
The Search Console topic import
Pro lists a Search Console topic import, which Starter and Growth do not. The pricing page names it without detail, so look in the account to see how it works. The idea is natural: your own search data shows the queries for which your sites already appear, and those queries make good topics because real people are already searching for them.
To use it well, make sure each site has a verified Search Console property and some history. Review the queries before importing anything. Look for those with many impressions and few clicks, and for questions that your site does not yet answer. The article on finding article ideas in Search Console query data explains how to read the data.
Imported topics still need weights, audience and tone. Treat them as a source of ideas, not as an automatic plan, and keep the topics that connect to your business goals. If a query is irrelevant, or invites readers you cannot serve, leave it out.
What to watch as volume grows
With 70 articles, small problems multiply. A wrong statement in one brief appears in many articles. A connection that fails stays unnoticed on one of five sites. Two sites may drift into competing for the same phrase. Prepare for these with a routine.
Keep a fact sheet for each site and update it whenever something changes. Scan the content map weekly for warnings. Keep a spreadsheet of main phrases per site to catch overlaps. Review a sample of articles from each site every month. Record what you changed in the briefs, so that you can see improvement.
Consider approval for the first month on each new site, as the home page says it is available any time. When a site’s output proves reliable, move to AUTO and rely on sampling. The article on scaling from 4 to 30 posts a month explains how to grow without losing control.
How AI Blog Autopilot helps
Pro gives a multi-site or multilingual business the writing, publishing, sharing and topic import in one account, with a content map to oversee it. Try the product with three free articles on AI Blog Autopilot, and see the current limits on the pricing page.
Related reading
The bottom line
Pro suits several brands, several markets or a content-led business: divide the 70 articles by value and review capacity, choose languages by customers and use the Search Console import as a source of ideas.
BUJ
What does the Pro plan include?
The pricing page lists 70 articles a month, 5 websites, all 60 networks, all 25 languages, evergreen reshares and the Search Console topic import for 99 euros a month.
How is Pro different from Growth?
Growth lists 30 articles, 2 websites and 3 languages. Pro lists 70 articles, 5 websites and all 25 languages, and adds the Search Console topic import.
Can I divide the articles between my websites?
You choose the split. Credits are monthly and do not roll over, so plan it each month.
Are articles written in each language natively?
The home page says each article is written directly in its language, not machine-translated.
Does Pro include client approval?
No. Team and client approval and API and white-label reports are listed on the Agency plan.


