Setting Up Google Search Console: Step by Step

Why you need it

Search Console shows which search terms bring visitors to you, how often your pages appear, which pages are indexed and what technical problems there are. Without it, you are working blind.

Setting up in five steps

Sign in with a Google account at search.google.com/search-console.
Choose “Add property”. The domain property is recommended, as it covers all variants (with and without www, http and https).
Verify ownership; for a domain property this is usually done with a DNS record, otherwise with an HTML file or a meta tag.
Under “Sitemaps”, enter the address of your sitemap, usually /sitemap.xml.
Wait a few days until the first data appears.

The most important reports

Performance: Clicks, impressions, position and search queries.
Page indexing: Which pages have been included, which have not, and why?
Core Web Vitals: Measurements of the user experience.
Manual actions: Notices about violations.

Domain or URL-prefix property: which to use when

The domain property combines all subdomains and protocols and requires proof of ownership via a DNS record. That assumes you have access to the domain management. If you do not, for example because a previous agency manages the domain, the URL-prefix property is the pragmatic route: you verify it with an HTML file or a meta tag, but then you only see the exact address you entered, for example only the https version with www. If in doubt, set up both; it costs nothing.

An example of reading the performance data

Suppose a heating engineer sees in the “Performance” report that the search query “heat pump Stuttgart” has many impressions but hardly any clicks, at an average position of around 9. That means the page is visible but rarely chosen. The first lever is then not more text, but a better title tag and description. If, on the other hand, a query sits at position 14 to 20 with solid demand, it is worth expanding the relevant page. That is how a table turns into concrete tasks.

Common pitfalls

Access held by one person only: If the Google account goes away, access is lost. Add further users under “Settings”.
Looking at the wrong property: If you have only set up the http version, you will see hardly any data. Check the selected property at the top left.
Drawing conclusions too early: Data appears with a delay and only goes back to when you set it up. Compare whole weeks or months, not individual days.
Overinterpreting indexing messages: “Discovered – currently not indexed” is not automatically an error for new or thin pages. What matters is whether it affects pages that are meant to appear in search.

Checking individual pages

With the URL inspection at the top of the tool, you can see for a single address whether it is in the index, when Google last crawled it and whether Google can fetch and render the page. After a major change you can request indexing there. That may speed up crawling, but it does not guarantee inclusion in the index and does not replace the sitemap. For the bigger picture, see SEO basics for businesses.

Backing up and sharing data

Search Console stores performance data for only about 16 months. If you need year-on-year comparisons, export the reports regularly as a spreadsheet or connect the tool to a reporting solution. Being able to set different levels of permission is also handy: an agency or an employee gets read access, while the company remains the owner. That way you keep control of the data even if the working relationship changes.

Next step

Take a quick look at the “Performance” report every week and watch which pages are growing. An SEO analysis helps with interpreting it.