What Is Google Search Console? The First Reports to Open
Search Console is the panel Google gives a site owner. You read how the site is crawled, which page made it into the index and which searches show it. A position is not for sale. The panel does not promise one either.
What the panel shows
Google's getting-started page describes the tool as a way to understand how the site performs on Google Search, and to see what can be done about its appearance so it can bring more relevant traffic. It reports on crawling, indexing and serving. Those three stages are separated in the SEO article. This article is about which screen you read them on.
You do not need to open the panel every day. If Google finds a new issue on the site, it sends an email. The getting-started page treats a look about once a month, or whenever you change the content, as enough. Data takes a few days to accrue. Collection starts as soon as someone adds the property, even before verification finishes. Collection does not mean an unverified person can read it.
Domain property or URL prefix
The first decision is the boundary of the property. The wrong boundary means you are reading an address you do not actually serve.
A Domain property looks like example.com. It is verified only with a DNS record. Verifying the root domain also verifies its subdomains. Verifying a subdomain does not verify the parent. This property gathers data for both http and https, and for subdomain variants, together.
A URL-prefix property is a specific start, such as https://www.example.com. It covers only URLs that begin with that prefix. A property for https://www.example.com does not include the host without www, or any other subdomain. The HTML file and the HTML tag are for this property type, not for a Domain property.
Illustrative example
Suppose a studio site is live at https://www.atelier.example. This is not a client record. The owner adds the property as https://atelier.example, without www. The live site redirects that host to the www version. The URL prefix they verified does not cover the addresses visitors and Google arrive at, because the www address does not start with that prefix.
There are two honest choices. Open a Domain property and verify it with DNS. Or create the URL prefix as the host you actually serve, https://www.atelier.example. Opening both is allowed. What gets confusing is which one is open in the report.
How ownership is verified
Verification shows Search Console that the site is yours. A verified owner has the highest level of permission. Google keeps that permission tight because the panel also opens actions that can affect how the site appears in search. Several people can verify the same property, with the same method or with different ones. If you use the same method, do not overwrite another owner's verification token.
Verification lasts while the token is present and valid. Search Console checks for it from time to time, using the Google Site Verifier user agent. If the token cannot be confirmed, you are notified. If it is not fixed, permission expires after a grace period the document does not give a length for. If every verified owner loses access, the other users on the property lose access too. Leaving the token on the live site is not a one-time setup.
A hosting panel often documents its own verification step. If the platform will not let you upload a file, read that help before forcing a general method. Adding more than one method is useful. If one breaks, for example a template change drops the Analytics tag, another keeps the property standing.
| Method | What it requires | Which property |
|---|---|---|
| HTML file | A file unique to you, at the property root, reachable without logging in. Do not change its name or contents. Search Console does not follow a redirect to a different domain when it looks for the file. | URL prefix. Not a Domain property. |
| HTML tag | A meta name="google-site-verification" tag in the head of the homepage, on a page that does not ask for a login. The page checked is the one that opens at the URL defining the property. | URL prefix. Not a Domain property. |
| DNS record | A TXT record at the domain provider. Verifying the root also covers subdomains. | The required path for a Domain property. Used on a URL prefix, it also verifies the Domain property. |
| Analytics or Tag Manager | A short path when a tracking snippet you can access is already on the page. If it is not, you have to set up that account first. | URL prefix. |
Four places to open first
After verification you do not need to tour the whole panel. Four places separate whether the site is being found, why a single address is missing and which search shows it.
Page indexing
Which pages are indexed, which are not, and why Google left them out. The getting-started page calls this overview the Index coverage report. The help page is titled Page indexing report. The name in the panel can change with the version. The question does not.
Performance
Traffic from Google Search, broken down by query, page and country. There are columns for impressions, clicks and what the document calls other metrics. This is not a ranking report. You read which questions show the site.
Sitemaps
If you submitted a sitemap, this is where you see when Google read the file and whether processing raised an error. Submitting can speed discovery. Pages can be found without a sitemap. The file itself is covered in the XML sitemap article.
Experience and security
The Core Web Vitals report shows page experience from real-use data. The detail is in the Core Web Vitals article. The Security issues report warns you if Google thinks the site may have been hacked. The Manual actions report lists cases where some or all of the site may not be shown in results.
The status of a single address
URL Inspection asks for a fully qualified URL inside the property you have open. If the address is not in that property, the tool will not inspect it. The first screen is not a live test. It shows the version Google most recently indexed, and search results are built from that version. The page may have changed since that crawl. The live test is for the version on the web now.
The verdict at the top is one of four things. "URL is on Google" means the address is eligible to appear in results. It does not guarantee that it will. The tool does not fold manual actions, security issues, legal removals and temporary blocks into that single verdict. The direct check is to search for the address on Google. "URL is not on Google" means the address cannot appear in results. The reason sits in the page indexing section.
The same screen has two canonical fields. The address you declared, and the address Google selected. Google takes your preference into account and may still choose another address. The canonical is read only from indexed data. The live test cannot predict whether the tested version will be treated as canonical. The detail is in the canonical article.
If robots.txt has blocked crawling, "Indexing allowed?" can still say Yes. Google cannot see a noindex rule in that case. The page may then appear in results while you believe you blocked it.
A request for indexing places the address in a queue. If the live test finds the page non-indexable, the request cannot be sent. The request does not guarantee that the page will enter the index. Google writes that the process usually takes about a day, and in some cases a week or two, or longer. There is a daily limit. The number is not published. For many pages, the document recommends a sitemap.
The order of a first session
The order below separates the two things a person opening the panel for the first time mixes up most often. Which property they are looking at, and whether the indexed version of an address matches the live one.
- Before you add the property, write down its boundary. All subdomains and both protocols, or only addresses that start with https://www.
- Verify with one method. Confirm in a private window that the token is visible without logging in. Where the verification tag sits belongs to the site and the software. A record in the panel does not mean the tag is on the live page.
- In the page indexing report, are the addresses you consider important in the index, and if not, what is the reason.
- Open the home page and one inner page with URL Inspection. The indexed version first, then the live test. Does the page Google sees resemble what the user sees.
- Does the user-declared canonical match the Google-selected canonical. If not, look for a conflicting address in the redirect and in the canonical tag.
- If you have a sitemap, open the sitemaps report. A small, internally linked site does not require one. The decision is in the sitemap article.
- Wait a few days for performance data. Then look at which queries show the page. Coming back when you change the content, or about once a month, is the pace the document suggests.
Sources
- Get started with Search Console
Accessed October 20, 2026
- Verify your site ownership
Accessed October 20, 2026
- URL Inspection tool
Accessed October 20, 2026
- Page indexing report
Accessed October 20, 2026