GuidesSEO

Google Search Console: how to set it up and use it

Google Search Console is Google’s free report on how your site performs in search. To start, add a property, prove you own it with a DNS record or an HTML tag, submit your sitemap, and then read the Performance and Page indexing reports. Any Google account can use it. Data starts collecting once the property is verified.

Updated November 16, 20265 steps6 min read

Grow my organic traffic →

$1 today. Cancel anytime before day 7.

Search Console setup, start to finish
  1. 1Add a propertyChoose Domain for everything on your domain, or URL prefix for one exact address.
  2. 2Verify ownershipAdd the DNS record Google gives you, or use an HTML tag or file for a URL prefix property.
  3. 3Submit your sitemapOpen Sitemaps, enter the sitemap path, and submit it once.
  4. 4Read PerformanceFilter queries and pages by clicks, impressions, CTR, and average position.
  5. 5Check Page indexingOpen the report weekly and look at why pages are not indexed.
On this page
  1. Add and verify your property
  2. Submit a sitemap
  3. Read the Performance report
  4. Check indexing and inspect URLs
  5. Common setup mistakes to avoid
  6. A ten-minute weekly routine
  7. Questions

Add and verify your property

Sign in with a Google account and add a property. A Domain property covers every protocol and subdomain under your domain, so http, https, www and blog all land in one view. It verifies only with a DNS record, which you add at your domain registrar or DNS host.

A URL prefix property covers one exact address, such as the https www version. It offers more ways to verify: an HTML file uploaded to the site root, an HTML tag in the head of the homepage, or an existing Google Analytics or Google Tag Manager connection. If you can reach DNS, pick Domain. If you only have access to the site’s CMS, URL prefix is the way in.

Leave the verification record or tag in place afterwards. Removing it can revoke access. Add anyone else who needs the data as a user under Settings instead of sharing a login.

Submit a sitemap

Open Sitemaps in the left menu, type the path of your sitemap, usually sitemap.xml, and submit it. Most CMS platforms generate one for you. The report shows when Google last read it and how many URLs it found.

A sitemap is a hint, not an order. It helps Google discover pages and tells it which URLs you consider canonical, but it does not guarantee indexing. List only the pages you want in search: no redirects, no noindex pages, no parameter duplicates. If pages in the sitemap are being skipped, the next section explains where to look.

You submit once. After that Google re-reads the file on its own schedule. Come back to the Sitemaps report only to confirm the status says Success.

Want the articles written for you?

Researches keywords and what competitors rank for. Publishes to WordPress, Webflow, Shopify or Framer once you approve.

Read the Performance report

Performance is where most people spend their time. It shows four numbers: total clicks, total impressions, average CTR, and average position. Switch between the Queries, Pages, Countries, and Devices tabs to slice them. The default view covers the last three months, and the report keeps about sixteen months of history.

Three views are worth building the habit around. Sort Queries by impressions and look for terms with a lot of impressions and a low CTR: the page ranks but the title does not earn the click, which is a title tag problem. Filter to one page to see every query it earns. Compare two date ranges to confirm whether a drop is real or seasonal.

Average position is an average across every search where you appeared, so it moves around for reasons that are not rankings. Use it to compare, not to report a single rank.

Performance data has limits worth knowing. Search Console shows aggregated data, and Google omits some rare queries to protect privacy, so the query rows will not add up to the total. Rows in tables are also capped, so export the data when you need a complete set to work with.

Check indexing and inspect URLs

The Page indexing report splits your known URLs into indexed and not indexed, with a reason for each group. Not every excluded URL is a problem. Redirects, pages with a noindex tag, and alternate versions are meant to be excluded. The ones to chase are important pages marked Discovered - currently not indexed or Crawled - currently not indexed. The fix for those is in pages that will not index.

For a single page, paste its address into the search bar at the top to open the URL Inspection tool. It tells you whether the page is indexed, which canonical Google chose, and what the live page looks like when Google fetches it. After you fix something, Request indexing asks Google to look again. The URL Inspection guide covers each field.

The same menu holds the Core Web Vitals report when your site has enough data. It is worth a glance, but the indexing report comes first.

Common setup mistakes to avoid

The most frequent mistake is verifying the wrong property. If your site lives on the https www version and you verify only the http version, the reports will be empty. A Domain property avoids this because it covers every version, which is the main reason to choose it when you can edit DNS.

The second is expecting instant data. A new property starts collecting data from the moment it is verified, and the Performance report fills in over the following days. Nothing before verification is backfilled, so verify early, even if the site is not launched.

Third, reading every excluded page as an error. Many are intended. Fourth, ignoring access: add colleagues and agencies as users with the right permission level and remove people who have left. An owner who leaves the company with the only login is a common and annoying way to lose a property.

A ten-minute weekly routine

Once a week: open Performance and compare the last 28 days to the previous period. Note the top pages that gained or lost clicks. Open Page indexing and check that the count of indexed pages did not fall without a reason. Check Sitemaps for errors. Then check the Security issues and Manual actions sections, which should say there are none.

Export the numbers monthly if someone needs a report. The SEO reporting guide shows what to put around them. For the technical issues Search Console surfaces, the technical SEO checklist gives the order to fix them in.

The part you can hand off: Sprites connects to Search Console and reads queries, pages and indexing status, can run a weekly index health check as an autopilot, and proposes fixes as approval cards you edit and approve before anything changes.

Questions

How do I submit a sitemap to Google?

Open Search Console, choose Sitemaps in the left menu, enter the sitemap path such as sitemap.xml, and select Submit. You only do this once. Google re-reads the file on its own, and the report shows the last read date and the number of URLs found.

What is Google Search Console used for?

It shows which queries and pages bring you search clicks, whether your pages are indexed and why some are not, and whether Google found problems such as manual actions or security issues. It is also where you inspect a single URL and request indexing.

Can I see who searched for my name?

No. Search Console reports aggregated queries, clicks, and impressions. It never shows which individual person searched or clicked. Rare queries may be omitted from the report to protect privacy.

Is Google Search Console free?

Yes. You need a Google account and a site you can verify. There is no paid tier. Search Console is separate from Google Analytics, which measures what visitors do after they arrive.

Domain property or URL prefix property?

Choose Domain when you can edit DNS, because it combines every subdomain and protocol into one report. Choose URL prefix when you can only add a tag or file to the site, or when you want a report scoped to one section or version of the site.

Keep going

Have Sprites grow your organic traffic

  • Researches keywords and what competitors rank for
  • Audits your pages and writes the articles
  • Publishes to WordPress, Webflow, Shopify or Framer once you approve