Comment corriger l’erreur 404 du plan de site WordPress SEO de Yoast ?

243 commentairesLaisser une réponse

1. Syed Balkhi says

   Mai 8, 2024 à 2:24 pm

   Hey WPBeginner readers,
   Did you know you can win exciting prizes by commenting on WPBeginner?
   Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
   You can get more details about the contest from here.
   Start sharing your thoughts below to stand a chance to win!

2. CB says

   Sep 2, 2014 à 3:00 pm

   Hi, just tried the second version editing the plug ins core files and the site has disapeared?? including the backend. just a white screen?? I replaced the code withy the original and nothing.

   Répondre

3. Matt Crystal says

   Sep 1, 2014 à 10:38 am

   Thank you! That worked by supplying the code in the .htaccess file, then unchecking the site map option and saving. Then, re-checking the box and saving again. Thanks!

   Répondre

4. Roderick van Straten says

   Août 27, 2014 à 7:36 am

   Added this code to the .htaccess and unchecked and checked it, but I only get a blank page now for the sitemap ..

   Répondre

5. mandingo345 says

   Août 8, 2014 à 11:33 am

   yes, without fix, just uncheck save recheck and saved.

   Répondre

6. Tidus Ha says

   Juil 24, 2014 à 11:28 pm

   the last update work perfect for me. thank you.

   Répondre

7. Jack says

   Juil 21, 2014 à 11:50 am

   After loosing quite some time trying to find what was wrong, I got it working by your suggestion « Uncheck the sitemap option in the Yoast’s SEO plugin and ‘save’ settings. After that re-checking the sitemap’s option fixes the error. »
   tnx very much!

   Répondre

8. johnny says

   Juil 15, 2014 à 7:10 pm

   Thank you so much! unchecking, saving, rechecking saving did the trick!

   Répondre

9. sc456a says

   Juil 14, 2014 à 6:05 pm

   After I added the code to htaccess and unchecked/rechecked Sitemap in the plugin, it worked! Thanks!

   Répondre

10. Taylor says

    Juil 12, 2014 à 1:41 am

    Worked!! Thank you!

    Répondre

11. alireza says

    Juil 11, 2014 à 6:13 pm

    it work for me too, Thanks a lot!

    Répondre

12. Leo says

    Juil 10, 2014 à 11:33 pm

    Uncheck then save, then go back check again and save, solved my problem. It should be at the begining before anybody try anything else! it worked for me thanks though

    Répondre

13. Elle Laurel Rose says

    Juin 20, 2014 à 8:19 pm

    Woohoo! Thanks. Mine probably wasn’t broken long because Google didn’t seem to mind yet. … But my site is only in a softer launch stage anyway… Slow crawls maybe. Luckily, I’m improving my site before my real projects go up (hopefully soon).

    Anyway I cannot thank you enough.

    Répondre

14. logitaki says

    Juin 13, 2014 à 11:40 pm

    I opened the class-sitemaps.php file but can’t find the section you are referring to « functiion () init code.. can you be more specific?

    Répondre

15. Basie says

    Juin 10, 2014 à 1:06 pm

    Editing the .htaccess file, un-checking sitemap generation, saving settings, re-checking, saving settings … fixed it for me! Thank you VERY much.

    Répondre

16. Tom Atkinson says

    Juin 6, 2014 à 12:31 am

    I found my issue was actually fixed purely by turning Yoasts sitemaps on and off from UI. Which is great!

    Répondre

17. Fernando says

    Juin 2, 2014 à 4:56 pm

    Were you able to fix this one? I’m having the same problem, I get a 404 on post-sitemap.xml. I didn’t check the PHP logs on what the error is but probably would be the same you’re getting.

    Répondre

    • Steve says

      Juin 6, 2014 à 2:26 pm

      No fix, and theres no replies to support threads on wordpress, other people are just disabling it and using another sitemap plugin.

      Répondre

18. Baidya nath Singh says

    Juin 2, 2014 à 9:08 am

    It worked with the first code to .htaccess. Thanks.

    Répondre

19. hayderabbass says

    Juin 1, 2014 à 3:33 pm

    Disabling the XML sitemap and re enabling them fix this issue for me. Thanks!

    Répondre

