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

# WordPress Connector

<Badge icon="arrow-left" color="gray">[Back to Search AI connectors list](/ai-for-service/searchai/content-sources#supported-connectors)</Badge>

The WordPress connector enables Search AI to ingest content from WordPress pages and posts, making that content available for search and answer generation.

| Specification     | Details      |
| ----------------- | ------------ |
| Repository type   | Cloud        |
| Supported content | Pages, Posts |
| RACL support      | Yes          |
| Content filtering | No           |

## Authorization Support

Search AI supports ingestion from both public and private WordPress sites. For private sites, WordPress uses **OAuth 2.0 authorization code grant type**. See the [WordPress OAuth documentation](https://developer.wordpress.com/docs/oauth2/) for details.

## Generating OAuth Client Credentials in WordPress

1. Go to the [WordPress developer page](https://developer.wordpress.com/apps).

2. Click **Create New Application**. Enter the following details.

   <img src="https://mintcdn.com/koreai/UwS79gPryFOfHx6d/ai-for-service/searchai/connectors/images/wordpress/OAuth-client.png?fit=max&auto=format&n=UwS79gPryFOfHx6d&q=85&s=5797ecb9a3fa75cacdc8850cf4463612" alt="OAuth Client" width="801" height="741" data-path="ai-for-service/searchai/connectors/images/wordpress/OAuth-client.png" />

   * **Name**: A name for the client (for example, *My App*).
   * **Redirect URLs**: The callback URL for authorization responses. Use the URL for your region or deployment:
     * JP Region: `https://jp-bots-idp.kore.ai/workflows/callback`
     * DE Region: `https://de-bots-idp.kore.ai/workflows/callback`
     * Prod: `https://idp.kore.com/workflows/callback`

3. Click **Create** to generate client credentials.

4. Copy and securely store the **Client ID** and **Client Secret** displayed on the next page. You will need these to configure the connector.

<img src="https://mintcdn.com/koreai/UwS79gPryFOfHx6d/ai-for-service/searchai/connectors/images/wordpress/client-credentials.png?fit=max&auto=format&n=UwS79gPryFOfHx6d&q=85&s=01d68b0d70e08375990e07f85234c132" alt="Client Credentials" width="1181" height="834" data-path="ai-for-service/searchai/connectors/images/wordpress/client-credentials.png" />

## Configuring the WordPress Connector in Search AI

1. Go to **Content > Connectors** and select the **WordPress Connector**.

2. Enter the following details:

   | Field                  | Description                                                                             |
   | ---------------------- | --------------------------------------------------------------------------------------- |
   | **Name**               | Unique name for the connector                                                           |
   | **Authorization Type** | Set to **Public** for publicly accessible sites; set to **OAuth 2.0** for private sites |
   | **Client Credentials** | Required only for OAuth 2.0 — provide the Client ID and Client Secret from WordPress    |
   | **Site URL**           | URL of the WordPress site to ingest content from                                        |

3. Click **Connect**. Once authenticated, the connector is ready to ingest pages and posts.

## Content Synchronization

Go to the **Configuration** tab and click **Sync Now** to ingest all accessible pages and posts immediately. Use **Schedule Sync** to set up recurring synchronization.

## Permissions and Access Control

* Public sites are accessible to all Search AI users.
* Private sites configured with **Public Access** in Search AI are accessible to all Search AI users, regardless of WordPress permissions.
* Private sites configured with **Permission Aware** access are accessible only to Search AI users who have access to the site in WordPress.

When switching from Permission Aware to Public Access, content becomes immediately accessible to all users. When switching from Public Access to Permission Aware, access information is fetched on the next sync. Trigger a manual sync for immediate effect.

For **public WordPress sites**, the `sys_racl` field is set to `*`. For **private sites**, the `sys_racl` field contains the identity information of team members added to the WordPress site. To view team members, go to the **Users** page on the site's dashboard.

<img src="https://mintcdn.com/koreai/UwS79gPryFOfHx6d/ai-for-service/searchai/connectors/images/wordpress/site-settings.png?fit=max&auto=format&n=UwS79gPryFOfHx6d&q=85&s=03eff82d6819ad376b6dcbc257493e97" alt="Access Control" width="1600" height="550" data-path="ai-for-service/searchai/connectors/images/wordpress/site-settings.png" />

<img src="https://mintcdn.com/koreai/UwS79gPryFOfHx6d/ai-for-service/searchai/connectors/images/wordpress/adding-users.png?fit=max&auto=format&n=UwS79gPryFOfHx6d&q=85&s=c3348cc5e791207d6b84eca6ce750adb" alt="Adding users" width="1061" height="532" data-path="ai-for-service/searchai/connectors/images/wordpress/adding-users.png" />

## Points to Note

* Comments and author information, if available for a page or post, are included as metadata fields in the ingested content and are also added to the chunk text.