Google Search Console Tutorial: Monitor Your SEO Performance

Google Search Console Tutorial: Monitor Your SEO Performance

Google Search Console is an indispensable tool for any business that wants to understand how its website performs in Google search results. Unlike Google Analytics, which tracks what happens after visitors arrive on your site, Search Console reveals how your site appears in search, which queries bring users to your pages, and whether Google can properly crawl and index your content.

For Singapore businesses competing for visibility in local and regional search results, Search Console provides data that simply cannot be obtained elsewhere. It shows you exactly which search terms drive impressions and clicks, highlights technical issues that may be hurting your rankings, and provides direct communication from Google about problems affecting your site’s search performance.

This google search console tutorial walks you through every essential feature of the platform. Whether you are new to SEO or looking to deepen your technical knowledge, you will learn how to verify your site, interpret performance data, fix indexing issues, submit sitemaps, and monitor Core Web Vitals — all the skills needed to support a strong SEO strategy.

Step 1: Verify Your Website in Search Console

Before you can access any data, you need to prove to Google that you own or manage the website. Search Console offers several verification methods, and the best choice depends on your technical setup and access level.

Domain property (recommended): This verification method covers all subdomains and protocols (http, https, www, non-www) under your domain. To use it, go to search.google.com/search-console and click “Add property.” Select “Domain” and enter your domain name (for example, “mybusiness.sg” without https://). Google provides a DNS TXT record that you must add to your domain’s DNS settings through your domain registrar (such as GoDaddy, Namecheap, or Vodien for Singapore domains). Once the record is added, click “Verify.” DNS propagation can take a few hours, so if verification does not succeed immediately, wait and try again.

URL prefix property: This method verifies a specific URL prefix, such as “https://www.mybusiness.sg.” It is simpler but only covers that exact prefix — meaning you would need separate verifications for http, https, www, and non-www versions. Google offers several verification methods for URL prefix properties: uploading an HTML file to your website’s root directory, adding a meta tag to your homepage’s head section, using your Google Analytics tracking code, using your Google Tag Manager container snippet, or adding a DNS record.

For WordPress sites: The easiest approach is often the HTML tag method. Copy the meta tag provided by Search Console, then use a plugin like Yoast SEO or Rank Math — both have dedicated fields for the Search Console verification code. Simply paste the code, save your settings, and click “Verify” in Search Console.

Grant access to others: After verification, you can add users under Settings, then Users and Permissions. Add your marketing team or digital marketing agency as either Full or Restricted users. Full users can view all data and perform actions like submitting sitemaps, while Restricted users can only view data.

Step 2: Use the Performance Report

The Performance report is the most valuable feature in Search Console for SEO practitioners. It shows how your website performs in Google search results over time, providing data on four key metrics.

Total clicks: The number of times users clicked through to your website from search results. This is your actual organic search traffic as measured by Google. Total impressions: The number of times your website appeared in search results, regardless of whether the user clicked. Average CTR (click-through rate): The percentage of impressions that resulted in clicks. Average position: Your average ranking position in search results for the queries that triggered your site.

Analyse by queries: Click the “Queries” tab to see which search terms are driving impressions and clicks to your site. Sort by impressions to discover queries where your site appears frequently but receives few clicks — these represent opportunities to improve your meta titles and descriptions to increase CTR. For Singapore businesses, look for local queries containing “Singapore,” “SG,” or area names like “Orchard,” “Tampines,” or “Jurong.” These queries indicate local search demand relevant to your business.

Analyse by pages: The “Pages” tab shows which of your pages receive the most search traffic. Identify your top-performing pages and analyse what makes them successful. Also look for pages with high impressions but low CTR — these pages rank reasonably well but fail to attract clicks, suggesting their search snippets need improvement.

Filter by date range: Use the date filter to compare performance across different periods. Comparing the last three months to the previous three months reveals trends in your organic search growth. If you recently published new content or made SEO changes, monitoring the performance report shows whether those efforts are producing results.

Filter by country and device: For Singapore businesses targeting the local market, filter results by country to see performance specifically from Singapore-based searchers. The device filter reveals whether your traffic comes primarily from mobile or desktop — in Singapore, mobile typically accounts for over 70 per cent of search traffic, making mobile optimisation critical.

Step 3: Monitor Indexing and Coverage

The Pages report (previously called the Coverage report) shows the indexing status of all URLs on your website. This is where you discover whether Google can find and index your pages — if a page is not indexed, it cannot appear in search results.

Understand the status categories: The report categorises URLs into several groups. “Indexed” pages are in Google’s index and can appear in search results. “Not indexed” pages have been discovered but are not in the index for various reasons. The report further breaks down reasons for non-indexing, which helps you diagnose and fix issues.

Common indexing issues: “Discovered – currently not indexed” means Google knows about the page but has not crawled it yet. This can indicate low-priority pages or crawl budget limitations. “Crawled – currently not indexed” means Google has crawled the page but decided not to index it, often because the content is thin, duplicated, or low quality. “Excluded by ‘noindex’ tag” means the page has a noindex meta tag or HTTP header, which is correct for pages you intentionally exclude from search. “Blocked by robots.txt” means your robots.txt file prevents Google from crawling the page.

Review regularly: Check the Pages report at least monthly. A sudden spike in “Not indexed” pages could indicate a technical problem — perhaps a website update accidentally added noindex tags or broke internal links. For Singapore businesses that rely heavily on organic traffic for leads and sales, catching indexing issues early prevents revenue loss.

Validate fixes: After resolving an indexing issue, click “Validate Fix” in Search Console. Google will re-check the affected URLs over the following days and update the report accordingly. This is faster than waiting for Google to naturally re-crawl the pages.

Step 4: Submit and Manage Sitemaps

A sitemap is an XML file that lists all the important pages on your website, helping Google discover and crawl them efficiently. While Google can find pages through links, submitting a sitemap ensures comprehensive coverage.

Generate your sitemap: Most website platforms generate sitemaps automatically. WordPress sites using Yoast SEO or Rank Math create sitemaps at yourdomain.sg/sitemap_index.xml. Shopify stores automatically generate sitemaps at yourdomain.sg/sitemap.xml. For custom-built websites, you may need to use a sitemap generator tool or have your developer create one.

Submit your sitemap: In Search Console, navigate to “Sitemaps” in the left menu. Enter the URL of your sitemap (for example, “sitemap.xml” or “sitemap_index.xml”) and click “Submit.” Search Console will process the sitemap and report how many URLs were discovered and how many were successfully indexed.

Monitor sitemap status: After submission, check the status regularly. The report shows whether the sitemap was successfully read and the last date Google processed it. If you see errors — such as “Couldn’t fetch” or “Has errors” — investigate immediately. Common issues include incorrect URLs in the sitemap, pages returning 404 errors, and sitemap formatting problems.

Keep your sitemap current: Ensure your sitemap updates automatically when you add, modify, or remove pages. Most CMS platforms handle this automatically. If your sitemap includes URLs that return 404 errors or redirect to other pages, clean them up to maintain a healthy sitemap. A well-maintained sitemap signals to Google that your website is properly managed, which can positively influence crawling frequency.

Step 5: Monitor Core Web Vitals

Core Web Vitals are a set of user experience metrics that Google uses as ranking signals. Search Console provides a dedicated report showing how your website performs against these metrics, based on real user data from the Chrome User Experience Report.

Understand the three metrics: Largest Contentful Paint (LCP) measures loading performance — how quickly the largest content element (usually a hero image or heading) becomes visible. Google considers LCP good if it occurs within 2.5 seconds. Interaction to Next Paint (INP) measures interactivity — how quickly the page responds to user interactions like clicks and taps. Good INP is under 200 milliseconds. Cumulative Layout Shift (CLS) measures visual stability — how much the page layout shifts unexpectedly during loading. Good CLS is under 0.1.

Review the report: In Search Console, navigate to “Core Web Vitals” under the Experience section. The report separates data for mobile and desktop, with URLs categorised as “Good,” “Needs Improvement,” or “Poor.” Click on any issue to see which URL groups are affected and what specific metric is failing.

Fix common issues: For poor LCP, common fixes include optimising images (using WebP format, applying lazy loading), implementing a content delivery network, reducing server response time, and minimising render-blocking resources. For poor INP, reduce JavaScript execution time, break up long tasks, and optimise event handlers. For poor CLS, always specify width and height attributes on images and videos, avoid inserting content above existing content dynamically, and use CSS transform animations instead of layout-triggering properties.

Prioritise mobile: In Singapore, where the majority of web browsing occurs on mobile devices, focus on mobile Core Web Vitals first. Mobile pages often have more performance challenges due to slower network connections and less powerful hardware. Work with your web design team to ensure your site delivers excellent mobile performance.

Step 6: Use the URL Inspection Tool

The URL Inspection tool allows you to check the indexing status of any specific URL on your website. It provides detailed information about how Google sees that page, making it invaluable for diagnosing issues with individual pages.

Inspect a URL: Enter any URL from your verified property into the search bar at the top of Search Console. The tool fetches the current indexing data for that URL, showing whether it is indexed, when it was last crawled, and whether any issues were detected.

Review the results: The inspection results show several key pieces of information. “URL is on Google” confirms the page is indexed and can appear in search results. “Coverage” shows how the page was discovered (sitemap, referring page, or other). “Mobile Usability” indicates whether the page passes mobile-friendliness checks. “Structured data” shows any schema markup detected and whether it contains errors.

Request indexing: If you have published a new page or made significant updates to an existing page, use the “Request Indexing” button to ask Google to re-crawl the URL. This does not guarantee immediate indexing, but it prioritises the URL in Google’s crawl queue. Note that there is a daily limit on indexing requests, so use this feature selectively for your most important pages.

View rendered page: Click “View Crawled Page” to see the HTML that Google retrieved and a screenshot of how Google rendered the page. This is particularly useful for diagnosing JavaScript rendering issues — if important content appears in the HTML source but not in the rendered version, your JavaScript may not be executing properly for Googlebot.

Step 7: Identify and Fix Common Errors

Search Console alerts you to various errors that can impact your website’s search performance. Understanding and resolving these errors promptly is a core part of maintaining strong SEO health.

404 errors (Page Not Found): These occur when Google tries to access a URL that does not exist. Check the referring pages to understand why Google is trying to reach these URLs. If the content has moved, implement 301 redirects from the old URLs to the new ones. If the pages were intentionally removed and no replacement exists, 404 errors will naturally resolve over time as Google removes them from its index.

Server errors (5xx): These indicate that your web server failed to respond to Google’s request. Occasional server errors are normal, but persistent ones suggest hosting problems. Contact your web hosting provider or check your server logs to identify the cause. For Singapore businesses using local hosting, ensure your server has sufficient resources to handle both user traffic and Googlebot’s crawling.

Redirect errors: These occur when redirects are misconfigured — for example, redirect chains (A redirects to B, which redirects to C) or redirect loops (A redirects to B, which redirects back to A). Simplify redirect chains so that each URL redirects directly to its final destination. Redirect loops must be broken by correcting the destination URL.

Mobile usability issues: The Mobile Usability report flags pages with problems like text too small to read, clickable elements too close together, and content wider than the screen. Given Singapore’s mobile-first search behaviour, fixing these issues is essential. Most mobile usability problems can be resolved through responsive web design and proper viewport configuration.

Structured data errors: If you use schema markup (such as LocalBusiness, Product, or FAQ schema), Search Console reports any validation errors. Common issues include missing required fields, incorrect data types, and deprecated markup formats. Fix these errors to ensure your pages remain eligible for rich results in search, which can significantly improve click-through rates.

Security issues: Search Console alerts you if Google detects malware, hacking, or other security problems on your website. These issues can result in warning labels appearing in search results, which devastates click-through rates. If you receive a security notification, act immediately — clean the affected pages, remove any malicious code, and submit a review request once the issue is resolved.

Frequently Asked Questions

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

After verifying your website, it typically takes two to three days before data starts appearing in Search Console. The Performance report has a data delay of approximately 48 hours, meaning the most recent data available is from two days ago. Historical data for your website may also be available going back to the time before you verified, as Google collects this data regardless of whether you have a Search Console account.

Should I verify both www and non-www versions of my site?

If you use a Domain property verification, this is unnecessary — the Domain property automatically covers all subdomains and protocol variations. If you use URL prefix verification, you should ideally verify all variants (http, https, www, non-www) to get complete data. However, the simplest approach is to use Domain verification, which provides the most comprehensive data coverage.

How often should I check Google Search Console?

For active websites, checking Search Console weekly is a good practice. Focus on the Performance report for traffic trends, the Pages report for new indexing issues, and any new messages or notifications from Google. If you are in the middle of an SEO campaign or have recently made significant website changes, checking daily is advisable until performance stabilises. Setting up email notifications ensures you are alerted to critical issues even between manual checks.

Can Search Console help me find keyword opportunities?

Absolutely. The Performance report reveals queries where your site appears in search results. Look for queries with high impressions but low average position (meaning you rank on page two or three) — these represent keywords where you have existing relevance but need to strengthen your content or build more backlinks to reach page one. Also identify queries with good rankings but low CTR, which suggest your meta titles and descriptions need improvement to attract more clicks.

What is the difference between Search Console and Google Analytics?

Search Console and Google Analytics serve complementary purposes. Search Console focuses on your website’s presence in Google search — it shows search queries, impressions, click-through rates, indexing status, and technical health. Google Analytics tracks what happens after users arrive on your site — page views, engagement, conversions, and user behaviour. For a complete picture of your SEO performance, you need both tools. They can also be linked together so you can view Search Console data directly within your GA4 reports.

How do I remove a URL from Google search results?

Search Console provides a URL Removal tool under the “Removals” section. You can request temporary removal of a URL, which hides it from search results for approximately six months. For permanent removal, you must also block the URL on your website — either by adding a noindex meta tag, returning a 404 status code, or blocking it in robots.txt. The temporary removal buys you time to implement the permanent solution. Note that the removal tool only affects Google search — it does not delete the page from your website or from other search engines.