Makey Updates

What Is a Sitemap and How to Submit It to Google Search Console

A sitemap is a file that helps search engines discover the important pages, images, videos, and other content on a website. For most sites, the most useful version is an XML sitemap containing a list of canonical URLs that Google can crawl.

A sitemap does not guarantee that every listed page will appear in search results. It gives Google useful discovery information, while your site structure, content quality, internal links, mobile experience, and technical health influence whether pages are crawled and indexed.

Submitting a sitemap through Google Search Console is a straightforward task for bloggers, online shops, service businesses, and Australian website owners. It is especially useful when a site is new, has many pages, or regularly publishes content for audiences in Sydney, Melbourne, Brisbane, Perth, and other locations.

How A Sitemap Supports Search Discovery

An XML sitemap acts as a roadmap for search engine crawlers. It can show Google which URLs are available, when pages were last updated, and how different content types are organised. A standard sitemap may include blog posts, category pages, product pages, and key service pages.

Sitemaps are particularly valuable for websites with weak internal linking, thousands of URLs, archived content, or pages that are difficult to reach through normal navigation. A newly launched Australian business website using a .com.au domain can benefit from a sitemap because it helps Google find its initial pages more efficiently.

The file usually lives at a simple address such as https://example.com/sitemap.xml. WordPress websites may use an automatically generated sitemap from WordPress core or an SEO plugin. Some platforms create a sitemap automatically, while custom-built websites may require a developer or hosting tool to generate one.

Sitemap Types And File Locations

The most common format is an XML sitemap. It contains URLs rather than visual page links and is designed for search engines. A large website can use a sitemap index, which is a master file linking to several smaller sitemaps for posts, products, images, or other sections.

An HTML sitemap is different. It is a normal webpage containing links that help human visitors navigate a site. It can support usability and internal linking, but it is not usually the file submitted in the Sitemaps report in Google Search Console.

You can often find a sitemap by checking these locations:

If none of these addresses work, check your SEO plugin, content management system settings, hosting documentation, or website developer. Do not submit a random URL that displays an ordinary webpage instead of a valid sitemap file.

Comparing Common Sitemap Options

The right sitemap setup depends on your platform, website size, and the type of content you publish. A small local trades business in Adelaide may need only one XML file, while a national retailer with thousands of products could use a sitemap index.

Sitemap option Best suited to Typical location or format Key consideration
XML sitemap Most blogs and business websites /sitemap.xml Lists important canonical URLs
Sitemap index Large websites with multiple sitemap files /sitemap_index.xml Connects several child sitemaps
Image sitemap Websites relying heavily on image search XML image extensions or separate file Useful for galleries and visual products
Video sitemap Publishers with significant video content Video XML sitemap Requires accurate video metadata
HTML sitemap Visitors and internal navigation A normal website page Not a replacement for an XML sitemap
RSS or Atom feed Frequently updated blogs Feed URL Google may use it for recent URL discovery

Sitemap files must use valid formatting, accessible URLs, and the correct website version. If your site redirects from HTTP to HTTPS, submit the HTTPS sitemap. The same principle applies to the preferred hostname, such as www.example.com.au or example.com.au.

Preparing Your Website Before Submission

Before adding a sitemap to Google Search Console, open it in a browser and check that it loads without a server error. Review a sample of URLs to ensure they are live, indexable, and canonical. A sitemap should not contain pages blocked by robots.txt, marked noindex, redirected to another URL, or returning a 404 error.

The listed pages should represent your valuable, public content. Exclude thin tag pages, internal search results, duplicate URLs, staging pages, and outdated versions that should not appear in search. If your website has location pages for Sydney, Canberra, and the Gold Coast, include them only when each page offers useful, distinct information.

Use these checks before submission:

A sitemap can contain thousands of URLs, but quality matters more than quantity. Google may ignore URLs that provide little value or conflict with other indexing signals, so keeping the file clean makes technical maintenance easier.

Submitting A Sitemap In Google Search Console

First, open Google Search Console and select the correct property. A Domain property covers variations such as HTTP, HTTPS, www, and subdomains after DNS verification. A URL-prefix property covers a specific version of the site, so the address must match the sitemap URL you submit.

Select Sitemaps from the left-hand navigation. In the field labelled for adding a new sitemap, enter only the path if the domain is already displayed, such as sitemap.xml or sitemap_index.xml. Select Submit. Google will attempt to fetch the file and display a submission status.

A successful submission means Google accessed the sitemap. It does not mean every page has been indexed. Use the Page Indexing report to review indexed, excluded, and error URLs. For a recently published article, the URL Inspection tool can show whether Google knows about the page and may provide a request for indexing option.

You generally need to submit a sitemap once. Google can revisit it automatically, so repeatedly submitting the same file will not speed up crawling. Submit it again when the address changes, such as after a migration from a staging domain to a live .com.au website.

Fixing Sitemap Errors And Indexing Delays

A “Couldn’t fetch” message may indicate that the file is unavailable, blocked, incorrectly formatted, or returning a server error. Open the sitemap directly, check the HTTP response, and confirm that your firewall, security plugin, or hosting provider is not blocking Googlebot.

An “URL not allowed” issue often occurs when the sitemap belongs to a different property or subdomain. For example, a sitemap hosted on shop.example.com.au may require the relevant property to be verified in Search Console. Mixed protocol versions, such as submitting an HTTP sitemap for an HTTPS site, can also cause confusion.

If the sitemap is accepted but pages remain unindexed, inspect individual URLs. Common reasons include duplicate content, poor internal linking, thin content, slow performance, mobile usability problems, or a page marked noindex. Google may also take time to crawl a new site, particularly when it has few external links or limited history.

Keeping Your Sitemap Healthy Over Time

Treat the sitemap as part of regular website maintenance rather than a one-time SEO task. Check Search Console after publishing a new site section, changing URL structures, moving to a new host, or launching an online store. Review coverage patterns instead of reacting to a single excluded URL.

A well-maintained sitemap should reflect the current website architecture. Remove old URLs after permanent deletions, update redirects carefully, and ensure internal links point directly to the preferred versions. Australian businesses serving multiple states should also keep location and service pages distinct, accurate, and supported by useful local details.

Open Google Search Console, locate the sitemap generated by your website, and submit it today. Then inspect a few important URLs, correct any technical errors, and monitor the Sitemaps and Page Indexing reports as your site grows.