Зміст
What Google Search Console is and why a business needs it
Who absolutely needs it: any business with a website that wants traffic from Google. Online store, services site, blog, landing page, no difference. If you invest money in SEO promotion and don’t look in Search Console, you’re paying for work whose results you can’t verify.
GSC vs Google Analytics: the difference
Google Search Console works before the click. It knows that a person entered a query, saw your site in the results at some position, and clicked (or didn’t). The data source is the Google search engine itself.
Google Analytics 4 works after the click. It picks the person up once they are already on the site: how many pages they viewed, how long they stayed, whether they reached the cart, whether they left a request. The data source is the tracking code on your pages.
| Question | Answered by Search Console | Answered by Analytics |
|---|---|---|
| Which keywords do people use to find me on Google? | Yes | No (Google hides organic search queries) |
| What is my position in search results? | Yes | No |
| Which pages are indexed? | Yes | No |
| How many people submitted a form? | No | Yes |
| Where did the traffic come from (sources)? | Partially (Google Search only) | Yes (all sources) |
The correct picture comes only from the two tools together. Search Console shows whether Google brings you visitors and for which words. Analytics shows what those people do next. That’s why we always connect both at the start of website analytics work: separately they each give you half the answer.
How to connect and verify your site
- Sign in to Search Console under the Google account that will be the main one for the site. Use a corporate email rather than a personal one, so you don't lose access if an employee leaves.
- Add a property. Google offers two types: "Domain" and "URL prefix." Domain covers the entire site at once: all subdomains, http and https. URL prefix covers only a specific address. For a business, "Domain" is almost always the better choice.
- Verify ownership. For the "Domain" type there is one method: add a TXT record in your domain settings (at your registrar or hosting provider). For "URL prefix" there are more options: an HTML file in the site root, a meta tag in the head section, or a linked Google Analytics or Google Tag Manager account.
- Click Verify. A DNS record sometimes takes up to a day to update, but usually Google sees it within minutes. The other methods work instantly.
https://site.com version, while the site also opens on https://www.site.com. To Google these are two different properties. Half the data is “smeared” across the unverified version, and the reports show an incomplete picture. The “Domain” type removes this problem: it collects every version into one profile.
How to submit a sitemap
Most content management systems generate the sitemap automatically. On WordPress it’s created by the Yoast SEO or Rank Math plugin (the address is usually /sitemap_index.xml), platforms like OpenCart and Shopify have built-in modules, and site builders form the sitemap themselves. Check that the sitemap actually opens: enter its address in a browser and a list of URLs should appear.
Next, in Search Console, open the Sitemaps section, enter the path (for example, sitemap.xml) and click Submit. After a few days you’ll see the status in the same section: how many URLs were read. A “Couldn’t fetch” status means the sitemap is unreachable at that address or contains errors. A status like “Discovered 500, indexed 120” is a signal that Google decided not to index more than two-thirds of the pages, and it’s time to find out why.
When we first open a new client’s Search Console, the picture is almost always the same: the sitemap was either never submitted, or an old one was submitted that’s missing half the new pages. It can be worse: the sitemap was serving hundreds of service and junk URLs (filters, sorting, technical pages), and Google was spending its crawl budget on those instead of product cards. The first thing we do at the start is look not at positions, but at this gap between “discovered” and “indexed.” It almost always shows where the site is getting in its own way of reaching search.
How to submit a sitemap
- Impressions – how many times your site appeared in the search results.
- Clicks – how many times it was clicked.
- CTR – the share of clicks out of impressions (clicks / impressions).
- Average position – your average place in the results.
How to find quick wins for growth
- Find queries with high impressions and low CTR. The site shows up often, but few people click. The likely cause is that the title and description in the results don't grab attention. Rewrite them. It's half an hour of work, and the lift in clicks is often one and a half to two times.
- Find queries in positions 8-20. This is "the second page and the bottom of the first." The page is already relevant, Google almost trusts it, and it just needs a little more: internal links, expanded text, an updated date. Pushing a page from position 12 to position 5 is far cheaper than writing a new one from scratch.
- Compare periods. Turn on the "last 28 days vs the previous period" comparison. Queries where the position dropped are your first signal that something broke or a competitor overtook you.
Indexing: why pages don't make it into Google
| Status in the Report | What It Means | What to Do |
|---|---|---|
| Discovered – Currently Not Indexed | Google knows about the page but has chosen not to index it, often due to thin or duplicate content | Improve content uniqueness and add internal links |
| Page with Redirect | The URL redirects to another address | Check whether the redirect is intentional |
| Blocked by robots.txt | The robots.txt file prevents search engines from crawling the page | Remove the restriction if the page should appear in search results |
| Excluded by 'noindex' Tag | The page contains a meta tag that prevents indexing | Remove the noindex tag from pages that should be indexed |
| Duplicate, Google Chose Different Canonical | Google considers this page a duplicate of another page | Review the canonical tag settings |
What to do when a page isn't indexed
Here is the step-by-step logic when an important page won’t make it into search. First, open it in URL Inspection and read the reason: GSC almost always names it directly. If the reason is “Blocked by robots.txt”, open your site’s robots.txt file (it lives at site.com/robots.txt) and find the Disallow line blocking the section you need. If it’s “Excluded by noindex tag”, check the page code for <meta name="robots" content="noindex">: sometimes this tag stays behind after a site is moved from a test server, where it was added on purpose.
Once the cause is fixed, return to URL Inspection and click “Request indexing.” It isn’t instant: Google puts the page in a queue and crawls it within a few hours to a few days. You can’t request indexing manually at scale (hundreds of pages), which is exactly why you need a correct sitemap that does it systematically.
The Links report: who links to your site
Internal links are more useful than they seem. A page that has many internal links pointing to it gets more weight in Google’s eyes. If your main commercial page has only two or three internal links, while some secondary article has fifty, you’re signalling the wrong priorities to Google yourself. This is a matter of sound internal linking, and the Links report shows you where the structure is skewed.
Technical reports: speed, mobile, penalties
Core Web Vitals. A report on page loading speed and stability, based on data from real users. Google uses these metrics as a ranking factor, so a slow site loses positions regardless of content quality. If the report is glowing red, it’s a reason for technical optimisation.
Mobile usability. Google indexes sites by their mobile version first. If text overflows the screen on a phone or the buttons are too close together, this report shows it.
Manual actions. The most important and most often forgotten report. If Google applies a manual penalty, for unnatural links, spam, or a hacked site, the notice appears right here. A penalised site can simply vanish from the results. In most cases the owner finds out from Search Console or doesn’t find out at all until traffic falls to zero. If you see a notice here, it’s not a reason to panic, but it is a reason to act fast: we handle search engine penalty removal separately, and the earlier you start, the easier the recovery.
How to connect GSC with analytics and see the data in one place
First, integration with Google Analytics 4. In the GA4 settings there’s a “Search Console links” option. After linking, Analytics gets a report where organic queries from GSC sit next to behaviour metrics: how many people came for a query, how many of them reached a conversion. This closes the blind spot of each tool alone: GSC doesn’t know what happened after the click, and GA4 doesn’t show the queries themselves. Together they show the full path: query, click, action on the site.
Second, export to Looker Studio. If you need a dashboard for a manager or client, GSC connects to Looker Studio (Google’s free report builder) as a data source. In half an hour you assemble a panel showing the trend of clicks, positions and top queries, without weekly manual downloads from the interface. The owner doesn’t need to go into Search Console: they open one tab and see the picture.
This exact setup – GSC, GA4 and a dashboard in one place – is what we configure at the start of SEO promotion, so that both the team and the owner look at the same data instead of arguing whose counter is “more correct.”
Why the numbers in GSC and Google Analytics don't match
- A click is not a session. Search Console counts clicks in search. If a person clicked but closed the page before the Analytics counter loaded, GSC counts the click and Analytics doesn’t. That’s why GSC usually shows more.
- Blockers and cookie refusals. Some visitors block analytics with browser extensions or don’t consent to cookies. This doesn’t matter for GSC (it counts on Google’s side), but in Analytics those people simply don’t appear.
- Different time zones and periods. The tools may count a day by different zones. At the turn of the month this creates a noticeable difference.
- Different definitions of “organic.” What Analytics counts as organic traffic and what GSC considers a click from Google search aren’t always the same. Analytics collects organic from all search engines, GSC only from Google.
What to check weekly: a short checklist
- The Performance report – compared with the previous period. Are clicks and positions rising or falling?
- Queries with low CTR – are there new candidates for a title rewrite?
- Indexing – has the number of excluded pages grown?
- Manual actions and Core Web Vitals – once a month, to check for new problems.
Search Console data is useful to compare not only with analytics but also with your advertising data. For example, if you rank well organically for a certain query, you may not need to overpay for it in paid search, and vice versa. This is the logic we apply during a PPC audit: organic data from GSC shows where ads are duplicating free traffic.
What an owner won't see alone: 5 common findings
- Keyword cannibalisation. Two or three pages of the site compete for the same query, confuse Google, and keep any of them from reaching the top. You can see this in the Performance report if you look at which URLs show for the same word.
- Pages in positions 8-15 that nobody pushes over the line. Dozens of queries sit "on the threshold" of the first page. Targeted work on them gives a faster lift than new content, but the owner doesn't see them, because they don't filter the report by position.
- Pages dropping out of the index after technical changes. A migration to a new platform, a change of URL structure, a site update, and part of the pages quietly fall out. Without a regular review, this only gets noticed when sales drop.
- The gap between impressions and clicks. The site shows up en masse, but the CTR is twice below the niche norm. The cause is almost always weak titles and descriptions that can be rewritten in a day.
- Opportunity queries the business never suspected. The Performance report surfaces phrasings you already get found by, but for which there's no dedicated page. It's a ready hint about which content to create next.
FAQ
-
What is Google Search Console and how is it different from Google Analytics?
Google Search Console shows how your site looks from the search engine's side: which queries it appears for, at what positions, which pages are indexed and where the technical errors are. Google Analytics shows what people do once they are already on the site: where they came from, how many pages they viewed, whether they left a request. GSC is before the click, Analytics is after the click. You need both for the full picture. -
How do I verify ownership of a site in Search Console?
The most reliable method is domain verification (a TXT DNS record in your domain settings), because it covers all subdomains and protocols at once. If you don't have DNS access, you can use an HTML file in the site root, a meta tag in the head, or a Google Analytics or Tag Manager account linked to the same site. After adding the record, click Verify and Google checks it within seconds. -
How do I check whether a page is indexed?
Paste the full page URL into the URL Inspection bar at the top of Search Console. If you see "URL is on Google" the page is in the index. If you see "URL is not on Google" the system shows the reason: not found in the sitemap, blocked by robots.txt, marked noindex, or carrying a canonical tag pointing to another page. You can request indexing from the same screen. -
What does the Performance report show and how do I read it?
The Performance report shows four metrics: impressions (how many times your site appeared in search), clicks (how many times it was clicked), CTR (the share of clicks out of impressions) and average position. The most useful slice is the Queries tab: it shows the actual words people use to find you. Pages with high impressions and low CTR are your fastest resource for growing traffic without new content. -
How do I submit a sitemap (sitemap.xml) to Search Console?
Open the Sitemaps section in the left menu, enter the path to your sitemap (usually sitemap.xml or sitemap_index.xml) and click Submit. Google starts crawling the listed pages. After a few days you'll see the status in the same section: how many URLs were read and how many made it into the index. A "Couldn't fetch" status means the sitemap is unreachable at that address or contains format errors.
