To submit your website sitemap, first find its public address and check that it lists the pages you want people to find. Then add that address in Google Search Console and Bing Webmaster Tools. Keep the result from each service.
Submission tells a search engine where a list of pages lives. It does not put every page in search results. This guide covers the handover and the checks after it, so you can report what happened without guessing.
The short answer
- Check the public file and its page list before submission.
- Keep separate Google and Bing submission records.
- Report confirmed indexing separately from a successful sitemap request.
How this guide was made
Official sitemap and IndexNow guidance was checked on October 10, 2026. The bakery worksheet and handover routine are editorial examples, not measured indexing results. This guide does not promise indexing or a search position.
Sources checked .
Find the sitemap your site already makes
Start in your site platform's search settings or ask the person who built the site. A common address ends in /sitemap.xml, but your platform may use a different path or a sitemap index that links to several files.
Open the address in a private browser window. You should reach a public file without signing in. An XML file may look like code. That is normal. A page saying that no style information is attached can also be normal, since this file is for machines.
Save the complete address in your launch notes. If your builder gives you a local file on your computer, ask where the live version will be hosted and what updates it when you publish.
Give the file an owner
Choose who checks the list after new pages go live. For a small shop, this might be the owner who edits the site. For an agency project, name both the editor and the person who fixes a broken export. This small step avoids an old list being forgotten after launch.
Check the addresses before submission
Google asks for complete page addresses and recommends listing the preferred version of each page. Use real modification dates when you include lastmod. Do not set every date to today just because a build ran.
Take five pages from the file and open them. Include your homepage, a service page, your contact page and two recent articles. Confirm that each address lands on the page you expected. A successful file download cannot tell you whether the list inside is useful.
- Use the public domain, not a preview address.
- Remove pages that were deleted or replaced.
- Check that each planned article appears once at its preferred address.
- Keep private account pages out of the public content list.
Source for this section: [1] Google guidance on building and submitting sitemaps
Submit the sitemap in Google Search Console
Open the Search Console property for the live site. The Sitemaps report requires owner permission to submit a sitemap. If you lack it, ask the owner to submit the file or arrange the right access. Add the sitemap address in that report and submit it. Save the address, date and result.
Read the result before closing the page. Google uses this report to show whether it could fetch and process the file. If it reports a problem, copy the exact message into your task list. Do not mark the task as complete just because you clicked Submit.
A successful submission is a useful checkpoint. Keep the page indexing check as a separate task. For example, write that the sitemap was accepted and that the new article URLs still need review.
Source for this section: [2] Google Search Console Sitemaps report
Submit the same public list to Bing
Add and verify the site in Bing Webmaster Tools, or use a site you already manage there. Open Sitemaps and submit the public sitemap address. Check its processing details and record any reported errors.
Use a separate row for Bing in your notes. A Google result is not evidence of what Bing has done. If one service reports success and the other cannot fetch the file, keep both results visible while you investigate.
Source for this section: [3] Bing Webmaster Tools sitemap help
Track the stage you have actually reached
The example below is an empty worksheet for an imaginary local bakery. It is not a report from a real site. Replace the example pages and leave the evidence blank until you have checked it.
Submission is your request. Crawling is the search engine visiting a page. Indexing is its decision to store and consider that page for search. Ranking is where it appears for a given query. These are different events, so use different columns or task states.
| Item | Evidence to save | What it proves |
|---|---|---|
| Sitemap submission | Service, file address and response | The request was sent or accepted |
| Sitemap processing | Last read date and file status | The service processed the list |
| Bakery service page | Recorded crawl and index status | What the service reports for that page |
| New cake guide | Recorded crawl and index status | What the service reports for that guide |
| Search visibility | Query, date and search report | Visibility for the measured searches |
Handle a failed fetch with a short support note
First copy the exact sitemap address from the report and open it while signed out. If it shows a login screen, a missing page or an error, give that result to your builder. Include when it happened and whether other public pages open.
If it opens for you but the report still shows an error, ask the builder to check server access and the file format. Send the service name and its exact message. A screenshot of the site homepage adds little here, since the failing resource is the sitemap.
After a repair, check the same address again. Record the repair time so you can tell whether a later report reflects the old problem. Avoid making several unrelated changes while trying to identify one cause.
Source for this section: [2] Google Search Console Sitemaps report
Keep discovery work tied to publishing
Add a simple check to your publishing routine: confirm the new page opens, appears in the blog list, and is present in the sitemap. Assign a later review of its search status. Choose a date that fits your team's workload, without treating that date as a search engine deadline.
IndexNow can notify participating search engines about changed URLs. It complements the sitemap and does not guarantee indexing. Use it when your platform supports it or your developer can set it up correctly. It is not proof that Google indexed the page.
When reporting a batch of twenty articles, keep the exact list you submitted. Say twenty pages were published, then state which submission steps succeeded and which page statuses have been confirmed. This makes the next review much easier.
Source for this section: [4] IndexNow frequently asked questions
Common questions
Does submitting a sitemap guarantee indexing?
No. It helps a search engine find pages. The engine still decides whether to crawl, index and show each page.
Must I create a new sitemap for every article?
Usually you update the existing file through your publishing system. Check how your platform works and confirm that the live file includes the new address.
Can I use one sitemap for Google and Bing?
Yes, a valid public XML sitemap can be submitted to both services. Record and review each service's response separately.
Sources and further reading
Numbered links beside each section point to the source used there. Our examples and checklists are guidance from SnapRebuild. They are not claims of test results. Product details can change.
SnapRebuild sells a website building service. These guides are published under our editorial team name and use AI for research and writing. This is not a claim of independent expert review. Read how we make and update our content. Found an error? Tell us.
Ready for a fresh start?
Bring your website or your business idea. Explore a SnapRebuild preview and decide what comes next.
Try your free preview