- Logging into a different CMS admin for every site, publishing by hand, and watching execution hours disappear into repetition.
- Every site has its own accounts, connectors and category structure; handover and review rely on spreadsheets and screenshots.
- As the site count grows, there is no single view of which sites are publishing normally and which have stale credentials.
Feature / Multi-Site Management
Every site, one console
Whether you run dozens of client sites or your own portfolio, the real friction of multi-site operations is never writing the article — it is sites scattered across CMS platforms, credentials living everywhere, and publish status tracked by hand. AI Publish converges all of it into one console.
The daily friction of multi-site operations
Onboarding and verification
Connecting a site takes three steps, with verification results shown immediately:
- Choose an access method: 14 PHP root connectors (WordPress, PbootCMS, Typecho and more) or 4 official API platforms (including Shopify) — 18 CMS and website builders in total.
- Verify: after uploading the connector or configuring API credentials, the platform verifies connectivity and permission scope right away, with failure reasons pointing to the next action.
- Sync categories: the remote category structure syncs into the platform; category mappings are stored per site so later tasks need no repeat setup.
See the WordPress and PbootCMS integration pages for detailed steps.
What unified management means
- Per-site credentials: every site uses its own connector or API credentials; keys are encrypted and never echoed back. Permission boundaries are documented in the Security Center.
- One list: view status, task volume and recent publish results for all sites in a single searchable, filterable list.
- Per-site configuration: category mappings, publishing schedules and template choices are saved per site — changes to one site never leak into another.
- Deletion on demand: deleting a site cleans up its credentials and task references, leaving no dangling data.
Quota and reconciliation
Costs are what spiral out of control first in multi-site operations. Billing here is built on active sites and successful articles:
- Active sites are counted per account; before exceeding your plan allowance you get an explicit prompt — overage is off by default and never silently billed.
- Only successfully published articles are billed; failures and retries are free.
- Site allowances by plan: Starter 3, Growth 10, Agency 30, Scale 100, Enterprise 300. Full pricing is on the homepage pricing table.
FAQ
- What happens when I hit the site limit? Pause sites you are not operating to release allowance, or upgrade the plan; upgrades are prorated for the remaining cycle.
- Can different sites use different CMS platforms? Yes — all 18 supported CMS platforms can be mixed within one account and verified independently.
- How do I prove management scope to clients? The site list, task records and publish results are verifiable directly in the console and can be exported for reconciliation.
Every site, one console
Whether you run dozens of client sites or your own portfolio, the real friction of multi-site operations is never writing the article — it is sites scattered across CMS platforms, credentials living everywhere, and publish status tracked by hand. AI Publish converges all of it into one console.