Google Search Console + XML Sitemap Setup — Done for You
TL;DR: We wire up Google Search Console the right way (Domain property, DNS verification, all subdomains covered) and submit a clean XML sitemap — so Google has a reliable map of your site from day one. One-time setup, no recurring dependency on us. See pricing.
Most indexing problems do not start with bad content. They start earlier — with a GSC property that only sees part of the site, a sitemap Google cannot parse, or a robots.txt that quietly blocks the crawler. This setup removes all three. Once the foundation is clean, tools like IndexNow and passive discovery can do their job, and you can use the URL inspection tool to confirm pages are actually getting picked up.
This service is part of our SEO services suite, but it stands on its own: it is the first thing we run before anything else touches a site.
What the setup covers
| Step | What we do |
|---|
| GSC property type | Create or migrate to a Domain property (DNS-TXT verification) — not URL-prefix, which misses subdomains and protocol variants |
| Ownership verification | Place the DNS record; confirm all subdomains (www, non-www, http, https) fall under one verified property |
| Sitemap audit | Review your existing sitemap or generate a clean one: no noindex URLs, no canonicalized-away pages, no redirect chains in the URL list |
| Sitemap submission | Submit via GSC Sitemaps panel — the only reliable submission path since Google retired the sitemap-ping endpoint in late 2023 |
robots.txt Sitemap: directive | Add the full sitemap URL to robots.txt so any crawler that ignores GSC still finds it |
| Fetch & inspect | Run initial URL inspection on key pages; document any crawl or coverage errors found at handover |
Check your URL → — 200 free credits, no account required.
Already know what you need? View pricing or reach out directly.
What the GSC + sitemap setup covers
Google Search Console gives Google a direct line to tell you when it cannot reach your pages, cannot index them, or finds something it considers a problem. But GSC only works if the property is set up correctly.
There are two property types. A URL-prefix property covers exactly one protocol and one subdomain — https://www.example.com is a different property from https://example.com. That means split data, split coverage, split alerts. A Domain property — verified via DNS-TXT record — wraps every subdomain and every protocol under one view. That is what we create. If a Domain property already exists, we verify the DNS record is placed correctly and the property is confirmed, not just pending.
Sitemap: what "clean" actually means
A sitemap is a list of URLs you want Google to consider for indexing. The word "consider" is important — submitting a URL does not guarantee indexing. What a clean sitemap does is remove the noise so Google spends crawl budget on URLs that matter.
A clean sitemap excludes:
- Pages marked
noindex
- Canonical-destination duplicates (the canonical URL stays; the variant does not)
- URLs that return 3xx redirects — Google will follow them, but the redirect chain belongs in the sitemap, not the endpoint
- Paginated archive pages that add no topical value
- Admin, login, thank-you, and other utility pages
We either audit your existing sitemap against these criteria or build one from scratch, depending on what your CMS outputs. The final file is validated for XML syntax and confirmed accessible at the submitted URL before we hand it over.
robots.txt: the backup channel
After Google retired the sitemap-ping endpoint in late 2023, there are two ways to tell Google about your sitemap: GSC submission and the Sitemap: directive in robots.txt. We use both. The robots.txt directive matters for crawlers that do not rely on GSC — and for situations where a GSC property is recreated or transferred without re-submitting the sitemap.
Why a clean setup is the foundation
Crawling and indexing are separate steps. Google first crawls a page (downloads it), then decides whether to index it. GSC and sitemaps operate at the crawl layer — they help Google find your pages. If that layer is broken, everything downstream is working against friction.
The most common problems we see before setup:
- URL-prefix property covering only
https://www. — the naked domain and http version have no coverage
- Sitemap submitted but returning 404 (it moved after a CMS migration and no one updated the reference)
- Sitemap containing 800 URLs when only 120 are canonical, indexable pages
- GSC ownership showing "unverified" because the DNS record was removed when the domain was transferred
None of these problems announce themselves loudly. The site appears to be configured. Traffic continues from already-indexed pages. New pages just do not get picked up — and without GSC, you would not easily know why.
A correct Domain-property setup with a verified DNS record and a clean sitemap eliminates this whole class of issue. It is also a prerequisite for using GSC's URL Inspection API reliably, and for interpreting coverage data accurately.
What you get afterward
This is a one-time setup. When we hand it over, you have:
- A verified Domain property in Google Search Console under your account
- A clean XML sitemap submitted via GSC and referenced in robots.txt
- A written handover note covering: property type, verification method, sitemap URL, any coverage errors found at time of setup, and what to do if you add new content sections
- No recurring dependency on us — the setup is yours, in your account, fully documented
After that, you can use IndexNow or on-demand indexing requests to push individual URLs without waiting for crawl. You can also run the index checker to confirm specific pages are indexed or spot problems early.
If you have a larger content operation and want ongoing managed indexing, that is a separate service — see pricing for the full breakdown.
Who this service is for
This setup is useful if:
- You just launched a site or migrated to a new domain and want a clean start
- You inherited a site and do not know if GSC is configured correctly
- You have noticed pages not appearing in search despite being live for weeks
- Your CMS is generating a sitemap but you have never verified what is actually in it
- You are about to start a content push and want indexing infrastructure in place before it begins
It is not the right fit if you are looking for ongoing ranking strategy, content audits, or link acquisition — those are different services. This is infrastructure.
From the field
Dmytro Puhach, Founder · 15+ years in SEO
The number of sites I have seen with a URL-prefix GSC property that has been in place for years — sometimes on sites with significant traffic — is higher than it should be. The owner does not know. The agency does not mention it. The data looks complete because existing indexed pages are reporting in fine.
What you lose is coverage of any URL variant that does not exactly match the prefix. You also lose the ability to trust your coverage error reports, because you are only seeing part of the picture.
Domain property setup with DNS verification takes minutes to configure and some hours for DNS propagation. The clean sitemap takes a bit longer — it depends on how noisy the CMS output is. But it is the kind of work that, once done correctly, stays done. I cannot think of a single indexing engagement we have run where fixing GSC and the sitemap first did not make the subsequent work measurably easier.
Frequently asked questions
What exactly do you set up?
We create or correct a Domain property in your Google Search Console account (verified via DNS-TXT record, covering all subdomains and protocols), audit or build a clean XML sitemap excluding noindex and redirected URLs, submit it through GSC, and add the Sitemap: directive to your robots.txt. You also receive a written handover note. That is the full scope — no add-ons, no retainer.
Do I need anything after that?
No ongoing maintenance from us, no. The setup is stable: DNS verification does not expire, sitemaps re-crawl automatically once submitted, and robots.txt directives persist. If you significantly restructure your site or add large new content sections, you would want to regenerate and resubmit the sitemap — but that is straightforward to do yourself, or we can do it as a separate task. Day-to-day, nothing requires attention.
Doesn't every CMS do this automatically?
CMS platforms generate sitemaps automatically, but what they include is rarely what you want. WordPress with Yoast, for example, will include tag archives, author pages, date archives, and attachment pages by default — none of which should be in a sitemap for a typical business site. Shopify sitemaps include product variants. Many CMS-generated sitemaps also fail to exclude pages marked noindex, which is a direct contradiction. The auto-generated file is a starting point, not a finished product. Same story for GSC: most CMS platforms will verify ownership via a meta tag or file upload (URL-prefix, single protocol), not DNS. The Domain property usually requires a manual step.
How long does setup take?
DNS propagation takes up to 48 hours — that is outside our control and is the same for everyone. Once the record propagates, GSC confirms the property automatically. The sitemap audit and submission happen in parallel. From the moment we start, expect handover within one to two business days in most cases. For very large sites with complex sitemap structures, we will scope it with you before starting.
