SitemapXML v.2

[mc12345678]

v1.5.5f PHP7.1 using plugin version 3.9.2

I am using Ultimate SEO URL's (USU) however sitemap(s) are being submitted as standard ZC urls (cPath?) - the issue is that sitemap submissions are NOT BEING INDEXED ... (5 sites)

I still have one site as v1.5.1 using a previous version of this plugin and the sitemaps are submitted using USU and submitted pages are being indexed.

Configuration settings for the old v1.5.1 and the newer 1.5.5f sites are the same in both admin/configuration/sitemapxml and /usu (I cannot see anything different) so I am stumped as to why the USU urls are not being submitted.

.... and yes I have seen a decline in SERP's rankings since the sites were upgraded to v1.5.5f with this sitemap problem. Yes Google is still finding pages and indexing them BUT not all of them and not as regularly as the CRON requests because the sitemap generated is using ZC standard urls - Google's response to all of the submitted url's is 'URL is not on Google - This page is not in the index, but not because of an error'. (see image)

IMAGES ARE NOT BEING INDEXED because the image submitted is for a product page that Google does not recognize!

I look forward to some assistance with this please. (it is more than likely I have done something wrong or not done something correctly).

many thanks,
Mike

Attachment 18134

Hello mc - any chance of a response to post #1906 immediately before torvista's post - appears to have been missed?

cheers,
Mike

So, I didn't "miss" it, but haven't dived into the inner workings of USU in a while. I do know that one change between earlier versions of ZC and ZC 1.5.5 was to add in a notifier in the html_output functions file that as described was pretty much specifically added to support USU (though another URI rewriter has been able to successfully access and use it as well). At any rate, it would seem that in the "load" process of generating the new URIs for the images (and perhaps product as well) that the zen_href_link response is not accounting for the rewrites. I would guess that it is related to that function. Could be a load sequence issue of the observer for the notifier, though Torvista has pointed out that SitemapXML uses a sequence number of 999 which is pretty high.