Step 1: Verify Your Property in Google Search Console
Before you can submit a sitemap, you must verify ownership of your website in Google Search Console (GSC). If you haven't set up GSC yet, go to search.google.com and click "Add Property".
Google offers several ways to verify your site. The most robust method is the Domain Property Verification, which requires you to add a DNS TXT record to your domain registrar (like GoDaddy, Namecheap, or Cloudflare).
Alternatively, you can verify via HTML file upload, HTML meta tag, or by linking your Google Analytics account.
Step 2: Upload Your Sitemap to Your Server
Once you have generated your `sitemap.xml` file using our Free Sitemap Generator, you need to upload it to the root directory of your website.
If you are using a CMS like WordPress, many plugins will generate and host this file dynamically for you. However, if you are working with a custom stack, you'll upload it manually via FTP, cPanel, or your hosting provider's file manager.
Verify that it works by visiting `https://yourwebsite.com/sitemap.xml` in your browser. You should see a tree of raw XML data.
Step 3: Submit the URL to Google
Log in to GSC, select your property, and navigate to the Sitemaps section located in the left sidebar menu under the "Index" tab.
You will see a section titled "Add a new sitemap". Because your domain is already verified, Google will pre-fill the domain part of the URL.
Simply type `sitemap.xml` into the input field and click the blue Submit button.
Step 4: Check for Errors and Coverage
After clicking submit, Google will display a "Sitemap submitted successfully" popup. However, the real test is checking the status a few days later.
Return to the Sitemaps report after a week. You should see the "Status" column read Success. If it says "Couldn't fetch" or "Has errors", you will need to click on the sitemap to view the specific issues (such as 404 errors, invalid URLs, or blocked robots.txt paths).
Troubleshooting Common Errors
Sometimes, Google Search Console will flag your sitemap submission with an error. Here are the most frequent issues and how to fix them:
- Couldn't fetch: This generic error often means Google's bot was blocked from accessing the file. Check your robots.txt to ensure it isn't blocking the sitemap file, and verify that your server isn't returning a 5xx error or blocking Googlebot via a firewall (like Cloudflare).
- Submitted URL blocked by robots.txt: This means your sitemap includes a URL that is simultaneously blocked in your robots.txt file. You must either remove the URL from the sitemap or unblock it in the robots file.
- Submitted URL has crawl issue: Google tried to visit a page in your sitemap, but encountered a broken link (404), a server timeout, or an infinite redirect loop. Clean up the affected URLs in your XML file.
Maintaining Your Sitemap Over Time
Submitting a sitemap is not a one-and-done task. For ongoing SEO health, your sitemap requires maintenance.
If you perform a major site migration, change your domain name, or transition from HTTP to HTTPS, you must generate a brand new sitemap and submit it to Google immediately to speed up the indexation of your new URL structure.
Additionally, it is a good habit to review the "Page Indexing" report in GSC monthly. Compare the number of URLs submitted in your sitemap against the number of URLs actually indexed. A large gap between these two numbers is a major red flag indicating that Google does not consider your content valuable enough to index, signaling deep quality or technical issues.