Web Search Indexing API

Name: Web Search Indexing API API
Brand: Web Search Indexing API
Availability: InStock

✓ Official Vendor SpecMarketingSeo Semoauth22 EndpointsREST

For Agents

Notify Google Search to crawl new or updated URLs and read the latest notification metadata. Useful for keeping job postings and live event pages current in search results.

Quickstart

Get started with Web Search Indexing API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"notify google search to recrawl a url"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Web Search Indexing API API.

Push URL_UPDATED notifications when a job posting or BroadcastEvent page is created

Push URL_DELETED notifications when a job posting or BroadcastEvent page is taken down

Retrieve the timestamp and type of the last notification submitted for a given URL

Trigger faster recrawls of supported page types without waiting for organic discovery

GET STARTED

Start building with Web Search Indexing API API

Explore with Jentic

View OpenAPI Document

Use for: I need to notify Google that a new job posting page is live, I want to tell Google a job listing has been removed, Check whether a URL has already been submitted to the Indexing API, Get the metadata for the last indexing notification on a page

Not supported: Does not handle sitemap submission, search analytics, or arbitrary page types — use only to push URL_UPDATED and URL_DELETED notifications for JobPosting and BroadcastEvent pages.

Use Cases

Patterns agents use Web Search Indexing API API for, with concrete tasks.

★ Time-sensitive job posting indexing

Career sites and job boards can call the Indexing API every time a posting is created, updated, or closed so Google Search reflects the change within hours rather than waiting for the next crawl. Each change is published with a URL_UPDATED or URL_DELETED notification on the urlNotifications:publish endpoint, which keeps Google's job posting structured data current.

Submit a URL_UPDATED notification for https://example.com/jobs/123 and confirm the response includes the new notifyTime.

Live broadcast event publication

Streaming platforms publishing pages with BroadcastEvent structured data use the Indexing API to inform Google when a live event page goes up and when it ends. Publishing a notification on the v3/urlNotifications:publish endpoint reduces the lag between event start and search visibility, which matters for short-window content.

Publish a URL_UPDATED notification for a livestream page and verify the urlNotificationMetadata returns latestUpdate.type=URL_UPDATED.

Indexing audit and resubmission

SEO teams use GET /v3/urlNotifications/metadata to verify whether a URL was successfully submitted, when, and with what notification type. This supports audits of indexing pipelines and lets agents detect URLs that need to be republished after a content change.

Call GET /v3/urlNotifications/metadata?url=https://example.com/jobs/123 and report latestUpdate.type and notifyTime.

Agent-driven indexing automation via Jentic

An agent listening to a job posting database can call the Indexing API through Jentic whenever a row changes. Jentic handles the OAuth 2.0 service account flow and exposes the publish operation as a single MCP tool, so the agent only needs to pass the URL and notification type.

From a webhook indicating a new job, call google_indexing_publish_url with type=URL_UPDATED for the new posting URL.

Key Endpoints

2 endpoints — the web search indexing api lets site owners notify google search when pages are added, updated, or removed so the index can be refreshed faster than crawl-based discovery.

METHOD

PATH

DESCRIPTION

POST

/v3/urlNotifications:publish

Publish an update or removal notification for a URL

GET

/v3/urlNotifications/metadata

Retrieve metadata for the latest notification on a URL

POST

/v3/urlNotifications:publish

Publish an update or removal notification for a URL

GET

/v3/urlNotifications/metadata

Retrieve metadata for the latest notification on a URL

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Indexing API service account JSON keys are stored encrypted in the Jentic vault. Agents receive a short-lived OAuth 2.0 access token scoped to https://www.googleapis.com/auth/indexing — the private key never enters the agent context.

Intent-based discovery

Agents search Jentic with phrases like 'notify google of url change' and Jentic returns the urlNotifications:publish operation with its full input schema, so the agent can build the request without reading Google's docs.

Time to first call

Direct integration: 4-8 hours to set up the service account, grant Search Console access, and implement the OAuth flow. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Search Console API

Search Console reports on impressions, clicks, and indexing status; Indexing API pushes change notifications

Use Search Console when the agent needs performance data or sitemap status; use Indexing API when it needs to push a recrawl request.

Complementary

Custom Search API

Custom Search returns programmable search results; Indexing API controls when pages enter the Google index

Use Custom Search to query Google for results; use Indexing API to make sure new pages appear in those results faster.

Complementary

Cloud Talent Solution API

Cloud Talent Solution stores and searches job postings; Indexing API tells Google Search the postings exist

Use Cloud Talent Solution to manage job content; pair with Indexing API to surface those jobs in Google Search.

FAQs

Specific to using Web Search Indexing API API through Jentic.

What authentication does the Web Search Indexing API use?

The API uses OAuth 2.0 with the https://www.googleapis.com/auth/indexing scope, typically issued to a Google service account that has been granted Owner permission for the property in Search Console. Through Jentic the OAuth credentials live in the encrypted vault and the agent receives a scoped access token at call time only.

Which page types are supported by the Web Search Indexing API?

Google currently supports the API for pages with JobPosting structured data and pages with BroadcastEvent embedded in a VideoObject. Submitting other page types is allowed but will not trigger faster crawling, and Google may ignore those notifications.

What are the rate limits for the Web Search Indexing API?

Google enforces a default daily quota of 200 publish requests and 180 metadata requests per project, with a burst limit of around 600 requests per minute. Quota increases can be requested via the Google Cloud console for high-volume careers sites.

How do I submit a URL update through Jentic?

Run jentic search 'notify google to recrawl a url' to find the publish operation, jentic load to fetch its input schema, then jentic execute with body {"url": "https://example.com/jobs/123", "type": "URL_UPDATED"} which calls POST /v3/urlNotifications:publish.

Can I check whether a URL was already submitted?

Yes. Call GET /v3/urlNotifications/metadata with the url query parameter and the response includes latestUpdate and latestRemove timestamps, so an agent can decide whether to resubmit.

Is the Web Search Indexing API free to use?

The API itself has no per-call charge — costs are governed only by the Google Cloud project quotas. The service account and Search Console verification are also free.