Google Search Console (GSC) is a free Google service that shows how the search engine sees your site: which queries it appears for in search results, which pages made it into the index, and where technical errors occur. Basic setup takes 10–15 minutes: you add a property, verify ownership of the site and submit a sitemap. Below is a step-by-step setup and a walkthrough of the reports worth checking every week.
Key points in 30 seconds
- Site ownership is verified by one of these methods: DNS record, HTML file, meta tag, Google Analytics or Tag Manager.
- A Domain property covers all subdomains and both protocols (http/https). It’s the better option.
- Submit sitemap.xml right after connecting: that way Google finds your pages faster.
- Key reports: Performance, Page indexing, Core Web Vitals.
- Data doesn’t appear instantly: the first numbers show up in 2–3 days, a complete picture in about two weeks.
What Google Search Console is and why you need it
GSC is Google’s webmaster dashboard. Unlike web analytics, which tracks the behavior of visitors you already have, Search Console shows what happens on the search side: how many times the site appeared in results, how many clicks it got, at which positions, which pages Google indexed and which it rejected, and why. It’s the first tool you open when diagnosing traffic drops, indexing problems and penalties. It’s useful for link building too: the Links report shows which domains link to your site and which pages get the most links.
Step 1. Add a property and choose its type
Sign in to Search Console with your Google account and click “Add property”. The service offers two types:
- Domain property: covers the entire domain with all subdomains and protocols (example.com, www.example.com, http and https). Verified via DNS only. The recommended option.
- URL-prefix property: only a specific address with the specified protocol. Suitable if you don’t have DNS access or need to track a single section.
For most sites, choose Domain: it gives you the full picture and doesn’t split data by protocol and subdomain.
Step 2. Verify site ownership
Google needs to confirm that the site belongs to you. The available method depends on the property type you chose.
| Method | What to do | Best for |
| DNS record (TXT) | Add a TXT record in the domain settings at your registrar | Domain property; works universally |
| HTML file | Upload the file to the site’s root folder | You have FTP or hosting access |
| HTML tag | Insert a meta tag into the <head> of the homepage | You have access to the template code |
| Google Analytics | Use the GA4 code already installed | The site already has analytics |
| Google Tag Manager | Use the installed GTM container | Tag Manager is set up |
After adding the record or file, click “Verify”. A DNS record can take up to several hours to propagate; if verification doesn’t pass right away, try again later.
Step 3. Submit a sitemap
A sitemap is a file listing all your important URLs. It helps Google discover and recrawl pages faster. In the Sitemaps section, enter the file address (usually sitemap.xml) and click “Submit”. After a while the status changes to “Success” with the number of URLs found. If it says “Couldn’t fetch”, check that the file opens via a direct link and doesn’t contain URLs blocked in robots.txt.
How to read the key Search Console reports
Once data has been collected, most of the work happens in a few reports.
The Performance report
The main report on search traffic. Four metrics: impressions (how many times the site was seen in search results), clicks, CTR (clicks as a share of impressions) and average position. Switch between the Queries, Pages, Countries and Devices tabs to understand what exactly brings traffic. The practical win: find queries ranking in positions 8–20 with high impressions but low CTR. You can push those into the top with content improvements and links.
The Page indexing report
Shows how many pages are indexed and how many are excluded, with the reason: “Discovered, currently not indexed”, “Crawled, currently not indexed”, “Page with redirect”, “Duplicate without user-selected canonical”, “Not found (404)” and others. This is your map of technical problems. A sharp rise in excluded pages is a signal that something has broken.
Core Web Vitals
A report on loading speed and stability (LCP, INP, CLS). Pages are split into “Good”, “Needs improvement” and “Poor”, separately for mobile and desktop. Slow pages rank worse, so keep the red zone under control.
How to check whether a specific page is indexed
Paste the page URL into the URL Inspection bar at the top of the dashboard. GSC will show whether the page is indexed, when it was crawled, which canonical URL Google chose and whether anything is blocking it. If the page isn’t indexed but should be, click “Request indexing”. That doesn’t guarantee instant inclusion, but it puts the URL in the crawl queue.
What to check in GSC every week
- Impressions and clicks trends in Performance: look for sharp drops.
- New errors in the Page indexing report.
- The Manual actions and Security issues sections: that’s where manual penalties show up.
- New referring domains in the Links report.
If you check the same things in the same order, it takes 15–20 minutes a week. The easiest approach is to compare the last 7 days with the previous 7: drops show up immediately and you don’t have to go by gut feeling. Did one group of pages fall? Look for the cause there: template, indexing, redirects. Did the whole site drop at once? First open Manual actions and compare the dates with Google updates.
Diagnosing common problems with GSC
| Symptom | Where to look | Likely cause |
| Traffic dropped | Performance → compare periods | Algorithm update, lost rankings, seasonality |
| Pages not indexed | Page indexing | noindex, duplicates, thin content, crawl budget |
| Exclusions spiked | Page indexing → reasons | robots.txt error, broken redirects |
| Penalty warning | Manual actions | Guideline violations, toxic links |
If the diagnosis shows a drop right after link building work, that scenario is covered in detail in our article on recovering a site from a penalty.
GSC vs Google Analytics 4: what’s the difference
These are two different tools. Search Console looks at the site from the search side: impressions, rankings, indexing. Google Analytics 4 tracks the behavior of users who are already on the site: sources, conversions, paths through the site. For the full picture you link them, and then GA4 pulls in search queries from GSC. It’s worth setting up both services together.
Search Console shows symptoms, but it doesn’t always explain the cause and it doesn’t fix the problem. If the reports show excluded pages, ranking drops or technical errors but it’s unclear what to tackle first, it makes sense to start with a full SEO audit: it turns scattered GSC signals into a prioritized work plan. How to read its results is explained in the article Technical SEO Audit. If your main pain is that pages aren’t getting indexed, start with Why Your Site Isn’t Getting Indexed, and for ranking drops, with the guide Rankings Dropped: How to Find the Cause.
Set up Search Console, but the reports show problems and you have no action plan? Order an SEO audit: we’ll sort out the GSC signals and put together a step-by-step plan to get your site into the top results.
