> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/marketing/wordpress-community.md).

# Wordpress

Connect WordPress posts, pages, comments, and media to Google Sheets or BigQuery with Coupler.io for content analysis and reporting.

WordPress is one of the most widely used content management systems in the world, powering everything from personal blogs to enterprise websites. With Coupler.io, you can pull your WordPress site's content, users, media, and more into your preferred destination for reporting, analysis, or automation.

## Why connect WordPress to Coupler.io?

* **Centralize your content data** — pull posts, pages, comments, and media into Google Sheets, BigQuery, or any other destination without manual exports
* **Track content performance over time** — combine WordPress data with analytics sources to see what's driving traffic and engagement
* **Automate reporting** — keep stakeholders updated with fresh WordPress data on a schedule you control
* **Use AI to analyze your content** — send posts or comments to ChatGPT, Claude, Gemini, or other AI destinations for summarization, tagging, or sentiment analysis

## Prerequisites

* A WordPress site with the REST API enabled (enabled by default on WordPress 4.7+)
* An **Application Password** generated from your WordPress user profile (go to **Users → Profile → Application Passwords** in your WordPress admin)
* Your WordPress site URL
* Your WordPress username

{% hint style="warning" %}
Coupler.io connects to self-hosted WordPress sites via the REST API. WordPress.com hosted sites may have different API access rules. If your site is behind a firewall or CDN like Cloudflare, you may need to whitelist Coupler.io's IP addresses.
{% endhint %}

## Quick start

{% hint style="success" %}
If you want to export WordPress posts to Google Sheets for editorial tracking or content reporting, start with the **Posts** entity — it's the most commonly used and gives you the richest dataset right away.
{% endhint %}

{% stepper %}
{% step %}
**Create a new data flow** in Coupler.io and select **WordPress** as your source.
{% endstep %}

{% step %}
**Enter your credentials.** You'll need your WordPress site URL (e.g., `https://yoursite.com`), your WordPress username, and the Application Password you generated from your user profile. Note that Application Passwords are different from your login password — make sure you're using the one from the Application Passwords section.
{% endstep %}

{% step %}
**Select an entity** to import. Choose from Posts, Pages, Comments, Users, Media, and more. See the table below for the full list.
{% endstep %}

{% step %}
**Choose your destination** — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude for content analysis.
{% endstep %}

{% step %}
**Run the data flow** manually to confirm everything is working before setting up a schedule.
{% endstep %}
{% endstepper %}

## Available entities

| Entity         | What it contains                             |
| -------------- | -------------------------------------------- |
| Posts          | Published and draft blog posts with metadata |
| Pages          | Static site pages and their content          |
| Page revisions | Version history for pages                    |
| Comments       | Reader comments with author and status info  |
| Users          | Registered users and their roles             |
| Categories     | Post categories and hierarchy                |
| Tags           | Post tags                                    |
| Taxonomies     | Custom taxonomy definitions                  |
| Types          | Registered post types                        |
| Media          | Uploaded files and image metadata            |
| Editor blocks  | Gutenberg block definitions                  |
| Plugins        | Installed plugins and their status           |
| Themes         | Installed themes                             |
| Statuses       | Available post statuses                      |
| Settings       | Site-level settings                          |

## WordPress data overview

Coupler.io pulls data from the WordPress REST API across 15 entities, covering everything from published content to site configuration. Here's a breakdown of what's available in each entity and how you can use it.

## Entities overview

| Entity         | Best for                                                           |
| -------------- | ------------------------------------------------------------------ |
| Posts          | Content audits, editorial calendars, publishing frequency analysis |
| Pages          | Site structure mapping, page inventory                             |
| Page revisions | Edit history and version tracking                                  |
| Comments       | Engagement analysis, moderation tracking                           |
| Users          | Author activity, role audits                                       |
| Categories     | Content taxonomy reporting                                         |
| Tags           | Tag usage and distribution                                         |
| Taxonomies     | Custom taxonomy structure                                          |
| Types          | Custom post type inventory                                         |
| Media          | Media library audits, file usage                                   |
| Editor blocks  | Block usage analysis                                               |
| Plugins        | Plugin inventory and status monitoring                             |
| Themes         | Theme tracking                                                     |
| Statuses       | Post status distribution                                           |
| Settings       | Site configuration snapshot                                        |

