What Is Google Search Console and How Do You Use It? A Beginner's Guide

Running a website without Google Search Console is like driving a car with the dashboard taped over. You can still move, but you have no idea how fast you are going or whether a warning light just came on. I have managed client websites since 2012, and this free tool is always the first thing I set up. In this guide I walk you through it at beginner level: setup, verification, the key reports and your first sitemap.

I will not hand you a glossary. Instead, I want to show you which report answers which question and how to read the numbers without panicking. By the end, you will have a simple monthly routine you can run yourself.

What is Google Search Console and what does it do?

Google Search Console is a free service from Google that shows how your website performs in Google Search. It reports impressions, clicks and search queries, tells you which pages Google has indexed and flags technical problems that block visibility. In short, it is the official line between Google and your site.

In practice, the tool does not raise your rankings by itself. However, it lets you catch problems early. For example, if a developer accidentally adds a noindex tag across the whole site, you see it here before sales drop. Google also uses this channel when it needs to warn you about a manual action or a security issue.

For managers, the biggest value is simple: the numbers come from Google's own records. Most third party SEO tools estimate traffic with models. Search Console, on the other hand, shows real impressions and real clicks. That is why the first thing I ask for in every consulting project is access to this account.

How is Search Console different from Google Analytics?

People mix the two up because both show traffic. The real difference, then, is where the measurement starts. Search Console measures the moment before a visitor arrives: appearing in the results and earning the click. Google Analytics measures what happens after the visitor lands. It tracks pages viewed, forms submitted and purchases made.

As a result, the two tools never match exactly. Search Console counts clicks. Analytics, however, counts sessions, and it often misses visitors who decline cookies. I have seen many teams sound the alarm over this gap when nothing was actually broken.

• Search Console covers impressions, clicks, queries, indexing and technical health.
• Google Analytics covers sessions, engagement, conversions and revenue.
• Used together, they show which queries lead to which conversions, so link the two.

Put simply, one tells you how many people looked at the shop window. The other tells you what visitors did inside the shop. So you need both views.

How do you set up a Google Search Console account?

All you need is a Google account. Go to the Search Console home page and click "Start now." Then the tool asks you to add a property. In other words, a property is simply the version of your site that Search Console will track.

Here is my strongest piece of advice: create the account with a permanent company login, not a personal email. If an agency or freelancer opens it under their own name, you may lose access to your data when the contract ends. I always ask clients to stay the owner and add me as a separate user.

Also, keep your expectations realistic. A brand new property may take a few days before the first data shows up. If someone verified the same property in the past, however, the historical data appears once you verify. So I recommend finishing the setup just before a new site goes live.

Should you choose a Domain property or a URL prefix property?

Search Console offers two property types, and your choice decides what data you see in one place. According to Google's verification documentation, a Domain property covers all protocols and all subdomains. In other words, http, https, www and subdomains such as blog all roll up into one view.

A URL prefix property only covers the exact address you enter and the paths below it. For example, a property for https://www.example.com will not include the http version or the version without www. That said, this type is useful when you want to track one folder on its own.

My own habit is to start every project with a Domain property. Then, if needed, I add URL prefix properties for specific folders, such as /de/ on a multilingual site.

Which verification methods can you use?

Google only shows data to the real owner of a site. Therefore, after you add a property, you need to prove ownership. The options also depend on the property type.

1. DNS record: you add a TXT record at your domain provider. This is the only method for a Domain property.
2. HTML file: you upload a small file from Google to the root of your site.
3. HTML tag: you paste a meta tag into the head section of your home page.
4. Google Analytics: if your Analytics code already runs on the site and you have edit rights, verification takes a few clicks.
5. Google Tag Manager: the same logic applies through your Tag Manager container.

The DNS record looks like the hardest route at first. In practice, it is also the most durable one, because it survives theme changes and plugin updates. On WordPress sites I have seen the meta tag disappear after a theme update more times than I can count. DNS changes can take a few hours to spread. So if Search Console says it cannot verify yet, wait and try again later.

