How to Set Up Google Search Console: Verify, Add Users and Submit a Sitemap

What a finished setup looks like

A complete Search Console setup is a short list: a verified Domain property, two verified owners, the right users, a submitted sitemap, email alerts, a link to Google Analytics and the bulk export running. The clicks take under an hour. The waiting takes longer, because DNS records and the first data can each need a few days to arrive. Search Console itself costs nothing, and a Google account is the only requirement to use it. Beyond that, you need access to one of three things: your DNS provider, your site's HTML, or your Google Analytics or Tag Manager account.

The fastest route depends on who you are. A developer with DNS access verifies a Domain property in minutes. A marketer without DNS access usually gets there faster through the Analytics or Tag Manager tag that already sits on the site. Whoever does it, verify with a Google account the business controls, not a contractor's personal Gmail. A property must have at least one verified owner, or no users will have access to it. If the only owner leaves, your access leaves too. Email groups cannot be added as users, so this has to be a real account.

The first decision: Domain or URL prefix

Sign in, open the property selector and add a property. The list shows both verified and unverified properties, and one account can hold up to 1,000 of them, though most businesses need one or two. Look before you add. If someone in the company created the property years ago, it appears here as unverified, and verifying it yourself unlocks everything collected since then. That is often months of history nobody knew existed.

Search Console then asks for a property type, and Google generally recommends Domain. A Domain property covers every subdomain and both protocols in one view, so pick it whenever you can edit DNS and enter the bare domain, without https:// or a path. A URL-prefix property covers one exact address and protocol. Pick it when you cannot touch DNS, or when you want a section on its own, such as example.com/blog/, and type the address exactly as visitors see it, including https and www if the site uses them. A site that answers on both http and https needs a separate URL-prefix property for each protocol. Get this wrong and the reports look empty.

Proving you own the site

Search Console accepts six verification methods: an HTML file, an HTML tag, Google Analytics, Google Tag Manager, Google Sites or Blogger, and a DNS record ^[1]. DNS is the only one that works for a Domain property, while URL-prefix properties can also use the file, the tag, Analytics or Tag Manager. Several people can verify the same property, with the same method or different ones. Pick the method you can maintain for years, not the one that is quickest today.

The DNS record

Copy the TXT record Search Console shows, open your DNS provider, add a TXT record for the root domain with that value, then return and click Verify. Google describes DNS as "More complex, but is the only way to verify a Domain property" ^[1]. It also survives site redesigns. Some configurations need a CNAME record instead; use whichever your provider supports. A new record can take up to two or three days before your provider starts serving it, although it is often a matter of minutes. If Verify fails, wait and retry before changing anything. It has usually just not propagated.

The HTML file or the meta tag

The file method means downloading a file and uploading it to your site's root folder. It works for URL-prefix properties only, and removing the file costs you verification, so a redesign that wipes the root folder breaks it. The meta tag goes into the head section of your home page, within the first 2MB of the file. Theme changes can delete it. On most content systems the safest place is a dedicated verification field in the SEO or site settings. A tag pasted into a theme file disappears with the next theme update, and your verified status goes with it after the grace period.

Analytics, Tag Manager and Google-hosted sites

If the site already runs Google Analytics, you can verify with it, as long as you use the same Google account for both tools and the tag sits in the head, not the body. Tag Manager works too, but you need Publish or Admin permission on the container, and its noscript part must sit right after the opening body tag. New Blogger blogs should be verified automatically, and Google-hosted sites verify when you sign in with the managing account.

When it fails, and how to keep it

Waiting for a developer? Click Verify later and resume another day. Data collection starts as soon as anyone adds the property, so nothing is lost. When a check fails, confirm the token sits on the exact property you added, that the protocol matches, and that a logged-out visitor can reach the file or tag. Login walls and geo-redirects break verification.

Passing once is not the end. Search Console periodically checks that your token is still present and valid. If it is gone, you are notified and lose access after a grace period, and Google says to leave the DNS record in place even after verification succeeds. Document where the token lives. Every verified owner is also notified when a new one is added, so an unfamiliar name deserves a look.

Owners and users: who holds the keys

The most painful Search Console problem is a property nobody can manage, and one step prevents it. Have a second person from the business verify independently, ideally with DNS. There is no maximum on verified owners per property, so if one owner leaves, the other keeps control. If all verified owners are removed, the remaining users lose access after a grace period ^[2]. Data keeps being collected, "but nobody will have access to it until someone verifies ownership" ^[2]. Recovery means verifying again, which needs DNS or site access.

Full, restricted and delegated access

Owners add everyone else under Settings, then Users and permissions, a page only owners can see. Click Add user, enter a valid Google account and choose a permission; the change takes effect very quickly. Full users see all data and can take some actions. Restricted users see most data and receive only the messages that affect them. A sensible default gives restricted access to writers, clients and anyone who only reads reports, full access to the person who manages SEO day to day, and ownership to two or three people who would still be there if an agency contract ended.

Limits, agencies and security

A property can have at most 100 non-owners, counting full, restricted and associate users, so clean up the list every quarter. For a removed owner, also delete their token, because removing an owner does not revoke it. Agencies that need ownership-level tools should be made delegated owners by the client, which needs no token and carries the same permissions. They should never verify with their own token and become the only owner. Finally, turn on two-step verification for every Google account with owner rights, since the queries and pages in Search Console reveal business priorities. Review users and associations twice a year.

Telling Google what to crawl

Submit the sitemap

