MBayDesign

Can I contact you via support email – would be easier to supply screenshots? However just fyi, the google search console errors are not particularly helpful.

I’ve filled out all location fields in venues and in events. The one event that is suddenly listed as “other” is by definition, as good as passed, however it shows no longer accessible (which is untrue) or the “item being validated is no longer present on the page.) The date of the event was yesterday which is one possibility for that. I had also **disabled showing upcoming events** which has all info ***except the event’s location.*** This is the event: https://www.carmelresidents.org/cra-event/carmel-by-the-sea-looking-forward-25-years/
The item that failed outright is the url I included in the original post which is a venue. The pending item is also a venue: https://www.carmelresidents.org/venue/the-carmel-womans-club/

Even though I disabled upcoming events in Settings (Show related events in the event page) – it is still showing on the above url, the venue, and as noted, no location is in the upcoming event code…

Agreed with bytepaul. I changed as well… The adjustment I made to the plugin file (changing noindex from true to false) did not produce a change, nor did unchecking the html ver.

Just for the record, I don’t know how accurate it is that simply adjusting that parameter to false will do the trick. I did tweak it on one of my sites and updated the file, but I’m not seeing a change in the currently generated sitemap.

Also, tweaked html off, because it really doesn’t need to be in that format anyway. In my opinion, if it’s for public consumption (and that, I think is the only reason to allow an html ver), better to design your own sitemap. No clue if that has any bearing.

Ultimately, better that the plugin author weighs in on this. ??

OK, I found the command creating the nofollow in the header – and the explanation for why it’s being tagged that way. FYI, it’s in the sitemap-core.php file starting on line 1574. Basically says: “Do not index the actual XML pages, only process them. This avoids that the XML sitemaps show up in the search results.”

This can be adjusted (you’d edit the file at your own risk – be sure to take a backup and know how to restore it), so it’s up to the individual if you want to tweak the file, I suppose. According to something I read, “Yes, Google may index your XML sitemap file and rank it in the search results … That being said, hundreds of Sitemap files are indexed and in the search results. They typically only come up for very specific searches, that likely won’t impact the normal searcher.”

That sounds fairly valid to me. I will likely tweak that setting to false to make google happy. ??

Received the same thing – email from google on 12/5. Looked at the source code for both the xml and the generated html of the sitemap and both files have a meta tag with noindex,follow:

<meta name=”robots” content=”noindex,follow”>

I’ve never looked at that source code before, so I don’t know if this has always been like this and google is only just now checking it, or if it’s in response to some conflict.

The Google XML Sitemaps plugin author needs to look into this. ??

Thank you – I had assumed it might have been the difference between a personal “page” (profile) vs “business” page, but I didn’t realize there was a restriction in the plugin until now. Thanks!

That worked like a charm, mglgis! Thanks for that! I had also submitted this issue to iThemes support in case they could help – he submitted a compatibility report and has also, hopefully, contacted the plugin author.

Thanks again!

Wow – I didn’t even go there – even though all affected sites are under development. It didn’t occur to me I suppose because the db backup was running fine … Thank you for pointing me in that direction!

Thanks very much for that info Mike. I wish it said that somewhere in the documentation – or if it already does, I guess I missed it.

Thanks again!

I saved multiple times as I was trying to get it to work.

Oh! I just looked and all my settings are gone. Oh, great. Well, they had been there all this time. Maybe that was a result of deactivating it at one point.

OK, they’re set again (I will have to tweak when I see it because I don’t remember some of them) and I’ve also exported the settings. Additionally, I looked at the preview page and found all the css at this link. https://blog.montereybaydesign.com/?A5_file=login_css&ver=1.0beta

I see there’s an update which I just did – and tried – then saved using inline and – Yay! It works! ?? Reactivated plugins – and all good.

Thank you for the update and for being on top of this one!

Debbie

Yes, off again. Thanks!

Thanks for looking! Here’s the login:

https://blog.montereybaydesign.com/wp-login.php

Incidentally, I deactivated ithemes security before checking the inline box. Thought might be interfering, but that doesn’t seem to be the case. Also, doesn’t fix it to change to default theme.

Thanks again