Why do you lose verification, and how do you keep it?

Verification is not a one time event. Google's documentation says it lasts as long as Search Console can confirm that your verification token is present and valid. The system also checks this on a regular basis. If it cannot find the token, you get a notice and then a short grace period before access ends.

In real projects, the same situations break verification again and again:

• A site redesign ships a new theme that no longer carries the old meta tag.
• A server move leaves the verification file behind on the old machine.
• A domain transfer drops some DNS records along the way.
• Someone removes the Analytics code or swaps it for a new account.

For this reason, I keep at least two methods active at the same time. For example, I leave an HTML file in place next to the DNS record. That way, access continues even if one method breaks. If you plan a site migration or domain change, put this check at the very top of your list.

Which four metrics in the Performance report matter most?

The Performance report is the screen people open most often. Google's Performance report documentation defines the four core metrics like this:

• Total clicks: how often users clicked through to your site from Google Search results.
• Total impressions: how often your site appeared in search results.
• Average CTR: clicks divided by impressions.
• Average position: the average position of the topmost result from your site.

Beginners struggle most with average position. Specifically, the number does not describe one fixed ranking. Instead, it averages many positions across different users, devices and queries. On its own, it can easily mislead you.

My advice is to read the four metrics together. If impressions rise while clicks stay flat, your title and description probably do not earn the click. In that case, check how your snippet looks with the Google SERP preview tool and rewrite it.

How do you filter and compare Performance data?

By default the report shows the last three months. However, the date filter lets you go back as far as 16 months, which is how long Search Console keeps this data. To separate a seasonal dip from a real loss, compare the current period with the same period last year.

Next, filters help you answer practical questions. Which page earns the most impressions? Do you perform better on mobile or on desktop? Which countries send clicks? In addition, Google now offers a filter that splits branded and non-branded queries automatically. Google announced it in November 2025 and opened it to all eligible sites in March 2026. You will not see it on sub-folder properties or on sites with very few impressions.

I rely heavily on the non-branded view, because that is where the real effect of SEO work shows. Branded searches come from people who already know you. New customers, on the other hand, usually arrive through non-branded queries. To pick the right ones, read my guide on finding keywords that drive sales.

Finally, note that the newest days on the chart appear as a dotted line. That data is preliminary and can still change over the next few days.

What does the Pages indexing report tell you?

The Pages report shows how many of the URLs Google knows about are in the index and why the rest stay out. People who have used the tool for years may remember it as the Coverage report. Above all, it is the starting point for technical SEO. You will see two groups here: indexed pages and not indexed pages.

Not every page outside the index is a problem. For example, old URLs that redirect, or thank you pages you deliberately set to noindex, belong there. Common reasons include:

• The page carries a noindex tag and Google respects it.
• The URL redirects to another page.
• The page returns a 404 error, so it no longer exists.
• Google treats a thin or empty page as a soft 404.
• Your robots.txt file blocks crawling.
• The page duplicates another URL and you did not declare a canonical.
• Google knows the URL but has not crawled it yet.

What matters is whether a page you want in the index ends up in this list. For instance, if a service page sits under "Blocked by robots.txt," check your rules right away. The robots.txt generator helps you rebuild them cleanly.

What does "Crawled, currently not indexed" mean?

This status worries beginners more than any other. It means Google visited the page and read it, but decided not to index it for now. In other words, it is not a technical error. Instead, it is a judgment call.

In my experience, the usual causes are simple. The content is thin, or it nearly duplicates another page. Sometimes no internal link points to the page at all. In other cases, the page just does not offer clear value to a searcher. E-commerce filter pages that copy each other often land here, for example.

"Discovered, currently not indexed" is a different story. Google knows the address but has not crawled it yet. Meanwhile, on large sites, crawl capacity or a slow server can cause this.

In both cases, the fix is not to hit the request indexing button over and over. Instead, strengthen the content, add internal links and merge duplicates. For the deeper technical side, see my article on technical SEO after AI.

How do you use the URL Inspection tool?

