How to Use Google Search Console: Reports and Errors Guide
How to use Google Search Console step by step: property setup, the Performance report, URL Inspection, page indexing errors and a weekly check routine.
How to use Google Search Console comes down to reading the site’s status in Google Search from four main screens: the Performance report, the Page indexing report, the URL Inspection tool and Sitemaps. First you add the site as a property and verify ownership. Then you use these reports to see which queries bring clicks, which pages are not indexed and why, and how Google sees each page.
In this guide I explain Search Console in practice, from setup to a weekly check routine. Coming from a software development background, I try to connect every warning in the reports to a piece of code, a template or a server response. I cover the overall technical framework in my what is technical SEO article, and how I run this work on my SEO services page.
What is Google Search Console and what is it used for?
Google Search Console is a Google tool that shows how a site performs on Google and what it should fix to improve its visibility. According to Google’s getting-started guide, the tool provides information on how Google crawls, indexes and serves websites in search results.[1] It is also known by its former name, “Google Webmaster Tools”.
The questions Search Console answers fall into three groups. The first is visibility: for which queries does the site appear, how often and at what position? The second is accessibility: can Google find, crawl and index the pages? The third is health: does the site have a manual action, a security issue or a structured data error?
Google says there is no need to sign in to the tool every day. When Google finds a new issue on the site, Search Console sends an email alert. Google’s recommendation is to check the account around once a month and whenever you change the site’s content.[1] On sites with many pages and frequent publishing, I keep this check weekly.
How do you set up Search Console?
Short answer
How do you set up Google Search Console?
Setting up Google Search Console is complete once you add the site as a property and verify ownership. First you choose between a Domain property and a URL-prefix property. A Domain property can only be verified with a DNS record. After verification, you submit the sitemap and wait for the data to appear.
- Sign in to search.google.com/search-console with your Google account.
- Choose the property type: Domain property or URL-prefix property.
- Enter the domain or the full URL prefix.
- Verify ownership with a DNS record, an HTML file or a meta tag.
- Submit your sitemap.xml address in the Sitemaps report.
- Wait a few days for the data to build up.
The most important decision during setup is the property type. Search Console supports two types of website property, and each covers a different set of URLs.[2]
| Feature | Domain property | URL-prefix property |
|---|---|---|
| Scope | All subdomains and protocols | Only URLs starting with the given prefix |
| Example | example.com | https://www.example.com/en/ |
| Verification | DNS record only | HTML file, meta tag, Google Analytics, Google Tag Manager, DNS |
| When? | To monitor the whole site in one place | For separate reports per language folder or subdirectory |
A Domain property covers the http and https versions together with subdomains such as www and m.[2] That is why a Domain property is my first choice for seeing the whole site. On multilingual sites, I also add separate URL-prefix properties for folders such as /en/ and /de/. This makes it easier to monitor each market’s performance on its own.
You can add up to 1,000 properties to one account.[2] According to Google’s help page, data collection starts as soon as the property is added to an account, even before verification, and data begins to appear within a few days.[2] So empty reports in the first days of a new site are not an error.
Users and permissions
Each Search Console property has owner, full user and restricted user roles. An owner can add and remove users and change settings. A full user sees most of the data and can take some actions. A restricted user can only view data. When you give access to an agency or a new team member, using one of these roles instead of ownership keeps control of the account with you.
How do you read the Performance report?
The Performance report shows a site’s click and impression data in Google Search results, broken down by query, page, country and device. According to Google’s help page, the report’s default view shows click and impression data for the past three months.[3] You can narrow the view by changing the date range, metrics and dimensions.
The report has four metrics. Google defines them as follows:[3]
| Metric | Definition | How I read it |
|---|---|---|
| Clicks | The number of times a user clicked through to the site from Google results | The search-side counterpart of organic traffic |
| Impressions | How many times the site appeared in search results | An indicator of demand and visibility |
| Click-through rate (CTR) | Clicks divided by impressions | How compelling the title and description are |
| Average position | The average position of the site’s topmost result | A trend indicator, not an exact ranking |
Average position is the most frequently misread metric. The value in the chart is the average of the topmost result for the entire site. The value in the table is calculated for the query or page in that row.[3] If a page sometimes appears at position 3 and sometimes at position 40 for the same query, the average can be misleading. That is why I read position query by query and together with impressions.
Dimensions and filters
The report’s table can be grouped by queries, pages, countries, devices, search appearance and dates.[3] With the search type filter, you can look at web, image, video and news searches separately. When you choose the 24-hour view, the chart shows hourly data, and this data is preliminary.[3]
These are the filters I use most:
- Regular expressions (regex) in the query filter: To exclude queries containing the brand name and see non-branded organic demand.
- Page filter: To monitor a category or a language folder (
/en/) separately. - Compare: To put the periods before and after an update or a site migration side by side.
- Country and device: To see whether there is a clear difference between mobile and desktop or between markets.
The chart total and the table total sometimes differ. Google explains this with a difference in how the data is aggregated: the query, country, device and date dimensions are aggregated by property, while the page and search appearance dimensions are aggregated by page.[3]
Finding pages with a low click-through rate
Click-through rate is calculated by dividing the number of clicks by the number of impressions; the formula is CTR = clicks ÷ impressions. Queries that get many impressions but stay at a low click-through rate are the fastest opportunities for title and description improvements. With the tool below, you can check in advance how a new title and description will look in the search result.
My first step is to sort the query table by impressions and look at rows with an average position between 4 and 15. For these queries, I recheck the search intent the page targets. To plan which page a query should belong to, I use the method from my keyword research guide.
How do you use the URL Inspection tool?
The URL Inspection tool shows a single URL’s status in Google’s index, the canonical address Google selected and crawl information. You open it by typing the full URL into the search box at the top of Search Console. According to Google’s help page, the tool lets you see the indexed version, test the live URL, request indexing and view the rendered version of the page.[4]
There is an important distinction here. The first result the tool shows is not a live test; it is based on the version Google indexed most recently.[4] If you have just fixed the page, you need to click “Test live URL”. The live test checks whether the current version of the page is indexable.
These are the three areas I look at most in the live test:
- User-declared canonical and Google-selected canonical: If the two differ, the canonical, internal link and redirect signals are in conflict.
- The crawled page’s HTML and screenshot: If content loaded with JavaScript is missing here, Google may not be seeing it either.
- Page resources: Blocked CSS or JavaScript files can break rendering.
Requesting indexing means asking Google to recrawl the URL; it does not guarantee indexing. Each property has a daily limit on inspection requests.[4] That is why I use the request only for newly published or substantially changed pages. For the same need on Bing and Yandex, I recommend the IndexNow protocol.
How do you fix errors in the Page indexing report?
The Page indexing report shows which of the URLs Google knows on a site are indexed, which are not, and why. The report’s first question is whether the URLs shown in gray, the ones not indexed, are left out for a good reason.[5] Not every unindexed page is an error. Old redirected URLs, parameterized duplicates and pages you marked noindex should not be in the index anyway.
According to Google’s help page, the list of example URLs shown for a status in the report is limited to 1,000 rows.[5] On large sites, I group the example list by URL pattern and think at the template level to see the full extent of a problem.
Here is how I summarize the most common statuses and where to check first:
| Status in the report | What it means | First check |
|---|---|---|
| Crawled - currently not indexed | Google crawled the page but did not index it | Content originality, thin content, internal link support |
| Discovered - currently not indexed | Google knows the URL but has not crawled it yet | Crawl budget, server response time, internal links |
| Duplicate, Google chose different canonical than user | The canonical you declared was not accepted | Consistency of canonical, internal links and sitemap |
| Excluded by ‘noindex’ tag | The page has a noindex directive | Was the directive added on purpose? |
| Blocked by robots.txt | Crawling is blocked with robots.txt | Is the block an intended rule? |
| Soft 404 | The page returns 200 but its content looks empty | Empty categories, out-of-stock products, error templates |
After fixing an issue, you can use the “Validate fix” button in the report to ask Google to recheck the affected URLs. Validation can take days. According to Google, it can take a week or so for a new page or site to be crawled and indexed.[5]
Sitemaps, removals and other reports
The Sitemaps report lets you submit an XML sitemap to Google and monitor whether the submitted sitemap has been read. According to Google, pages can be discovered without a sitemap, but submitting a sitemap through Search Console might speed up discovery.[1] The report shows the sitemap’s status, the date it was last read and the number of URLs discovered.
Other reports are used less often but matter at critical moments:
- Removals: Used to quickly hide content from Google results. According to Google, a successful request lasts only about six months; a permanent solution requires deleting the content or adding noindex.[1]
- Manual actions: Shows manual actions Google has applied to part or all of the site and which section is affected.[1]
- Security issues: Reports detections of malware, hacked content or social engineering.
- Core Web Vitals: Classifies URL groups against the LCP, INP and CLS thresholds based on real user data.
- Enhancements: Lists valid and invalid items for structured data types such as products, FAQs and breadcrumbs.
- Links: Shows the external sites linking to the site most and the pages receiving the most internal links.
- Crawl stats (under Settings): Shows Googlebot’s daily request count, response times and response codes.
On ecommerce sites, the Enhancements and Product snippets reports are the first places I look to catch schema errors on product pages. For a full store audit, you can use the steps in my ecommerce SEO checklist article.
What is the difference between Search Console and Google Analytics?
Search Console measures the search stage before the user reaches the site, while Google Analytics measures behavior after the user arrives. The impression, ranking and query data in Search Console is not available in Analytics. The session, engagement and conversion data in Analytics is not available in Search Console either.
That is why the numbers in the two tools never match exactly. Search Console counts a click in the Google search result. GA4 counts a session when the page loads and the measurement tag fires. If cookie consent is declined, the page loads slowly or the user immediately goes back, Analytics may not record the session. This gap should be read not as an error but as two different measurement points.
Connecting the two tools through the Search Console link inside GA4 lets you see query data and landing page engagement in the same report. I set up this link in every project to see which pages turn organic traffic into conversions.
A weekly Search Console check routine
Using Search Console regularly and with a purpose is the cheapest way to catch problems before traffic drops. The checklist below is the routine I run once a week on sites that publish frequently. On smaller sites, running the same list once a month is enough.
If I see a clear drop in traffic, I first follow Google’s own approach: is the drop site-wide, limited to a group of pages, or limited to a specific country or device? These three breakdowns usually separate a technical error from seasonality or an algorithm update.
Conclusion
Using Google Search Console starts with reading four screens regularly: the Performance report, the Page indexing report, the URL Inspection tool and Sitemaps. Choosing the right property type sets the scope of the data. Reading average position and unindexed pages in context prevents false alarms.
As a next step, add a Domain property for your site, submit your sitemap and put the checklist above on your calendar. If you want to connect the issues you see in the reports to the technical infrastructure, the crawling, indexing and rendering sections in my what is technical SEO article are a good place to start. You can find more about me on the about page.
Key terms
- Google Search Console
- Google Search Console is a free Google tool that lets site owners monitor how their site is crawled, indexed and served in Google Search. Its main reports are Performance, Page indexing, URL Inspection, Sitemaps and Manual actions.
- Domain property
- Domain property is the Search Console property type that groups all subdomains (www, m and others) and all protocols (http, https) of a domain into a single property. It can only be verified with a DNS record added at the domain name provider.
- URL-prefix property
- URL-prefix property is the Search Console property type that covers only URLs starting with a specific protocol and address. It can be verified with several methods, such as an HTML file, a meta tag, Google Analytics and Google Tag Manager, and is used to monitor language folders separately.
- URL Inspection tool
- URL Inspection tool is the Search Console tool that shows a single URL's status in Google's index, the canonical address Google selected and crawl information. Its live test checks whether the current version of the page is indexable, and it lets you request indexing.
Frequently asked questions
What is Google Search Console used for?
Google Search Console is a Google tool that shows how a site appears in Google Search, which queries bring clicks and why certain pages are not indexed. It also reports crawling and indexing problems, manual actions and security issues.
Should I choose a Domain property or a URL-prefix property?
If you want to monitor the whole site in one place, a Domain property is more complete because it includes all subdomains and protocols. However, it can only be verified with a DNS record. If you want to monitor a specific language folder or protocol separately, you can add a URL-prefix property as well.
When does Search Console data start to appear?
According to Google's help page, data starts to appear a few days after the property is added. Data collection starts as soon as the property is added, even before it is verified. That is why it is normal for reports on a new site to look empty in the first days.
Does requesting indexing get a page indexed immediately?
No. Requesting indexing in the URL Inspection tool asks Google to recrawl the page, but it does not guarantee indexing. There is also a daily request limit for each property. That is why the request should be used only for new or substantially changed pages.
What is the difference between Search Console and Google Analytics?
Search Console measures the stage before the user reaches the site: impressions, clicks and rankings in Google Search. Google Analytics measures behavior after the user arrives: sessions and conversions. One does not replace the other; they are used together.
Sources
The full topic: Technical SEO guide ↗