What is Google Search Console? Complete Beginner's Guide (2026)

What is Google Search Console?

Google Search Console is a free web service from Google that lets you monitor, maintain, and troubleshoot how your site appears in Google Search results. Think of it as the official channel of communication between Google and your website. When Google encounters a problem crawling, indexing, or ranking a page, GSC is where Google tells you about it. When you want to ask Google to recrawl a page, submit a sitemap, or check if a URL is indexed, GSC is where you do it.

The tool was first launched in 2006 as Google Webmaster Tools. In 2015 Google rebranded it to Google Search Console to reflect that the audience is no longer just webmasters, but marketers, SEOs, designers, and small business owners. The product was rebuilt from the ground up in 2018 with a faster interface, 16 months of historical data, and clearer reports. The 2018 version is the one you use today.

You access it at search.google.com/search-console with any Google account. There is no paid tier and no usage cap on the standard reports. Once verified, GSC will collect data about your site continuously, even if you never log in.

Why every site owner needs it

If your site is not in Google Search Console, you are flying blind. You will not know which keywords actually bring users to your site, which pages Google has indexed, whether Google has issued a manual penalty against your domain, or whether your site has been hit with a security warning that is scaring users away. None of that information is available anywhere else for free.

Some specific reasons GSC is non-negotiable:

• It is the only source of real query data. Google Analytics will tell you a user came from organic search, but it will not tell you which keyword they searched. GSC is the only free tool that reveals the actual search terms.

• It tells you when Google cannot index your pages. If your robots.txt is blocking crawlers, if a page is marked noindex by mistake, or if a server error is preventing indexing, GSC will surface the problem in the Pages report.

• It alerts you to manual actions and security issues. If a human reviewer at Google decides your site is violating spam guidelines, you will only find out through Search Console. Same for hacked content warnings.

• It is required for many other tools. Most third-party SEO platforms, including RankFrame, integrate with GSC to pull live performance data. Without verification, those integrations cannot work.

• It is free, forever. Unlike most SEO tools, there is no trial, no upgrade, no per-domain pricing. You can verify hundreds of properties on one account.

What data does Google Search Console show you?

Search Console captures data across four broad categories: search performance, indexing status, user experience, and security. Here is what each category gives you.

Search performance data

• Impressions: how many times a link to your site appeared on a Google search results page that was viewed.

• Clicks: how many times users clicked one of those links.

• Click-through rate (CTR): clicks divided by impressions, expressed as a percentage.

• Average position: the average ranking of your URLs across all impressions, weighted by query.

• Queries: the actual search terms users typed. You can filter and segment by query, page, country, device, search appearance, and date.

Indexing data

• Indexed pages: how many of your URLs Google has accepted into its main index.

• Not indexed pages: URLs Google knows about but has decided not to index, with a reason for each (Crawled, currently not indexed; Discovered, currently not indexed; Excluded by noindex tag; etc.).

• Sitemaps: which sitemaps you have submitted, when they were last fetched, and how many URLs were discovered.

• URL Inspection tool: live status of any single URL, with details on the last crawl, the rendered HTML, mobile usability, and any structured data Google detected.

User experience data

• Core Web Vitals: field data from real Chrome users measuring Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).

• Mobile Usability: historically reported issues like text too small or clickable elements too close. This report was retired in late 2023 but the data still informs ranking.

• HTTPS: whether your site is fully served over HTTPS and whether any HTTP URLs are leaking into the index.

Security and manual action data

• Manual actions: human-issued penalties for spam, unnatural links, thin content, sneaky redirects, or other guideline violations.

• Security issues: alerts when Google detects malware, phishing, hacked content, or social engineering on your site.

How to set up Google Search Console

Setup takes about 5 to 10 minutes. You need a Google account and access to either your domain registrar, your CMS, or your DNS provider. Here is the full process.

Sign in and add a property

Go to search.google.com/search-console and sign in with the Google account you want to use. If you run a business, use a shared Google Workspace account so the property does not get locked to one individual.

Click Add property in the top-left dropdown. You will see two options: Domain and URL prefix.

Choose Domain or URL prefix

Domain property covers every subdomain (www, blog, shop) and every protocol (http, https) under a single property. It can only be verified by DNS record. This is the recommended option for most sites because it gives the most complete picture.