URL Inspection shows how Google sees a single page. First, paste the full address into the search bar at the top of Search Console. Within seconds, you learn whether the page is on Google.

According to Google's URL Inspection documentation, the tool offers two views. The first is the indexed version: the last copy Google stored, the last crawl date and the canonical URL Google selected. The second is the live test. It checks the current page in real time and shows the robots.txt and noindex status. It also gives you a screenshot of the rendered page.

The gap between the two views teaches you a lot. For example, if you fixed an error yesterday, the indexed version still shows the old problem. The live test, in contrast, tells you right away whether your fix works.

One warning from the documentation itself: "URL is on Google" does not mean the page will appear for every search. Being indexed only makes a page eligible to rank. After that, quality and relevance still decide the rest.

When should you request indexing?

The URL Inspection screen includes a "Request indexing" button. In short, it adds the page to Google's crawl queue. Google says processing usually takes a day or two and sometimes longer. In addition, there is a daily quota per property.

So use the button selectively. These are the cases where I use it:

1. You publish a new and important page, such as a new service page.
2. You fix a critical error, for example removing a noindex tag someone added by mistake.
3. You change a key part of a page, such as prices or contact details.

Trying to push hundreds of pages one by one wastes time. For bulk discovery, Google itself points you to sitemaps. Also, sending the same request again does not speed things up. If the page is already in the queue, patience is the right move.

How do you submit a sitemap in Google Search Console?

A sitemap is an XML file that lists the important pages on your site. Google's sitemap documentation sets the limit at 50,000 URLs or 50 MB uncompressed per file. Larger sites, therefore, split their URLs across several files and use a sitemap index.

1. First, find your sitemap URL. WordPress and most platforms create one automatically. If you need to build one by hand, use the XML sitemap generator.
2. Open the URL in your browser and confirm that the file loads cleanly.
3. In Search Console, open "Sitemaps" from the left menu.
4. Enter the URL and click "Submit."
5. After a few days, check that the status reads "Success" and note the number of discovered pages.

A sitemap does not guarantee indexing. Google treats it as a hint instead. Still, it clearly helps discovery on new sites, large sites and sites with weak internal linking. Don't forget to add a sitemap line to your robots.txt file as well.

What do the Core Web Vitals and HTTPS reports show?

These two reports in the Experience section summarize how people experience your site. The Core Web Vitals report relies on real Chrome user data about loading, responsiveness and visual stability. It groups URLs as "Good," "Needs improvement" or "Poor."

Keep in mind that this is field data, not a lab test. Low traffic sites, for example, may not have enough data, so the report can look empty. That is normal and not an error.

The HTTPS report shows whether your pages load over a secure connection. Mixed content and invalid certificates show up here.

One more note: Google retired the old Mobile Usability report and the Mobile-Friendly Test tool on December 1, 2023. Google pointed users to Lighthouse in Chrome instead. If an older guide still tells you to open that report, it is out of date. When I build sites through my web design service, I run these mobile checks from day one.

Why do the Manual actions and Security issues reports matter?

These two reports are usually empty, and empty is good news. When they fill up, however, your visibility can suffer badly.

A manual action means a human reviewer at Google decided your site violates the spam policies. Paid links or hidden content that misleads users can trigger one, for example. The report then names the issue and the affected pages. After you fix the problem, you send a reconsideration request from the same screen.

The Security issues report tells you if attackers compromised your site or if it hosts harmful software. A hacked site can trigger a red warning page in visitors' browsers. Consequently, a notice here is never something to leave for next week.

Search Console also sends critical alerts by email. Make sure notifications stay on and that they reach an inbox someone actually reads.

What are the Links report and the Removals tool for?

The Links report shows two things. First, it lists which of your pages other sites link to most. Second, it shows which pages receive the most internal links. Specifically, it is a sample, not a full backlink database. Still, it is enough to see which content attracts links naturally.

That said, people often skip the internal links view. If an important service page sits near the bottom, your site simply does not point to it enough. That is one of the easiest SEO fixes there is.

