• Hi there

    with the latest update, all sitemaps (posts, page…) are posted with 1 or 2 at the end in the index sitemaps – like sitemaps/post-sitemap1.xml or sitemaps/page-sitemap1.xml – but these pages do not exist. The ‘normal’ ones (aka sitemaps/post-sitemap.xml or sitemaps/page-sitemap.xml) are the ones which should be used and still properly generated
    this causes lot of trouble for search engines which can not fine the xxx1 sitemaps

Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Author Benjamin Denis

    (@rainbowgeek)

    Hi,
    try to flush your permalinks please.

    I have exactly the same error on 6 different sites where I have SEOPress installed. This appeared with the latest update. Flushing permalinks does not solve the problem. Please advise…

    • This reply was modified 5 years, 7 months ago by bibiweb.
    Plugin Author Benjamin Denis

    (@rainbowgeek)

    Can you share some URLs to test?

    Le problème semble corrigé depuis hier. Les sitemaps ont toujours un “1” ajouté à la fin, mais au moins il n’y a pas d’erreur 404 comme c’était le cas hier matin. Quelques exemples :
    https://www.aaz-ch.org/sitemaps.xml/
    https://www.aubergedesaviese.com/sitemaps.xml/
    https://www.bibibalades.ch/sitemaps.xml/

    Hier ils étaient tous en erreur dans Google Search Console et dans Bing Webmaster Tools… maintenant je vais pouvoir les renvoyer. ??

    Le problème subsiste sur un de mes sites
    https://www.samatc.ch/sitemaps.xml

    I have the same issue. Flushing permalinks doesn’t resolve the issue. What else can I try and any idea why this is happening?

    Just to clarify, even after flushing permalinks, if I use View Your Sitemap the post-sitemap1.xml and page-sitemap1.xml files are still reported.

    Yes @markwill, the “1” suffix is still there, but at least in most cases the link is functional. The only exception (regarding the sites I support) is the samatc.ch site I reported above where I still get a 404 Error when I try to follow those links,

    Same problem here. Pretty frustrating.

    https://www.triggerpressers.com/sitemaps.xml

    Any news?

    I see this wasn’t fixed with the update that was released today.

    WHY CAN’T THIS BE SOLVED?????
    You’ve updated several times since this bug appeared!

    Same problem here on two of my sites. Contacted the support because of the bought pro version and did not get any answer in the last two weeks. I am really upset and think it is best to switch to another tool.

    So I have a comment and a question about this.

    My comment is that, as far as I can tell, this has no direct impact on SEO. While it’s disconcerting to see Google report broken sitemaps (can’t find the versions without the numeric postfix), if one clicks on sitemap.xml then Google reports all those with the postfix.

    For my own site, at least, it seems that Google is perfectly aware of the ones with the postfix, is pulling them in just fine and they are right up to date. I have not yet seen any noticeable impact on SEO. So, unless someone can tell me to the contrary, I don’t THINK this is quite the SEO-wrecker that someone of us have assumed.

    If I am correct on that, then my bigger concern is in the form of a question. Is the lack of response (both here and through support channels it seems) indicative of what we can expect in the future?

    For something so crucial to how Google interprets our sites and has the potential to do real damage (I’m looking at you Yoast!), I want a stable, well-supported plugin and – so far – SEOPress looked like a good move to me. But the absence of any response, recently, here and elsewhere is very concerning to me for the future. Clearly it’s causing a lot of concern for folks here – whether with good reason or not – so seeing these concerns being ignored is worrying.

    • This reply was modified 5 years, 6 months ago by markwill.
    • This reply was modified 5 years, 6 months ago by markwill.
    Plugin Author Benjamin Denis

    (@rainbowgeek)

    Hi all!

    In order to support paginated sitemaps, a number is added at the end of each sitemap.
    This is normal.
    It does not impact your SEO.
    Reminder: Google doesn’t care about the url of the index sitemap, and URLs inside.

    For those who get a 404 error, please update your permalinks.

    For those who are on NGINX, update your NGINX configuration file as mentioned in the SEO > XML sitemaps page. The rules of rewriting are indicated there.

    For those who get errors in Search Console: just submit your index sitemaps not each urls. Eg: https://example.com/sitemaps.xml. Resubmit the sitemap if you want to speed up the Google bot.

    Finally, if you still have problems, open a topic on the forum or a ticket if you are PRO.

    Thank you!

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Since the last update, sitemaps are posted with 1 and 2 in the index sitemaps’ is closed to new replies.