How to Set Up Google Search Console in 2026: Step-by-Step Guide

Google Search Console is free, but the setup screens assume you already know what a “property” is and why Google wants a DNS record. Pick the wrong option and you can spend a week staring at an empty report. This guide walks through the whole Google Search Console setup in five steps, using only what Google’s own documentation says, so you get it right the first time.

What You Need Before Setting Up Search Console

To set up Google Search Console you need three things: a Google Account, a published website that anyone can open without a password, and access to either the site’s code or its domain settings. Google’s property guide says one Search Console account can hold up to 1,000 properties, so a single login covers every site you run.

The sign-up page is the official Google Search Console homepage. Click Start now, sign in with the Google Account you want to own the data, and you land on the welcome screen. There is no separate registration form and no fee.

What kind of access do you actually need? It depends on the verification method you pick later:

• Access to your domain provider’s DNS settings, if you want a Domain property (the most complete option).
• The ability to edit your homepage’s HTML or upload a file to the site root, for most URL-prefix methods.
• Edit rights in Google Analytics or Publish rights in Google Tag Manager, if those tools already run on the site.
• Admin access to your site builder (WordPress, Shopify, Squarespace, Wix), if you prefer the platform’s built-in connection.

Not sure whether your DNS lives with your registrar or your web host? Our explainer on what a domain does versus what hosting does sorts out which company controls which settings.

One reassurance from Google before you start: adding a property “does not affect your website or platform property on Google Search.” If you stop halfway or hit a setup problem, Google says “it won’t hurt your website.” You can save your progress and come back.

Which Google Account should you use? Use one your business controls, not a personal account that leaves with an employee or a freelancer. Everyone else can get their own access later through users and permissions, covered in Step 4.

Key Takeaways

One Search Console account can hold up to 1,000 properties, according to Google’s property guide. Choose a Domain property if you can edit DNS, because it covers every subdomain and protocol. Verify ownership, then keep the verification token in place for good. Submit your sitemap, give teammates their own user access instead of sharing a login, and link Google Analytics 4 last.

Domain Property vs URL-Prefix Property: Which to Choose

A Domain property covers your whole domain and needs DNS verification; a URL-prefix property covers only one exact address and offers many verification methods. Google’s property guide defines a Domain property as one that includes “all subdomains (m, www, and so on) and multiple protocols (http, https, ftp),” while a URL-prefix property “includes only URLs with the specified prefix, including the protocol.”

	Domain property	URL-prefix property
What you type	example.com	https://www.example.com/
What it covers	Every subdomain and every protocol	Only URLs that start with that exact prefix
Verification	DNS record only	HTML file, HTML tag, Google Analytics, Google Tag Manager or DNS
Good for	Seeing all of a site’s search data in one place	One section of a site, or when you can’t edit DNS

Google’s own examples make the difference concrete. A URL-prefix property for http://example.com/ includes http://example.com/dresses/1234, but not the https version and not the www version of the same page. A Domain property for example.com includes all three, plus addresses like http://support.m.example.com/dresses/1234.

So which should you pick? We recommend a Domain property for most small sites. Nothing falls through the cracks when a site moves from http to https or adds a blog subdomain. Pick a URL-prefix property when you only manage one folder of a bigger site (for example example.com/es/), when you want separate data for each language folder, or when you have no access to DNS. You can always have both: Google lets you add a URL-prefix property next to an existing Domain property.

Platform and Google-hosted properties

Search Console now lists two more property types in the same menu. Platform properties track how your posts on Instagram, TikTok, X and YouTube perform on Google Search, Discover and Google News. Google announced on July 29, 2026 that platform properties “are globally available to everyone.” They verify through an existing website property or by logging in to the platform, and they only report Google traffic, not views inside the app. Google-hosted properties cover sites on Google Sites, Blogger and Workspace. If you run a regular website, you can ignore both for now.

Step 1: Sign In and Add Your Property

Adding a property takes about a minute: open the property selector, choose Add property, pick the type and enter your address. According to Google’s instructions, data collection “starts as soon anyone adds the property to their Search Console account, even before verification,” so it pays to add the property today even if verification has to wait.

