Google Search Console is one of the most important tools if you want to know how Google sees your website and how it is found in Google search.
Among other things, you can use it to track which search queries bring visitors to your website, which pages appear in Google, whether Google detects any indexing issues, and how clicks, impressions, and positions are developing.
Using the Google Search Console is free. Before you can view your website's data, you must add the website as a so-called property and verify your authorization for it.
In this guide, we will show you how to set up a website in Google Search Console, which property type you should choose, and how verification via a DNS record works.
Briefly explained: The Search Console does not automatically improve your rankings. It provides you with data and diagnostic tools that help you better understand how Google crawls, indexes, and presents your website in the search results.
What is the Google Search Console? #
Google Search Console, or GSC for short, is a Google service used to monitor and analyze a website's presence in Google Search.
Key options include, among others:
- Analyze search queries and clicks,
- Evaluate impressions and average positions,
- Investigate indexing issues,
- check individual URLs,
- Submit XML sitemaps,
- Viewing Core Web Vitals reports,
- identify certain technical problems.
Therefore, the Search Console is part of the basic equipment for website operators who want to monitor their visibility on Google.
What the Search Console does not do #
Setting up Search Console does not automatically lead to better rankings, nor does it guarantee that Google will index every page of your website.
It is primarily an analysis and diagnostic tool.
Set up Search Console
↓
Analyze Google data
↓
Identify issues
↓
Investigate causes
↓
Improve website targetedlyImportant: You don't need to install Google Search Console for your website to generally appear on Google. Rather, Search Console gives you access to important information and tools regarding your website in Google Search.
Open Google Search Console #
Open Google Search Console at:
Log in with the Google account you want to use to manage the website in the future.
For business websites, you should, if possible, use a permanently available corporate account rather than relying exclusively on a private account belonging to an employee or an external service provider.
What is a property? #
Google refers to a website or a defined website area within the Search Console as Property.
When adding a website, there are generally two important variants available for websites:
Domain property or URL-prefix propertyThe choice is important because both variants have a different scope.
Comparison of Domain Property and URL-Prefix Property #
| Property | Domain property | URL prefix property |
|---|---|---|
| Input | example.com | https://www.example.com/ |
| HTTP and HTTPS | contain | only specified prefix |
| www and without www | contain | only specified prefix |
| Subdomains | contain | not automatically included |
| Subdirectories | contain | within the specified prefix |
| Confirmation | DNS | multiple methods possible |
What does a domain property track? #
For example, if you create the following domain property:
example.com
different variants of this domain are captured together.
For example:
https://example.com/
https://www.example.com/
http://example.com/
https://shop.example.com/
https://blog.example.com/The underlying paths also belong to the domain property.
This is a significant advantage over a single URL-prefix property.
What does a URL-prefix property track? #
In contrast, a URL-prefix property only applies to URLs that begin with the exact specified prefix.
Example:
For example, this makes:
Captured.
However, the following variant is not automatically included:
Also:
http://www.example.com/
has a different protocol than the specified HTTPS prefix.
Which property should you choose? #
If you have access to the DNS management of your domain, is a Domain property in many cases the most sensible main property.
It has the advantage that different protocols and subdomains are recorded together.
For:
example.com
Don't you need separate properties for this:
https://example.com/
https://www.example.com/
https://shop.example.com/create, just to cover the domain as a whole.
Recommendation: If you can manage your domain's DNS records, we usually recommend a domain property for the complete website.
When is a URL-prefix property useful? #
A URL-prefix property can be useful if you want to look at a specific area only or do not have access to the DNS configuration.
It can also be used in addition to a domain property if you want to manage or view certain sections separately.
For example:
So, a domain property and additional URL-prefix properties are not mutually exclusive.
Add domain property #
Open the property selector in Search Console and select the function to add a new property.
Then select the option Domain.
Enter only the domain.
Correct:
example.com
Not:
and not:
For a domain property, the protocol and URL path do not belong in the input.
Why must ownership be verified? #
The Search Console contains information about a website's presence in Google Search and provides management and diagnostic features.
Google must therefore ensure that you are actually authorized to access this data and features.
For a domain property, this verification is done via the domain's DNS.
Verify domain property via DNS #
After adding the domain, Google will show you an individual DNS record for verification.
Frequently, this involves a TXT record based on the following principle:
google-site-verification=INDIVIDUELLER-BESTAETIGUNGSCODE
This value is provided by Google for your verification.
Important: Always copy the actual verification value from your own Search Console. The value shown here is only an example.
Where does the TXT record need to be entered? #
The TXT record must be created in the authoritative DNS zone of the domain in question.
That is not necessarily the same company where you originally registered the domain.
The decisive factor is which nameservers or which DNS service are currently responsible for the domain.
If your domain uses CURIAWEB's DNS management, you can manage DNS records via the cPanel Zone Editor.
We explain how to use it at Using the DNS Zone Editor in cPanel.
Create TXT record in DNS #
The exact interface depends on the DNS provider used.
Basically, you need a TXT record for the domain.
The schema could look like this, for example:
Type:
TXT
Name / Host:
example.com
or depending on the DNS system @
Value:
google-site-verification=INDIVIDUAL-VERIFICATION-CODEWhat input is required in the name or host field depends on the respective DNS system.
Attention: Don't wear blindly
@one, if your DNS management expects a different spelling. Some systems expect the full domain, others use@or an empty field for the main domain.
Do not overwrite existing TXT entries #
A domain may already have multiple TXT records.
This can be used to store information for email authentication or other services, for example.
An additional Search Console verification record usually does not mean that existing TXT records should be replaced.
Attention: Do not delete or overwrite any existing TXT records just to add the Google verification record. Create the record requested by Google in addition to the existing ones.
Save DNS record and start confirmation #
After saving the TXT record, switch back to Google Search Console.
Click there Confirm.
Google then checks whether the expected DNS record can be found.
If the test is successful, ownership is confirmed.
Google hasn't found the TXT record yet #
DNS changes are not necessarily immediately visible everywhere.
If the Search Console doesn't find the entry immediately after saving, that doesn't automatically mean it was entered incorrectly.
Check first:
Is the TXT record saved?
Was the complete Google value adopted?
Is the entry in the correct DNS zone?
Is the name/host correct?
Are the currently responsible nameservers known?
Is the entry already publicly resolvable?We explain how DNS changes and their propagation work at DNS Propagation Explained: How Long Do DNS Changes Take?.
Check TXT record publicly #
If the verification fails, you can check whether the TXT record is being publicly served via DNS.
What is crucial is not just that you see the entry in some management interface, but that it is actually published by the responsible DNS infrastructure.
Basics on checking DNS records can be found at Check DNS records.
Why the wrong DNS zone is a common mistake #
For example, a domain can be registered with provider A while its nameservers point to provider B.
If you then create the Google TXT record only in an inactive DNS zone at provider A, this record will not be used in the public DNS.
Domain registered with Provider A
Nameservers point to Provider B
↓
Active DNS zone is located at Provider B
↓
Google TXT record must be published thereTherefore, it is important not to equate the registry, registrar, hosting, and DNS with one another.
DNS Verification After a Nameserver Change #
If you change your domain's nameservers or DNS provider later, you must ensure that the Google verification record is also present in the new DNS zone.
Otherwise, the confirmation method used may be lost.
Therefore, during a DNS migration, do not only transfer A, AAAA, CNAME, and MX records, but also relevant TXT and other verification records.
Do not delete Google verification listing after successful setup #
The DNS record serves as proof not only during the initial setup process.
Google may verify ownership again at a later time.
The confirmation entry should therefore remain as long as it is needed for verification.
Important: Do not simply delete the Google verification record from the DNS again after successful setup.
Verify URL prefix property #
For a URL-prefix property, additional verification methods besides DNS are available.
Depending on the website and configuration, methods can include, for example:
HTML file
HTML meta tag
Google Analytics
Google Tag Manager
DNSbe offered.
Which methods are available or can be successfully used depends on the respective configuration and the necessary permissions.
Confirmation via HTML file #
With this method, Google provides a specific HTML file.
This must be accessible on the website at the location specified by Google.
If the file is removed later, the basis for this confirmation method may also be lost.
Confirmation via HTML meta tag #
Google can also provide a verification tag for a URL-prefix property.
For example, the principle looks like this:
<meta
name="google-site-verification"
content="INDIVIDUELLER-BESTAETIGUNGSCODE"
>Here too, the exact value comes from your own Search Console.
The tag must be present in the location designated by Google in the HTML of the website.
WordPress SEO Plugins and Google Verification #
Some WordPress SEO plugins offer an input field for a Google verification code.
This can potentially be used to implement the HTML tag method for a URL-prefix property without manually editing a theme file.
Whether and where this function is available depends on the plugin used.
If you have already successfully verified a domain property via DNS, additional HTML verification for the same full domain is usually not necessary.
DNS or WordPress plugin – which method is better? #
For a domain property, this choice does not arise: it is verified via DNS.
That has a practical advantage. The confirmation does not depend on the WordPress theme used or a specific plugin.
If you change your theme later or remove an SEO plugin, the DNS record remains unaffected.
Therefore, DNS verification is a robust solution for a permanently managed website.
Search Console and Google Analytics are not the same #
Google Search Console and Google Analytics fulfill different tasks.
Simplified:
Google Search Console
→ Google Search appearance
→ Search queries
→ Clicks
→ Impressions
→ Positions
→ Indexing
→ Crawling and search issues
Google Analytics
→ Website behavior
→ Sessions / Users
→ Pages and events
→ Interactions
→ Conversions depending on setupThe systems can complement each other, but they do not replace one another.
Search Console does not require a tracking code on every page #
For example, if you verify your website as a domain property via DNS, you do not need to add a Search Console tracking code to every single page.
This is what distinguishes Search Console from traditional web analytics systems, which often execute their own code on the website for data collection.
Search Console gets its search data from Google.
Search Console and Data Privacy #
The pure DNS verification of a domain does not add any JavaScript tracking code for visitors to your website.
This is important to distinguish from other Google services that may be embedded directly on the website.
The data protection requirements that apply to your specific website and other services used must be assessed independently of this.
When will the first data appear? #
After successful setup, you should not expect all reports to be completely filled out immediately.
Search Console needs time until the corresponding data is available or processed in the reports.
In the case of a new website, there may simply still be little search activity.
Practical Tip: If a newly set up Search Console initially shows hardly any data, do not change the configuration immediately. Give Google some time first and check again later.
An empty Search Console does not automatically mean an error #
For a new or low-visibility website, impressions and clicks may be low.
This is to be distinguished from a technical problem.
If no data appears even after some time, you should check, among other things:
Is the correct property open?
Has the correct domain been entered?
Is the ownership verified?
Is the website publicly accessible?
Does Google already know the website?
Are pages indexable?Search Console does not automatically mean indexing #
Adding a website to Search Console does not guarantee that Google will index all URLs.
Google decides based on various technical and content signals which pages are crawled and indexed.
If important pages do not appear in the Google index, you should investigate the specific cause.
We will cover that under Google is not indexing my website: Check causes.
Use the URL inspection tool #
After setup, the URL inspection tool is one of the most important tools in Search Console.
Enter the complete URL of your website there.
Example:
The Search Console can then provide you with information on whether Google knows the URL and how it is treated regarding indexing.
Do not confuse URL inspection with a ranking test #
URL Inspection doesn't tell you what position a page ranks for every keyword.
It is primarily used to investigate a specific URL in connection with Google and indexing.
For queries, clicks, impressions, and positions, you use the performance report.
Submit XML sitemap #
After setup, you should check whether your website provides a correct XML sitemap.
You can submit these in the Search Console via the sitemaps section.
A sitemap helps Google discover relevant URLs of a website.
However, it does not guarantee that every URL included will be indexed.
We cover the setup and submission in detail at XML Sitemap: What it does and how to submit it to Google.
Multiple sitemaps are possible #
Depending on the content management system, a website can have a sitemap index that points to several individual sitemaps.
For example, different content types can be listed separately within it.
You should therefore not assume that every website necessarily has only a single XML file.
Get to know the performance report #
In the Search Console performance report, you can track how your website appears in Google Search.
Key performance indicators include:
Clicks
Impressions
CTR
average positionThese four values are frequently misinterpreted. Therefore, we discuss them separately under Understanding Google Search Console: Clicks, Impressions, CTR, and Position.
Check indexing reports regularly #
The Search Console also provides information on which pages Google has indexed or why certain URLs were not indexed.
Not every excluded URL is automatically an error.
Examples of URLs that may intentionally not be indexed, depending on the website, are:
Redirect targets or old URLs
certain internal search pages
administrative areas
duplicates
intentionally excluded pagesThe crucial question is always whether a important desired page Missing.
Not every Search Console message is a problem #
The Search Console reports various states. Some of these are purely informational or correspond exactly to the desired configuration.
For example, if an old URL has been permanently redirected to a new URL, the old URL no longer needs to appear as a normal indexed page.
We explain how permanent redirects work at Set up a 301 redirect: Permanently redirect URLs.
Properly assessing 404 reports #
Even 404 URLs that have been found are not automatically a reason to panic.
An intentionally removed page without a meaningful replacement may respond with a 404 status.
This becomes problematic, for example, if an important page is accidentally no longer accessible or internal links point to non-existent URLs.
You can find more about this at Find and fix 404 errors.
Core Web Vitals in Search Console #
Search Console can also provide reports on Core Web Vitals.
This concerns real usage data and not just a single Lighthouse test.
We explain the meaning of LCP, INP, and CLS under Core Web Vitals Explained: LCP, INP and CLS.
Add multiple users #
You should not share Google account credentials with other people.
For example, if an agency, an employee, or an SEO specialist needs access to Search Console, they can be added as a separate user.
This ensures that it remains traceable who has access, and permissions can later be adjusted or removed again.
Important: Do not share your personal Google password just so someone can get access to Search Console. Use user and permission management.
Distinguish between owner and user #
Search Console distinguishes between different permission levels.
A verified owner has extensive rights to the property. Other users can be added with appropriate permissions without having to use your login credentials themselves.
Grant only the permissions a person actually needs for their task.
Retain at least one permanent holder #
For company websites, it should be ensured that the company itself has permanent access to the property.
Do not rely exclusively on the Google account of an external agency or a single employee.
Otherwise, if collaboration or staffing changes, this can cause unnecessary access issues.
What happens during a website relaunch? #
A relaunch does not automatically mean that you need a new Search Console property.
If the domain remains the same, the existing domain property can generally continue to be used.
However, after a relaunch, you should pay special attention to the following points:
old URLs and redirects
404 errors
indexing status
XML sitemap
robots.txt
Core Web Vitals
performance developmentThis is why Search Console is an important monitoring tool, especially right after a relaunch.
Special planning is required when changing domains #
If not only the design or CMS changes, but the actual domain, it is a much larger change.
Then, among other things, new properties, redirects, internal links, sitemaps, and other SEO aspects must be taken into account.
Therefore, a domain change should not be treated like a conventional website relaunch.
Use Search Console regularly #
After setting it up, you shouldn't simply forget about the Search Console.
Regular monitoring helps to identify developments and problems at an early stage.
Of particular interest are:
performance development
important search queries
strong and weak points
indexing issues
sitemap status
Core Web Vitals
manual actions
security issuesDo not overinterpret Search Console data on a daily basis #
SEO data fluctuates and developments take time.
A single day with fewer clicks does not automatically mean a website has an SEO problem.
Therefore, compare meaningful time periods and consider, for example, days of the week, seasonality, and changes in search behavior.
How to properly interpret the performance data will be covered in the next article.
Common setup errors #
choose wrong property type
enter https:// for a domain property
think of www only as full domain coverage
create TXT record in the wrong DNS zone
overwrite existing TXT records
delete Google verification record later
confuse Search Console with Google Analytics
expect complete data immediately
view Search Console as a ranking booster
consider every unindexed URL an error
share login credentials with agencies instead of creating your own usersChecklist: Set up Google Search Console #
Select Google Account
↓
Open Search Console
↓
Add property
↓
Select domain property
↓
Enter domain without https://
↓
Copy Google TXT value
↓
Open responsible DNS zone
↓
Add TXT record
↓
Leave existing DNS records unchanged
↓
Save record
↓
Verify in Search Console
↓
Keep verification record permanently
↓
Get to know URL Inspection
↓
Check and submit XML sitemap
↓
Monitor performance data
↓
Check indexing reports
↓
Add additional users via permissions if neededSummary #
Google Search Console is a central tool for monitoring your website's presence in Google search and evaluating technical and SEO-relevant information.
If you have access to DNS management, a domain property for the entire website is in many cases the most sensible choice. It covers different protocols, subdomains, and URL paths of the domain.
Ownership of a domain property is verified via DNS. For this purpose, Google provides an individual verification record that is published in the domain's active DNS zone.
Existing TXT entries must not simply be overwritten in the process. Even after successful confirmation, the Google verification entry should remain in place.
After setup, you can analyze search queries, clicks, and impressions, inspect URLs, submit sitemaps, and investigate indexing issues, among other things.
The Search Console does not automatically make your website more successful on Google. However, it provides you with the data you need to see what Google is actually doing with your website – and for sound SEO work, that is much more valuable than guesswork.
