Mar 27, 2019
Sitemap could not be read in new GSC
Can you please help me to solve this problem?
Details
This question is locked and replying has been disabled.
Community content may not be verified or up-to-date. Learn more.
Last edited Mar 27, 2019
Mar 27, 2019
That the new console says 'couldnt fetch' is a bug in the console.
Pending is the real status!
Original Poster SatguruTechnologies Bhawan marked this as an answer
May 1, 2019
Alas there is no real way (that I know of!) to tell between them.
But can try using the URL Inspection on the sitemap url. it SHOULD say not indexed (it's a sitemap not a page, so shouldn't be indexed!), but can use the Live Test, to check if Googlebot CAN fetch it!
Again as its a sitemap, NOT a page, DON'T use the 'Request Indexing' button!
If Google can fetch it, it's most likely just Pending, which case just wait.
Last edited May 2, 2019
Original Poster SatguruTechnologies Bhawan marked this as an answer
May 2, 2019
OK, so live-tested it (not inspected) and I got "URL is not available to Google".
Note, that "URL is not available to Google" is an opinion on indexablity.
... all interested in from the live test, is if the sitemap was 'fetched'. That can see the source of the sitemap in the 'View tested page' area, or that it shows
It's a sitemap, so doesn't need be in 'indexed' (in the webs page index!)
So, should I assume that there is something wrong on my end then?
Not necessarily!
In your case your sitemap index has 'X-Robots-Tag' on it, preventing indexing. That is why not available to Google search index.
(So the fact that Google shows that message, in THIS case is probably good. Shows Google fetched it, and found the X-Robots-Tag!)
... but Google can also get "URL is not available to Google", if unable to crawl/fetch, so don't take it itself to mean good.
...so again, look in 'Page fetch' (under 'Crawl') section for success :) - and/or 'view tested page' for visible code
Original Poster SatguruTechnologies Bhawan marked this as an answer
Apr 2, 2019
What does it matter?
Now you 'know' that couldn't fetch can be wrong (ie its really pending) - can just carry on with your day.
That the console would show 'pending' more correctly isnt exactly going to change your life :)
Diamond Product Expert Travler. recommended this
May 25, 2019
This is an old thread that's been answered.
Anyone wanting help with their own sites should open their own post.
Diamond Product Expert barryhunter recommended this
All Replies (105)
That the new console says 'couldnt fetch' is a bug in the console.
Pending is the real status!
Original Poster SatguruTechnologies Bhawan marked this as an answer
Nov 16, 2019
Nov 20, 2019
There is a real problem with Google reading sitemaps in certain cases, but I have not been able to identify the root cause.
I suspect it may have something to do with structured sitemaps, which google Search Console now fails to read, after the SC update. Yoast SEO wordpress plugin as an example constructs the sitemaps into several xml files, and sitemap_index.xml works as an index only, not containing any actual pages, but only acts as an index to more sitemap files, which actually contain the page urls.
Symptoms:
- Google Search Console complains "Sitemap could not be read" on sitemaps listed in the index xml
- Live test on the actual page sitemap xml returns "Page fetch: Successful"
- Other sitemap test tools return "valid content" and "fetch ok" for the said sitemaps
- Yet, Google Search Console complains, and has not read/refreshed the sitemaps for 6 months!
Also, I do not see anyone from Google (!) saying a word here in this discussion thread. - So, it's all speculation - and as usual, nobody from Google bothers to comment.
Nov 26, 2019
i submitted my sitemap on Google Search Console yesterday by using plugin yoast SEO.
GSC dind't even found one URL but i actually see all the urls when i check inside the same sitemap!
Really hope someone can help me
Nov 26, 2019
Nov 26, 2019
No. It can take weeks (if not longer!) for a sitemap to be processed, and show in the Console.
The 'Coverage' report is only updated every few days, (can usually see the last date top right), but even then the status may be older.
The console is good for observing long term trends, and forming patterns. Its not 'immidate'!!!?!
Nov 29, 2019
and when I resubmit it, it show the same error
any solution to fix this
Nov 30, 2019
Nov 30, 2019
Its still sitting in the queue.
Resubmitting the sitemap wont help. Its already known about and just waiting.
resubmitting isnt a way to 'jump' the queue (intentionally!)
my site map is not read not showing pages why???Mar 4, 2020
Sitemaps can take time to process.
Particully in case of a sitemap index. THere is the delay in rpcessing the index file, and the dealy in processing the child sitemaps.
Months delay is not all that unusual. Dont expect new sitemaps to be processed quickly.