Google Search Console: Invalid Sitemap Address
The message “The incorrect address of the site map” may appear already when you try to add a map in Google Search Console. On the authentic screenshot from the panel you can see the listed sitemap.xml and a warning requiring the correct path. The image itself confirms the message, but does not determine the cause. Start with the type of service in Search Console and whether the map is publicly available at the address assigned to the appropriate site.
Example error screen
A sample of the issue in the application interface. Use the diagnostic steps below to identify the cause.
How to Recognize Cause
Check the exact service address in the Search Console property selector. Domain-type service includes protocols and subdomains other than a URL prefix service. Notice if the field of adding the map has already displayed a fragment of the base address.
Open full map address in the new window, for example https://your-domaina.pl/sitemap.xml. Check if the browser shows XML maps and the server returns HTTP 200, not 404, redirect to the login screen or HTML page with an error.
Compare the domain and map protocol with the actual site domain. Check the web variant, possible HTTP→HTTPs redirects and whether the site is under a different prefix than currently selected in Search Console.
Step by step solution
1. Enter Google Search Console and select the correct service from the list on the left. Open the Indexing section → Site Maps. Do not try to report a map for another domain or accidental version of the site.
2 . In the Add Map box see if the interface shows a part of the address. If so, specify the remaining correct path, such as sitemap.xml. If full URL is expected, enter the actual HTTPS address of the map. Don't duplicate the domain fragment.
3 . Verify the presence of file or route /sitemap.xml on the server. In Next.js App Router, the map can be generated by app/sitemap.ts; after changing the code, make sure the production deployment includes a new route.
4 . Check that the map content is a valid XML with an address or canonical address of the actual subpages. The map must not only indicate non-existent addresses or the preview environment instead of production.
5 . If a map is available, but the form still rejects the value, switch to the right service, verify its type and try the correct full address or path corresponding to the field. Separate the validation problem of the form from the robot download error.
6 . After you have added the map correctly, go to the table of uploaded site maps, open its details and check the download status. Use the URL Inspection separately for one subpage to verify its indexing.
How to see if the problem is gone
The form field accepts the correct path, the map goes to the list of maps sent, and its full address can be opened without logging in. This confirms the acceptance of the application, not the indexation of all parties.
After the next reading of Search Console, it should not show the map itself download error. If the status is still incorrect, check the detailed report and the server response, and do not assume that the problem concerns the content of the entire site.
What to do
Do not confuse the warning about the invalid address entered in the form with the later status “Unable to download”. It's two different stages of diagnostics.
Do not send multiple copies of the same map with random prefixes and do not promise immediate indexation after accepting the file.
