How can we help?

A sitemap helps a search service discover website addresses. Use your actual shop’s public sitemap, not a product-shopping feed or a sitemap belonging to another site.

Check the shop’s sitemap

1. Confirm the public shop address, including HTTPS and the intended domain.
2. Check the sitemap address for that shop. The existing ShopTill-e route is the shop address followed by /sitemap.xml; ask support to confirm it if that address does not return the expected sitemap.
3. Open it and check that it contains the intended shop’s page addresses rather than an error, login page or another site’s content.
4. Inspect representative product and page links. Check their hostname, availability and actual customer-facing destination.
5. Investigate missing, incorrect or private addresses before submitting the sitemap.

Submit the checked address

1. Open the intended verified website property in Google Search Console with the required owner access.
2. Open its Sitemaps report.
3. Enter the checked sitemap address in the add-sitemap control and submit it.
4. Read the reported status and open any error details. Check back for its actual processing result.

Example: use the current domain

After a planned domain change, check the sitemap and its entries use the intended website address before submitting it for the corresponding property. Opening one correct product page does not establish that every sitemap entry is correct.

If Google cannot read it

Keep the exact sitemap address, property, status and error for support. A successful sitemap read does not guarantee that every listed page is indexed. See Google’s Sitemaps report guidance.

Search Console verification · Product feeds.

Check individual addresses, not just the XML opening

A browser may show an unstyled XML tree when the sitemap opens. That confirms you can inspect its contents; it does not establish that all listed addresses are correct or accepted by a search service.

• Check the listed domain: the address used to open the XML and the page addresses inside it can differ. Confirm that the entries use the intended customer-facing domain.
• Review duplicate entries: record repeated page addresses and check their intended source before changing content.
• Look for joined or malformed addresses: an entry containing two website addresses joined together needs investigation. Keep the exact entry and intended destination for support.
• Open representative pages: compare the actual destination, content and availability, including products with options.

Do not delete a valid page merely to remove a questionable generated entry. Have the source link or sitemap behaviour checked. A page opening successfully is also separate from its indexing status.