How to check a website sitemap and submit it to Search Console
A sitemap is an XML list of public website URLs that helps a search engine discover pages. First check that the file really returns XML, then verify the domain in Google Search Console and submit the sitemap for that same domain.
Check what the sitemap URL returns
Open /sitemap.xml on your published domain. It should return a sitemap document with a urlset or sitemapindex root, not the homepage, a login form or an error screen. Every listed page should be public, published and use the correct HTTPS domain.
A website that returns its homepage for every unknown path can make a missing sitemap look successful. Check the response body as well as the HTTP status. Put the sitemap address in robots.txt and link useful pages in normal navigation.
Verify the property you actually own
A Search Console Domain property covers a domain and its variants and uses a DNS verification record. A URL-prefix property covers the specified URL prefix and supports other verification methods. Use the method Search Console offers for your property and keep its verification record in place.
Domain ownership verification and an API key are different things. A Google sign-in, Places key or Analytics tag does not by itself verify a Search Console property. Only an authorised owner should change the DNS or connect the property.
Submit and inspect the result
Submit the exact sitemap URL. If Search Console says it could not fetch the file, check redirects, authentication, firewall rules, the XML body and the domain. Then inspect a representative public page to see what Google can access.
Separate three outcomes: the sitemap was received, the page was discovered, and the page was indexed. A successful submission does not prove the last two. Changes may need recrawling and search engines do not guarantee inclusion.
What this means for a Woro-built website
Woro’s own public websites have sitemaps. Customer web-builder sitemap and Search Console setup are a separate capability and were not verified in the deployed builder reviewed on 4 October 2026. Do not assume that publishing a customer page creates these files automatically.
Until that flow is implemented and verified, use your hosting platform’s supported sitemap and verification options or ask the site operator to configure them. Never give a third party your Google password.
Sources: Google sitemap guidance and Search Console verification.
Questions people ask
Is Google Analytics the same as Search Console?
No. Analytics measures visits and configured events; Search Console reports how Google discovers and shows your site.
Should private pages appear in the sitemap?
No. List public canonical pages intended for discovery, excluding drafts, account screens and pages you have told search engines not to index.
Next: SEO, AEO and GEO: a practical checklist for a business website