WordPress

The WordPress connector indexes content from WordPress sites so people can search public pages, posts, comments, tags, and categories in Glean. It brings WordPress content and selected metadata into Glean for enterprise search. The integration targets published, public-facing content.

Supported features

The connector crawls content exposed through the WordPress REST API. Only published and publicly accessible content is indexed. Restricted WordPress content is not permission-enforced in Glean in this version: everyone in your Glean organization can see everything that was indexed.

Supported objects

• Pages (published, public)
• Posts (published, public)
• Comments (attached to posts and pages)
• Tags
• Categories
• Custom posts (requires manual endpoint configuration)

Supported API endpoints

• /pages: Page content and metadata
• /posts: Post content and metadata
• /comments: Comments on pages and posts
• /tags: Tag metadata for posts and pages
• /categories: Category metadata

Custom post types are supported if you enter their REST endpoints manually in the Glean connector configuration.

Limitations

• Only published content that is not password-protected or private is crawled. Drafts, password-protected items, and private posts or pages are not indexed.
• No permission propagation: indexed content is visible to all Glean users in the organization, regardless of WordPress role-based access.
• Nested categories are not fully supported for faceting; only directly assigned categories are indexed.
• No author attribution: the connector does not attach or surface author information in indexed documents (names, emails, or IDs).
• Activity data (for example view counts) is not supported in the initial version.
• Popularity-based ranking, private content, and per-user visibility are not part of this connector.

Requirements

Technical requirements

• The WordPress site must be reachable over the internet (publicly or through allowlisted IP ranges if you use network restrictions).
• The WordPress REST API must be enabled and reachable.
• WordPress 5.6 or later is required for application passwords.

Credential requirements

• Access to a WordPress Administrator account to create an application password.
• The application password and matching WordPress username for Glean to call the API.
• The WordPress site hostname for connector configuration.

Permission requirements

• Creating application passwords requires a WordPress administrator account (or another account with sufficient privileges).
• Because the connector only crawls public content, Glean does not map WordPress roles or per-user visibility.

Configuration and setup

You configure the WordPress connector in the Glean Admin console. You gather credentials and hostname from WordPress, then enter them in the connector.

Prerequisites

• A running WordPress site (version 5.6 or later)
• WordPress admin access
• Glean Admin console access

Authentication and credentials

1. In WordPress, sign in as an administrator, open the user profile, and create a new Application password for Glean.
2. Save the new application password and the associated username.
3. In the Glean Admin console, enter the WordPress site hostname, that username, and the application password in the WordPress connector fields.

Setup instructions

1. Sign in to WordPress as an administrator and open your user profile.
2. Create an Application password used only for Glean.
3. Store the application password and username securely.
4. Open the Glean Admin console and select Add Connector → WordPress.
5. Enter the following:
   • WordPress site hostname (for example, docs.example.com)
   • Application password (from step 3)
   • Username (from step 3)
6. (Optional) To crawl custom post types, add the REST API endpoints for those types in the connector settings.
7. Save the configuration and run a crawl or test to confirm authentication.