How to Connect Your Website to Creaiter

What connecting actually gets you

A connected site changes the kind of request you can make. Instead of write a post about winter storage, you can say write it and publish it Friday morning, and the whole chain runs.

1. 01Publish a finished draft straight to your site without leaving the chat.
2. 02Schedule a post for a future date and let it go out on its own.
3. 03Keep the repository status in step with reality, so draft, scheduled, and published mean what they say.

Before you connect

Four things to settle first. Each one is a common reason a connection fails at the last step.

1. 01Know which platform you are on. WordPress, Wix, Vercel and custom sites each connect differently, and picking the wrong one wastes ten minutes.
2. 02Have a site account that is allowed to create and publish posts. A contributor-level account will fail at publish time, not at connect time.
3. 03Turn off anything blocking outside access while you test, such as maintenance mode or a password wall across the whole site.
4. 04Decide which author the posts should appear under, because that follows the account you connect.

Connecting WordPress

Open Settings in Creaiter, find the website connection, and choose WordPress. Creaiter tells you which details it needs. Give it exactly those and nothing extra.

Two details cause most failures. The first is the address: use the address where your posts actually live, including https, with no extra path on the end. The second is the account: sites protected by a security plugin or an extra sign-in step may need that plugin told to allow the connection.

Once it saves, Creaiter shows a connection state. Treat that as a claim, not proof. The next section is how you prove it.

Connecting Wix

Wix connects from the same place in Settings. Choose Wix, then follow the authorization steps as they appear, signing in with the account that owns or manages the site you want to publish to.

If you manage several Wix sites from one login, confirm which site the connection landed on before you publish anything real. Publishing a client's post to the wrong site is a bad ten minutes.

You can have more than one platform connected at a time. When more than one site is connected, name the site when you ask the chat to publish rather than assuming it picks the one you meant.

Verify with a real test post

A connection badge tells you a credential was accepted. It does not tell you a post can reach the site. The only honest check is to publish something.

1. 01Ask the chat for a short throwaway post, something like a 200 word note you would never keep.
2. 02Publish it to the connected site from the chat.
3. 03Open your site in a browser and confirm the post is there, with the title and formatting intact.
4. 04Check the author, the category, and the URL are what you expected.
5. 05If you plan to use scheduling, repeat once with a post set a few minutes out, and watch it land.
6. 06Delete the test post from your site when you are done.

If the connection shows disconnected

Connections drop. Passwords change, tokens expire, plugins update. A disconnected state is usually credentials rather than a fault, and reconnecting fixes it.

1. 01Reconnect from Settings first. That resolves most cases and takes under a minute.
2. 02Confirm the site loads normally in a browser and is not in maintenance mode.
3. 03Confirm the account you connected still exists and still has publishing rights.
4. 04If you changed your address, moved to https, or migrated hosts, connect again from scratch rather than editing the old entry.
5. 05If it reconnects and then drops again, stop retrying and contact support with the site address and roughly when it started.