> ## Documentation Index
> Fetch the complete documentation index at: https://docs.weelkit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# WordPress.com setup

> Connect a WordPress.com site with OAuth, review the discovered schema, and verify with a draft before going live.

The WordPress.com integration publishes to sites hosted on WordPress.com, authorized through WordPress.com's own OAuth flow.

> [!NOTE]
>
> This integration is **distinct from the self-hosted WordPress integration**. If your site runs WordPress on your own hosting, choose **WordPress** in Weelkit and connect it with the Weelkit Plugin instead. The connection, authentication and lifecycle described here apply only to sites hosted on WordPress.com.

## Connect a site

**1. Authorize with WordPress.com**

In Weelkit, open **Organization settings → CMS**, choose **Connect CMS**, and choose **WordPress.com**. You are sent to WordPress.com to authorize the Weelkit app against your account. Weelkit never sees your WordPress.com password — only the token WordPress.com issues.

**2. Select a site**

Weelkit lists the sites your authorization grants access to. Choose the WordPress.com site to publish to: each connection publishes to one site. Connect a staging site first if you have one — see [Testing integrations](https://docs.weelkit.com/integrations/testing-integrations.md).

**3. Schema discovery**

Weelkit discovers the site's available post types from WordPress.com. Choose one writable type as the primary publishing destination. Weelkit then discovers only that type's fields and taxonomies.

| Field | Notes |
| - | - |
| `title` | Post or page title |
| `content` | Body content |
| `excerpt` | Short excerpt |
| `slug` | URL slug |
| `date` | Publish date |
| `categories` | Category reference, when the selected type supports it |
| `tags` | Tag reference, when the selected type supports it |
| `author` | Post author |
| `featured_image` | Featured image; its mapped details appear in the article's image panel |
| `sticky`, `password`, `parent`, `format` | Native post settings |
| `likes_enabled`, `sharing_enabled` | Likes and sharing settings |
| `discussion.comments_open`, `discussion.pings_open` | Discussion settings |
| `metadata` | Native metadata add or update operations |
| `menu_order`, `page_template` | Page settings, when the selected type supports them |

**4. Review the mapping**

Weelkit suggests mappings from canonical Weelkit fields (and any mapped [organization custom fields](https://docs.weelkit.com/integrations/organization-article-fields.md)) onto the discovered schema. The suggestions do nothing until an administrator reviews and **saves** the mapping — only the saved mapping enters the generation contract.

**5. Set the publishing defaults**

Choose the **Default status** (**Draft** or **Published**) and what happens **When the article already exists**.

**6. Verify a test draft**

Choose **Verify test draft**. Weelkit uses the saved mapping to create a draft on the site and read it back. You can inspect it on WordPress.com, or choose **Delete draft**.

**7. Ready**

The connection is ready. Articles are sent to the site from the editor, as described in the [publishing overview](https://docs.weelkit.com/integrations/overview.md#mode-a-schema-backed-destination).

Other post types are not automatically treated as references. Weelkit fetches category or tag options only when the selected primary type's discovered taxonomy fields explicitly reference them.

When you verify the test draft, inspect its featured image and every mapped **Alternative text**, **Caption**, **Image title** and **Description** value on WordPress.com. Each detail appears in Weelkit only when its mapping enables it.

## Connection lifecycle

> **Expired access**
>
> If WordPress.com requires fresh authorization, sending and status checks pause. Choose **Reconnect** to authorize again. Reconnecting the same site preserves its saved mapping and published links.

> **Revoked access and missing scope**
>
> If you revoke the Weelkit app on WordPress.com, or the authorization lacks a scope Weelkit needs, the connection shows the same **Connection Error**. Choose **Reconnect** and authorize with the requested scopes to resume.

> **Rate limiting and transient errors**
>
> WordPress.com rate limits and transient server errors are retried **only for safe reads** — discovery and readback. If a write's outcome is uncertain, choose **Check original CMS send**. Weelkit retains its original identity and does not blindly create another post.

## Status and address

Weelkit keeps each article's status in step with its WordPress.com post. A **published** post makes the article **Published**. A **draft**, **scheduled**, **pending**, **private** or **trashed** post makes it **Draft**, and so does a post deleted from the site. The post's public link becomes the article's address once it's live. See [After you send](https://docs.weelkit.com/integrations/overview.md#after-you-send).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.