Open Sitemaps, paste the sitemap address into Add a new sitemap and click Submit ^[3]. You are not uploading anything; you are telling Google where the file lives, and only owners can do it. Sites of about 500 pages or fewer may not need a sitemap at all. Submitting one does not force Google to crawl every URL in it, but it marks the pages you consider important and lets you filter the Page indexing report by that list.

Most hosting platforms generate the sitemap for you; on WordPress core it lives at /wp-sitemap.xml. If you are unsure, robots.txt often lists it, and a sitemap may hold up to 50,000 URLs, which small sites never approach. After submission, read the status. Success means Google read the file, Has errors means it read part of it, and Couldn't fetch means it could not get it at all. Google retries for a few days, then stops if the sitemap stays unavailable.

Check robots.txt and the home page

Next, open Settings and the robots.txt report, which shows the files Google found for your top hosts. Having no robots.txt at all is fine. An unreachable one is worse. It stops crawling for 12 hours. Then paste your home page into the inspection bar at the top; the URL must belong to the property you have open. Google strongly recommends that your home page is indexed, because it discovers most other pages through links from it.

If the verdict says the URL is not on Google, run a live test. For a new site, requesting indexing of the homepage is the best first step: click Test live URL, then Request indexing. There is a daily quota, so leave the other pages to the sitemap. If the home page is still not indexed after a week, solve that first. The usual causes are a robots.txt block, a noindex tag or a login wall.

Alerts, Analytics and the AI setting

Open the settings menu, then Email preferences, and keep notifications on. Preferences are set per user, not per property, so each person checks their own. Security issues and manual actions arrive by email. Make sure at least two people get them. The bell icon opens the message panel, which keeps all property messages from the past year, up to 2,000 of them, but only while the property has a verified owner. Read the backlog once after setup.

To link Analytics, open Settings, then Associations, and pick your Analytics property. You need ownership in Search Console and edit rights in Analytics, and one Analytics property can be associated with only one Search Console property at a time. The most common complaint afterward is that no Search Console data appears in Analytics. The fix is usually simple. Those reports are unpublished by default, so publish the collection from the Library. Last, open Settings, then Search generative AI. Include is the default. Leave it unless the business has decided to keep its content out of AI Overviews and AI Mode.

Keeping history: bulk export and Bing

Search Console keeps a 16-month window, and the bulk export is how you keep more. If history matters, open Settings, then Bulk data export, and connect a Google Cloud project with billing. The first export happens up to 48 hours after a successful configuration. There is no backfill. Every month you wait is a month of data that will never exist beyond the window. Then add Bing Webmaster Tools, which lets a site already verified in Search Console import that ownership directly. It takes minutes, covers Bing and Copilot, and is the cheapest second source of search data you will ever add.

Platform-specific setups

WordPress, Shopify and Wix

On WordPress, Google recommends Site Kit, the only plugin it officially sponsors. It verifies the site and shows Search Console data in the dashboard, needs WordPress 5.2 and PHP 7.4 or newer, and asks each admin to connect a Google account. Our WordPress setup guide goes further. Shopify stores can verify with the HTML tag pasted into the theme.liquid layout file, just below the opening head tag, with the store password page turned off. Shopify generates /sitemap.xml at the root of each domain, and DNS verification needs a custom domain, not a myshopify.com address.

Stores with separate country domains must verify and submit each one, because every domain has its own sitemap. Three country domains mean three properties to watch. Wix needs a paid plan and a connected domain before it can connect to Search Console; its help articles disagree slightly on the plan, but both versions require the connected domain. You can verify through the Wix SEO settings or its SEO setup checklist, and Wix submits the sitemap for you.

Staging sites, domain moves and social accounts

Keep staging sites out of Google with a login or a noindex tag rather than relying on Search Console, because removals are temporary. If the site moved domains, verify both the old and the new one; the Change of Address tool needs owner rights on both, using the same Google account. Set 301 redirects first and keep them for at least 180 days. Creators can also add Instagram, TikTok, X or YouTube accounts as platform properties, which Google made available to everyone on July 29, 2026. They show only Google Search performance.

The first week, the first month, and the mistakes that surface later

Open the property after verifying and most reports will be empty. Normally data appears in 2-3 days, and it can take up to a week for a site newly added to Search Console ^[4]. Google collects continuously and publishes in intervals. Since collection starts when the property is first added, the best moment to add it is launch day. By day three to seven, Performance should show clicks and impressions. The default view covers three months, but only the days since setup exist. Do not judge a new site by its first week. Set up on a Monday and take your first real look the following Monday.

After a month, check that indexed pages are rising, that no manual actions or security issues appeared, that the sitemap shows Success and that your top pages are indexed. Google suggests that light users look in every month or so. Put it on the calendar. For what to do with the numbers, our Performance report guide picks up from here. Most setup problems, though, are quiet mistakes that show up months later as a gap nobody can explain:

• Verifying with a personal account instead of a company one.
• Choosing a URL-prefix property with the wrong protocol. Google calls the http and https mix-up probably the most common reason traffic looks missing, and a Domain property removes it.
• Removing the verification tag or file during a redesign.
• Forgetting the second owner.
• Submitting a sitemap full of redirects.
• Checking the wrong property. A sitemap submitted in one property is not visible in another, so keep a short list of the properties you created and why.

The bottom line

Set up Search Console once, and set it up properly: a Domain property, DNS verification, two owners, a sitemap, alerts and the bulk export. Everything else in the tool works better on that foundation. Shortcuts become gaps later. Add Bing in five minutes, then move on to the reports themselves, starting with our guide to fixing page indexing errors.