{% hint style="info" %}
The **start date** filter applies to Pages, Comments, Media, and Editor blocks. For all other entities (Posts, Users, Categories, etc.), all available records are always returned regardless of the date range you set.
{% endhint %}

## Posts

#### Fields

| Field           | Description                                  |
| --------------- | -------------------------------------------- |
| id              | Unique post ID                               |
| date            | Publish date and time                        |
| date\_gmt       | Publish date in GMT                          |
| modified        | Last modified date                           |
| slug            | URL-friendly post identifier                 |
| status          | Post status (publish, draft, pending, etc.)  |
| type            | Post type                                    |
| link            | Full URL to the post                         |
| title           | Post title (rendered)                        |
| content         | Full post content (rendered HTML)            |
| excerpt         | Post excerpt                                 |
| author          | Author user ID                               |
| featured\_media | Featured image media ID                      |
| comment\_status | Whether comments are open or closed          |
| categories      | List of category IDs                         |
| tags            | List of tag IDs                              |
| format          | Post format (standard, video, gallery, etc.) |

## Pages

#### Fields

| Field       | Description                       |
| ----------- | --------------------------------- |
| id          | Unique page ID                    |
| date        | Creation date                     |
| modified    | Last modified date                |
| slug        | URL slug                          |
| status      | Page status                       |
| title       | Page title                        |
| content     | Page content (rendered HTML)      |
| author      | Author user ID                    |
| parent      | Parent page ID (for nested pages) |
| menu\_order | Page order in menus               |
| template    | Page template in use              |

## Comments

#### Fields

| Field         | Description                               |
| ------------- | ----------------------------------------- |
| id            | Comment ID                                |
| post          | Post ID the comment belongs to            |
| author\_name  | Display name of commenter                 |
| author\_email | Email address of commenter                |
| date          | Comment submission date                   |
| content       | Comment content                           |
| status        | Approval status (approved, pending, spam) |
| type          | Comment type                              |
| parent        | Parent comment ID (for threaded replies)  |

## Users

#### Fields

| Field            | Description                                          |
| ---------------- | ---------------------------------------------------- |
| id               | User ID                                              |
| name             | Display name                                         |
| url              | User website URL                                     |
| description      | User bio                                             |
| slug             | URL-friendly username                                |
| registered\_date | Registration date                                    |
| roles            | Assigned roles (administrator, editor, author, etc.) |
| capabilities     | User capability flags                                |

## Media

#### Fields

| Field          | Description                                   |
| -------------- | --------------------------------------------- |
| id             | Media item ID                                 |
| date           | Upload date                                   |
| slug           | Media slug                                    |
| status         | Media status                                  |
| title          | Media title                                   |
| author         | Uploader user ID                              |
| source\_url    | Direct URL to the file                        |
| media\_type    | Type (image, file, etc.)                      |
| mime\_type     | MIME type (image/jpeg, application/pdf, etc.) |
| media\_details | Width, height, file size, and generated sizes |
| post           | Post the media is attached to                 |

## Common metric combinations

* **Posts + Users** — Join on `author` ID to see publishing activity per author. Use the **Join** transformation in Coupler.io to merge these two entities in a single data flow.
* **Posts + Categories** — Map category IDs to names for content distribution reporting.
* **Comments + Posts** — Join on `post` ID to analyze which content drives the most engagement.
* **Multiple WordPress sites** — Use the **Append** transformation to stack posts or pages from two or more sites into a single unified dataset.

## Use cases by role

{% tabs %}
{% tab title="Content teams" %}

* Audit your full post library with status, author, and category in one spreadsheet
* Track publishing cadence — how many posts go live per week or month
* Identify pages that haven't been updated recently by sorting on the `modified` field
* Export comments to analyze reader sentiment or flag spam patterns
  {% endtab %}