URL prefix property only covers exact URLs that match the prefix you enter, including the protocol and subdomain. It supports more verification methods, including HTML tag, HTML file, Google Analytics, and Google Tag Manager. This is the right choice if you cannot edit DNS or if you only want to track one specific subdomain.

If you are unsure, add both: a Domain property for full coverage and a URL prefix property for the exact site you care about.

Verify ownership

Choose one of the verification methods (covered in detail below) and complete the steps Google shows you. Once verified, do not remove the verification record or tag, because Google periodically rechecks it. If verification fails, your property will be marked unverified and data collection will pause.

Submit your sitemap

Once verified, go to Indexing > Sitemaps and submit your sitemap URL (usually /sitemap.xml). Google will fetch it within a few hours and start using it to discover pages. You can submit more than one sitemap if your site has separate ones for blog posts, products, or images.

Wait for data

Performance data takes 1 to 2 days to appear after verification. Indexing reports populate as Google crawls your URLs, which can take days for new sites and longer for very large sites. Core Web Vitals data requires enough real-user traffic to populate the Chrome User Experience Report and may take weeks on low-traffic sites.

Verifying ownership: 5 methods compared

Google offers five ways to prove you own a property. The right one depends on what you have access to.

For most CMS-based sites, the HTML meta tag method is the fastest. You paste a snippet that looks like this into your site's head:

<meta name="google-site-verification" content="abc123longverificationstringxyz" />

<meta name="google-site-verification" content="abc123longverificationstringxyz" />

<meta name="google-site-verification" content="abc123longverificationstringxyz" />

Then you click Verify in Search Console. Google fetches your homepage, reads the tag, and confirms ownership. The whole process typically takes under 30 seconds.

Tip: verify multiple ways Google recommends keeping more than one verification method active. If your CMS strips your meta tag during a redesign, the DNS or GA fallback keeps your property verified. Add backups under Settings > Ownership verification.

The key reports and how to read them

Search Console has a lot of menu items, but five reports do most of the work. Master these and you have covered 90 percent of what GSC is useful for.

1. Performance > Search results

This is the report you will open most often. It shows total impressions, clicks, average CTR, and average position over a date range you choose (up to 16 months). You can group results by:

• Queries: the actual search terms users typed

• Pages: which URLs on your site are getting impressions

• Countries: where in the world your impressions come from

• Devices: desktop, mobile, or tablet

• Search appearance: rich result types like FAQ, sitelinks, or video

• Dates: day-by-day trend over your selected window

You can stack filters. For example, filter to Pages contains /blog/ and Country = United States and Device = Mobile to isolate exactly the segment you want to analyze.

2. URL Inspection

The URL Inspection tool is a single search bar at the top of the Search Console interface. Paste any URL on your verified property and Google will show you:

• Whether the URL is indexed and eligible for Search

• The last crawl date and the user-agent that crawled it

• The canonical URL Google selected (which may differ from your declared canonical)

• Indexing allowed status, including any robots.txt or noindex blocks

• Mobile usability and Core Web Vitals (when available)

• Detected structured data with validation errors

You can also click Test live URL to fetch the current version of the page in real time, which is useful when you have just shipped a fix and want to confirm it.

3. Indexing > Pages

This report tells you how many of your pages are indexed and, just as importantly, why some are not. Google groups not-indexed URLs by reason. Common reasons include:

• Crawled, currently not indexed: Google fetched the page but decided not to index it, often because content quality is borderline or duplicate.

• Discovered, currently not indexed: Google knows the URL exists (usually from a sitemap or link) but has not crawled it yet.

• Duplicate without user-selected canonical: Google found multiple very similar pages and picked a different one as canonical.

• Excluded by noindex tag: the page has a noindex directive (intentional or not).

• Page with redirect: the URL redirects somewhere else, so it does not get indexed itself.

• Soft 404: Google thinks the page returns successful HTTP status but shows a not-found message.

4. Sitemaps

Submit your XML sitemap here. Google will report when it was last fetched, the success status, and how many URLs were discovered. If the count is much lower than your real page count, your sitemap may have a generation bug. If the status is Couldn't fetch, your sitemap URL is broken or blocked.