The Removals tool lets you hide a page from search results for a limited time. It helps when a document went live by mistake, for instance. However, the removal is temporary. To remove a page for good, delete it, add noindex or put it behind a password. If you moved pages recently, check the redirects with the redirect checker.

What should you watch when you add users and permissions?

Search Console has three main roles: owner, full user and restricted user. An owner can add or remove users and change every setting. A full user sees most data and can take some actions. Finally, a restricted user can only view data.

This is the setup I recommend:

• The company stays the verified owner through a permanent company account.
• You add the SEO consultant or agency as a full user.
• Managers and people who only read reports get restricted access.
• When a contract ends, you remove access the same day.

This gives you two benefits. First, the data always stays with the company. Second, you know who did what. Additionally, when you link Search Console to your Google Analytics property, you can see search data next to conversion data.

One more habit pays off: review the user list at least once a year. Former staff, finished agencies and unknown email addresses pile up over time. Almost every account I have taken over had forgotten access like this. The cleanup takes five minutes and puts you back in control. Do the same for your Analytics and Google Ads accounts too.

How often should you check Google Search Console?

Google's own getting started guide is reassuring here: you do not need to check every day. Instead, when a new issue appears, Google emails you. The suggested rhythm is roughly once a month and after any major change to the site.

This is the monthly routine I give my clients:

1. In the Performance report, compare the last 28 days with the previous period. Then compare them with the same period last year.
2. Look at non-branded clicks on their own.
3. In the Pages report, check that the indexed count has not dropped unexpectedly.
4. Scan the Sitemaps section for errors.
5. Check whether any new URLs moved into the "Poor" group in Core Web Vitals.
6. Confirm that Manual actions and Security issues are still empty.

Once you get used to it, the routine takes less than half an hour. My guide on how to read a digital marketing report helps you turn these checks into a clear update for management.

Which report answers which question?

Beginners often feel overwhelmed by the number of reports in the menu. Yet once you tie each report to a question, the tool becomes much easier. Also, your whole team starts to speak the same language. This is the mapping I teach:

• "Why did our traffic drop?" Open Performance and compare date ranges.
• "Why doesn't my new page show up?" Run URL Inspection.
• "How many of my pages does Google know?" Check the Pages report.
• "Is my site slow for real users?" Go to Core Web Vitals.
• "Did we get a penalty?" Look at Manual actions.
• "Which pages attract links?" Open the Links report.

With this map, you go straight to the answer instead of clicking around. Above all, that discipline matters during a traffic drop. After all, the cause is sometimes not a technical error at all but a change in the results page. For example, impressions can grow while clicks fall because AI summaries answer the query. I cover that in detail in my article on zero click searches.

Common beginner mistakes to avoid

Over the years I have seen the same mistakes repeat across companies of every size. So knowing them in advance can save you months. Moreover, most of them need no developer at all, only a few settings and some attention.

• Creating only a URL prefix property and never seeing data for the http or non-www version.
• Tying verification to a single meta tag and losing access during a redesign.
• Treating average position as the one measure of success.
• Assuming every page outside the index is a problem and creating busy work.
• Pressing the request indexing button for the same pages every day.
• Declaring either Search Console or Analytics "wrong" because the numbers differ.

None of these mistakes comes from a lack of technical skill. They all come from not fully understanding what the tool measures. So once the definitions in this guide click, most of the mistakes disappear on their own.

How do you turn Google Search Console data into action?

Data stays a chart until you make a decision with it. The real value of Search Console is that it tells you what to fix and what to grow. These are the three actions I use most:

1. Rewrite titles and descriptions for pages with high impressions and a low CTR.
2. Strengthen pages for queries with an average position between 8 and 20. This range is a starting point from my field experience, not a guarantee.
3. Support important pages that are not indexed with internal links and deeper content.

On most small and mid sized sites, these three steps bring the fastest return. On a large site, or after a migration, the picture can get more complex. If that is your situation, we can review your account together as part of my SEO consulting work.

My final word: do not set up Google Search Console once and forget it. Give it half an hour a month. In return, you get a more honest picture of your site's health than many agency reports provide.