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

# Saved page reviews

> Request a review when saving an Erdo page, then read its complete findings.

Set `request_review: true` when creating or updating an Erdo page to check its layout,
forms and compliance copy with the page's judge lenses. The save returns a `review`
object containing `id`, `page_id`, and `status: "running"` before browser capture,
Lighthouse and the judges finish. The page is already saved.

Use the CLI for a material edit to a live page:

```bash theme={null}
erdo pages update <page-id> --html @page.html --request-review
```

The CLI prints the review ID, waits for it, then displays all issues and available
mobile Lighthouse scores. Each issue carries severity, category, description and a
suggested fix. An unavailable Lighthouse category stays absent.

To return immediately, add `--no-wait`. Read the result later without running another review:

```bash theme={null}
erdo pages update <page-id> --html @page.html --request-review --no-wait
erdo pages review <page-id>
erdo pages review <page-id> --review-id <review-id> --wait
```

`erdo pages deploy` also accepts `--request-review` and `--no-wait`. Each explicit
request gets its own ID, including another request for unchanged content. Re-reading
an existing ID does not run the judges again.

## REST and MCP

Create with `POST /v1/pages` or update with `PUT /v1/pages/:pageID`, including
`request_review: true`. Read the latest explicit review using:

```http theme={null}
GET /v1/pages/review/:pageID
GET /v1/pages/review/:pageID?review_id=<review-id>
```

The MCP tools are `erdo_deploy_page`, `erdo_update_page`, and
`erdo_get_page_content_review`. The reader takes `page_id` and an optional `review_id`.
Reads require access to the page in its owning organization. A review ID belonging
to another page or organization is not returned.

The review moves from `running` to `ready` or `failed`. A `ready` review contains
`result`, with the full `issues`, `summary`, `judges` and available `lighthouse`
measurements. A page without applicable lenses returns `result.reviewed: false`
with a `reason`. A `failed` review contains `error` and `completed_at`. Reviews
interrupted by a server restart become readable failures after twenty minutes;
request a new review to try again. The CLI exits unsuccessfully when a review fails.

The in-chat builder and edit tools continue to receive findings inline so they can
repair the page in the same turn. Reviews requested through page saves use the
same judges and do not open a separate Activity item.

For reviews of external URLs, use [Page reviews](https://docs.erdo.ai/page-reviews.md).


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