5. Core Web Vitals

This report uses real-user data from the Chrome User Experience Report (CrUX) to grade your URLs as Good, Needs improvement, or Poor for each Core Web Vital metric. URLs are grouped into similar templates, so you do not have to fix every page individually. If the report says 0 URLs, your site does not have enough Chrome traffic to populate the field data, and you should rely on lab data from PageSpeed Insights instead.

Bonus: Links

The Links report shows which external sites are linking to you (top linking sites and top linked pages) and your internal linking patterns. It is not as detailed as paid backlink tools like Ahrefs or Majestic, but it is the only first-party source for what Google itself considers your link profile to look like. Use it to spot toxic referral spam and to identify which pages are well linked internally.

Bonus: Security & Manual Actions

If everything is fine, both reports will simply say No issues detected. That is the goal. If anything appears here, treat it as a top priority. Manual actions can drop your traffic to zero overnight, and security warnings will trigger browser-level interstitials that turn users away.

GSC vs Google Analytics: what is the difference?

The single most common confusion among new site owners is the difference between Google Search Console and Google Analytics. Both are free Google products. Both deal with website data. But they answer fundamentally different questions.

You should use both. GSC tells you how to get more clicks from Google. Analytics tells you whether those clicks turn into business. They complement each other and you can even link the two so GSC data appears inside the Analytics interface under Acquisition > Search Console.

What Google Search Console does NOT do

GSC is incredibly useful, but it is not a complete SEO platform. Knowing the limits will save you time looking for features that do not exist.

• It does not show traffic data the way Analytics does. No sessions, no pageviews, no bounce rate, no time on page. Clicks are not the same as sessions because one user can click the same result twice in two sessions.

• It does not show competitor data. You cannot see your competitors' rankings, traffic, or backlinks in GSC. For that you need a tool like Ahrefs, Semrush, or RankFrame.

• It does not give you live ranking scores. Average position is averaged across many impressions and locations. It is not a real-time rank tracker. If you want to see your rank for a specific keyword in a specific city today, you need a dedicated rank tracker.

• It does not show every keyword. A significant share of long-tail queries are anonymized to protect user privacy. You will see your top queries but never the full picture.

• It does not crawl your site for technical issues on demand. The Pages report only shows what Google has tried to index. For a comprehensive technical audit (broken links, redirect chains, missing alt text), you need a dedicated crawler.

• It does not write or fix anything for you. GSC tells you what is wrong. Implementing the fix is up to you and your CMS.

• It does not show data for non-Google search engines. Bing has its own equivalent called Bing Webmaster Tools.

Common misconception

Many new SEOs check Search Console daily and panic when impressions drop. Daily fluctuation is normal. Look at 28-day or 3-month trends, not day-over-day movement, before drawing conclusions.

If you have a Framer site

Framer fully supports Google Search Console verification, but a few specifics are worth knowing. The simplest verification path for a Framer site is the HTML meta tag method against a URL prefix property. Here is the workflow:

1. In Google Search Console, click Add property > URL prefix and enter your full Framer site URL (for example https://yoursite.com, including https and the correct subdomain).

2. Choose the HTML tag verification method. Copy the meta tag Google generates.

3. In Framer, open your project and go to Site Settings > General > Custom Code. Paste the meta tag into the Start of <head> tag field.

4. Publish your site so the change goes live.

5. Return to Search Console and click Verify.

Once verified, submit your Framer sitemap. Framer auto-generates a sitemap at /sitemap.xml for every published site. Go to Indexing > Sitemaps in GSC, paste sitemap.xml into the field, and click Submit.

Where things get interesting is what you do with that GSC data day-to-day. Logging into Search Console, switching properties, applying filters, and exporting CSVs is fine but slow when you live inside the Framer editor. RankFrame integrates directly with Google Search Console and pulls live performance data into Framer itself. You can see top queries, top pages, indexing status, and average position right next to the page you are editing. When you spot a page with high impressions but low CTR, you can rewrite the meta title in the same panel and republish without leaving Framer.

For Framer-specific verification walkthroughs, see our guides on verifying a Framer site in Google Search Console and submitting a Framer sitemap.