No. Only posts that successfully publish to WordPress count against your monthly limit. Outlines are free and unlimited — generate 100 outlines, reject 90, publish 10, and you’ve used 10 of your monthly quota. This is how we price “per quality, not per AI call”.

Any post that successfully publishes to your connected WordPress sites. This includes standard pillar posts, backlink posts, and mention posts. Unused outlines do not count against your limit.

No. Cloud Stack Pages are tracked and capped entirely separately from your standard WordPress publishing limits.

The dashboard shows a soft block — you can still generate outlines and drafts, but the final “Publish to WordPress” step is disabled until the next billing cycle, unless you either upgrade or let overage billing kick in at the posted per-post rate. No auto-upgrade, no surprise bills. If you upgrade mid-cycle, you’re pro-rated for the remainder.

On the Network plan, yes — BYO-key is available on dedicated infrastructure. On Operator and Agency, we use our own API keys and absorb the cost into your subscription. Most customers prefer this because our volume pricing with Google and OpenAI is better than what they’d get individually.

A “site” is one WordPress installation (one URL, one set of credentials). You can have many clients, each owning many sites. A “post” is one blog article published to one site. Your plan’s connected-site count is the scalability lever — it’s what you’re really paying for. The monthly post and Cloud Stack Page figures are fair-use soft caps on top, e.g. the Agency plan covers up to 50 connected sites and up to 350 published posts/mo across all of them combined, not a fixed per-site quota.

Most fanout does — the REST API and IndexNow work fine on WordPress.com business plans. WebSub hub notification requires the <atom:link rel="hub"> tag in your feed, which WP.com doesn’t let you customize. On WP.com, you’ll get IndexNow fanout but not WebSub pushes. On self-hosted WordPress (the WP Engine / EBN / your own host case), everything works.

The content pipeline is queued — BullMQ retries with exponential backoff for up to 3 attempts per job. If all attempts fail, the post saves as “error” in the dashboard with both provider failure reasons preserved. You retry manually after the APIs recover. No partial/corrupted content is ever published.

ChatGPT is part of the IndexNow consortium (OpenAI joined in 2024). When Blog MONKEE submits to Bing IndexNow, that submission reaches OpenAI’s indexer as part of the consortium fanout. Whether OpenAI actually ingests your URL into its live web retrieval pipeline depends on OpenAI’s own quality signals — same as Google crawling a page after Search Console submission. See the /fanout page for the full integrity position.

Operator and Agency plans: yes, via dashboard → Settings → Billing. Paused subscriptions retain your clients, brand profiles, and site connections. Scheduled auto-blogs don’t fire while paused. Resume anytime. Network plans: contact your account engineer.

Nothing. Blog MONKEE publishes to your WordPress sites — the content lives in your WordPress database, not ours. Cancellation deletes your Blog MONKEE account (clients, campaigns, metadata, scheduled jobs) after a 30-day grace period, but every published post remains on your WordPress sites because it was never hosted here. Blog MONKEE never held the content hostage.

Yes — Agency and Network plans have one-click WP Engine API import. You paste your WP Engine API credentials once, and Blog MONKEE pulls every site in your WPE account with metadata pre-mapped. Same for Easy Blog Networks. Typical agency gets 40 sites added in under 60 seconds.