Back to blog

How to Set Up Google Search Console: Verify, Submit Your Sitemap, Read the First Reports

How to Set Up Google Search Console: Verify, Submit Your Sitemap, Read the First Reports
Table of contents

To set up Google Search Console, pick a property type, verify the site, submit your sitemap and let the reports fill in. The steps are the same whether you search in English or for “Google Search Console einrichten”, and the setup fits into one sitting on WordPress, Webflow, Shopify, Wix or Squarespace.

  • Pick URL-prefix for a typical small-business site: it offers five ways to verify, while domain properties need DNS.
  • Expect first data 2 to 3 days after adding the property and a readable trend after 2 weeks.
  • “Couldn’t fetch” on a sitemap usually means a wrong URL or protocol mismatch and often clears within days.
  • Give helpers Full User access instead of your Google password, which keeps your login private.

Google Search Console Einrichten, Step 1: Domain or URL-Prefix Property?

If you run one website on one address and have no subdomains, pick URL-prefix. It gives you five ways to verify, and at least one of them works on every common CMS. A domain property can only be verified through a DNS TXT record at your domain provider. That’s fine if you’re comfortable in your registrar’s settings and a hurdle if you’ve never opened them.

Property typeWhat it coversHow you verifyChoose it when
DomainEvery protocol and subdomain (http, https, www, shop., blog.)DNS TXT record onlyYou run subdomains or want everything in one view, and you can edit DNS
URL-prefixOne exact address, such as https://www.yoursite.comHTML file upload, HTML tag, Google Analytics, Google Tag Manager or DNSYou have one site on one address, especially on a website builder

Before you pick a method, check what your platform already offers, because many hosts have their own simpler route. On WordPress, install the Site Kit plugin or paste the HTML tag into your SEO plugin’s field. On Webflow, paste the tag into the custom code settings and republish.

Shopify takes the tag in theme.liquid through the theme code editor. Wix has its own verification meta-tag field in the SEO settings, and Squarespace offers a built-in Google Search Console connection in its settings, so you won’t touch any code there at all.

Closed builders all work about the same way. FASO, for example, doesn’t allow file uploads at all, so the HTML tag is the only route. If you have no access to the file system, go straight for the tag.

If you choose the domain property anyway, the TXT record is less scary than it looks. Leave the host or name field blank or set it to “@”, and paste Google’s generated string as the value. Take a screenshot of your current DNS settings first so you can undo anything. Your provider can take up to two or three days to publish the record, so a failed first attempt usually just means the record hasn’t gone live yet.

Once you’re verified, add a second method as well, for example the HTML tag on top of the DNS record. If a theme update or a site rebuild wipes out the tag later, you keep access to your data.

Finding and Submitting Your Sitemap in Google Search Console

Your CMS almost certainly generates a sitemap already. All you need is its exact URL. Open the address in your browser first: if you see a page of XML, you’ve found the right one.

  • Shopify, Wix, Squarespace: yourdomain.com/sitemap.xml
  • Webflow (after publishing with active hosting): /sitemap.xml
  • WordPress with Yoast/Rank Math: /sitemap_index.xml
  • WordPress 5.5+ without SEO plugin: /wp-sitemap.xml

That WordPress split catches a lot of people, because they only try /sitemap.xml, get an error and assume they don’t have a sitemap.

In Search Console, open Sitemaps in the left menu, enter the path after your domain and click Submit. Google crawls the sitemap right away. “Success” means Google fetched and processed it without errors. Then look at the discovered URLs count, which should roughly match the number of pages and posts you’ve actually published. If you have twelve articles and five core pages, a number somewhere in that range is a good sign.

“Couldn’t fetch” means Google couldn’t retrieve the file at the moment it checked. Your site isn’t broken, and the status doesn’t hurt your rankings. The usual cause is a wrong URL, such as a normal page address instead of the sitemap file. The other common cause is a mismatch between the sitemap and the verified property, for example http against https or www against non-www.

Fix the URL and resubmit. Google keeps retrying for several days anyway, and in most cases the status clears on its own. If it doesn’t, run a live test on the sitemap URL with URL Inspection. You want to see “Crawling allowed: Yes” and “Page fetch: Successful.”

As an extra safeguard, add the line Sitemap: https://yourdomain.com/sitemap.xml to your robots.txt file. Webflow already does this for you.

What the Empty Dashboard Is Telling You (and When Reports Fill In)

A blank dashboard on day one means nothing is wrong. Google starts collecting data for a property as soon as you add it, even before verification, but it takes a few days to accumulate. Performance data usually becomes available within two to three days, and a 24-hour view now shows the latest hours with only a short delay.

Google doesn’t publish an official number of weeks for when a new site should start pulling impressions, so treat the checkpoints below as a practical rhythm for a site with a handful of articles. Day 1 is the setup itself: verify, submit the sitemap, turn on email alerts for sitemap errors and manual actions, and run URL Inspection on your most important page. Invite users only once verification has gone through, so you can tell problems apart.

  1. Day 3: Open Performance. A few impressions and zero clicks is healthy; empty means check your sitemap.
  2. Week 2: Open Page indexing. Most articles should be indexed and the first queries visible in Performance.
  3. Month 2: Compare impressions week over week. A slow climb is the signal you’re looking for.

Core Web Vitals often still says there isn’t enough data at month two, which is normal because it relies on real visitor traffic. The real red flag: week 2 with almost nothing indexed and a sitemap that still won’t fetch.

At month two, decide whether organic content deserves more budget. Look for indexed pages, rising impressions, and queries matching what your buyers search for. If all three align, more articles will likely compound results. If queries don’t match what you sell, fix your topics before scaling.

