Sitemaps are necessary part of our web work, and we need them to get more "Google love". But for the past one month or so, I have not been able to submit sitemaps on Google search console.
I used https://technicalseo.com/tools/fetch-render/ to check, and I passed there successfully. I used sitemap validator and that too showed no errors. It seems that something might be wrong with the search console.
Yesterday I started another site and used the same Wordpress plugin to generate a sitemap and then used the same google account to log-in to search console, and tried adding a property, this time it worked.
If I submit any new sitemap, it says couldn't fetch and if I try to resubmit existing one, then it is successful. But last read date is 6 months back, so I assume it doesn't work.
What are the possible solutions? The live testing says, that it's unable to fetch, because it is noindex. I feel that there is nothing wrong with keeping sitemaps noindex, because sitemaps should not appear in search. In-fact my second domain also got sitemaps submitted with noindex
I am using WordPress php 7.3, and HTTP/2
My sitemap Url is https://milyin.com/sitemap.xml
My HTTP headers are:
HTTP/2 200
server: nginx
date: Thu, 22 Aug 2019 12:23:21 GMT
content-type: text/xml; charset=UTF-8
vary: Accept-Encoding
x-robots-tag: noindex, follow
link: <https://milyin.com/wp-json/>; rel="https://api.w.org/"
last-modified: Wed, 21 Aug 2019 14:03:48 GMT
etag: W/"59184deaadc3de11f553f5a8fbaac7f0"
x-httpd: 1
x-robots-tag: index, follow
host-header: 192fc2e7e50945beb8231a492d6a8024
x-proxy-cache: MISS
content-encoding: gzip
x-robots-tag
headers in your response. (Not necessarily an issue, but you also have 2 overlapping Vary response headers when looking at the response.) You mention.htaccess
, however, your response headers are coming from an Nginx server? You also seem to be employing service workers (to help generate the sitemap)? Maybe related, maybe not, but when I test your sitemap using a local CURL gui I don't get any response for some reason?!