{% tab title="Marketers" %}

* Combine WordPress posts data with Google Analytics in Coupler.io to connect content to traffic
* Export posts to ChatGPT or Claude for automatic SEO analysis, meta description generation, or content gap identification
* Monitor tag and category usage to ensure your taxonomy stays consistent over time
  {% endtab %}

{% tab title="Site administrators" %}

* Pull a plugins inventory to track which plugins are active, inactive, or need updates
* Audit user roles and capabilities to keep access permissions in check
* Monitor media library growth by exporting the Media entity and filtering by date
* Use the Settings entity to snapshot site configuration before making changes
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* The WordPress REST API must be publicly accessible for Coupler.io to connect. Security plugins that block REST API access will prevent the connection.
* If your site uses Cloudflare or another CDN/WAF, its bot protection may block Coupler.io requests and return a non-JSON error response.
* Custom post types created by plugins or themes are not included in the **Posts** entity by default — they appear under **Types** but may need custom API endpoints to retrieve their content.
* Application Passwords require WordPress 5.6 or later. On older versions, you'll need a plugin like "Application Passwords" to enable this feature.
* The `content` and `excerpt` fields in Posts and Pages return rendered HTML. If you need plain text, you'll need to strip HTML tags in your destination.

## WordPress common issues

### Connection issues

<details>

<summary>WordPress site is not connecting</summary>

The most common reasons a WordPress site fails to connect:

* **REST API is disabled** — some security plugins (like Wordfence or iThemes Security) have an option to disable the REST API for non-logged-in users. Check your security plugin settings and allow REST API access, or whitelist Coupler.io.
* **Wrong site URL** — make sure you're entering the root URL of your site (e.g., `https://yoursite.com`) and not a specific page URL.
* **Incorrect credentials** — double-check that you're using an **Application Password** (found under Users → Profile → Application Passwords in your WordPress admin), not your regular login password.
* **Site is on a local server or behind a VPN** — Coupler.io can only connect to publicly accessible URLs.

</details>

<details>

<summary>"Non-JSON response" error when connecting</summary>

This error usually means something is intercepting the API request before WordPress can respond — most commonly Cloudflare's bot protection or a WAF (web application firewall).

To fix this:

1. Log in to your Cloudflare dashboard and check your firewall rules for any rules that would block automated requests.
2. Temporarily disable "Bot Fight Mode" or "Under Attack Mode" and test the connection.
3. If you use a different security layer, look for rules blocking requests to `/wp-json/` endpoints and add an exception for Coupler.io.

{% hint style="warning" %}
Cloudflare and similar CDN services blocking the WordPress REST API (`/wp-json/`) is the most frequently reported connection error for WordPress in Coupler.io.
{% endhint %}

</details>

### Missing data

<details>

<summary>Only some posts are being imported — not all of them</summary>

The WordPress REST API paginates results, and by default Coupler.io fetches all pages. However, if your site has a very large number of posts, timeouts can interrupt the process.

* Check whether the missing posts have a specific status (draft, private, pending) — the API may only return published posts depending on your authentication level.
* Make sure your Application Password belongs to a user with sufficient permissions (Editor or Administrator) to read all post statuses.

</details>

<details>

<summary>The start date filter doesn't seem to work for Posts</summary>

The start date parameter applies only to **Pages, Comments, Media, and Editor blocks**. For Posts, Users, Categories, Tags, Taxonomies, Types, Themes, Statuses, and Settings, all records are always returned regardless of the date you set.

If you only want recent posts, filter by the `date` or `modified` column in your destination after the import.

</details>

<details>

<summary>New posts or pages aren't showing up after a refresh</summary>

If a scheduled or manual refresh isn't picking up new content, check:

* The data flow ran successfully (look for errors in the run log)
* Your destination sheet or table isn't being overwritten incorrectly — if you're using **Append** mode, duplicates may be hiding new rows
* The post status — newly created posts in "pending" or "draft" status may not be visible depending on the API user's role

</details>

### Permission errors

<details>

