Thread Starter
gfuzz
(@gfuzz)
…and to be clear, the sitemap submission fails when I submit the sitemap in google search console, because of the “noindex” error.
Hi there!
The sitemap is fine having the x-robots-tag: noindex, follow header. This behavior is intended, and it prevents the sitemap being shown directly on search engines. It doesn’t stop them from using the sitemap.
Also, be sure to notify Google of the updated robots.txt file if you’ve just switched to The SEO Framework. A cached copy of your robots file in their system might prevent them from accessing it.
Now, many of the pages on your website are controlled by non-conventional software that takes over the default WordPress behavior, which tells the content is restricted.
As such, these pages can’t be indexed. But, The SEO Framework isn’t aware of this.
So, you should enable the “noindex” option for the restricted pages in the SEO meta box found underneath the content editor. This option will remove the pages from the sitemap, too.
After that’s resolved, it might take a few days (or weeks) before Google notices this. The errors on Google Search Console should fade over time.
I hope this helps! Good luck!
Thread Starter
gfuzz
(@gfuzz)
Sybre,
Thank you for the detailed response and great support. I appreciate it, and it is well explained to me.
Yes, for some reason, in googles NEW search console the attempt at sitemap submission shows an error ‘no index unable to fetch’ . However, in the CLASSIC (old) search console the submission has seemed to work.
It says the sitemap is pending in CLASSIC search console, so I am just waiting for confirmation.
Really a fantastic product. Thank you again.
