Google Search Console: A Beginner’s Guide

Google Search Console is a free tool from Google that shows how your website performs in Google Search. It tells you which searches bring people to your site, which pages Google has indexed, and what technical problems are stopping pages from appearing. If you own or manage a website, it is the first SEO tool to set up.

This Google Search Console guide is written for beginners. It covers how to add and verify your site, then walks through the reports you will use most: Performance, Page indexing, URL Inspection, Sitemaps and Core Web Vitals.

You do not need any technical background to follow it. You will need access to your website or your domain settings for the verification step.

What is Google Search Console?

Google Search Console is Google’s own dashboard for website owners. It reports how often your pages appear in Google Search, how often people click them, which queries trigger them and whether Google can crawl and index them. It costs nothing, and the data comes straight from Google rather than from a third-party estimate.

That last point is why I set it up before anything else on a new project. Paid SEO tools estimate traffic from their own data. Search Console shows what actually happened in Google.

It is useful for:

• Business owners who want to know whether their site is visible in Google at all.
• Marketers who need to see which pages and searches bring in visitors.
• Developers who need to confirm Google can crawl and render a site after changes.
• Agencies and freelancers who report on SEO work for clients.

Search Console vs Google Analytics

Beginners often mix the two up. They answer different questions, and most sites need both.

How to set up Google Search Console

Setting up Search Console means adding your website as a “property” and proving you own it. Google’s help page on adding a website property describes two website property types. Pick the right one first, because it decides how much of your site you see.

Google’s page says a Domain property needs DNS record verification, unless the site runs on a Google product such as Blogger or Google Sites. When you type a Domain property, leave out the https:// and the www. Data collection starts as soon as the property is added, and the page says to expect data within a few days.

Here are the steps:

1. Sign in to Search Console with the Google account the business will keep long term, not a personal account that might leave with a staff member.
2. Open the property selector and choose to add a property.
3. Choose Domain (recommended) or URL-prefix and enter your domain or address.
4. Pick a verification method and follow the instructions.
5. Click Verify. If DNS changes have not spread yet, save the method and try again later.

How to verify your site in Search Console

For a Domain property, Search Console gives you a TXT record to add in your domain provider’s DNS settings. Copy it exactly, save it, then return to Search Console and click Verify. Some providers apply changes quickly. Others take longer, so a failed first attempt usually just means waiting.

URL-prefix properties offer other methods, such as uploading an HTML file to your site, adding a meta tag to your homepage, or using an existing Google Analytics or Google Tag Manager setup. These are handy if someone else controls the DNS.

Two habits save trouble later:

• Leave the verification in place. Search Console keeps checking it. Remove the DNS record, file or tag and you can lose access.
• Add a second owner. If the only owner leaves the business, getting back in becomes a chore. Add another person under Settings, then Users and permissions.

If an agency or freelancer needs access, add them as a user from that same screen rather than handing over your Google login. Owners can add and remove users. Full users can see all data and take some actions, while restricted users mostly just view.

The Performance report: clicks, impressions, CTR and position

The Performance report shows how your site does in Google Search results. It is where you will spend most of your time. Google’s Performance report documentation defines four metrics.

The same page explains that the chart’s average position covers your whole site, while the table shows it for each query or page. The default view is the past three months. The most recent data can be preliminary, shown as a dotted line, and may still change.

How to read the Performance report

Below the chart is a table with tabs. Each tab groups the same data a different way:

• Queries: the searches people typed when your site appeared.
• Pages: which URLs appeared and earned clicks.
• Countries and Devices: where searchers were and what they used.
• Search appearance: special result types your pages showed in.
• Dates: the figures day by day.

The most useful habit is combining a filter with a tab. Click a page, then switch to the Queries tab, and you see every search that page appeared for. That shows you whether a page is ranking for what you intended. If it is not, your keyword research and the page content may need another look.

Use the date filter’s compare option to put two periods side by side, such as the last three months against the three before. Compare like with like, though. A seasonal business will always look worse in its quiet months.

A quick win for beginners: sort the Pages tab by impressions, then look for pages with plenty of impressions and few clicks. Their title tags and meta descriptions are worth rewriting first. My on-page SEO checklist covers how.

The Page indexing report: which pages Google has stored

The Page indexing report shows how many of your URLs Google has indexed and why the others were not. A page that is not indexed cannot appear in Google Search, so this report tells you whether your important pages are even in the running.

Google’s Page indexing report documentation is clear that you should not expect every URL to be indexed. Duplicates, pages you blocked on purpose and pages without useful content are meant to stay out. It also says that if your site has fewer than 500 pages, you probably do not need this report and can check with a site: search instead.

The reasons you are most likely to see include:

• Alternate page with proper canonical tag: usually fine. Google found a duplicate and indexed the version you pointed to.
• Page with redirect: usually fine, as long as you meant to redirect it.
• URL marked ‘noindex’: check each one was deliberate.
• Not found (404) and Soft 404: fix them if real pages are affected.
• Crawled – currently not indexed and Discovered – currently not indexed: worth a closer look if your key pages are listed.
• Server error (5xx): talk to your developer or host if it keeps happening.

Once you fix an issue across the site, open it in the report and click Validate fix. Google’s page says validation typically takes up to about two weeks. If you are not sure which issues matter, my SEO audit checklist starts with exactly these indexing checks.