Here is the exact flow:

1. Open Search Console and click the property selector at the top of the left menu (on a brand-new account, the welcome screen opens instead).
2. Select + Add property.
3. Choose Website property, then choose Domain or URL prefix.
4. Type your domain (example.com) for a Domain property, or the full address with protocol (https://www.example.com/) for a URL-prefix property.
5. Pick a verification method and follow the steps on screen, or click Verify later to save your progress.

What if you can’t finish in one sitting? Verify later saves the property as unverified. When your DNS record or tag is in place, select the saved property in the property selector and click Verify.

Two details save trouble later. First, type the protocol that your site really uses. Google warns that a property with no data several days after verification often has the wrong URL, “for example, you specified http instead of https.” Second, domains with non-Latin characters work as typed; Google supports internationalized domain names, so bücher.example.com shows up correctly.

Taking over a site that someone already set up? You may not need to add anything. If an owner has already granted you access, the property simply appears in your property selector.

Step 2: Verify Ownership

Verification proves to Google that you control the site, and it is the step that unlocks all data and tools. Google’s verification help page says a verified owner “has the highest degree of permissions in Search Console,” which is why Google asks for proof before it hands over the keys. Search Console supports six methods:

Method	Works for	What you need	Watch out for
Domain name provider (DNS)	Domain and URL-prefix properties	Login to your domain provider	Records can take up to two or three days to go live
HTML file upload	URL-prefix only	Ability to upload a file to the site root	The file must open without a login
HTML tag	URL-prefix only	Ability to edit the homepage <head>	The tag must sit in the first 2MB of the page
Google Analytics tracking code	URL-prefix only	Edit rights in Analytics; gtag.js or analytics.js in the <head>	Same Google Account in both tools
Google Tag Manager	URL-prefix only	Publish or Admin permission on the container	The noscript part must follow the opening <body> tag
Google Sites or Blogger	Sites on those services	Same Google Account as the site	Older blogs use the HTML tag method

DNS verification for a Domain property

DNS is the only way to verify a Domain property, and for many providers it is also the easiest. If Search Console lists your provider, choose it, log in, and verification “should occur immediately,” according to Google. Otherwise Search Console gives you a TXT record that starts with google-site-verification=. Add it at your provider with the host field left blank or set to @, then click Verify. A few setups need a CNAME record instead; Google’s help page explains how to check which one applies using the Google Admin Toolbox.

Don’t know who your DNS provider is? It is usually the company you bought the domain from. Our comparison of domain registration sites shows where each major registrar keeps its DNS settings.

Google’s most important warning is about what happens after success: “To stay verified, don’t remove the DNS record from your provider, even after verification succeeds.” The same goes for the HTML file and the meta tag. Search Console checks for the token periodically, and if it disappears your permissions expire after a grace period.

Tips that apply to every method

• Add a second method as a backup. Google suggests this in case a template change removes, for example, an Analytics tag.
• Child properties verify themselves. Once example.com is verified, a new property such as https://example.com/blog/ is verified with the same method automatically.
• DNS on a URL-prefix property counts twice. Google says that if you use the DNS method on a URL-prefix property, “you will also be auto-verified for the Domain property.”
• Tag methods follow redirects. Search Console looks for the tag on the page where a logged-out visitor lands. The file method does not follow redirects to another domain.
• Several people can verify the same property, each with their own token. Just don’t overwrite another owner’s token.

Is there a way to check whether your DNS provider is serving the record yet? Yes. Look up your domain in the Google Admin Toolbox; if the google-site-verification value isn’t listed, wait a day or two and try again.

Step 3: Submit Your Sitemap

Submitting a sitemap means telling Google where your sitemap file lives so it can find your important URLs faster. Google’s getting started guide says pages can be found without one, but that submitting a sitemap “might speed up your site’s discovery.” According to Google’s sitemap guidelines, one sitemap can hold up to 50,000 URLs or 50MB uncompressed, and bigger sites split their URLs across several files listed in a sitemap index.

Do you even need this step? Google’s Sitemaps report page says probably not if your site has about 500 pages or fewer and every page is reachable through links from the homepage. Sites on hosted builders such as Squarespace or Wix usually have the sitemap managed for them. For everyone else, it takes two minutes:

1. Find your sitemap. Most CMSs and SEO plugins publish it at an address like /sitemap.xml or /sitemap_index.xml.
2. Run a live URL inspection on the sitemap address and check that Page fetch says Successful.
3. Open Indexing > Sitemaps, paste the address into Add a new sitemap and click Submit.

You need owner permissions on the property to submit through the report, according to that same help page. Without them, list the sitemap in your robots.txt file instead. You also can’t upload a sitemap file to Google; you only tell Google its address.

Each sitemap then shows one of three statuses: Success, Has errors or Couldn’t fetch. Success means every URL Google could parse is queued for crawling, which is not a promise that every page gets indexed. The report only lists sitemaps submitted through it or through the API, and it shows up to 1,000 of them.

When sitemap URLs still don’t make it into Google, the cause is usually on the page itself. Our guide to the most common Search Console indexing problems and their fixes walks through each status in the Page indexing report.

Step 4: Add Users and Set Permissions

Adding users gives teammates, freelancers or an agency their own access, so nobody has to share your Google login. Google’s users and permissions page says a property can have a maximum of 100 non-owners, and only owners can add or remove anyone. There are four roles:

• Owner: full control. A verified owner proved ownership with a token; a delegated owner was added by another owner without a token. Both have the same rights.
• Full user: “view rights to all data and can take some actions.”
• Restricted user: “simple view rights on most data.”
• Associate: an account that acts on your site’s behalf in another Google product (Google’s example is the Chrome Web Store) without seeing Search Console data.

Here is what each role can do with the features that matter most during setup, taken from Google’s permission table:

Feature	Owner	Full user	Restricted user
Add users and owners	Yes	No	No
Link a Google Analytics account	Yes	No	No
Performance and all other reports	Yes	Yes	Yes
URL Inspection	Yes	Yes	Fetch only
Remove URLs	Yes	Yes	View only
Change of Address	Yes	View only	View only
Disavow links	Yes	Yes	No
Verify fixes	Yes	Yes	No

To add someone, open Settings > Users and permissions, click Add user, enter their Google Account email, choose a permission level and save. Each person needs a valid Google Account, and Google says “an email group cannot be added as a user.”

Which role should a freelancer get? In our view, Full is enough for nearly all SEO work, because it covers reports, URL Inspection and fix validation. Keep Owner for people who should also manage users and links. The owner limits are generous: delegated owners can be added until a property reaches 500 total owners, and verified owners have no maximum.

Removing an owner takes one extra step. A removed verified owner can verify again for as long as their token stays on your site. Remove the user, then delete their HTML file, meta tag or DNS record. Search Console lists leftovers under Unused ownership tokens, and Ownership history records every owner added or removed.

Step 5: Link Google Analytics 4

Linking Google Analytics 4 puts Search Console’s query and landing page data next to what visitors do on your site. The Analytics Help page on the integration says the link adds two reports to Analytics, and that Search Console data reaches both tools “48 hours after it is collected by Search Console.”

You need two permissions: the Editor role on the Analytics property and verified ownership of the Search Console property. Then:

1. In Google Analytics, open Admin and, under Product links, click Search Console Links.
2. Click Link, then Choose accounts, and pick the Search Console property you own.
3. Click Confirm, then Next, and select the web data stream for your site.
4. Review the settings and submit.

The two new reports are Google Organic Search Queries (queries with Search Console metrics) and Google Organic Search Traffic (landing pages with both Search Console and Analytics metrics). Here’s the catch most people miss: the Search Console report collection is “unpublished by default.” Open Library in the Analytics menu and publish it, or the reports won’t show up in the navigation.

Know the limits before you link. One web data stream links to one Search Console property, and the reverse is also true. Links can’t be edited, only deleted and created again. Analytics shows at most 16 months of Search Console data, the same window Search Console keeps. Do you need this link to use Search Console at all? No. It is optional, which is why it comes last.

Platform Notes: WordPress, Shopify, Squarespace and Wix

Most site builders have a shortcut for Search Console verification, and Google itself suggests checking your host’s documentation before trying the standard methods. The verification help page also notes that “Site Kit is the only plugin that is officially sponsored by Google,” so research any other plugin before you install it.

WordPress

Site Kit by Google is the official plugin. It is free and open source, needs WordPress 5.2 or later and PHP 7.4 or later, and reported more than 5 million active installations on its WordPress.org page on October 24, 2026. Install it from Plugins > Add New, connect your Google Account and follow the setup flow; it handles verification without editing code. If several admins want access, each one connects their own Google Account. We’d start with Site Kit on a new WordPress site simply because it comes from Google. SEO plugins that offer a field for the HTML tag are an alternative, and the tag ends up in the same <head> either way.

Still picking a host for a new WordPress site? Our guide to choosing WordPress hosting by plan type covers what to compare. And if the site is mainly a blog, our guide to getting blog posts found in Google picks up where this setup ends.

Shopify

Shopify’s sitemap help page uses a URL-prefix property and the HTML tag method:

1. Add a URL-prefix property with https:// and choose HTML tag.
2. In Shopify admin, open Online Store, then Edit code on your theme, then theme.liquid.
3. Paste the meta tag on a blank line directly below the opening <head> tag and save.
4. Click Verify in Search Console. If it fails, Shopify suggests waiting 15 minutes and trying again.

Turn off private mode first, because Google can’t reach a private store. Shopify generates sitemap.xml automatically at the root of each domain. Stores on the Basic plan or higher that use international domains verify each domain and submit each sitemap separately.

Squarespace

Squarespace connects from inside the site, according to its verification guide. Open the Analytics panel, click Search keywords, click Connect, sign in to Google and click Allow. Keyword data can take 72 hours to appear. A few rules apply: trial sites can’t be verified because they are hidden from search engines, passwords must be off, and Squarespace doesn’t support the file upload method. If you just connected a third-party domain, Squarespace recommends waiting 48 hours before verifying. A “Couldn’t fetch” message on a new sitemap may appear for 24 to 48 hours while Google processes it.

Wix

Wix needs an upgraded site with a connected domain. The simplest route is Connect to Google in the Wix SEO Setup Checklist. The manual route, from the Wix verification guide, uses a URL-prefix property with the full https://www address: copy the HTML tag, paste it under SEO & GEO > Tools and settings > Site Verification, then click Verify in Search Console. Wix notes that the checklist can’t verify a site more than once; after that, use the manual method.

What to Expect in Your First Week

Expect an empty or nearly empty Performance report for the first few days; that is normal, not a setup error. Google’s data documentation says it “can take up to a week to generate data” for a new site or a site newly added to Search Console, and that collected data normally appears in 2 to 3 days after the fact.

A realistic timeline looks like this:

When	What you’ll see
Right after verification	The property opens, most reports are still empty
After a few days	First Performance data: clicks, impressions, CTR and position
Up to a week	Data for a brand-new site, at the slow end of Google’s estimate
After 48 hours of collection	The same Search Console data inside linked Google Analytics reports

Daily figures follow local time in California, so they won’t line up exactly with tools that use your own time zone. Still nothing after a week? Google points to two common causes: the wrong protocol in a URL-prefix property, or a site that simply isn’t getting clicks in Search yet. Need a ranking snapshot before your own data shows up? Our walkthrough of ways to see where your pages rank on Google today covers free rank checkers and clean manual searches.

How often should you log in afterward? Google’s getting started guide says “there is no need to sign in to the tool every day,” because Search Console emails you when it finds new issues. It suggests checking “around once every month.” Once data arrives, our guide to what each Search Console report means for SEO explains the reports one by one, and our walkthrough on reading keyword positions in the Performance report covers queries and rankings in depth.

Removing a Property or Moving to a New Domain

Removing a property only takes it off your own list, unless you are its last verified owner. Google’s Remove a property page warns: “If you are the last verified owner of a property, all users of the property will lose access to the property in Search Console.” Open Settings and click Remove property. You stop receiving notifications, but your message history is kept.

Does removing the property cut off your access for good? Not by itself. If your verification token stays on the site, you can add the same property again and click Verify. Google also lets you re-add a removed property without verification “as long as the property still has one verified owner.” To remove your access completely, delete your own token too, and only yours, since deleting someone else’s token removes their access.

Moving to a new domain

A domain move is a different job, and Search Console has a dedicated Change of Address tool for it. Google’s Change of Address help page says to use it after you have moved and redirected the site, for example from example.com to example.org. The requirements are strict:

• You own both the old and new properties, with the same Google Account.
• Both are domain-level properties, not path-level ones like example.com/petstore/.
• The old homepage, and ideally every canonical page, 301-redirects to the new site.

Don’t use the tool for an http-to-https move, a switch between www and non-www, moving pages within one site, or changing hosting without changing URLs. Google handles those through redirects and canonical tags.

After a successful request, both sites show a notification for 180 days. Google asks you to keep the redirects for at least 180 days and recommends paying for the old domain for at least a year, so nobody else can buy it and misuse it. After a move, check the new property’s Page indexing report; our guide to fixing Google Search Console indexing issues explains what each status means.

Troubleshooting Common Setup Problems

Most failed setups come down to Google not finding the token where it looks, or looking at the wrong address. These are the errors Google’s verification help page lists most often, with the usual fix:

Problem	Likely cause	Fix
Verification file not found	File renamed, moved or behind a login	Upload the exact file to the site root and open it in an incognito window
Meta tag not found	Tag placed in the <body> or on a draft page	Put the tag inside the <head> of the live homepage
DNS TXT record not found	Provider not serving the record yet	Wait a day or two, then click Verify again
No Analytics code found	Tag missing, modified or in the <body>	Use the unmodified gtag.js snippet in the <head>
Server timed out or DNS error	Site down, slow or misconfigured	Check that the site loads, then retry
Property shows no data	Wrong protocol (http vs https)	Add the property again with the right address

Why does verification fail when everything looks right? Often it’s the account. The Analytics and Tag Manager methods require the same Google Account in both tools, and both Wix and Squarespace tell you to double-check which Google Account you approve the connection with.

A last scenario catches teams off guard: the only verified owner leaves. Google’s advice is to verify ownership again yourself with a new token. After that, you can remove the previous owner’s token so they can’t verify again. If you find an owner you don’t recognize at all, Google warns that “you might have been hacked.”

Your Search Console Setup Checklist

Setting up Google Search Console comes down to five steps, done once and done in order. Most of the work happens in the first hour; the rest is waiting for data. Here is the whole process in one list:

1. Add a Domain property (or a URL-prefix property if DNS is out of reach).
2. Verify ownership, add a backup method, and leave the token in place.
3. Submit your sitemap and check that it says Success.
4. Give each teammate their own access at the lowest role that fits.
5. Link Google Analytics 4 and publish the Search Console report collection.

What should you do after that? Come back in a week, then once a month. Search Console will email you if something breaks in between. Keep in mind that it only covers sites you own and queries you already appear for; for keyword ideas and competitor checks, see how far the free plans of four SEO suites go.

References

• Google Search Console
• Search Console Help: About Search Console
• Search Console Help: Add a website or platform property to Search Console
• Search Console Help: Verify your site ownership
• Search Console Help: Managing owners, users, and permissions
• Search Console Help: Sitemaps report
• Search Central: Build and submit a sitemap
• Search Central: How to Use Search Console
• Analytics Help: Connect Search Console to Google Analytics
• Search Console Help: About Search Console data
• Search Console Help: Remove a property
• Search Console Help: Change of Address tool
• Search Central Blog: Platform properties roll out globally
• Site Kit by Google on WordPress.org
• Shopify Help Center: Finding and submitting your sitemap
• Squarespace Help Center: Verifying your site with Google Search Console
• Wix Help Center: Connecting your site to Google in the Wix SEO Setup Checklist
• Wix Help Center: Verifying your site with Google Search Console