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

# Trigger a page crawl

> Queue a URL for immediate crawling so a change you just published is audited right away.



## OpenAPI

````yaml other-apis/monitoring/openapi.json POST /v1/check_url
openapi: 3.0.3
info:
  title: Conductor Monitoring APIs
  description: >-
    Complete collection for all Conductor Monitoring APIs.


    ## The 3 API Tokens


    | Token Variable | API | Purpose |

    |---|---|---|

    | `reporting_api_token` | Reporting API v1 + v2 | READ — extract SEO data,
    stats, pages, issues, alerts |

    | `cms_api_token` | CMS API v1 | WRITE — trigger immediate page re-crawl
    after publishing |

    | `enrichment_api_token` | Data Enrichment API v1 | WRITE — push custom
    field values (revenue, owner, etc.) into pages |


    All tokens found under: ****Account** > **Account** tab > **Integration
    Tokens****


    ## Rate Limits

    - Reporting API: 6 req/sec/IP (429 for 1 min if exceeded)

    - Data Enrichment API: max 1,000 URLs/request, 1 req/sec/website
  version: 1.0.0
servers:
  - url: https://api.cm.conductor.com
security: []
tags:
  - name: Reporting API v2 - Entities
    description: |-
      Current version — use this for all new integrations.
      Token: reporting_api_token
      Purpose: Read-only SEO data extraction.
  - name: Reporting API v2 - Data
    description: |-
      Current version — use this for all new integrations.
      Token: reporting_api_token
      Purpose: Read-only SEO data extraction.
  - name: Reporting API v2 - Alerts
    description: |-
      Current version — use this for all new integrations.
      Token: reporting_api_token
      Purpose: Read-only SEO data extraction.
  - name: Reporting API v1 (Legacy)
    description: >-
      Original Reporting API — will be deprecated. Same reporting_api_token as
      v2.


      Key differences from v2:

      - website_id is a URL path segment, not a query param

      - Has /gds (Google Data Studio) and /metrics endpoints not in v2

      - No LFA endpoint

      - Fewer response fields


      Migrate to v2 when possible.
  - name: CMS API v1
    description: >-
      Trigger immediate re-crawls when content is published.

      Token: cms_api_token (separate from Reporting API)

      Typical use: call from CMS publish hooks (WordPress, Contentful, Drupal,
      etc.)
  - name: Data Enrichment API v1
    description: >-
      Push custom data into Conductor Monitoring pages.

      Token: enrichment_api_token (separate from Reporting and CMS APIs)


      Use cases: revenue per page, page owner, qualified leads, content score,
      last reviewed date.


      Setup:

      1. **Settings** > **Enrichment Fields** > **Create Enrichment Field**

      2. Choose type: string, number, boolean, or date

      3. Copy the Enrichment Field ID for use in requests


      Rate limits: max 1,000 URLs/request, 1 req/sec/website


      Once pushed, enrichment data can be used to:

      - Filter pages

      - Create segments

      - Set change alerts

      - View in page detail
paths:
  /v1/check_url:
    post:
      tags:
        - CMS API v1
      summary: Trigger Page Crawl (check_url)
      description: >-
        Queues the given URL for immediate crawl.


        URL must be absolute (include https://) and belong to a website
        registered in your account.


        Responses:

        - 200 {status: ok} — crawl queued

        - 400 — invalid URL or website not in account

        - 401 — bad token

        - 422 — malformed Authorization header
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - url
              properties:
                url:
                  type: string
                  format: uri
            example:
              url: https://www.example.com/url-to-check/
      responses:
        '200':
          description: Crawl queued.
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    example: ok
              example:
                status: ok
        '400':
          description: Invalid URL or website not in account.
        '401':
          description: Bad token.
        '422':
          description: Malformed Authorization header.
      security:
        - cmsApiToken: []
components:
  securitySchemes:
    cmsApiToken:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Send your CMS API token as `Authorization: token {cms_api_token}` — the
        literal string `token`, a space, then the token itself. Find it in
        Conductor Monitoring under **Account** > **Account** tab > **Integration
        Tokens**.

````