20. Ben Billson says

    Juin 1, 2014 à 8:48 am

    I was having an issue with the sitemap 404’ing when trying to access it.

    I tried adding the first ifmodule, no joy, then remembered I had another ifmodule in place to handle redirects after updating my permalink structure.

    I removed the redirect ifmodule, restarted Worpress SEO, then the sitemaps started working. Re-added the redirect ifmodule, and everything now appears to be working just fine. I’ve also checked the status in GWT and Bing WT and it’s all looking good. Thanks for the help!

    Répondre

21. Rob Cooper says

    Mai 29, 2014 à 12:51 am

    I put the first Ifmodule into htaccess and it spit out some weird single line of content, with no links.

    I read through the comments

    then I rebooted Yoast’s sitemap option:

    i unchecked the « Enable XML Sitemap Here » and saved

    I re-checked it and saved

    checked my sitemap and it was there, formatted properly with xsl stylesheet being applied and links all worked

    Répondre

22. chiappa says

    Mai 27, 2014 à 9:44 pm

    I have no idea where to put that code. There is no line like: « function init() » in class-sitemaps.php

    Répondre

23. Katrina Isabelle says

    Mai 27, 2014 à 2:54 pm

    Try going into your permalink settings and saving them again. If you can’t access the back end of your site because of the 500 error, then remove that htaccess file.

    Répondre

24. Katrina Isabelle says

    Mai 27, 2014 à 2:53 pm

    Hello! I think you should add one more step at the very beginning: Re-save your permalink settings! I found that re-saving my permalink settings solved the issue for me. No need to go into the htaccess file.

    Répondre

    • EB says

      Juil 2, 2014 à 4:25 pm

      Exactly, solved my problem too.

      Répondre

    • Alfonso says

      Oct 9, 2014 à 2:18 pm

      this fixed the issue for me, re-saving the WP permalinks

      Répondre

25. Steve says

    Mai 23, 2014 à 12:41 pm

    I get the following error only on post-sitemap, all other sitemaps work ok:
    Fatal error: Allowed memory size../plugins/wordpress-seo/inc/class-sitemaps.php on line 713
    I tried the htaccess and wpseo-functions edits but no luck.
    I deactivated every plugin, still no luck.
    I deleted wpseo and reinstalled but still same problem and now on the wpseo dashboard and sitemaps page I get this error:
    Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘wpseo_xml_sitemaps_init’ not found or invalid function name in /home/justplay/public_html/wp/wp-includes/plugin.php on line 470

    I have two sites running the same theme, plugins etc and one works ok one has this errors, wierd.

    Répondre

26. Jane Hockley says

    Mai 9, 2014 à 1:34 am

    Thank you – i found just by unchecking and saving and then re-checking the site map option for the yoast plugin google webmaster was able to find my site map

    Répondre

    • eliascan says

      Juin 11, 2014 à 7:51 am

      Worked for me too. Thanks

      Répondre

    • Jared Eitnier says

      Juin 18, 2014 à 3:49 pm

      Worked for me as well, good call.

      Répondre

    • Michael Erickson says

      Juil 3, 2014 à 8:53 pm

      Thanks Jane!

      Répondre

    • Taylor says

      Juil 12, 2014 à 1:32 am

      Thank you!! Worked like a charm

      Répondre

    • Jesse says

      Juil 26, 2014 à 9:14 pm

      This worked for me too. Thanks!

      Répondre

    • Brent Norris says

      Août 15, 2014 à 7:13 pm

      yep got rid of the 3 errors displayed in webmaster tools. thanks

      Répondre

    • Saw Panse says

      Oct 4, 2014 à 6:23 pm

      Worked like a charm. Thanks @janehockley:disqus

      Répondre

27. Abhishek Mishra says

    Mai 5, 2014 à 12:19 am

    Guys really you are amazing, yeah AMAZING.. this blog is really helpful for me

    Répondre

28. Jake Ratliff says

    Mai 3, 2014 à 5:10 pm

    When I tried the htaccess method, it crashed my site. I just added this code into the htaccess file (via the Yoast plugin):

    # WordPress SEO – XML Sitemap Rewrite Fix

    RewriteEngine On
    RewriteBase /
    RewriteRule ^sitemap_index.xml$ /index.php?sitemap=1 [L]
    RewriteRule ^([^/]+?)-sitemap([0-9]+)?.xml$ /index.php?sitemap=$1&sitemap_n=$2 [L]

    # END WordPress SEO – XML Sitemap Rewrite Fix

    And then clicked the « save changes to .htaccess » button. I can’t go anywhere without the 500 error now. What did I do wrong? Anyone know how to fix this?

    Répondre

