Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Identity Auth / Google / Google Site Verification API
Google Site Verification API logo

Google Site Verification API

Browse all Google APIs
38
AI ReadinessNon-Ready (F)38/100
See full scorecard
Official vendor OpenAPI document · agent-readyIdentity 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.

Jentic One on GithubView OpenAPI Document

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fsiteverification" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fsiteverification" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

G

Google Site Verification API

- Non-Ready (F)
38/100
100
Foundational Compliance
56
Developer Experience & Jentic Compatibility
15
AI-Readiness & Agent Experience
94
Agent Usability
63
Security
63
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

15

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
60%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

63

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
62%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

63

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1
62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Google Site Verification API by hand means registering an OAuth client, walking users through the consent screen, and refreshing access tokens against the www.googleapis.com/siteVerification/v1 host yourself. Through Jentic you install once, import the Site Verification API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

Site Verification puts the web resource in the URL path (/webResource/{id}), so a rule can pin your agent to the resources you name: it can request tokens and read a resource and nothing else. You choose the operations it may call, so updating or deleting a web resource is not included unless you add it.

Credential isolation

Your Google OAuth credential for Site Verification is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'verify a domain via DNS TXT with Google' or 'get a verification token', and Jentic returns the matching Site Verification operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Search Console API

→

Reads search analytics and inspects URLs once a property has been verified via Site Verification.

Use Site Verification first to claim a property. Use Search Console afterwards to read or write data on it.

Complementary

Google Indexing API

→

Notifies Google about URL changes - also requires a verified site.

Use Site Verification to prove ownership. Use Indexing API to push URL change notifications afterward.

Complementary

Google Cloud DNS API

→

Adds the DNS TXT or CNAME records that Site Verification expects when using DNS-based methods.

Use Cloud DNS to programmatically place verification records. Use Site Verification to confirm them with Google.

Complementary

Google Analytics API

→

Often paired with verified sites for cross-property reporting.

Use Site Verification to claim a property. Use Analytics for on-site behaviour data once verified.

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the Google Site Verification API?

Yes. Because you run Jentic One yourself, your own rules decide which Site Verification operations and which OAuth credential the agent may use. Since the web resource sits in the URL path (/webResource/{id}), you can pin the agent to the resources you name and let it only request tokens and read a resource. Updating or deleting a web resource is not included unless you explicitly add those operations.

GET STARTED

Start building with Google Site Verification API

Explore with Jentic One
View OpenAPI Document