What Google Search Console is — and what it is not
Google Search Console is a free service from Google that shows how your website appears in Google Search. It tells you which search queries bring up your pages, how often people click through, whether Google can crawl and index your site, and what problems it finds along the way. It is the only place where Google itself tells you what it thinks of your site.
That makes it the first tool to set up on any new website. Without it, you cannot know whether a page is indexed, which queries it ranks for, or whether a sudden traffic drop is a ranking problem, a crawling problem or a penalty.
It is worth being clear about what it is not. Search Console is not web analytics. It only reports on traffic that comes through Google Search, Google News and Discover — it cannot tell you how many people typed your address directly, arrived from social media or clicked an email link. That is the job of Google Analytics, and the two tools complement each other: Search Console shows how people found you on Google, Analytics shows what they did once they arrived. Section seven links them together.
Search Console also cannot make Google index your site or rank it higher. Adding a property does not change your position in the results, and requesting that Google crawl a page does not guarantee it will be indexed. What it does is show you the state of things and give you the tools to fix what is broken.
Before you start: what you need
Setting up Search Console takes about fifteen minutes of clicking and, in the worst case, up to two days of waiting — the waiting is for DNS changes to spread across the internet, not for Google. Before you start, gather four things so the process runs in one sitting.
First, a live website on a domain you control, with at least a few published pages. Search Console works on any site, on any platform — WordPress, a static site, a shop — but the site must be reachable on the public internet. A site still on a local test server or behind a password cannot be verified, because Google has to reach it to check the verification.
Second, a Google account you intend to keep. Use a business account or an account owned by the site, not a personal Gmail that belongs to one employee. The property is tied to the account that creates it, and if that account is lost, so is the easiest route back into the property. If someone else manages the site, they can be added as a user afterwards (see section eleven).
Third, access to either your domain's DNS settings or your website's admin area. Which one you need depends on the property type you choose in the next section: a Domain property needs DNS access, while a URL-prefix property can be verified through WordPress instead.
Fourth, your sitemap address. For most WordPress sites this is yourdomain.com/sitemap.xml, generated automatically by an SEO plugin such as Rank Math or Yoast SEO, or by WordPress itself. You do not need the sitemap to start the setup — it is submitted after verification — but knowing the address in advance saves a round trip. One account can manage up to 1,000 properties.
Step 1: Add your site as a property
A property is Search Console's word for a website you want to monitor. To add one, go to search.google.com/search-console and sign in with the Google account from the previous section. Click the property selector at the top left, then Add property. Search Console asks you to choose between two types.
A Domain property covers your entire domain: every subdomain, both http and https, and the www and non-www versions, all in one place. You create it by typing just the domain, for example example.com — no protocol, no www, no path. Google automatically includes www.example.com, m.example.com and any other subdomain. This is the type Google recommends for most sites, because it gives the complete picture in a single property.
A URL-prefix property covers only the URLs that start with the exact address you type, including the protocol. If you enter https://example.com/blog/, you will only see data for pages under /blog/. That is useful when you manage one section of a larger site, but it is a trap for a normal site: enter https://example.com and you will miss the http version and any subdomain entirely. If your site has www and non-www versions, or http and https, each needs its own URL-prefix property, and your data ends up split across several properties.
For a site you own outright, choose the Domain property. The only price is that it can only be verified through a DNS record, which is covered in the next section. If you cannot touch your DNS settings — for example, a client controls the domain and will not give you access — use a URL-prefix property instead and verify it through one of the methods in section five. Google has also started adding platform properties for Instagram, TikTok, X and YouTube accounts, rolling out gradually — for a website, choose the website property option.
Step 2: Verify ownership with a DNS record
Verification is the step where most people stall, so here is the plain version. Google needs proof that you control the site before it shows you its data — otherwise anyone could look up anyone else's search traffic. For a Domain property, there is only one verification method: a DNS record. You add a small text record to your domain's DNS settings, and Google checks that it is there.
When you create a Domain property, Search Console shows you a TXT record that starts with google-site-verification= followed by a long string of characters. Copy the whole value exactly — a single wrong character fails the check. Then open your domain registrar or DNS provider in another tab and find the DNS settings, sometimes called DNS management, DNS zone editor or nameservers, depending on the provider.
Add a new record with these values: the type is TXT, the host or name is @ (which means the root domain itself — some providers want the field left blank instead), the value is the string Google gave you, and the TTL can stay at its default. Save the record, go back to Search Console and click Verify. If Google can already see the record, verification succeeds immediately and the property opens.
Often it does not succeed on the first try, and that is normal. DNS changes take time to spread across the internet — anywhere from a few minutes to up to 48 hours. If verification fails, do not delete the record and start again: the record is probably fine, and Google simply cannot see it yet. Wait an hour or two and click Verify again. You can also click Verify later, finish the DNS step at your leisure, then select the saved property and click Verify.
Step 2 (continued): The four URL-prefix verification methods
If you chose a URL-prefix property, Google offers four verification methods, and the right one depends on what access you have. All four prove the same thing — that you control the site — so pick the one that is easiest in your setup and ignore the rest.
Method 1: HTML file upload
Google gives you a small HTML file to download. Upload it to the root directory of your website — the same folder that holds your homepage — using your hosting control panel's file manager or an FTP client. The file must be reachable at yourdomain.com/googleXXXXXXXXXXXX.html, exactly as Google shows it. Once it is in place, click Verify. This method suits anyone comfortable with a file manager, and it works on any platform. The file must stay on the server: deleting it later can unverify the property.
Method 2: HTML tag
Google gives you a meta tag — a single line of HTML starting with <meta name="google-site-verification". Copy it and paste it into the <head> section of your homepage, before the closing </head> tag. On WordPress, the easiest place is your SEO plugin: Rank Math has a Webmaster Tools field under General Settings, Yoast SEO has one under Settings. This is the fastest method for most WordPress users, because it needs no file access and no DNS change. The tag must stay on the homepage: removing it, or switching to a theme that drops it, unverifies the property.
Method 3: Google Analytics
If Google Analytics is already installed on the site, you can verify through it — no file and no tag needed. This only works when the Analytics tracking code is on the site and you are signed in to Search Console with the same Google account that has access to the Analytics property. If you set up Analytics using the guide on this site, this method is the path of least resistance: the tag is already there, so verification is a single click. If Analytics was installed by someone else under a different account, this method will fail, and you should use the HTML tag instead.
Method 4: Google Tag Manager
If the site runs Google Tag Manager, verification works the same way: the Tag Manager container snippet must already be on the site, and you must be signed in with the same Google account that manages the container. If you do not use Tag Manager, setting it up just for verification is more work than the HTML tag, so skip it.
Whichever method you pick, the same rule applies as with DNS: verification is not a one-time event. Keep the file, the tag or the Analytics code in place. Search Console checks ownership periodically, and if the proof disappears, the property becomes unverified and the data locks until you verify again. If verification keeps failing, check for the wrong property type, a typo in the pasted value, or a caching plugin serving an old homepage without the tag.
Step 3: Submit your sitemap
Once the property is verified, the next step is to tell Google where your pages are. A sitemap is a file that lists the pages you want Google to find, and submitting it helps Google crawl the site more efficiently It does not guarantee that Google will index every page in the sitemap, and it does not change rankings. It is a map, not a command.
To submit it, open the Sitemaps report in the left sidebar — under Indexing, then Sitemaps — paste the sitemap address and click Submit. For most sites the address is simply sitemap.xml, and Search Console adds the domain automatically. If your SEO plugin generates more than one sitemap — a common setup is a sitemap index that points to separate sitemaps for posts, pages and categories — submit the index file, and Google will follow the links inside it.
After submitting, the report shows a status for each sitemap. Success means Google fetched the file and read it. A Couldn't fetch error usually means the address is wrong, the file is blocked by robots.txt, or the server returned an error when Google asked for it — open the address in a browser and check what it returns. Submitting a sitemap is a one-time action per sitemap, not a daily task: Google re-checks the sitemap on its own schedule and picks up new pages as they appear in it. Resubmitting the same sitemap does not speed anything up. What matters is keeping the sitemap accurate — it should list live pages and update automatically when you publish. If your site has no sitemap at all, do not let that block you: Google can still find and index your pages through links.
Step 4: Link Google Analytics 4
Search Console and Google Analytics answer different questions, and linking them puts both answers in one place. With the link in place, Analytics can show Search Console data — which queries brought people to a page — next to its own behaviour data, so you can see not just that a page gets visits, but which searches sent them and what those visitors did next.
To link them, open Search Console, go to Settings, then Associations, and connect the Google Analytics property for the same site. The link can also be created from the Analytics side, under Admin, then Product links, then Search Console links. Either direction creates the same connection, and it only needs to be done once.
Two things the link does not do. It does not import historical Search Console data into Analytics — the combined reports only cover the period after the link is made, so link the two accounts as early as possible. And it does not change what either tool collects: Search Console still reports on Google Search traffic, Analytics still reports on all traffic, and the link simply lets each one show the other's data where it is relevant. If you have not set up Analytics yet, the guide on this site walks through it step by step — set that up first, then come back here and make the link.
Your first week: the four reports that matter
Search Console has many reports, and most of them can wait. In the first week, four are worth opening — they answer the only questions a new site has: is Google finding the site, is it indexing the pages, and is anyone arriving from search?
1. Performance
The Performance report is the report you will open most. It shows total clicks, total impressions, average click-through rate and average position for your site in Google Search, plus the same numbers broken down by query, page, country and device. In the first week the numbers will be small or empty, and that is normal — the report fills in as Google records searches. Its real value appears over months, when you can see which queries bring traffic and which pages are one position away from the first page.
2. Pages (under Indexing)
The Pages report shows which of your pages Google has indexed and which it has not, with a reason for each excluded page. In the first week, expect most pages to sit in one of the not-indexed groups — Google has not got around to them yet. What you are checking for is errors: server errors, redirect errors, pages blocked by robots.txt.
3. URL Inspection
URL Inspection answers one question about one page: what does Google know about this URL? Paste any full URL from your site into the search bar at the top of Search Console and it reports whether the page is indexed, when Google last crawled it, whether the mobile version renders correctly, and which canonical URL Google chose. It is the fastest way to check a single new post, and it is where you ask Google to crawl a page again after fixing it.
4. Core Web Vitals (under Experience)
The Core Web Vitals report groups your pages into Good, Needs improvement and Poor, based on real visitor data — loading speed, interactivity and layout stability. A new site usually has no data here yet, because the report needs enough real visits to measure. When data appears, the same fixes that move this report — image sizes, caching, a faster host — also move the rankings.
Two reports you can ignore for now: Manual actions, which stays empty unless Google has penalised the site, and Security issues, which only matters if the site is hacked. Search Console will email you if either one ever changes.
How to read the Performance report without fooling yourself
The Performance report looks simple — four numbers at the top, a chart, and a table of queries — but each number has a specific meaning, and misunderstanding one of them leads to wrong decisions.
An impression means someone saw a link to your site in the search results. The link does not need to be clicked, and in most cases it does not even need to be scrolled into view — if it was on the page of results the user received, it counts. A click means someone clicked a link that took them out of Google to your site; clicking something that stays inside Google, such as a query refinement, is not a click. The click-through rate is simply clicks divided by impressions, and the average position is the topmost position your link occupied, averaged across every query where it appeared.
Two consequences follow. First, a position of 5 does not mean your page ranks fifth for a search you care about — it is an average across all the queries where the page appeared, including ones you never targeted. A page can sit at an average position of 25 because it appears at position 3 for one query and position 60 for twenty others. Always filter the report by a single query or a single page before judging a ranking. Second, a link only gets a position recorded when it gets an impression: a page on the third page of results that nobody scrolls to has no recorded position at all, and the report shows a dash instead of a number.
The date range is the other control that matters. The report defaults to the last three months, and the date picker lets you compare one period with another — this month against the previous month, or the last 28 days against the one before. Use comparisons before celebrating or panicking: a drop that matches a holiday weekend is not a ranking problem. Once a week, sort the Queries table by impressions: queries with many impressions and few clicks are your opportunities — Google is already showing the page, and a better title can turn impressions into visits.
Fixing the first indexing problems
Most new sites hit the same indexing wall: pages exist, the sitemap is submitted, and Search Console still says they are not indexed. Usually nothing is broken — Google simply has not crawled them yet, and new sites wait in a queue behind established ones. But some exclusions are real problems, and the Pages report tells you which is which.
Open Indexing, then Pages, and read the reasons Google gives for the pages it has not indexed. "Discovered — currently not indexed" means Google knows the URL exists but has not crawled it yet: this is the normal queue, and the fix is patience plus internal links — link to the page from your homepage or from a popular post so Google's crawler finds it through the site's own structure. "Crawled — currently not indexed" means Google crawled the page and decided not to index it, usually because the content is thin, duplicated or very similar to another page: the fix is content, not settings — make the page genuinely useful and different from the pages around it.
A few reasons need action rather than patience. A "Blocked by robots.txt" entry means your robots.txt file is telling Google not to crawl the page — check the file and remove the block if the page should be indexed. A "Page with redirect" entry means the URL redirects somewhere else: Google indexes the destination, not the redirect, so check the redirect is intentional and the destination is indexed. A "Soft 404" means Google thinks the page looks like an error page even though it returns a success code — usually a thin or empty page, or a page that says "not found" in its text.
For a single page you care about, use URL Inspection. Paste the URL, read what Google reports, and if the page looks correct but is not indexed, click Request indexing. That asks Google to crawl the page again soon — it does not guarantee the page will be indexed, and there is a limit on how many requests you can make, so use it on pages that matter and that you have actually fixed, not on every page at once. One rule covers most indexing trouble: never try to force it. Submitting the same sitemap repeatedly or requesting indexing for dozens of pages a day does not make Google index pages faster.
Adding users and keeping access safe
Sooner or later someone else will need to see your Search Console data — a developer fixing an error, an SEO consultant auditing the site, a colleague writing content. The safe way to give them access is to add them as a user on the property, never to share your Google account password. A shared password gives them everything the account owns; a property user gets only that property, and you can remove them in a minute when the work is done.
To add someone, go to Settings, then Users and permissions, and add their Google account email address. Search Console has three levels. A verified owner has full control: they can see all the data, change settings, use every tool and manage other users. There are two kinds of owner — verified owners, who proved ownership through one of the methods in sections four and five, and delegated owners, who were granted ownership by a verified owner — but both have the same permissions. A full user can see all the data and use most of the tools, but cannot change settings or manage users. A restricted user can see most of the data but cannot take actions such as submitting sitemaps or requesting indexing.
For most help, full user is the right level: the person can see everything they need to diagnose a problem, but cannot change the property's settings or add other people. Restricted user suits someone who only needs to read the reports, such as a content writer checking which queries a post ranks for. Owner should stay with as few people as possible — ideally one account owned by the site, plus a backup owner account in case the first is ever lost. If someone asks for owner access, ask what they need it for: most tasks work fine as a full user.
Two access habits prevent most lockouts. First, keep the verification proof in place even after adding users — if the TXT record, HTML file or meta tag disappears, the property becomes unverified and every user loses access at once. Second, review the user list once in a while and remove anyone who no longer works on the site.
New in 2026: the Search Generative AI performance report
Search Console gained a new report in 2026, and it matters more than most of the year's other changes. On 3 June 2026, Google announced dedicated Search Generative AI performance reports in Search Console, giving site owners a separate view of how often their pages appear inside AI Overviews and AI Mode in Search, and inside generative AI features in Discover. After a staged rollout that started with a subset of websites, Google rolled the reports out to all websites worldwide on 31 August 2026.
The report answers one question: how often did links to your site appear in Google's AI features? It breaks the answer down by page, country, device and date, so you can see which of your pages Google's AI surfaces and where. What it does not show is equally important: it reports impressions only. There are no clicks, no positions and no click-through rate in this report, and it does not split AI Overviews from AI Mode — the two are counted together. Clicks from AI features still appear in the main Performance report, mixed in with ordinary search clicks, so the generative AI report is a visibility measure, not a traffic measure.
For most sites the report will be small or empty at first, and that is expected: a page only appears in it if Google's AI features actually showed a link to it, and many sites will have few or no such impressions. When numbers do appear, read them as a sign of which content Google considers worth citing — Google says appearing needs nothing beyond being indexed and eligible for a snippet, with no new files or markup. One related control arrived with the report: a site-wide setting under Settings, then Search generative AI, that opts the site out of appearing in AI Overviews, AI Mode and generative AI features in Discover. Opting out also stops Google using the site's content to generate responses in those features, so it is a decision to make deliberately, not a toggle to flip because the numbers look small.
Mistakes that break Search Console data — and how to avoid them
Most Search Console problems are not Google's fault — they are setup mistakes that split, hide or corrupt the data.
The most common mistake is creating the wrong property type. A URL-prefix property for https://example.com misses the http version, the www version and every subdomain, and a second property created later to cover them starts collecting from zero — the months of data in the first property stay in the first property. Choose the Domain property from the start, and if you already have a URL-prefix property, add the Domain property now and let both collect: the new one will not backfill the past, but it will give you the complete picture from today onwards.
The second mistake is removing the verification proof. A site redesign, a theme change or a DNS cleanup deletes the meta tag, the HTML file or the TXT record, and the property silently becomes unverified. Nobody notices until someone opens Search Console and finds the data locked. Treat the verification record as part of the site's infrastructure, like the domain renewal: note where it lives, and check it survives every redesign, migration and hosting move.
The third mistake is expecting data immediately. Search Console data starts collecting as soon as the property is added — even before verification — but it takes a few days for anything to appear, and the first weeks will look empty. A new property with no data is not broken; it is new. The mistake is to "fix" it by creating a second property, changing the property type or re-verifying, all of which restart the wait. Set it up once, submit the sitemap, and come back in a week.
The fourth mistake is submitting the wrong sitemap — an old sitemap from a previous platform, a sitemap that lists deleted pages, or a sitemap URL that redirects. Google trusts the sitemap you submit, so a stale one sends the crawler to dead pages and leaves new pages undiscovered. After any migration or plugin change, open the sitemap address in a browser and check it lists the pages the site actually has. The fifth mistake is reading the reports without a filter: the Performance totals mix every query and page together, so one number can hide the story. Always filter by page or query, and compare periods, before deciding what happened.
Finally, do not confuse Search Console with a ranking tool. It reports what Google recorded, after the fact, with a delay of a few days. It will not tell you where you rank right now, it will not predict where you will rank next week, and its numbers will never match a rank tracker's numbers exactly — they measure different things. Used for what it is — Google's own record of how your site performs in its search results — it is the most honest tool in SEO. Set it up once, keep the verification in place, and read it every week.
Frequently asked questions
Is Google Search Console free?
Yes. Google Search Console is a free service from Google, with no paid version and no limit on the number of properties up to 1,000 per account. You do not need it to appear in Google Search, but without it you cannot see how Google views your site or what problems it has found.
How long does Search Console take to show data?
Data collection starts as soon as the property is added, even before verification, but nothing appears in the reports for a few days. The Performance report fills in gradually, and the first weeks will look empty on a new site. If a property still shows no data after several days, the usual cause is the wrong property URL — for example, an http property for an https site.
Do I need Search Console if I already have Google Analytics?
Yes, because they answer different questions. Search Console shows how people found your site on Google — the queries, the impressions, the clicks and the indexing state of your pages. Google Analytics shows what people did after they arrived, from every source, not just search. Most sites run both, and linking them puts the search data next to the behaviour data in Analytics.
What is the difference between a Domain property and a URL-prefix property?
A Domain property covers the whole domain — every subdomain, both http and https, and the www and non-www versions — in one place, and it can only be verified with a DNS record. A URL-prefix property covers only URLs starting with the exact address you enter, so https://example.com misses the http version and every subdomain. For a site you own outright, the Domain property is the right choice.
How do I submit a sitemap to Search Console?
Open the Sitemaps report under Indexing in the left sidebar, paste your sitemap address — usually just sitemap.xml — and click Submit. Google will fetch the file and report a status: Success means it read the file. You only need to submit each sitemap once; Google re-checks it on its own schedule. If your SEO plugin generates a sitemap index, submit the index and Google will follow the sitemaps inside it.
Why does Search Console say a page is not indexed?
The common reasons are that Google has not crawled the page yet, which is normal for a new site and fixes itself with time and internal links; that Google crawled it and chose not to index it, usually because the content is thin or duplicated; or that something blocks it, such as robots.txt, a redirect or a soft 404. The Pages report under Indexing gives the exact reason for each page.
Search Console reports on Google Search traffic. Google Analytics 4 reports on what those visitors do once they arrive. The GA4 guide sets up the other half of the picture.
Set up Google Analytics 4 on WordPress ↗