29. Jake Ratliff says

    Mai 3, 2014 à 4:52 pm

    I tried the htaccess fix and now I get a 500 Internal Server Error.

    Répondre

30. Mark Haller says

    Mai 1, 2014 à 4:13 am

    @NicolasJoly:disqus you star, well done, thanks so much!

    Répondre

31. Tiffany Marie McAnally says

    Avr 29, 2014 à 8:39 pm

    So it still doesn’t work for me… I feel like beating my head against a wall. As much as I love the plugin, I think I’m just going to lose it in favor of something that’s actually functional.

    Répondre

32. Jérôme Lafforgue says

    Avr 24, 2014 à 4:29 pm

    Thanks, work fine in wpseo-functions.php file @ line 461

    Répondre

33. ast says

    Avr 23, 2014 à 12:21 pm

    for me worked fine!
    thank you

    Répondre

34. NicolasJoly says

    Avr 23, 2014 à 9:24 am

    @Matt Klein, it’s in the wpseo-functions.php file @ line 461

    Répondre

35. NicolasJoly says

    Avr 23, 2014 à 9:01 am

    @Matt Klein, the ‘init’ function is now ‘wpseo_xml_sitemaps_init’ in the wpseo-functions.php, @line 461

    Add just :
    global $wp_rewrite; before the $GLOBALS define
    and
    $wp_rewrite->flush_rules(); after the add_rewrite_rule…

    /**

    * Initialize sitemaps. Add sitemap & XSL rewrite rules and query vars

    */

    function wpseo_xml_sitemaps_init() {

    $options = get_option( ‘wpseo_xml’ );

    if ( $options[‘enablexmlsitemap’] !== true ) {

    return;

    }

    // redirects sitemap.xml to sitemap_index.xml

    add_action( ‘template_redirect’, ‘wpseo_xml_redirect_sitemap’, 0 );

    if ( ! is_object( $GLOBALS[‘wp’] ) ) {

    return;

    }

    global $wp_rewrite;

    $GLOBALS[‘wp’]->add_query_var( ‘sitemap’ );

    $GLOBALS[‘wp’]->add_query_var( ‘sitemap_n’ );

    $GLOBALS[‘wp’]->add_query_var( ‘xsl’ );

    add_rewrite_rule( ‘sitemap_index.xml$’, ‘index.php?sitemap=1’, ‘top’ );

    add_rewrite_rule( ‘([^/]+?)-sitemap([0-9]+)?.xml$’, ‘index.php?sitemap=$matches[1]&sitemap_n=$matches[2]’, ‘top’ );

    add_rewrite_rule( ‘([a-z]+)?-?sitemap.xsl$’, ‘index.php?xsl=$matches[1]’, ‘top’ );

    $wp_rewrite->flush_rules();

    }

    Répondre

36. Matt Klein says

    Avr 18, 2014 à 3:19 am

    There is no function init area in my class-sitemaps.php file. Could it be called something else. What line is it on?

    Répondre

37. Regina Falkowski says

    Avr 17, 2014 à 1:13 pm

    Added the code to .htaccess file and it worked like a charm! Thanks for the fix

    Répondre

38. Alec Byrne says

    Avr 17, 2014 à 4:42 am

    Adding the .htaccess worked for me – thanks very much

    Répondre

39. Desainwebs says

    Avr 14, 2014 à 10:22 pm

    Still not work for me

    Répondre

40. Ollie says

    Avr 11, 2014 à 12:46 pm

    Htaccess fix worked for me.

    But as Scott in the first comment above says, I needed to uncheck the XML sitemap checkbox and save. Then recheck it and save again for the sitemap to show up. I think that would be worth mentioning in the article.

    Répondre

    • WPBeginner Support says

      Avr 13, 2014 à 12:44 pm

      Ollie, yes we have updated the article.

      Répondre

      Administrateur

41. Steve Patterson says

    Avr 11, 2014 à 11:21 am

    Thanks this worked for me editing the .htaccess file. I unchecked sitemaps off then back on and also changed mine from 1,000 to 400. If you are on a shared server, I would use a lower number so that less CPU usage is done on your domain.

    Répondre

42. scott says

    Avr 6, 2014 à 11:23 am

    Hi guys,

    I had to troubleshoot this issue too. My site is hosted in a sub directory of a main site. So I had to set the following line:

    RewriteBase /scottmortiz/

    I then had to uncheck the mina Site Map XML option in the plugin, and save. Then re-check the plugin and save. Hope this works for some of you.

    -Scott

    Répondre

