QuQi for WordPress.com
Your articles go live on your WordPress.com site the moment they are ready, formatted and tagged.
Connecting WordPress.com
A site hosted on WordPress.com is not the same thing as a WordPress install you run yourself, and it connects differently, so it has its own card. It signs in with an access token created through the WordPress.com developer apps rather than an application password. Once it is connected the behaviour is the same as any other publishing destination: finished articles arrive complete, and they hold your single publishing slot.
- 01
Create the access token
WordPress.com issues one through its developer apps. This is the part that differs from a self-hosted site, which uses an application password instead.
- 02
Connect from the Integrations page
Give your site address and the token. QuQi proves the credentials before storing them, so a connection you can see on the page is one that worked.
Who works with WordPress.com
What it handles for you
- Finished articles posted to your WordPress.com site on schedule
- A publishing calendar that fills itself instead of sitting empty
- Drafts held back for review while you are still building trust
- A recorded reason whenever a post is refused, so nothing fails silently
Common questions about WordPress.com
Why is WordPress.com a separate integration?
Because it authenticates differently. A self-hosted WordPress site connects with an application password, while WordPress.com wants an access token created through its developer apps. Same writing, same calendar, same crew behind it, but the connection step is genuinely not interchangeable, so it gets its own card rather than a confusing shared one.
Can I switch to self-hosted later?
Yes. Disconnect the WordPress.com card and connect the self-hosted one, since a website points at one publishing destination at a time. Your written work lives in QuQi rather than in the connection, so changing where articles go does not cost you anything already written.