Submitting Your Sitemap to Google Search Console

This is part two of a three-part series on sitemap submission. The overview post covers why this matters and the broader plan. This post is the specific Google flow.

Google Search Console is the dashboard Google provides to every site owner who wants visibility into how Google sees their site: which pages are indexed, which are not and why, what queries trigger impressions, what the click-through rate looks like, and where crawl errors are showing up. The dashboard is free, the verification is permanent, and the submission flow takes about ten minutes if it is your first time. Here is the exact sequence I run for every site I launch.

The two property types and why I always pick Domain

Google Search Console offers two ways to register a property: Domain and URL prefix. The difference matters and the cleaner choice is almost always Domain.

A URL prefix property is scoped to one specific protocol-and-host combination, like https://pikespeakwebdesigns.com. If your site has both http:// and https:// versions, or both www. and apex versions, you would need a separate property for each. Each property has its own verification, its own reports, and its own sitemap submission. Three properties for one site is awkward.

A Domain property covers every protocol and every subdomain under the same root domain. http://pikespeakwebdesigns.com, https://pikespeakwebdesigns.com, https://www.pikespeakwebdesigns.com, and https://blog.pikespeakwebdesigns.com all roll up to one property. One verification, one set of reports, one place to submit sitemaps. It is the better default in every case I can think of, with one exception: if your DNS provider does not let you add TXT records (rare, but some legacy registrars are restrictive), then URL prefix is the fallback.

Verifying ownership with a DNS TXT record

Domain properties verify exclusively through DNS. You add a single TXT record to your domain's DNS configuration, Google reads it within a few minutes, and ownership is permanently verified. The exact flow:

1. Sign into Search Console with the Google account you want to own the property. (For a client engagement I always use a dedicated account, not the owner's personal Gmail.)
2. Click "Add Property" and choose Domain. Enter the apex domain (pikespeakwebdesigns.com, no www, no https://).
3. Google generates a TXT record that looks like google-site-verification=AbC123XyZ.... Copy the value.
4. Open your DNS provider's control panel (Cloudflare, Namecheap, GoDaddy, whoever). Find the DNS records section for the domain. Add a new TXT record: name is @ or the apex domain, value is the string you copied. TTL can be the default (usually 3600 or "Auto").
5. Save the DNS change. Most providers propagate in under a minute. Google's verification check usually finds it within a few minutes after that, sometimes immediately.
6. Back in Search Console, click "Verify". If it fails the first time, wait two minutes and try again. If it fails after fifteen minutes, the most common cause is the TXT record being scoped to a subdomain instead of the apex.

The TXT record stays in DNS permanently. Don't remove it after verification or Google may re-check ownership and fail to find it.

Submitting the sitemap

Once the property is verified, the sitemap submission is one screen and one field.

1. In the left nav, click Sitemaps.
2. The "Add a new sitemap" field appears at the top. The path prefix (https://pikespeakwebdesigns.com/) is already filled in for you. You only enter the path: typically sitemap.xml.
3. Click Submit.

That is the entire sitemap submission. Google fetches the file within seconds, parses it, and reports back: number of URLs discovered, last-read date, status. The "Submitted URLs" count populates immediately. The "Indexed URLs" count starts at zero or one (the homepage is usually already indexed by this point) and climbs over the next few weeks.

What "Page indexing" actually tells you

The Page Indexing report is where you watch the index build out. The report categorizes every URL Google has discovered into two buckets:

• Indexed. Google has crawled the page and added it to the search index. It can appear in search results.
• Not indexed. Google has either not yet crawled the page, or crawled it and decided not to index. Each "not indexed" reason is listed: "Discovered – currently not indexed" (queued, hasn't been crawled yet), "Crawled – currently not indexed" (crawled, decided to not index, often because the page is thin or duplicate), "Page with redirect" (the URL redirects somewhere else, the destination is the canonical), "Excluded by 'noindex' tag" (the page asks not to be indexed, intentional in most cases), and a handful of others.

For a freshly-submitted sitemap, expect the indexed count to start small and climb steadily. By six weeks, a typical small business site lands somewhere between 60% and 90% of its sitemap URLs indexed. The 10-40% that does not get indexed is usually pages Google has judged thin, or duplicate-content concerns, or pages that should be excluded from the sitemap in the first place.

Requesting indexing for high-value pages

The URL Inspection tool, accessible from the search bar at the top of Search Console or the left-nav, lets you request priority crawling for individual URLs. The flow:

1. Paste the URL into the inspection bar.
2. If the URL is not yet indexed, click Request Indexing.
3. Google queues the URL for priority crawl. The crawl usually happens within a few hours, indexing within 24 to 48 hours.

The feature is rate-limited (around ten requests per day) so use it on the pages that matter most: pricing, contact, the homepage's main service hub pages. For everything else, the sitemap-driven background crawl is sufficient.

Performance report: the long-term feedback loop

Once pages are indexed, the Performance report is where you see what queries are actually triggering impressions. By default it shows "Web search" performance over the last three months. The four numbers that matter:

• Total clicks. Visitors who clicked from a Google search result.
• Total impressions. Times a page from your site appeared on a search results page, regardless of whether it was clicked.
• Average click-through rate (CTR). Clicks divided by impressions.
• Average position. The mean rank position of the impressions.

For a brand-new property, all four numbers will be zero or near-zero for the first several weeks. The first impressions typically appear within 14 to 21 days; the first clicks within 30 to 45 days. By 90 days you have a baseline for what queries the site is showing up for and where the click-through rates are.

This is the report I check monthly for every site I host. The patterns worth watching are: queries with high impressions but low CTR (the title and meta description are not compelling enough), queries where the page's average position is between 7 and 12 (one rank improvement away from the top of page two), and queries the client never expected to rank for (genuine free traffic from related search intents).

The next post in the series covers the same flow for Bing Webmaster Tools, where the dashboard is different but the indexing economics matter more than most small-business owners assume.