Might be issue with a shared IP resolving to another site on your server due to a DNS issue of some kind, however Yoast sitemap should only be pulling the canonical links from your actual slugs.
Resaving your permalinks after major updates is highly recommended.
Also explicitly putting your exact site name/URL into your wp-config file can also help quite a bit, I’ve found.
Hi Chris / neotrope
Thanks for your comments. The site is actually NOT on a shared IP.
The wp-config file I did check out. It actually has the code
define(‘WP_SITEURL’, SP_REQUEST_URL);
define(‘WP_HOME’, SP_REQUEST_URL);
and is being reported correctly on the WP setting (although greyed out).
Currently I have Sitemap disabled in Yoast SEO and a separate Sitemap plugin being used which works perfectly… Does make one concerned about the Yoast plugin.
Well, I was referring to the define wp_home explicitly which helps with http to https switchovers:
https://codex.wordpress.org/Editing_wp-config.php#Blog_address_.28URL.29
But if the sitemaps work on 200,000 sites but not yours, chances are there is a conflict with something … so, you’ll have to investigate further if you think there is a hack, some problem with the pages with wrong info, etc.
I was seeing that other people had other problems with sitemaps in Yoast SEO… but not this sort of error. So I guess I agree with you it could to be a conflict with very strange results.
Could, but unlikely, be something with the Newsmag theme which I now see has yet to be tested with PHP 7.
Thanks for your thoughts.
PHP7 could be the culprit … as I don’t think all the code in WordPress is quite yet fully compliant with PHP7, nor are *most* plugins.
We’re moving to PHP7 in couple of months with new web server to support http/2 vs doing OS reload on our 2013 server (blah blah…)….
You *could* try switching back to php 5.5x or whatever from your hosting panel, which should have that option to see what happens.
(( I don;t work here … just helpful soul, mining for karma points …. ))
I have re-checked the PHP 7 situation. WordPress itself was declared fully compatible with PHP 7 at it’s official release in Nov 2015.
With a code check only the theme appears only to have two minor errors and one plugin, WP Super Cache, three errors. Both seem, on a run time and community view, in practice work ok.
Checking for conflicts between plugins is the next on the list. However a random error is going to be difficult to check for…
Good luck to Chris / neotrope on your move to PHP 7. As you say this will also enable support for http/2 which has additional speed advantages.
Needs a more robust response to this problem. I’ve noticed a LOT of other have the same sort of sitemap problem. Me included. Just started happening. Seems the site map might not even being created. Can’t even find it in the WP folder.
http://screencast.com/t/Yi1Eb4dpv
You guys just ignoring the sitemap problem? I see about 10+ complaints, but no support or fix over several months. What’s up?
We’ve been having a ton of issues with the Yoast plugin for the last few days and the sitemap issue is one of them.
We’re also getting an error message that says “Huge SEO Issue: You’re blocking access to robots. You must go to your Reading Settings and uncheck the box for Search Engine Visibility.” But, when we go to “uncheck” this box, it’s already unchecked. Yet, the warning is still there… Any thoughts?
Not sure if this helps anyone, but what I do to ensure my version of Yoast is updated properly
a) upload via FTP; delete old folder, upload new one (not ‘overwrite’)
b) resave permalinks
c) clear transients with wp-optimize
d) resave pemalinks again
e) go to the yoast > title/meta, resave options
If having any other issue;
a) disable plugin from the ‘plugins’ panel
b) re-enable plugin from the plugins panel
c) resave permalinks
All of these seem to keep it working across our network, for both the regular and pro versions.
Not sure if it will help any of you, but might be worth a try 🙂
