How do I mock the Google Search Console API locally?

Install stunt, add a one-service block to stunt.yaml (adapter: embedded:gsearchconsole-style), and run stunt up. You get a local, stateful stand-in for Google Search Console API v1 — 11 routes over rest — with no remote account, no network, and no bills.

Is the Google Search Console API mock data synthetic?

Yes — entirely. The adapter returns generated data only; stunt's adapter lint rejects real-looking secrets and PII at build time. It simulates the shape and behavior of Google Search Console API (routes, status codes, pagination, webhooks), never real records.

← all adapters

gsearchconsole-style

simulates Google Search Console API v1

restadapter v0.2.011 routes

verification

SDKverified with google-api-go-client v0.293.0· surface 11 · not implemented 2 · differs 4

use it

# add to stunt.yaml
services:
  gsearchconsole:
    adapter: embedded:gsearchconsole-style

# then
$ stunt up

The embedded: source extracts this adapter from the binary — no git clone, fully offline.

how to mock the Google Search Console API locally

Install stunt, paste the service block above into stunt.yaml, run stunt up — then point your client at localhost instead of Google Search Console API. It works offline, keeps state across requests and restarts, and every response is synthetic: the route shapes, status codes, pagination, and webhook delivery follow the real Google Search Console API v1 surface — the data is fake, the behavior is real.

backing stores

sites

api surface (11)

generated from the adapter manifest — exactly what boots, nothing more · covers 90% of the real API's 11 routes (derived from sdk google-api-go-client @ v0.293.0)

11 routes

GET/webmasters/v3/sites

GET/webmasters/v3/sites/{siteUrl}

PUT/webmasters/v3/sites/{siteUrl}

DELETE/webmasters/v3/sites/{siteUrl}

POST/webmasters/v3/sites/{siteUrl}/searchAnalytics/query

GET/webmasters/v3/sites/{siteUrl}/sitemaps

GET/webmasters/v3/sites/{siteUrl}/sitemaps/{feedpath}

PUT/webmasters/v3/sites/{siteUrl}/sitemaps/{feedpath}

DELETE/webmasters/v3/sites/{siteUrl}/sitemaps/{feedpath}

POST/v1/urlInspection/index:inspect

POST/webmasters/v3/sites/{siteUrl}/inspect

SDK-verified behaviors (7)

✓Sites.List returns the seeded properties
✓Sites.Get returns the property with permissionLevel
✓Sites.Add starts unverified and lists immediately
✓Searchanalytics.Query returns keyed metric rows
✓Sitemaps.Submit + List round-trip
✓UrlInspection.Index.Inspect returns an index-status verdict
✓Unknown site Get -> googleapi 404

Not implemented (2)

16-month window not modeled; ranges derive at most 90 days / ~1800 cells
No country dimension in search analytics

Differs from the real API (4)

Regex filters (includingRegex/excludingRegex) degrade to equals/notEquals
Site verification completes ~2s after sites.add via derive-on-read clock
Inspection verdicts keyed to magic path tokens (noindex, soft404, servererror)
URL-prefix sites/sitemaps addressed by single-segment paths (decoded routing)

full scorecard →

want more of the Google Search Console API surface? adapters are YAML + Starlark — the authoring guide covers adding routes, fixtures, and state machines. Open an issue for anything big first, or just file a PR — merged routes ship in the next release.