ARTICLE
Notes

Why does Search Console return 403 when the site is verified?

19 November 2026Majed Alandajani

I wanted to pull search numbers into my panel. The account was connected and the scope granted, and Search Console showed the site as verified.

The result: 403, with no useful message.

The cause

Search Console registers a site in one of two forms.

A domain property, sc-domain:example.com, covers the domain along with every subdomain and every protocol under it.

A URL prefix, https://example.com/, covers exactly that URL.

My requests carried the URL form while the site was registered as a domain property. Seen from the API's side, the 403 is honest: the account has permission on the site as a whole, and no permission on the specific form my request named.

The fix I applied

Do not guess the form. Ask for it.

The API exposes an endpoint that lists every property the account holds. Call it and match the returned properties against your host; whatever the listing gives you is the value to send.


ask:   which properties do I hold?
match: which one covers my domain?
use:   what came back, not what you expected

An improvement I added

Cache the result so the listing call does not run on every request.

Clear that cache as soon as it stops working. A property that was once correct can be removed or changed later, and a cache with no invalidation keeps failing forever against a value that was right once.

The wider lesson

A 403 with no detail usually means the resource you named is in a form the other side does not recognise.

Whenever an API accepts an identifier in more than one shape, there is often also a call that returns the correct one; request that before constructing anything yourself. Here it came down to one extra line, after an hour of guessing.

Related reading

Have a project in mind?
Tell me what you want to build. Your first 15 minutes of consulting are free.
Book a consultation