Google Site Verification API
Browse all Google APIs✓ Official Vendor SpecIdentity AuthIdentity Verificationoauth27 EndpointsREST
For Agents
Prove ownership of websites and DNS domains to Google so they can be claimed in Search Console, Analytics, and other Google products.
Use for: Verify ownership of example.com via DNS TXT record, Get the meta tag I need to place on my homepage to verify the site, List every site I have verified with my Google account, Add another email address as an owner of a verified property
Not supported: Does not handle search analytics, URL indexing, or DNS record creation — use for proving and managing site or domain ownership with Google only.
The Google Site Verification API lets owners prove control over a website or DNS domain so that Google services like Search Console, Analytics, AdSense, and Webmaster Tools recognise them as the verified owner. Agents request a verification token (HTML file, meta tag, DNS TXT, or DNS CNAME), place it on the property, and then call insert to verify ownership. Verified resources can be listed, retrieved, updated, and deleted, and ownership can be shared with other Google accounts.
Install Jentic One Beta
Connect the Google Site Verification API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Google Site Verification API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Google Site Verification API.
Request a verification token in any of four formats: HTML file, HTML meta tag, DNS TXT, or DNS CNAME
Verify ownership of a website or domain by calling insert after placing the token
List every webResource the authenticated user has verified
Retrieve a single verified webResource to see owners and verification method
Update or replace owner sets on a verified resource to share ownership
Delete a verification record when a property is no longer owned
Use Cases
Patterns agents use Google Site Verification API for, with concrete tasks.
★ Search Console Onboarding Automation
When platforms onboard customer websites to Google Search Console, they automate Site Verification first. The flow is: call getToken to obtain a DNS TXT or HTML meta token, instruct the customer to place it, then call insert to verify. Once verified, the platform can also call the Search Console API on behalf of the customer.
Call POST /token with verificationMethod='DNS_TXT' for site type=INET_DOMAIN, then once the customer places the record call POST /webResource with the matching identifier.
Multi-Property Ownership Audit
Agencies and platforms managing many properties periodically list every verified webResource, cross-reference against the customer roster, and surface any properties that should be unclaimed. The API exposes list, get, and delete on webResources so this audit can run end to end without UI scraping.
Call GET /webResource to list every verified site, then for each one decide whether to call DELETE /webResource/{id} based on the current customer list.
Co-Ownership Management
Add or remove co-owners on a verified property without re-verification. The update and patch operations on a webResource accept a new owners array, which is useful when team members change or when a managed-services provider hands ownership back to the end customer.
Call PATCH /webResource/{id} with owners=['old@example.com','new@example.com'] to add a co-owner without disturbing the verification token.
AI Agent Property Manager
An AI agent acts as a property manager for an SEO or marketing platform — verifying customer sites, watching for failed verification (token removed), and re-running verification when DNS changes. Through Jentic the agent searches by intent and never holds the customer's Google OAuth refresh tokens directly.
On a webhook from a customer's DNS provider, call POST /webResource for the affected domain to re-run verification and notify the customer of the result.
Key Endpoints
7 endpoints — the google site verification api lets owners prove control over a website or dns domain so that google services like search console, analytics, adsense, and webmaster tools recognise them as the verified owner.
METHOD
PATH
DESCRIPTION
POST
/token
Request a verification token in a chosen format
POST
/webResource
Verify a site after placing the token
GET
/webResource
List every verified site for the user
GET
/webResource/{id}
Retrieve a specific verified resource
PATCH
/webResource/{id}
Update owners on a verified resource
DELETE
/webResource/{id}
Delete a verification record
POST
/token
Request a verification token in a chosen format
POST
/webResource
Verify a site after placing the token
GET
/webResource
List every verified site for the user
GET
/webResource/{id}
Retrieve a specific verified resource
PATCH
/webResource/{id}
Update owners on a verified resource
DELETE
/webResource/{id}
Delete a verification record
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Customer Google OAuth refresh tokens are stored encrypted in the Jentic MAXsystem vault. Agents receive only a short-lived scoped access token at execution and never see the customer's long-lived refresh token, even when running batches of verifications.
Intent-based discovery
Agents search Jentic by intent (e.g. 'verify a domain via dns txt with google') and Jentic returns the matching token and webResource operations with their input schemas, so the agent does not have to navigate the verification token model from docs.
Time to first call
Direct integration: 1-2 days to handle OAuth, token placement instructions, and verification retries. Through Jentic: under 30 minutes — search, load, execute, with credential isolation handled at the SDK layer.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Google Site Verification API through Jentic.
What authentication does the Google Site Verification API use?
The API uses OAuth 2.0 with the siteverification or siteverification.verify_only scope. Through Jentic the OAuth client and refresh tokens are stored encrypted in MAXsystem and a scoped token is provided at execution.
Which verification methods does the API support?
Four methods: an HTML file uploaded to the site root, an HTML meta tag in the homepage head, a DNS TXT record on the domain, and a DNS CNAME record on the domain. Site type INET_DOMAIN supports DNS methods; SITE supports the HTML methods.
What are the rate limits for the Google Site Verification API?
Google enforces a default per-project quota of around 100 queries per second and reasonable daily caps; verification calls are typically infrequent so most callers stay well under the limits. Quotas can be raised via the Cloud Console quota page.
How do I verify a site through Jentic?
Run the Jentic search query 'verify ownership of a site with google', load POST /token to fetch the token, place it on the site or in DNS, then load POST /webResource to confirm verification. Jentic injects the OAuth token at execution.
Can I add multiple owners to a verified site?
Yes. PATCH /webResource/{id} or PUT /webResource/{id} with an updated owners list lets you add or remove co-owners. The verification token itself does not need to be replaced.
Does the API support sub-paths or only full origins?
Site verification covers a full HTTP origin (scheme + host) for SITE type and a full registrable domain for INET_DOMAIN. Sub-path verification is not supported; granular access is handled at the Search Console level instead.
GET STARTED