Installing and configuring Google Search Console

Setting up Google Search Console takes three steps: create a property (domain or URL-prefix), prove you own it, then submit your XML sitemap. The whole process takes about fifteen minutes and is the first building block of any technical tracking, for SEO as much as for GEO.

Create an account and choose the right property type

Go to search.google.com/search-console with a Google account and click "Add property." You'll be offered two options:

Domain property: covers the entire domain, across all subdomains and protocols (http, https, with or without www). This is the recommended option in most cases, since it gives you a complete view and avoids duplicating properties.
URL-prefix property: covers only one exact URL (for example, only https://www.yourdomain.com). Useful if you can't edit your domain's DNS records, or if you want to track a specific subfolder in isolation.

If you have control over your domain's DNS configuration, go with the domain property — it simplifies everything else downstream.

Verifying the property: the available methods

Google needs to confirm you actually control the site before granting access to its data. Several methods exist depending on the property type you chose:

DNS record (TXT) — the only method available for a domain property. Google gives you a value to add as a TXT record with your host or DNS registrar. Propagation can take anywhere from a few minutes to 48 hours.
HTML meta tag — for a URL-prefix property, Google provides a <meta name="google-site-verification" content="..."> tag to insert in the <head> of the homepage.
HTML file upload — a uniquely named file (e.g. google1234567890.html) provided by Google, placed at the site root and reachable directly at yourdomain.com/google1234567890.html.
Google Analytics or Google Tag Manager — if either is already installed and you have admin rights on it, verification happens automatically with no extra step.

Pick whichever method matches your technical access: DNS if you manage the domain name, meta tag or HTML file if you only have access to the site's code.

Submitting the sitemap

Once the property is verified, go to the "Sitemaps" entry in the side menu. Enter your XML sitemap URL (usually sitemap.xml or sitemap_index.xml, appended after your domain) and click "Submit." This step isn't required for Google to crawl your site, but it speeds up discovery of new pages and gives Google an explicit list of the URLs you consider important.

If you're not sure whether a sitemap already exists, just test yourdomain.com/sitemap.xml directly in your browser. Most CMSs (WordPress with Yoast or Rank Math, Shopify, Webflow) generate one automatically.

Extra settings worth doing right away

A handful of settings, done once the property is verified, save time down the line:

Link Google Analytics 4 if you already have it installed, so you can later cross-reference crawl and traffic data.
Add other team members as users (Settings > Users and permissions menu), with an access level that matches their role (read-only or full owner).
Check the "Configuration" > "Changes" section, which lists structural changes Google has detected (title tag changes, canonical changes, etc.) — useful for spotting unintended modifications.
If the site is multilingual, don't expect Search Console to handle international targeting automatically: that depends on your hreflang implementation, which needs to be checked separately.

Once this setup is done, the next step is learning to read your data in Google Search Console to turn this access into an actionable diagnosis. It's also worth installing Bing Webmaster Tools, which follows the same logic and matters for visibility in Copilot's answers.