The URL Inspection tool: checking one page

The URL Inspection tool tells you what Google knows about a single URL. Paste any address from your property into the search bar at the top of Search Console. You will see whether the URL is on Google, plus details about how it was crawled and indexed and which canonical Google chose.

Google’s URL Inspection tool documentation explains the difference between the two views:

• The indexed result shows the most recently indexed version of the page, which may be older than what is live now.
• Test live URL fetches the page in real time. It confirms whether Google can access the page, but not that it will be indexed.

After you publish or update an important page, you can click Request indexing. Be realistic about what that does. The same page says a request does not guarantee the page will be indexed, there is a daily limit on requests, and you cannot request indexing for a page the live test finds non-indexable. For many new or updated pages at once, submit a sitemap instead.

I use this tool most after a site change: inspect a few key templates, run a live test and check that the rendered page still shows the main content and links.

The Sitemaps report: telling Google what to crawl

A sitemap is a file listing the URLs you want search engines to know about. Most content management systems and SEO plugins create one for you, often at an address such as /sitemap.xml or /sitemap_index.xml.

To submit it:

1. Open your sitemap in a browser to confirm it loads.
2. In Search Console, open the Sitemaps report.
3. Enter the sitemap URL in the “Add a new sitemap” box and click Submit.
4. Check the status. “Success” means Google read it without errors. “Couldn’t fetch” or a list of errors means something needs fixing.

You need owner permission to submit a sitemap. Keep it clean: only canonical URLs that load properly and that you want indexed. A sitemap full of redirects and 404s sends mixed signals. The technical SEO checklist covers sitemaps and robots.txt together.

The Core Web Vitals report: page experience data

The Core Web Vitals report shows how your pages perform for real visitors, using field data from the Chrome UX Report. It covers three metrics: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability).

The report groups similar URLs together and labels each group Good, Needs improvement or Poor, separately for mobile and desktop. A group’s status is set by its worst metric. If your site has little traffic, the report may say there is not enough data, which is normal for small or new sites.

When a group is flagged, open it, note the example URLs and test them in PageSpeed Insights to find the cause. Fix the template, not just one page, because the whole group usually shares the same problem.

Other Search Console reports worth checking

You do not need every report every week, but these are worth knowing:

• Links: your top linked pages, the sites that link to you most, the most common link text and your most internally linked pages. Useful for spotting important pages with few internal links.
• Manual actions: shows whether a human reviewer at Google has found pages that break its spam policies. You want to see no actions listed.
• Security issues: flags problems such as hacked content. Again, you want nothing listed.
• Settings: where owners manage users and permissions.

If a manual action ever appears, fix every affected page before you request a review, and explain in the request what you changed.

A simple Search Console routine

Search Console is most useful when you look at it regularly and briefly, rather than once a year in a panic. Here is a routine I would suggest for a small business site:

1. Weekly (10 minutes): open the overview, scan for new alerts, and check that clicks have not dropped sharply.
2. Monthly: compare the last month with the one before in the Performance report. Note pages and queries that rose or fell.
3. Monthly: check the Page indexing report for new issues affecting pages you care about.
4. After any site change: inspect key URLs with a live test and check the sitemap status.
5. Quarterly: look at Core Web Vitals and Links, and export Performance data you want to keep for reporting.

Common Google Search Console mistakes

• Setting up only one URL-prefix property (for example http:// without www) and missing most of the data. A Domain property avoids this.
• Treating every “not indexed” page as a problem. Many are expected. Focus on pages that should rank.
• Requesting indexing over and over for the same page. It does not speed things up and you will hit the daily limit.
• Reading average position as a ranking. It is an average across every query and impression, so one figure can hide very different positions.
• Losing access because the only owner left, or the verification record was deleted during a hosting move.
• Looking at clicks without context. Seasonality, a site migration or a new competitor can all move the numbers.

FAQs

Is Google Search Console free?

Yes. Google Search Console is free for anyone who can verify they own or manage a website. You only need a Google account and access to your domain settings or website files to complete verification, after which you can add other users to the property.

How long does it take for data to appear in Search Console?

Google’s help page on adding a property says to expect data within a few days. Data collection starts as soon as the property is added, even before verification is complete. Brand new websites may show very little at first simply because Google has not crawled or ranked many pages yet.

What is the difference between Search Console and Google Analytics?

Search Console reports how your site appears in Google Search: impressions, clicks, queries and indexing. Google Analytics reports what visitors do on your site from every source, including enquiries and sales. Search Console tells you how people found you on Google, and Analytics tells you what happened after they arrived. Linking the two puts some search data inside Analytics.

Why are my pages not indexed in Google?

Open the Page indexing report and look at the reason given for each URL. Common causes are a noindex tag, a robots.txt block, a redirect, a canonical pointing elsewhere, a 404 or Google deciding the page is not worth indexing yet. Some of these are deliberate and fine. Fix the ones affecting pages you want to rank, then validate the fix.

Get help reading your Search Console data

Setting up Search Console takes an afternoon, and checking it for a few minutes each week will tell you more about your site than most paid tools. If you would like an experienced eye on what your reports are saying and which fixes to do first, take a look at my GA4 and analytics setup services.