<summary>Getting a 401 or 403 error</summary>

A 401 error means authentication failed. Re-generate your Application Password from **Users → Profile → Application Passwords** and update it in Coupler.io.

A 403 error means the authenticated user doesn't have permission to access that resource. Switch to an Administrator-level Application Password to ensure full API access.

</details>

### Data discrepancies

<details>

<summary>Post content includes raw HTML instead of plain text</summary>

The `content` and `excerpt` fields return rendered HTML from the WordPress REST API. This is expected behavior. To work with clean text, use your destination's built-in functions to strip HTML tags (e.g., `REGEXREPLACE` in Google Sheets or a transformation step in BigQuery).

</details>

<details>

<summary>Categories and tags show as IDs, not names</summary>

The Posts entity returns category and tag IDs, not their display names. To resolve this, add the **Categories** and **Tags** entities as additional sources in your data flow and use the **Join** transformation to match IDs to names.

</details>

## WordPress FAQ

<details>

<summary>Does Coupler.io work with self-hosted WordPress sites?</summary>

Yes — Coupler.io connects to self-hosted WordPress sites via the REST API. Your site must be publicly accessible (not behind a VPN or local server). WordPress.com hosted sites may have more restricted API access depending on your plan.

</details>

<details>

<summary>What's an Application Password and where do I find it?</summary>

An Application Password is a separate credential you generate specifically for third-party integrations — it's not your regular WordPress login password. To create one, go to your WordPress admin, navigate to **Users → Profile**, scroll down to **Application Passwords**, enter a name (e.g., "Coupler.io"), and click **Add New Application Password**. Copy the generated password immediately — it won't be shown again.

Application Passwords require WordPress 5.6 or later.

</details>

<details>

<summary>Can I export only new posts or pages since the last sync?</summary>

Coupler.io always fetches all records for Posts (the start date filter doesn't apply to Posts). To work with only recent content, use the Append import mode so new records accumulate over time, or filter by the `date` or `modified` column in your destination after the import. For Pages and Comments, the start date filter is supported.

</details>

<details>

<summary>Can I connect multiple WordPress sites to the same data flow?</summary>

Yes. Add each WordPress site as a separate source in your data flow and use the **Append** transformation to combine their data into a single destination. This is useful for agencies or multi-site networks that want unified content reporting.

</details>

<details>

<summary>Why do my posts show category IDs instead of category names?</summary>

The WordPress REST API returns category and tag IDs in the Posts entity. To get the actual names, add the Categories and Tags entities as additional sources and use the **Join** transformation in Coupler.io to match IDs to their labels.

{% hint style="info" %}
See the [Data Overview](#wordpress-data-overview) for a full list of fields available in Posts, Categories, and Tags.
{% endhint %}

</details>

<details>

<summary>What happens if Cloudflare is blocking my WordPress connection?</summary>

Cloudflare's bot protection or WAF rules can intercept Coupler.io's requests to the WordPress REST API and return an HTML error page instead of JSON — which causes a "non-JSON response" error in Coupler.io. To fix this, log in to Cloudflare and either add a firewall rule to allow requests to `/wp-json/`, or temporarily disable Bot Fight Mode to test the connection.

{% hint style="info" %}
See [Common Issues](#wordpress-common-issues) for more detail on this error and how to resolve it.
{% endhint %}

</details>

<details>

<summary>Can I use WordPress data with AI tools like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can export your Posts or Comments entity directly to one of these destinations for tasks like content summarization, SEO analysis, sentiment analysis, or automatic tagging.

</details>

<details>

<summary>Why is the data refresh not working on a schedule?</summary>

A scheduled data flow requires a successful manual run first. If your refresh is silently failing, check the run log in Coupler.io for errors. Common causes include expired Application Passwords, a security plugin change on your WordPress site, or Cloudflare rules that started blocking the API after your initial setup.

{% hint style="info" %}
See [Common Issues](#wordpress-common-issues) for a full list of connection and permission troubleshooting steps.
{% endhint %}

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/marketing/wordpress-community.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
