Property setup in Google Search Console
· 2 min read
Create and verify a Google Search Console property (URL-prefix or Domain) so gsc-indexer can inspect your URLs without 403 errors.
Before gsc-indexer can inspect anything, Google has to know you own the
site. This guide gets you a verified property.
What is a "property"?
In Google Search Console, a property is a website (or part of one) you've
proven you control. You can only inspect URLs that belong to a property you
have access to. If the URL's host doesn't match the property, you'll get a
403 You do not own this site error later. so get this right now.
Sign in to Search Console
- Go to search.google.com/search-console.
- Sign in with the Google account that manages your site.
Add your property
Click Add property.
Choose the URL-prefix property type (the other type, Domain, needs DNS access and is overkill here).
Enter the exact prefix, including
https://andwwwif you use it:https://www.toolsura.com/
Exact match matters.
https://toolsura.com/andhttps://www.toolsura.com/are different properties. Inspect the URL exactly as it appears in the property prefix, or you'll hit a 403.
Verify ownership
The easiest method for most sites is the HTML file upload:
- On the verification screen, pick HTML file.
- Download the file Google gives you (it looks like
google1234567890abcdef.html). - Upload it to the root of your site so it's reachable at
https://www.toolsura.com/google1234567890abcdef.html. - Click Verify.
Other options (HTML tag in <head>, Google Analytics, DNS record) work too. pick whichever you can complete.
Confirm it worked
You should land on the property dashboard. That's it. the property exists and you own it.
What's next
You still can't run the tool yet. GSC property access uses your Google login, but the CLI runs unattended and needs a service account instead. Continue to create a service account and grant it access.
Sources
- Google Search Console
- URL Inspection API documentation
- Google Search APIs overview
- Service account OAuth (Google Identity)
- About service accounts (Google Cloud IAM)
- Verify site ownership
- Property types: URL-prefix vs Domain
- URL Inspection tool help (request indexing)
- Indexing API (JobPosting/BroadcastEvent only)
Written by
Abhay Khant
Hi, I'm Abhay Thakor
I'm a developer, builder, and technology enthusiast interested in turning ideas into useful products.
I enjoy working across web development, cybersecurity, automation, SEO, and content creation. Rather than only learning technologies individually, I like putting them together to build things that people can use.
One of my main projects is Toolsura, a free online utility platform that brings practical tools into one place. I'm building Toolsura as a product and a learning project where I can explore development, infrastructure, SEO, content distribution, automation, and product growth.
What I Build
My work currently revolves around several areas:
Web development with Next.js, React, Tailwind CSS, and modern web technologies
Backend development with Go, APIs, databases, and server-side systems
Automation using n8n, APIs, Docker, and connected services
SEO and content systems for building organic search traffic
Cybersecurity including web security, bug bounty, SOC concepts, and malware analysis
Content creation including video editing, YouTube content, graphics, and promotional videos
I enjoy going beyond tutorials and experimenting with complete systems, from the frontend interface all the way to the backend, deployment, automation, and distribution.
Toolsura
Toolsura is one of the projects I'm most actively building.
The idea is simple: create useful, accessible online tools that solve small problems quickly.
Toolsura includes utilities for things such as text, JSON, URLs, PDFs, images, security checks, and other everyday technical tasks.
Building it has also become a practical way for me to learn how a modern web product works.
That means working on:
Product → Development → Infrastructure → SEO → Content → Distribution → Automation → Growth
Technology & Learning
I'm particularly interested in understanding how systems work rather than simply learning how to use them.
My development work has included technologies such as:
Next.js · React · TypeScript · Tailwind CSS · Go · Gin · GORM · PostgreSQL · MongoDB · Docker · RabbitMQ · MinIO · Strapi
I've also worked with Linux environments and tools such as Kali Linux, Termux, and related security tooling.
My cybersecurity interests include web application security, bug bounty research, SOC analysis, and malware analysis.
Building in Public
I also create content around the things I build and learn.
This includes:
Tutorials and technical articles
YouTube videos
Product demonstrations
Visual explainers
Promotional videos
SEO-focused educational content
My goal is to turn projects and experiments into useful resources that other people can learn from.
Why I Build
For me, building is one of the best ways to learn.
Instead of learning a technology in isolation, I prefer starting with a real problem and figuring out what is required to solve it.
Sometimes that means writing code. Other times it's debugging a deployment at midnight, or working out why a page isn't being indexed, why an API isn't behaving correctly, or how to automate something that would otherwise take hours.
Those problems are part of the process.
Every project gives me another opportunity to understand how technology works in the real world.
What I'm Working Toward
I'm continuing to develop my skills across software engineering, cybersecurity, automation, and digital products.
At the same time, I'm building Toolsura into a useful platform and experimenting with different ways to create, distribute, and grow technical products.
There is still a lot to learn, but that's exactly what makes building interesting.
Let's Connect
If you're interested in web development, cybersecurity, automation, SEO, online tools, or building products, feel free to connect.
I'm always interested in learning, experimenting, and building something useful.
Build. Learn. Improve. Repeat.