43. Chris says

    Avr 6, 2014 à 8:09 am

    Hi Steven,
    thank alot. This helped me, too. But to get the rewrite working I had to disable the xml function, save it, and enable (and save it) again. Seems obvious, but maybe this is worth a note in the article. I will safe this article in my personal wordpress help register.
    Thanks,
    Chris

    Répondre

    • Dan says

      Avr 10, 2014 à 2:07 pm

      Thank you Chris! This fixed my 404 problem with Yoast’s XML Sitemap feature.

      Répondre

    • Jason Judge says

      Avr 12, 2014 à 11:55 am

      Ah, switch it off, then switch it back on again. Thanks:-) It is not as obvious as you think. My sitemaps also did not work (getting a 404) until I did this. I did not have to make any of the other changes described in this post.

      Répondre

44. Shanthi Ganesan says

    Avr 6, 2014 à 2:42 am

    @PEKKO Hi Tried your techniques it really works well,thanks a lot for sharing….

    Répondre

45. Lukas says

    Mar 19, 2014 à 4:05 am

    Nothing is working in my case – still Error 404 …

    Répondre

46. Ryan says

    Mar 17, 2014 à 11:51 pm

    Beauty, fixed it for me too.. thanks for putting this up

    Répondre

47. lloyd says

    Mar 4, 2014 à 6:35 pm

    this just broke my websites … now getting an internal server error…

    Répondre

48. Rosie says

    Fév 28, 2014 à 7:47 pm

    The edit to .htaccess files was just the trick. Thanks for posting this! You saved me a whole lot of time and trouble.

    Répondre

49. Pekko says

    Fév 27, 2014 à 3:42 pm

    I was just facing the same issue. i unticked the box (Check this box to enable XML sitemap functionality) — pressed save, and then ticked the box again, after that It found the sitemap again, Hope it will be there!

    Répondre

    • Anisa says

      Mar 4, 2014 à 7:45 pm

      I use this technique, and it worked

      Répondre

    • John says

      Mar 13, 2014 à 2:18 pm

      This worked for me, as well. Thx!

      Répondre

    • Cara Sherlock says

      Mar 15, 2014 à 3:55 pm

      Unchecking, saving and then rechecking worked for me too. Thx!

      Répondre

    • Badprimer says

      Mar 19, 2014 à 4:14 am

      [..unticked the box (Check this box to enable XML sitemap functionality) — pressed save, and then ticked the box again..]

      Worked for me. Thx!!

      Répondre

    • Kerry says

      Avr 5, 2014 à 8:24 am

      Thank you! Worked for me too! So simple. The author of this article should add this too.

      Répondre

    • bruce says

      Avr 7, 2014 à 11:44 am

      This also worked for me. turn off sitemaps. save. turn them back on. save. fixed

      Répondre

    • David says

      Avr 8, 2014 à 11:21 am

      Same for me, unchecked, saved, checked, saved, voila!

      Répondre

    • hobbsy says

      Mai 3, 2014 à 8:59 am

      this worked for me too

      Répondre

50. Hugo says

    Fév 22, 2014 à 10:10 am

    Hi,

    I’m still having some troubles with my website:
    My site map contains a lot of files like this one:
    http://www.blenheimgang.com/wp-content/uploads/media/2013/09/BCRR-E30-25.jpg
    and they refer to a broken link. How can I delete them?

    Répondre

    • WPBeginner Support says

      Fév 25, 2014 à 4:44 pm

      Doesn’t look like a broken link.

      Répondre

      Administrateur

51. Steven says

    Fév 21, 2014 à 9:18 am

    I’ll just share what worked for me, by changing the ‘max entries per site map’ to 250 (ie. something less than 1000) I managed to fix the 404 error. I think the server was having issues processing 1000 entries which is the default.

    Répondre

    • Maggie says

      Fév 27, 2014 à 4:22 am

      Hi Steven, this is great solution! I just fixed the problem by your method. Thank you very much!

      Répondre

    • PromInc says

      Mar 11, 2014 à 10:52 am

      Thanks Steven – this resolved my issue as well. The ‘max entries…’ field was blank for me; simply adding any value seemed to work, which is good as I felt 250 was a bit low. Very simple but effective solution.

      Répondre

    • Nick Root says

      Mar 28, 2014 à 10:58 pm

      That worked thanks for the tip!

      Répondre