In short and in plain language
Search Console is a tool from Google. It shows how your website appears in Google search. It also shows errors and warnings.
First, you add a property. This is the area that Google reports on. A domain property covers the whole domain. A URL-prefix property covers only one part.
Then you show Google that the website is yours. For the whole domain, this only works with an entry in the DNS. The DNS is the address book of the internet. For one part, a file or a short code also works.
Your business should be the owner itself. The agency only gets the user role. This way, access stays with you, even if you change agencies.
Finally, you send in the list of your pages. This list is called a sitemap. Also turn on the emails. This way, you hear about problems early.
Google Search Console shows how Google finds a website, crawls it and displays it in search: with search queries, clicks, indexing issues and security notices. Setting it up is manageable, yet it may be missing altogether or sit in the account of a former service provider. The very first step decides who will own the data and settings later on. A verified owner has the most extensive permissions in Search Console (Search Console Help). Whoever holds that role can add and remove users, change settings and register a move of the website to a new domain. This article walks through the setup step by step: choosing between a domain property and a URL-prefix property, verification by DNS record, HTML file or meta tag, splitting roles between your business and your agency, submitting the sitemap and making sure the notifications land in the right inbox.
Key points at a glance
- A domain property covers all subdomains and protocols and can only be verified with a DNS record. A URL-prefix property covers exactly one prefix, including the protocol (Search Console Help).
- For manually added DNS records it can take up to two or three days before your provider serves the record (Search Console Help). The TXT record stays in place permanently after verification.
- The verified owner should be a business Google account with two-factor sign-in. The agency works as a full user, and its verification tokens are removed from DNS and the website when the contract ends.
- A single sitemap may be at most 50 MB uncompressed or contain 50,000 URLs (Google Search Central). An owner submits it through the Sitemaps report; alternatively, a reference in robots.txt is enough.
- Email notifications are set per user for all properties and are turned on by default (Search Console Help). The inbox of the owner account needs a person who reads it every day.
- The performance report can be extended to the last 16 months (Google Search Central). Data collection starts when the property is added, so it pays to set it up before the first problem shows up.
Why the business should set up Search Console itself
In Germany, 91.7 percent (Eurostat) of enterprises with ten or more employees had their own website in 2025; the figure covers all sectors except agriculture, forestry, fishing, mining and the financial sector. No statistic records how many of these businesses have verified their website as owners in Search Console. One scenario can be avoided, though: the agency that builds the website also creates the Search Console property, using its own Google account. As long as the collaboration runs, nobody notices. When the business switches providers, it loses access, history and the settings that only owners may change.
Google itself explains why verification is so strict: site owners in Search Console have access to sensitive Google Search information about a website and can take actions that affect its presence in Google Search and other Google services (Search Console Help). These include user management, property settings, submitting sitemaps through the Sitemaps report and the Change of Address tool for a domain move.
Timing matters as well. Data collection for a property begins as soon as it is added to a Search Console account, even before verification (Search Console Help). If you add the property early, you have comparison data on hand when you need it: after a relaunch, after a sudden drop in visitors or for a year-over-year comparison. Which questions to ask an agency about access and roles before hiring them is covered in our article Checking SEO and GEO offers.
Before you start: account, access, responsibility
Fifteen minutes of preparation before you add the first property are well spent. The most important question is which Google account you use for the setup. The verification file and the meta tag are tied to the user who created them: the file is linked to that account and can only be used by that person to verify (Search Console Help). If you verify with an employee’s private account, ownership is bound to that person. A better choice is an account that belongs to the business, for example on a role address of your own domain, with credentials stored in a defined place. An email group, on the other hand, cannot be added as a user; every person needs a valid Google account (Search Console Help).
This account needs a second sign-in step. The BSI recommends hardware-based two-factor authentication methods in particular, in addition to a strong password (BSI). An account with owner rights in Search Console is a worthwhile target: whoever takes it over can remove other users and change the property settings. The following list should be complete before the first click.
- A business Google account with two-factor sign-in and a documented place where the credentials are stored
- Access to DNS management at your domain provider, or a person who may add records there
- Access to the content management system or server in case a file or meta tag is needed
- A list of all address variants: with and without www, http and https, subdomains such as shop or booking
- The address of the XML sitemap, usually at /sitemap.xml or listed in robots.txt
- A person in the business who reads the Search Console messages and passes them on
If you do not control DNS management yourself, clarify in advance who is registered as the domain holder and who maintains the records. If both sit with a former provider, that is the first construction site. Our article Who owns your website? explains how domain, access and usage rights fit together. If you get your domain and web hosting from one provider, you will usually find DNS management in that provider’s customer area.
Domain property or URL prefix: the first decision
When you add a website, Search Console asks for the property type. There are two types, which differ in scope and verification. A domain property is a domain-level property that includes all subdomains such as m or www as well as multiple protocols, namely http, https and ftp (Search Console Help). You enter only the domain name, without protocol, path or www: Search Console automatically turns www.sample.example into the property sample.example, which contains both variants (Search Console Help). We use the .example ending here because it is reserved for examples in documentation (RFC 2606).
A URL-prefix property, in contrast, includes only URLs with the specified prefix, including the protocol (Search Console Help). The property https://www.sample.example/ therefore covers neither http://www.sample.example/ nor https://sample.example/ without www, and no subdomain such as shop.sample.example. If a site supports several protocols or subdomains, each variant needs its own URL-prefix property. This is where gaps appear in practice: the property was created for http years ago, the site has long since moved to https, and the reports show hardly any data.
| Feature | Domain property | URL-prefix property |
|---|---|---|
| Input | sample.example | https://www.sample.example/ |
| Scope | all subdomains, protocols http, https and ftp | only URLs with exactly this prefix |
| Verification | DNS record only | HTML file, meta tag, Google tags or DNS |
| Typical use | main property for the whole website | sections such as /blog/ or a language folder |
| Requirement | access to DNS management | access to server, CMS or tag container |
For a business with one website, the domain property is the right main property in most cases. Google calls domain properties useful because they include data for all protocols and subdomain variants (Search Console Help). A forgotten http version or subdomain does not drop out of the reports. Sections can be added later: for the domain property, you can create additional URL-prefix properties for individual subdomains, protocols or folders (Search Console Help). A Search Console account can include up to 1,000 properties (Search Console Help), so lack of space is no reason to skip separate properties for a shop, a blog or language versions.
Some features depend on the property type. The branded queries filter, for example, is only available for top-level properties, not for folders or subdomains. How it works and what it is good for is described in our article on separating branded queries in Search Console.
Verification by DNS record: the route for the domain property
There is exactly one verification route for a domain property. In its overview of methods, Google describes it as more complex, but the only way to verify a domain property (Search Console Help). The only exceptions are properties that belong to a Google product such as Blogger or Google Sites. You verify with a record in the DNS settings of your domain that Search Console specifies. A TXT record is a resource record that holds descriptive text in the Domain Name System (RFC 1035); Google reads it as proof that you manage the domain.
- Choose the Domain property type and enter the domain name without protocol and without www; the domain name provider method is then preselected.
- If your provider appears in the Search Console list, choose "Start verification" and sign in there. Otherwise, select the TXT record type and copy the value shown.
- In your domain provider’s DNS management, create a new TXT record: leave the host or name field empty or enter @, and paste the copied string into the value field.
- Save, wait a little and click Verify in Search Console.
- Leave the record in place after verification so that the verification stays valid.
Type: TXT
Name: @ (or leave empty)
Value: google-site-verification=AbC123...xyz
TTL: provider defaultAccording to Google, manually added records can take up to two or three days (Search Console Help) before the provider serves them. If verification fails right after you save, there is no cause for concern: Google advises trying again after one to two days (Search Console Help). The last step in the list matters. The DNS record should not be removed even after successful verification, so that the verification is preserved (Search Console Help). Search Console checks regularly whether the verification token is still present and valid; if it can no longer be confirmed, your permissions expire after a grace period (Search Console Help).
In less common cases, Search Console asks for a CNAME record instead of TXT. This applies to domain names that already have a CNAME record pointing to a parent domain; according to Google, the most common case is that no CNAME is found and the TXT route applies (Search Console Help). With CNAME, Search Console provides a name and value pair whose value points to dv.googlehosted.com. One advantage of the DNS route shows when you use it for a URL-prefix property: the domain property is then verified automatically as well (Search Console Help).
If DNS management still sits with your old provider
File, meta tag, Tag Manager: routes for the URL-prefix property
URL-prefix properties offer several methods. On the verification page, Search Console shows the methods that are available and recommended for your site (Search Console Help). Three of them are the obvious choices for businesses with their own website.
With the HTML file, you upload a file provided by Search Console to the root directory of your website. Name and content must not be changed; only additional line breaks at the end are allowed. The file must be reachable without signing in, which you can test in a private browser window. Redirects are risky with the file: Search Console does not follow them to a different domain (Search Console Help). The safest option is to place the file directly at the address the verification wizard names. If you delete the file later, you lose the verification.
With the meta tag, you add a line named google-site-verification to the head section of your homepage. The homepage must be reachable without signing in, and the tag must be within the first 2 MB (Search Console Help) of the file, which affects very few sites. Many content management systems provide a dedicated field for this; in WordPress you can add the tag through the theme or a plugin. Search Console looks for the tag on the page a visitor who is not signed in reaches when opening the property address.
If a Google Tag Manager container is already embedded on the site, publish or administrator permission for that container is enough; Search Console and Tag Manager must be used with the same Google account (Search Console Help). Verification through an existing Google measurement snippet works in a similar way. Both routes, however, depend on another service and its account. If the container is replaced or only loads after consent, the verification can drop away. For ownership by the business, the DNS record, the file and the meta tag are the more independent routes.
HTML file
A good fit if you can reach the server via FTP or a file manager. Works for URL-prefix properties only and stops working once the file is deleted.
Meta tag
A good fit if your CMS offers a field for the head section. The tag is easily lost when the theme changes.
DNS record
The only route for the domain property and independent of server and templates. Verifies the domain property automatically as well.
Relaunch and verification
Owner or user: who gets which role
Verification makes you a verified owner. Search Console also has delegated owners, whom a verified owner makes owners without a token of their own; both types have the same permissions (Search Console Help). The difference lies in removal: a delegated owner is removed in user management, while a verified owner is only fully removed once their token is also gone from the website or DNS. A property must have at least one verified owner, otherwise no other users can access it (Search Console Help).
Below the owners there are two user roles. Full users can view all data and take some actions, restricted users can view most data (Search Console Help). For ongoing SEO support, the full user role is usually enough; for reporting only, the restricted role will do. The agency therefore does not need an owner account to do good work. Which rules on access, roles and verification tokens belong in the contract is summarized in our article Questions before hiring an SEO.
If a former provider created the property, the order of steps is decisive. First, verify yourself as owner with a token of your own. Then you can revoke the verification of previous owners by removing their verification tokens (Search Console Help). Deleting an owner from the user list does not finish the job: their tokens are neither deleted nor revoked, and as long as one of them exists, they can reverify ownership (Search Console Help). Search Console lists the remaining tokens under Settings, Users and permissions, Unused ownership tokens.
- Add your own token, meaning a DNS record, file or meta tag, and verify yourself as owner.
- Check under Users and permissions who is listed as owner and who as user.
- Remove former owners and delete their tokens: foreign TXT records, files and meta tags.
- Be careful with shared tokens: the same token can also verify other Google services, such as Merchant Center.
- If the collaboration continues, add the provider again as a full user.
The fourth point deserves care. The same verification token can be used for different services, such as Merchant Center or Google Workspace besides Search Console, and removing it can have a negative effect there (Search Console Help). Before deleting a foreign TXT record, it is therefore worth asking what else it is needed for.
Submit the sitemap and check the homepage
Once the property is verified, the sitemap comes next. It lists the addresses Google should crawl and helps mainly with larger or newly launched websites. If you have a small site with about 500 pages or fewer (Search Console Help) and all pages can be reached through links from the homepage, Google says you probably do not need a sitemap or the Sitemaps report. For an online store or a site with many articles, things look different.
You submit the sitemap in the Sitemaps report. This requires owner permissions for the property; without them, you can reference the sitemap in robots.txt (Search Console Help). Each individual sitemap is limited to 50 MB uncompressed or 50,000 URLs (Google Search Central). Larger inventories are split across several sitemaps and bundled in a sitemap index file. The file must be UTF-8 encoded; if it sits in the root directory, it applies to all files on the site (Google Search Central).
Sitemap: https://www.sample.example/sitemap.xmlAfter submission, the report shows the status of the last fetch. If a fetch fails, Google retries for a few days; after that, the sitemap must be resubmitted once the problem is fixed (Search Console Help). It is then worth opening the URL Inspection tool: enter the homepage and check whether it is indexed and which address Google considers canonical. First performance data appear after a few days (Search Console Help).
Notifications: messages that need to arrive
Search Console sends messages to site owners when an important event occurs on their website (Search Console Help). That can be a new owner, an indexing problem or a manual action; Google reports the latter in the report of the same name and in the Search Console message center (Search Console Help). All messages are also shown in the property’s message panel, but most people notice them by email. To make sure they arrive, two things are needed: email notifications turned on and an inbox that someone reads.
Email preferences are set at the user level, not at the property level, and apply to all properties of an account (Search Console Help). By default, email delivery is enabled. You reach the settings via User settings and then Email preferences. One point matters for the role split: restricted users only receive messages that concern them (Search Console Help). If you give the agency restricted rights only, you need to read or forward the messages yourself.
- In the owner account, open User settings, Email preferences and check that email notifications are enabled.
- Do not mute message types about new owners, security issues or manual actions.
- Forward the account’s mail to an inbox that is read every day.
- Name a deputy who sees the messages during vacation or sick leave.
- Review the property’s message panel once a quarter.
A message about a new owner deserves special attention. If you do not recognize an owner, your account may have been hacked, Google warns (Search Console Help). In that case, removing the token and checking the website for tampering go together. If you have commissioned website care, clarify in advance who acts in this situation and how quickly.
The first weeks: what to look at first
By default, the performance report shows clicks and impressions for the last three months (Search Console Help). Using the date filter, you can extend the range to the last 16 months (Google Search Central). If you want to keep performance data for longer, you can set up a bulk data export in the property settings, which lets you export, store and analyze the data (Search Console Help). The export runs daily from the day it is set up, requires a Google Cloud project with billing and does not include historical data from before the setup (Search Console Help); that, too, argues for an early start. For the first weeks, two questions are enough: does the site appear for its own name, and which queries without the brand name already bring clicks?
The Crawl stats report in the settings shows how often Google crawled the site in the last 90 days (Search Console Help). A sudden drop can point to server problems or a blocking robots.txt. For businesses that serve a region, queries with a local reference are worth a look; what counts for visibility in your area is explained under local SEO.
Another reason for an early setup shows up when you change domains. The Change of Address tool requires you to be an owner of both the old and the new property and to manage both with the same Google account (Search Console Help). If you are planning a move, clarify ownership beforehand. How the move itself works is described in our article on moving to a new domain.
Common pitfalls and their causes
Search Console error messages are brief, but the causes repeat. The following overview lists typical messages and symptoms and, based on the help pages, maps them to a possible cause.
| Message or symptom | Possible cause | Fix |
|---|---|---|
| DNS TXT verification record not found | Record not yet propagated or in the wrong field | Host empty or @, copy the value exactly, verify again after one to two days |
| Verification file redirects | Redirect to a different domain | Place the file at the stated address or use the meta tag |
| Meta tag is incorrect | The page carries another user’s tag | Copy your own tag from Search Console, do not overwrite other tags |
| Verification lost after a relaunch | Tag or file removed during the rebuild | Add a second method, carry the token over before go-live |
| Property shows no data | Wrong protocol in a URL-prefix property, such as http instead of https | Add a domain property or correct the prefix |
| User cannot be added | Email group instead of a Google account | Enter the person’s own Google account |
Most errors do not occur during setup but months later: when hosting changes, when the template is replaced or when DNS management moves to another provider. If you use the DNS record as your verification route, template changes cannot break it, but when you switch DNS providers you need to remember to take the TXT record along. A short entry in the business’s access register with method, account and token location saves a search later.
What should be settled when the setup is done
At the end of the setup, five things are settled: a domain property verified by DNS with the business account; additional URL-prefix properties for a shop, blog or language versions where needed; a submitted sitemap without errors; notifications turned on in an inbox that is read; and an agency that works as a user. Document this once, and the next change of provider leaves no gap in access.
If you would rather not handle the setup yourself, you can commission it as part of our SEO services; the owner account stays with you. Questions about an existing property that still sits with a former provider are welcome through our contact form.
Related Articles
Branded or not: separating queries in Search Console
Search Console's filter separates branded from non-branded queries: what it counts, when it is missing, limits, a regex cross-check and year-over-year analysis.
Checking SEO or GEO offers: questions before hiring
How to check SEO and GEO offers: Google's questions for providers plus checks on reporting, access, contract term and AI texts, without ranking promises.
Site Name and Favicon: How Your Brand Shows Up on Google
Site name and favicon appear above every Google result. How to align WebSite markup, og:site_name, the title and a favicon of 48 px or more on your home page.