Provisional data: The latest days in the Performance report are preliminary and get replaced with final numbers after a few days. A sharp dip on the very last day is usually an incomplete day, not a traffic drop.

If you want more output without writing it yourself, Claire’s SEO content writing services start at €199 and cover topic research, articles in your voice and publishing after your approval.

Fixing ‘Ownership Verification Failed’ and ‘Not Indexed’ Statuses

Verification usually fails because the DNS record hasn’t gone live yet, so Google recommends waiting one to two days before you retry. With the HTML tag, the usual cause is a site that wasn’t republished or a tag that doesn’t sit in the head of your homepage.

The two “not indexed” statuses have different causes. Discovered means Google knows the URL but hasn’t crawled it yet, usually because of crawl capacity, slow server responses or weak internal linking. On small, young sites it often clears by itself. Crawled means Google visited the page and decided not to index it for now, which points to content quality, near-duplicates or canonical signals. Either way, you don’t need to resubmit, because Google can still index the page later.

  • “Ownership verification failed”: wait one to two days, then check record type, host and full string.
  • “Discovered – currently not indexed”: link to the page from your homepage and related articles, then wait.
  • “Crawled – currently not indexed”: improve or merge the page, and check duplicates and canonical signals.

If you suspect an old agency or former employee still holds ownership, check the unused ownership tokens in your settings before you start over with a new property.

Giving Someone Access Without Sharing Your Google Password

Add helpers as users with their own Google account under Settings, then Users and permissions. Search Console has three user roles, and for an agency, freelancer or tool the right one is almost always Full User.

RoleCan doCan’t doGive it to
OwnerEverything, including adding and removing users and changing permissionsNothing is off limitsYou, plus one backup person on your team
Full UserView all data, submit sitemaps, use URL Inspection and most other actionsManage usersAn agency, freelancer or tool that needs to take action
Restricted UserView Performance and Page indexing dataSubmit sitemaps, take actions in URL Inspection, share report linksSomeone who only analyses the data

Only give Owner rights to someone who needs to add or remove people themselves, which a helper rarely does. For a one-time look, you don’t need a role at all: every report page has a Share link button that sends a view of just that report. You won’t hit a limit either. A property allows up to 100 Full, Restricted or Associate users, and there’s no cap on verified owners.

The same setup works when you hand ongoing work to a tool instead of an agency retainer. The tool gets its own seat, and your login stays private. With that access, an AI agent can realistically find pages that collect impressions but few clicks, spot queries you have no matching article for, and flag indexing problems as they appear.

Claire can be added this way, as a Restricted User for analysis or a Full User if it should also submit sitemaps and inspect URLs. If you’d rather have the whole process run for you, Managed Claire is a GEO and SEO service from €1,999 that works from the same delegated access. A traditional agency or freelancer would get exactly the same kind of seat.

Search Console counts Google’s own AI features but doesn’t separate their clicks out. Appearances in AI Overviews and AI Mode are included in your normal “Web” search data, and a click on a link inside AI Mode counts like any other click. A separate Generative AI section in the Performance report now breaks down impressions by page, country and date. It doesn’t show clicks, so it measures visibility, not traffic.

  • Visible: Impressions and clicks from AI Overviews and AI Mode in Web totals, plus Generative AI section data.
  • Not visible: Data from ChatGPT, Perplexity or Microsoft Copilot (non-Google products).

For those tools you need a different measurement. In your analytics tool, filter referral traffic for chatgpt.com, chat.openai.com, perplexity.ai and bing.com/chat to see the visits these tools send you. To understand why you are or aren’t being cited in the first place, Claire’s GEO Audit checks your site against more than 70 points across technology, content, authority and brand.

Your Setup Is Done: Here’s What Comes Next

In week one, Search Console’s real value isn’t the data, because there’s barely any yet. Its value is that “is SEO working?” stops being a gut feeling and becomes a set of dated checks.

So the one thing to do now is to add three reminders: day 3 to check whether the first data is there, week 2 to see whether your pages are indexed and the first queries show up, and month 2 to decide whether the trend is worth more investment. Do it today, before the dashboard fills up and checking stops feeling urgent.

Between those dates, leave the reports alone. A new site changes slowly, and checking every day mostly shows you provisional numbers.

FAQ

Can I switch from URL-prefix to a domain property later without losing my data?

Yes, because you don’t switch, you add. Create the domain property alongside the existing one and verify it through DNS. Your URL-prefix property keeps its data, and you can run both side by side for as long as you like.

Do I need to verify both www and non-www versions of my site?

Usually not. With a URL-prefix property, verify the exact version your site redirects to, since that’s where your traffic ends up. If you want every variant in one view, a domain property covers www, non-www, http and https automatically.

Why does Google Search Console show different numbers than my analytics tool?

They count different things. Search Console records clicks from Google Search results, while your analytics tool counts sessions from every source and loses visitors who decline cookies or block tracking. A gap between the two is normal, so compare trends, not exact totals.

How often should I check Search Console once the first weeks are over?

Once a week for a quick look at Performance and Page indexing, and once a month for a proper comparison. Email alerts cover the urgent problems in between, so checking daily rarely tells you anything new.

Does submitting a sitemap help my site get indexed faster?

Usually, yes. Google crawls the sitemap right after you submit it, which helps it discover new pages quickly. A sitemap doesn’t guarantee indexing, though. Whether a page gets indexed still depends on its quality and on how well it’s linked from the rest of your site.

byClaire

Content marketing like this article?

AI search already answers your customers’ questions. The only question is: with whom?

Discover moreTry it for free
Trusted by 500+ DACH users