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

# Start Google Verification

> Get a TXT verification token from Google Site Verification API

<Warning>
  **Account Limit**: Each Google account can only manage up to **1,000 websites** in Search Console at any given time. This is a hard limit enforced by Google.
</Warning>

## Overview

This endpoint initiates Google Search Console verification by requesting a TXT verification token from Google's Site Verification API.

Call this endpoint in **parallel** with `/start-certificate` to get both TXT records for the user to add via Entri.

## Path Parameters

<ParamField path="org_id" type="string" required>
  The Clerk organization ID (e.g., `org_xxx`)
</ParamField>

## Response

<ResponseField name="status" type="string">
  `success` or `error`
</ResponseField>

<ResponseField name="txt_record" type="object">
  The TXT record to add for Google verification

  <Expandable title="properties">
    <ResponseField name="name" type="string">
      The TXT record name (usually `@` for apex domain)
    </ResponseField>

    <ResponseField name="value" type="string">
      The TXT record value (e.g., `google-site-verification=abc123...`)
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="message" type="string">
  Error message if status is `error`
</ResponseField>

## Example Response

```json theme={null}
{
  "status": "success",
  "txt_record": {
    "name": "@",
    "value": "google-site-verification=abc123xyz789"
  }
}
```

## Database Updates

On success, the following columns are updated in `ai_sites`:

* `google_verification_token`: The verification token
* `google_verification_status`: Set to `PENDING`