Search Console
- Everything up to the click
- What Google crawled and indexed
- The searches you appeared in
- Technical faults Google found
- Manual actions and security warnings
Google Search Console
See your site the way Google does
Search Console is the only place Google tells you directly what it found on your site, what it kept, and what people searched to reach you. Without it you are guessing about your own pages.
Google Search Console is a free tool that shows how Google itself crawls, indexes and ranks your site. It reports which pages made it into the index, which did not and why, which searches your pages appeared in, and what people clicked. It is the only direct line you have to Google's own view of your site.
Setting it up is quick. Reading it correctly is the actual skill, because a good half of what it flags is not a problem, and a few of the quietest lines in it are the ones costing you work.
What Search Console tells you that nothing else can
Every other tool is inferring. This one is reporting.
Whether your pages are actually in Google
Not whether they rank: whether they exist as far as Google is concerned. A page that is not indexed cannot rank for anything, at any price, no matter how good it is. This is the first thing worth knowing and the thing owners most often assume rather than check.
Which searches you already appear in
Real queries, with impressions and clicks, from the actual results. This is the least fictional keyword data you will ever get, because it is not an estimate of what people might search. It is what they did search, and what happened when your page showed up.
The useful pattern here is rarely the top row. It is the queries where you appear but nobody clicks, and the ones where you are just off the visible results. Those tell you which pages are nearly working, which is where effort pays best. That work is local SEO or content, not a Search Console setting.
What Google hit when it tried to read your site
Server errors, pages blocked from crawling, redirect chains, mobile rendering faults, and structured data it could not parse. These are the faults technical SEO exists to fix, and this is where they surface first.
Whether something has gone badly wrong
Manual actions and security issues both land here, and nowhere else. If Google has penalised your site or flagged it as hacked, this is where you find out. Not having the property verified means not finding out.
Verification: use a domain property
Small decision, disproportionate consequences, so it is worth understanding rather than clicking past.
Search Console offers two kinds of property. A URL prefix property covers exactly the address you type and nothing else. A domain property is verified with a DNS TXT record and covers your whole domain: www and non-www, http and https, and every subdomain, all in one place.
The URL prefix route is why so many businesses have their data fragmented across several properties, each holding a slice of the truth, none showing the whole site. The domain property avoids that entirely, and the only extra requirement is being able to add a TXT record to your DNS.
That last bit is where it stalls for most owners: nobody knows who controls the DNS, or the login went with a previous web person. If your DNS is on Cloudflare it is a moment's work. If it is somewhere unknown, finding out is worth doing anyway, because your email and your website both depend on it.
Search Console and Analytics answer different questions
People use the names interchangeably and then wonder why the numbers disagree. They disagree because they are measuring different halves of the same visit.
Analytics (GA4)
- Everything after the click
- Which pages people actually read
- Whether they reached your contact form
- All traffic, not just Google search
- Needs a tag on the page to see anything
"Not indexed" is not always a bug
This is the single biggest source of unnecessary panic in the tool, and occasionally of unnecessary invoices.
The indexing report splits your pages into indexed and not indexed, and the not-indexed list is longer than people expect. That list is not a fault list. It is a list of decisions, and plenty of them are your own decisions working correctly.
- Excluded by noindex tag. You told Google not to index it and Google obeyed. On a thank-you page, a login page or a print view, that is the system working. Our own payments page is deliberately kept out of the index for exactly this reason.
- Alternate page with proper canonical tag. Google found a duplicate and honoured the canonical you set. Correct by design.
- Duplicate, Google chose a different canonical. Worth a look. Google is disagreeing with you about which version is the real one, and sometimes it is right.
- Crawled, currently not indexed. Google saw the page and did not think it was worth keeping. Uncomfortable, but honest feedback about the page rather than a technical fault.
- Discovered, currently not indexed. Google knows the page exists but has not got to it. Often a sign the site is not being crawled much, or the page is not linked to from anywhere that matters.
- Blocked by robots.txt, or server error. These are real. Fix them.
Chasing every line in that report to zero is a waste of money. Knowing which lines are decisions and which are faults is the whole job. There is a longer breakdown at Search Console errors and what they mean.
How we approach it
-
Verify the domain properly
A domain property via a DNS TXT record, so every version of your site reports into one place instead of four partial ones.
-
Submit a sitemap that reflects reality
A sitemap listing your canonical, indexable pages. Not redirects, not noindex pages. A sitemap full of pages you do not want indexed sends mixed signals about your own site.
-
Read the indexing report honestly
Separate the real faults from the decisions working correctly, so effort goes where it changes something.
-
Fix what is genuinely blocking pages
Crawl blocks, server errors, redirect chains and broken canonicals. This is where indexing problems actually get solved.
-
Link it to analytics
Connect the property to GA4 so search data and on-site behaviour sit together and a search can be followed through to an enquiry.
-
Show you what to watch
Two or three things worth checking, and everything you can safely ignore. A tool you understand gets opened; a tool that alarms you gets muted.
Who this is for
- Anyone who has a website and no Search Console property, which is more businesses than you would guess
- Owners who cannot find their pages in Google and do not know if it is an indexing or a ranking problem
- Businesses whose data is scattered across several half-verified properties
- Anyone getting emails from Google about their site that they do not understand
- Sites about to be redesigned or moved, where you want a before and after you can trust
When this is not the right fit
- Anyone expecting the tool to improve rankings by itself. It reports; it does not rank. The improvements come from acting on what it shows.
- Businesses wanting to know what visitors do on the site. That is analytics, not this.
- Anyone who wants every line in the indexing report driven to zero. Some of those lines are your own site working correctly, and chasing them costs money for nothing.
- Sites with no ambition to be found in search at all. Rare, but they exist, and they do not need this.
What SolvenceHQ can help with
Search Console is quick to set up and easy to misread. The value is in verifying it in a way that captures your whole site, then telling you honestly which of its warnings deserve your attention.
- Domain property verification by DNS TXT record, covering every version of the site
- Sitemap generated and submitted so it matches your real canonical pages
- Indexing and coverage reports diagnosed, faults separated from correct behaviour
- Crawl blocks, server errors and redirect problems traced and fixed
- Search performance data read for you: where you are close, and what to do about it
- Linked to Google Analytics for the full picture from search to enquiry
- DNS handled directly if your domain is on Cloudflare
Common questions
Is Search Console the same as Google Analytics?
No. Search Console is about how Google sees your site: what it crawled, what it indexed, and which searches showed your pages. Google Analytics is about what people do after they arrive.
The clearest way to hold them apart: Search Console covers everything up to the click, analytics covers everything after it. Link the two and you can follow a search all the way through to an enquiry.
Why does Search Console say my pages are not indexed?
It depends entirely on the reason it gives, and some of those reasons are not problems. "Excluded by noindex tag" on a thank-you page means your site is working correctly. "Duplicate, Google chose a different canonical" is often Google agreeing with your own setup.
The ones worth acting on are pages you want found that are being blocked, crawled and rejected, or never discovered at all. We wrote up the common reports here: Search Console errors and what they mean.
Should I verify a domain property or a URL prefix property?
A domain property, in almost every case. It is verified with a DNS TXT record on your domain and then covers every version of the site at once: with and without www, http and https, and every subdomain. A URL prefix property covers only the exact version you entered, which is how businesses end up with their traffic split across several properties and no complete picture.
The DNS record is the only extra step, and if we already handle your DNS through Cloudflare it takes moments.
Does Search Console help my rankings?
Not directly. It is instrumentation, not a lever. Nothing you click inside it makes Google rank you higher, and submitting a URL does not buy you a position.
What it does is show you the faults that are holding you back and the searches you are already close on. Acting on those can improve things. The tool itself just tells you the truth about where you stand.
How long until Google indexes a new page?
There is no promised timeframe and anybody quoting one is guessing. It can be quick for a site Google crawls often, and slow for a new site with few links pointing at it. Requesting indexing for an important page nudges the queue; it does not command it.
What you can control is making the page easy to find and worth keeping: reachable by internal links, in your sitemap, not blocked, and genuinely useful. That is technical SEO territory.
Related services and guides
Google Analytics setup
Measure what happens on your site, without collecting personal data.
Technical SEO
The crawling, indexing and structure work search engines depend on.
Local SEO
Get found by people searching for your service near you.
Google Search Console errors
What the common reports mean, and which ones are not problems.
Website not showing on Google
Work out whether it is not indexed, not ranking, or not there at all.
Cloudflare management
DNS, SSL, caching and protection, configured properly.
Get a Quote
Pages missing from Google, or reports you cannot read?
Tell us which pages you expect to see and what Search Console is showing instead. We will tell you which of it actually matters.