---
title: "List Pages"
method: GET
path: "/wordpress/sites/{site_id}/pages"
tags: ["wordpress"]
---

# List Pages

`GET /wordpress/sites/{site_id}/pages`

## Request

- Base URL: `https://api.xeorank.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.xeorank.com/wordpress/sites/{site_id}/pages`
- Auth: API key in header `X-Agent-Key`

List pages/posts/Elementor templates/Editor V4 components (post_type=elementor_component,
connector ≥ 0.9.18) on the connected WordPress site.

``search`` narrows by title or slug. It exists because agents overwhelmingly
arrive holding a URL — the user pastes one — and without it the only route
from URL to post_id was to page through the whole site and match by eye.
On a 150-page site that is several very large responses to learn one
integer, and it was previously accepted-and-ignored rather than rejected,
so the caller had no signal that the filter did nothing.

## Path parameters

- `site_id` string, uuid, required

## Query parameters

- `post_type` string
- `limit` integer
- `search` string, nullable: Match against title, slug or full URL. A URL is reduced to its last path segment, so a browser address can be pasted directly.
- `email` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/xeorank/apis/seo-intelligence-engine.md) · [All operations](https://skmtc.dev/xeorank/apis/seo-intelligence-engine/llms.txt) · [OpenAPI document](https://skmtc.dev/xeorank/apis/seo-intelligence-engine/revisions/449a3fd73454?raw)
