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

# Submit a page for indexing

> Notifies Google via the Indexing API that a URL has been added/updated (`URL_UPDATED`) or removed (`URL_DELETED`).

**Requires:** A Google Search Console connection with the `indexing` OAuth scope, and the connected account must be a **verified owner** of the property. If the current connection predates indexing support, reconnect from the RankSpot dashboard (Integrations → Google Search Console) to grant the scope.

**Note:** A successful response means Google received the notification — it does not guarantee or immediately confirm indexing. Use `POST /gsc/inspect` afterwards to check status.



## OpenAPI

````yaml https://api.rankspot.ai/docs-json post /v1/gsc/index
openapi: 3.0.0
info:
  title: RankSpot Public API
  description: >-
    The RankSpot Public API gives you programmatic access to your workspace data
    — keywords, backlinks, competitors, content topics, articles, and more.


    ## Authentication


    All endpoints require a Bearer API key in the `Authorization` header:


    ```

    Authorization: Bearer <your-api-key>

    ```


    Generate API keys from **Settings → API Keys** in the RankSpot dashboard.
    Each key is scoped to a single workspace.


    ## Pagination


    List endpoints return a consistent envelope:


    ```json

    {
      "data": {
        "total": 120,
        "offset": 0,
        "limit": 20,
        "count": 20,
        "items": [...]
      }
    }

    ```


    Use `offset` and `limit` query parameters to paginate. Default limit is
    **20**, maximum is **100**.


    ## Status codes


    | Code | Meaning |

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

    | 200  | Success |

    | 201  | Created |

    | 204  | No content (delete / unarchive) |

    | 400  | Validation error or business rule violation |

    | 401  | Missing or invalid API key |

    | 404  | Resource not found or belongs to another workspace |
  version: '1.0'
  contact: {}
servers:
  - url: https://api.rankspot.ai
    description: Production
security: []
tags:
  - name: Articles
    description: >-
      AI-generated blog articles. Articles are created automatically when a
      topic is sent to generation — they cannot be created directly via the API.
  - name: Backlinks
    description: >-
      Backlinks discovered for your domain and your competitors' domains.
      Backlinks are auto-synced on a background interval and cannot be created
      via the API.
  - name: Categories
    description: Categories for organising topics and articles within your workspace.
  - name: Competitors
    description: >-
      Competitor domains tracked in your workspace. Once added, keywords and
      backlinks for each competitor are fetched asynchronously on a background
      sync interval.
  - name: Forum Opportunities
    description: >-
      Forum threads and community posts surfaced as potential link-building or
      engagement opportunities.
  - name: Keywords
    description: >-
      SEO keywords tracked in your workspace, enriched with search volume,
      competition, and AI-generated relevance scores.
  - name: People Also Ask
    description: >-
      "People also ask" questions discovered from search results for your
      tracked keywords.
  - name: Topics
    description: >-
      Content topic ideas that can be turned into articles. Create topics
      manually or let RankSpot generate them from your keyword clusters.
  - name: Search Console
    description: >-
      Google Search Console performance data — clicks, impressions, CTR, and
      average position for your connected property. Requires GSC to be connected
      from the RankSpot dashboard.
paths:
  /v1/gsc/index:
    post:
      tags:
        - Search Console
      summary: Submit a page for indexing
      description: >-
        Notifies Google via the Indexing API that a URL has been added/updated
        (`URL_UPDATED`) or removed (`URL_DELETED`).


        **Requires:** A Google Search Console connection with the `indexing`
        OAuth scope, and the connected account must be a **verified owner** of
        the property. If the current connection predates indexing support,
        reconnect from the RankSpot dashboard (Integrations → Google Search
        Console) to grant the scope.


        **Note:** A successful response means Google received the notification —
        it does not guarantee or immediately confirm indexing. Use `POST
        /gsc/inspect` afterwards to check status.
      operationId: GscController_requestIndexing
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/GscIndexUrlDto'
      responses:
        '201':
          description: >-
            The raw `urlNotificationMetadata` from the Indexing API.
            `latestUpdate`/`latestRemove` are only present once Google has
            processed prior notifications for the URL.
          content:
            application/json:
              schema:
                example:
                  url: https://example.com/blog/my-post
                  latestUpdate:
                    url: https://example.com/blog/my-post
                    type: URL_UPDATED
                    notifyTime: '2026-06-21T12:00:00Z'
      security:
        - bearer: []
components:
  schemas:
    GscIndexUrlDto:
      type: object
      properties:
        url:
          type: string
          example: https://example.com/blog/my-post
          description: >-
            The fully-qualified URL to notify Google about. Must belong to a
            property you own.
        type:
          type: string
          enum:
            - URL_UPDATED
            - URL_DELETED
          default: URL_UPDATED
          description: >-
            URL_UPDATED to (re)index a new or changed page, URL_DELETED to
            request removal.
      required:
        - url
  securitySchemes:
    bearer:
      scheme: bearer
      bearerFormat: JWT
      type: http

````