If you have just opened Google Search Console and feel lost among a dozen reports, you are not alone. Here is the short version of Google Search Console for beginners. Verify your site, submit a sitemap, then spend most of your time in three places: the Performance report, the Page indexing report and the URL Inspection tool.
Everything else is either a health check you look at once a week, or an alert you only act on when Google emails you. In this guide I walk through each report in plain words, show what I look for, and end with the 15-minute weekly routine I recommend.
Google Search Console for Beginners: What It Is and Is Not
Search Console is Google’s free tool for site owners. It shows how your pages appear in Google Search, which searches bring people to you, and whether Google can crawl (visit and read) and index (store and show) your pages.
It is not a full analytics tool. It does not tell you what visitors do after they land, how long they stay or whether they buy. That is the job of Google Analytics or a similar tool. I think of Search Console as the view from Google’s side of the results, and analytics as the view from inside your site. That’s also why Search Console and GA4 numbers rarely match.
It is also where Google reports manual actions, security problems and serious indexing issues. It tells you by email as well as in the tool.
Step 1: Add and Verify Your Property
A “property” is the website, or part of a website, that you want data for. When you add one, Google asks you to pick one of two types.
Domain Property vs URL-prefix Property
| Feature | Domain property | URL-prefix property |
|---|---|---|
| What it covers | Every subdomain and protocol: http, https, www, m., shop. and so on |
Only URLs that start with the exact address you enter, including the protocol |
| How you enter it | example.com (no www, no https) |
https://www.example.com/ |
| Verification | DNS record only | Several methods: HTML file, HTML meta tag, Google Analytics, Google Tag Manager or DNS |
| Best for | Seeing the whole site in one place | Sites where you cannot edit DNS, or when you want a separate view of one section |
If you can edit your DNS settings, I always recommend starting with a Domain property. It catches traffic to versions of your site you may have forgotten, such as an old http address or a www version that still gets visits.
You can add URL-prefix properties later for certain sections. For example, a business with a blog at example.com/blog/ can add that as its own property, so its reports show only the blog. Google allows up to 1,000 properties per account. Its official guide to adding a property explains each verification method in detail.
How DNS Verification Works
- In Search Console, click the property selector, choose Add property, pick Domain and type your domain.
- Copy the TXT record Google shows you. It starts with
google-site-verification=. - Log in to your domain registrar or DNS host and add a new TXT record with that value. Leave the host field as
@or blank, depending on your provider. - Go back to Search Console and click Verify. If it fails, wait a while and try again, because DNS changes can take time to spread.
Do not delete the TXT record after you are verified. Search Console checks it from time to time, and removing it can remove your access. I often see this happen when someone tidies up old DNS records.
Add Your Team as Users
Under Settings > Users and permissions, you can add colleagues or an agency. Give “Full” permission to people who need to submit sitemaps or request indexing. Give “Restricted” to people who only need to look. My rule is to keep ownership with the business’s own account, not with an outside person.
Step 2: Submit Your Sitemap
A sitemap is a file that lists the URLs you want Google to know about. Most CMSs and SEO plugins make one for you, often at /sitemap.xml or /sitemap_index.xml.
- Open Indexing > Sitemaps.
- Enter the sitemap path after your domain, for example
sitemap.xml, and click Submit. - Check that the status says “Success”. If it says “Couldn’t fetch” or “Has errors”, open the sitemap URL in your browser to check that it loads and is valid XML.
Submitting a sitemap does not promise indexing. It helps Google find pages, mainly new ones or pages with few internal links. If you run a large site, how Google spends its crawling effort also matters. We cover that in our guide to crawl budget and when it matters.
The Performance Report: Your Most Important Screen
Open Performance > Search results. This shows how your site does in Google Search over time. Data goes back up to 16 months, and the default view is the last three months. This is where I spend most of my time in Search Console.
The Four Metrics
- Clicks: how many times someone clicked through to your site from Google Search.
- Impressions: how many times a link to your site appeared in results the user could see or scroll to. If two of your pages show for one search, that counts as one impression in the chart total.
- CTR (click-through rate): clicks divided by impressions.
- Average position: the average ranking of your highest result. Position 1 is the top. A lower number is better.
Dimensions: Queries, Pages, Countries, Devices
Below the chart is a table with tabs. The ones you will use most are:
- Queries: the search terms that showed your site. Some rare queries are hidden for privacy, so the query totals will not add up to the chart totals.
- Pages: which URLs got clicks and impressions.
- Countries and Devices: where your searchers are and what they search on.
- Search appearance: traffic from rich results and other special result types, if your site has them.
Filters That Answer Real Questions
Click + Add filter to narrow the data. Here are a few filters that are easy for beginners:
- Query contains your brand name: shows how much traffic comes from people already looking for you. Use “Doesn’t contain” to see non-brand traffic. In my view, that is the real test of your SEO.
- Page contains
/blog/: shows one section of the site on its own. - Page equals a single URL, then the Queries tab: shows every search term that one page appears for. This is the fastest way to see whether a page matches the need you wrote it for.
Compare Date Ranges
In the date filter, choose the Compare tab. Compare the last 28 days with the 28 days before, or the same period last year if your business is seasonal. The table then shows the change for every query and page, so you can sort by the biggest drops.
There is also a 24 hours view, added in December 2024, that shows hourly data for recent activity. It helps when you have just published something time-sensitive. Recent data is marked as preliminary and can change for a few hours.
How to Read the Numbers Without Panicking
Impressions can move for reasons that have nothing to do with your rankings. In September 2025, many sites saw impressions fall and average position improve at the same time. This came after a change in how Google serves results to some tools. If you saw a sudden drop around then, read our explainer on why Search Console impressions fell in September 2025 before you change anything.
Also note that clicks and impressions from AI Overviews and AI Mode are included in the Web search totals. They are not shown as a separate line.
A Quick Win From the Performance Report
This is the first check I run on any site. Filter to the last three months, open the Queries tab, and sort by impressions. Look for queries with high impressions, a position between about 5 and 15, and a low CTR. Google already sees these pages as relevant, but people are not clicking.
Often the fix is a clearer title and a better snippet. Our guide on writing meta descriptions Google actually uses covers the snippet side.
Search Console Insights: The Simple Summary View
Search Console Insights used to be a separate beta tool. On 30 June 2025, Google announced a new Insights report built into Search Console itself. It has been rolling out slowly since then, so some accounts may not see it yet.
It is made for people who want answers without building filters. It shows:
- Total clicks and impressions, compared with the period before.
- Your top pages and queries, plus those “trending up” and “trending down”.
- The countries your clicks come from.
- Achievements, such as reaching a new click milestone.
Insights covers Google web search only, not image, video, news or Discover. Clicking any item opens the Performance report with that filter already on.
URL Inspection: Check One Page in Detail
Paste any URL from your property into the search bar at the top of Search Console. The URL Inspection tool tells you what Google knows about that page.
- “URL is on Google”: the page is indexed and can appear in results.
- “URL is not on Google”: the page is not indexed, and the tool says why. For example, “Excluded by ‘noindex’ tag” or “Crawled – currently not indexed”.
- Page indexing details: the last crawl date, whether crawling was allowed, and the canonical URL (the main version) Google chose compared with the one you set.
Click Test live URL to see how Googlebot fetches the page right now. I use this after every fix, because the main result shows the indexed version, which may be weeks old.
If the page is new or recently updated, click Request indexing. There is a daily limit, and requesting the same URL again and again does not speed things up.
Page Indexing: Which Pages Are in Google and Which Are Not
Open Indexing > Pages. The chart splits your known URLs into “Indexed” and “Not indexed”. The table below lists the reasons pages are not indexed.
The key idea for beginners: not every “Not indexed” URL is a problem. Many are left out on purpose, and that is healthy. In my experience, this report scares beginners more than any other. Common examples:
- Alternate page with proper canonical tag: a duplicate that correctly points to the main version. Usually fine.
- Page with redirect: old URLs that send visitors somewhere else. Fine if you meant the redirect.
- Excluded by ‘noindex’ tag: fine for thank-you pages or internal search results. A problem if an important page is listed.
- Not found (404): fine for deleted pages with no replacement. Worth fixing if people still link to them.
- Crawled – currently not indexed and Discovered – currently not indexed: Google knows these pages but has not indexed them. Look for thin, duplicate or poorly linked pages here.
Click any reason to see example URLs. Ask one question about each: “Do I want this page in Google?” If the answer is yes, fix the cause and use Validate fix to ask Google to check again.
The Removals tool, also under Indexing, hides a URL from results for a while. It is for urgent cases, not for deleting pages for good.
Core Web Vitals: Real-User Speed and Stability
The Core Web Vitals report, under Experience, groups your URLs as Good, Needs improvement or Poor. It does this separately for mobile and desktop. It uses field data from real Chrome users, so low-traffic sites may see “Not enough data”.
The three metrics, with the “Good” limits from web.dev’s Core Web Vitals overview, are:
- Largest Contentful Paint (LCP): how fast the main content loads. Good is 2.5 seconds or less.
- Interaction to Next Paint (INP): how fast the page responds to taps and clicks. Good is 200 milliseconds or less.
- Cumulative Layout Shift (CLS): how much the layout jumps while loading. Good is 0.1 or less.
Similar pages are grouped, so one template fix often moves many URLs at once. The data covers a rolling 28-day window, so improvements take a few weeks to show.
HTTPS: Is Every Page Served Securely?
The HTTPS report, also under Experience, counts how many of your indexed URLs use HTTPS. The goal is simple: as close to 100% as you can get.
If HTTP URLs show up, look for a missing redirect from HTTP to HTTPS. Also check for canonicals and sitemaps that still point to http:// addresses.
Enhancements: Structured Data and Rich Results
The Enhancements section only shows up for structured data types Google finds on your site. Structured data is code that tells Google what a page contains. A recipe site may see a Recipes report. An online shop may see Product snippets and Merchant listings. A site with breadcrumb markup will see Breadcrumbs.
Each report shows valid items and items with issues. Errors stop a page from being eligible for that rich result, so I fix those first. Warnings mean optional fields are missing. The page can still be eligible, but filling them in can make the result more complete.
Valid markup does not promise a rich result. If you have no Enhancements section at all, Google simply has not found supported structured data on your site.
Manual Actions and Security Issues
Under Security & Manual Actions are two reports you want to see empty.
- Manual actions: a human reviewer at Google has found a spam policy violation, such as unnatural links or low-value content made at scale. Affected pages, or the whole site, can drop or vanish from results.
- Security issues: Google has found hacked content, malware or deceptive pages. Browsers may show warnings to visitors.
“No issues detected” is the message you want. If something shows up, the report explains the problem and gives a Request review option. Fix the issue fully across the whole site first. Then explain clearly what you changed in the review request. The mistake I see most is asking for a review before the fix is complete.
Links: Who Links to You and How You Link Internally
The Links report, near the bottom of the menu, has two parts.
- External links: your most linked pages, the top sites linking to you, and the anchor text (link words) they use. It is a sample, not a full list, but it is Google’s own data.
- Internal links: which of your pages get the most links from other pages on your site.
For beginners, I find the internal links table the more useful one. If a key service page has very few internal links, add links to it from related articles and your menu.
A Simple Weekly Google Search Console Routine for Beginners
Fifteen minutes once a week covers most sites. This is the routine I suggest.
- Check email and the Overview page. Look for new messages, manual actions or security issues. These come before everything else.
- Compare the last 7 days with the 7 days before in the Performance report. Sort pages by the change in clicks and note any big drops.
- Check the Insights report for content trending up or down, if your account has it.
- Open Page indexing and see whether the “Not indexed” count jumped. Click any new or growing reason.
- Inspect new pages you published that week with URL Inspection, and request indexing if needed.
- Look quickly at Core Web Vitals, HTTPS and Enhancements for new Poor URLs or errors.
- Write down what changed and why. A simple shared document with the dates of site updates makes future drops much easier to explain. This habit has saved me more time than any report.
Once a month, go deeper. Compare 28-day periods, review non-brand queries, and look for pages with high impressions and low CTR. Do not judge anything on one or two days of data, because daily numbers swing.
Conclusion
Getting started with Google Search Console for beginners comes down to a short list. Verify a Domain property, submit your sitemap, learn the Performance report filters, and use URL Inspection whenever a page is not acting as expected. The other reports are health checks. Look at them weekly and act only when something changes.
My suggestion for your next step: set up the property today and run the “high impressions, low CTR” check from the Performance section. It usually turns up a few pages where a better title and description can win clicks you are already close to getting.
