Você está tentando corrigir o erro 404 do mapa do site do Yoast SEO no WordPress?
O Yoast SEO é um dos plug-ins de SEO mais populares para WordPress. Devido a um conflito de plug-ins ou a configurações incorretas do WordPress, ele pode mostrar um erro 404 quando você tenta visitar seu sitemap XML.
Neste artigo, mostraremos a você como corrigir facilmente o erro 404 do sitemap XML do Yoast SEO no WordPress.
O que está causando o erro 404 do Sitemap do Yoast SEO no WordPress?
O mapa do site do Yoast SEO ajuda os mecanismos de pesquisa a encontrar todo o conteúdo do seu site que você deseja que eles encontrem e indexem.
A correção do erro garante que os mecanismos de pesquisa possam acessar o mapa do site e descobrir todas as páginas e o conteúdo do site, o que pode resultar em melhor visibilidade e classificação nos mecanismos de pesquisa. Isso também ajudará a classificar seu conteúdo mais rapidamente do que sem um mapa do site.
O WordPress vem com um sitemap XML padrão que você pode enviar ao Google Search Console e a outros mecanismos de pesquisa.
Esse mapa do site em XML pode ser acessado digitando o seguinte URL na barra de endereços do navegador.
https://example.com/sitemap.xml
No entanto, esse mapa do site padrão gerado pelo WordPress é muito básico. Para corrigir isso, todos os principais plug-ins de SEO do WordPress, como o All in One SEO for WordPress ou o plug-in Yoast SEO, criam seus próprios sitemaps XML com mais recursos.
Quando você usa o mapa do site XML gerado pelo seu plug-in de SEO do WordPress, esses plug-ins reescrevem o atalho padrão do mapa do site XML do WordPress.
Isso significa que o URL do mapa do site mencionado acima agora enviará os usuários para os mapas do site gerados pelo seu plug-in de SEO do WordPress.
Infelizmente, isso pode causar um erro 404 em alguns sites devido a conflitos de plugins ou configurações incorretas do WordPress.
Dito isso, vamos dar uma olhada em como corrigir facilmente o erro 404 do mapa do site do WordPress no plug-in Yoast SEO.
1. Atualizar a estrutura de links permanentes do WordPress
O WordPress vem com uma estrutura de URL amigável para SEO (também chamada de permalinks). Essa estrutura de URL usa um sistema de redirecionamento para informar ao seu servidor de hospedagem na Web qual página deve ser carregada quando um usuário digita um URL no navegador.
Normalmente, essas configurações de permalinks são atualizadas automaticamente quando você faz alterações em seu site.
No entanto, às vezes o WordPress pode não conseguir atualizar a estrutura de permalink, o que pode causar o aparecimento do erro 404 do mapa do site do Yoast SEO.
Isso pode ser facilmente corrigido visitando a página Configurações ” Permalinks na área de administração do WordPress e simplesmente clicando no botão “Salvar alterações”.
Isso atualizará as configurações de permalink do WordPress. Agora você pode visitar a página do sitemap XML para ver se isso resolveu o problema.
Se isso não resolveu o problema, você pode continuar lendo.
2. Atualização manual de Permalinks
Se a atualização da estrutura de links permanentes do WordPress não corrigir o erro 404, você poderá informar manualmente ao servidor da Web para redirecionar os usuários para a página de mapa do site do Yoast SEO.
Para fazer isso, você precisará adicionar o seguinte código ao seu arquivo .htaccess.
# Yoast SEO - XML Sitemap Rewrite Fix
RewriteEngine On
RewriteBase /
RewriteRule ^sitemap_index.xml$ /index.php?sitemap=1 [L]
RewriteRule ^locations.kml$ /index.php?sitemap=wpseo_local_kml [L]
RewriteRule ^geo_sitemap.xml$ /index.php?sitemap=geo [L]
RewriteRule ^([^/]+?)-sitemap([0-9]+)?.xml$ /index.php?sitemap=$1&sitemap_n=$2 [L]
RewriteRule ^([a-z]+)?-?sitemap.xsl$ /index.php?yoast-sitemap-xsl=$1 [L]
# END Yoast SEO - XML Sitemap Rewrite Fix
Observação: Se o seu site WordPress estiver instalado em um subdiretório ou pasta (por exemplo, https://example.com/mywebsite/ ), será necessário usar o seguinte código.
# Yoast SEO - XML Sitemap Rewrite Fix
RewriteEngine On
RewriteBase /mywebsite/
RewriteRule ^sitemap_index.xml$ /index.php?sitemap=1 [L]
RewriteRule ^locations.kml$ /index.php?sitemap=wpseo_local_kml [L]
RewriteRule ^geo_sitemap.xml$ /index.php?sitemap=geo [L]
RewriteRule ^([^/]+?)-sitemap([0-9]+)?.xml$ /index.php?sitemap=$1&sitemap_n=$2 [L]
RewriteRule ^([a-z]+)?-?sitemap.xsl$ /index.php?yoast-sitemap-xsl=$1 [L]
# END Yoast SEO - XML Sitemap Rewrite Fix
Não se esqueça de substituir /mywebsite/ pelo nome de seu subdiretório.
Esse código simplesmente informa ao seu servidor da Web quais páginas devem ser exibidas quando os usuários acessarem os sitemaps XML do Yoast SEO.
Agora você pode tentar visualizar o mapa do site XML para ver se isso resolve o problema.
3. Mudar para um plug-in de Sitemaps XML
Se os métodos mencionados acima não resolveram o erro 404 na página do mapa do site XML do Yoast SEO, você pode tentar usar um plug-in separado para gerar mapas do site XML para seu site.
A desvantagem dessa abordagem é que você terá que contar com um plug-in separado para gerar sitemaps XML e com o Yoast SEO para outros recursos de SEO.
Primeiro, você precisa instalar e ativar o plug-in XML Sitemaps. Para obter mais detalhes, consulte nosso guia passo a passo sobre como instalar um plug-in do WordPress.
Como você está usando o Yoast SEO, ele mostrará automaticamente uma notificação para desativar o plug-in XML Sitemaps ou a funcionalidade de mapa do site do Yoast SEO.
Clique no botão Toggle Yoast SEO’s XML Sitemap para continuar.
Isso o levará à guia Features (Recursos ) na página SEO ” General (Geral ). A partir daí, você precisa rolar para baixo até a opção XML Sitemaps e desativá-la.
Não se esqueça de clicar no botão “Save Changes” (Salvar alterações) para armazenar suas configurações.
Agora você pode alternar para a página Settings ” XML-Sitemap para configurar seus sitemaps. Para a maioria dos sites, as configurações padrão funcionariam imediatamente.
Mas você sempre pode definir as configurações de acordo com suas necessidades.
Agora você pode enviar o URL do mapa do site XML para o console de pesquisa do Google e outros mecanismos de pesquisa.
4. Mudar para o All in One SEO for WordPress
Se todas as etapas de solução de problemas falharem e você não quiser usar um plug-in separado para gerar sitemaps XML, esse método poderá ajudá-lo a corrigir o problema de erro 404 do sitemap.
Para esse método, você precisará do All in One SEO para WordPress. Ele é o melhor plugin de SEO para WordPress do mercado e uma alternativa muito melhor ao Yoast SEO.
Você pode ver nossa comparação entre Yoast e All in One SEO para obter mais detalhes sobre as diferenças.
O All in One SEO (AIOSEO) vem com sitemaps XML avançados com opções fáceis de gerenciar que lhe dão controle total sobre o que incluir ou excluir dos sitemaps XML.
Primeiro, você precisa instalar e ativar o plug-in All in One SEO para WordPress. Para obter mais detalhes, consulte nosso guia passo a passo sobre como instalar um plug-in do WordPress.
Observação: Há também uma versão gratuita do All in One SEO para WordPress, que inclui a maioria dos recursos de sitemap XML, exceto sitemaps de vídeo e notícias.
Após a ativação, o plug-in o guiará por um assistente de configuração. Você pode seguir nosso guia sobre como configurar corretamente o plugin All in One SEO para WordPress se precisar de ajuda durante a configuração.
O All in One SEO também permitirá que você importe dados de SEO do Yoast SEO.
Isso garante que todas as suas meta tags e títulos de SEO anteriores permaneçam inalterados.
Após a configuração inicial, você pode ir para a página All in One SEO ” Sitemaps para definir as configurações do sitemap XML.
Você pode clicar no botão Open Sitemap para ver se o erro 404 do mapa do site foi corrigido no WordPress.
Depois disso, você define as configurações do mapa do site, se necessário.
Por exemplo, o All in One SEO permite que você escolha o que incluir em seus mapas de sites. Você pode adicionar ou remover tipos de post, taxonomias, posts individuais e páginas.
O All in One SEO também permite que você crie vídeos, notícias, mapas de sites RSS e mapas de sites HTML para o seu site.
Esses sitemaps também podem ser enviados ao Google Search Console e a outros mecanismos de pesquisa. Isso ajuda os mecanismos de pesquisa a encontrar rapidamente o conteúdo mais recente em seu site.
Esperamos que este artigo tenha ajudado você a corrigir o erro 404 do Sitemap do Yoast SEO no WordPress. Talvez você também queira consultar nosso guia completo de solução de problemas do WordPress ou ver como corrigir erros comuns do WordPress.
Se você gostou deste artigo, inscreva-se em nosso canal do YouTube para receber tutoriais em vídeo sobre o WordPress. Você também pode nos encontrar no Twitter e no Facebook.
Syed Balkhi says
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!
D Moran says
I just bought the Genesis Framework theme and then installed the yoast seo plugin and activated. I then tried to generate my sitmap and get this same 404 error.
“Not found, error 404
The page you are looking for no longer exists. Perhaps you can return back to the site’s homepage and see if you can find what you are looking for. Or, you can try finding it by using the search form below.”
Does this mean that the theme I got from Genesis is badly coded? Did I waste my money??
WPBeginner Support says
It is highly unlikely, Genesis Child Themes purchased from StudioPress are very well coded. Try deactivating all your plugin to find out if a plugin is causing this issue.
Administrador
Chris Sparks says
I had a similar issue after installing Yoast SEO. I deactivated the plugin, then restarted and the URL system picked up and started working as expected. This seems to be related to how the permalink structure is set up as only one of our sites has experienced this issue.
Thanks for posting!
Kase Dean says
I don’t know what just happened.
But that fixed it!
Thank you
john says
hello I tried fixing the 404 error code and now I get the following messege:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
and after that i remove the folder of plugin seo and nothing is working again what can i do???
WPBeginner Support says
Do you see an error? Can you access WordPress admin area?
Administrador
Eoin Healy says
Another easy way to fix the sitemaps is to simply disable sitemap functionality and enable it again…. works for me every time, doesn’t matter what plugins i have installed.
In Admin, to go SEO > XML SItemaps
Under ‘XML Sitemap’ uncheck ‘Check this box to enable XML sitemap functionality.’, hit save, check the box again and hit save.
Brent G says
Eoin, Thanks for the great solution!!!!
George says
This worked for me as well. Thanks!
Fred Higson says
This worked for me too! Cheers Eoin!
Jeremy Hogan says
So simple and yet so effective. This was the answer for me as well. Thanks!
Tyler says
Great solution, Eoin! Thanks so much for letting us know!
Margot Barrios says
I already fixed using the first option, how would I know if it’s working already? Should I need to wait for Google’s webmaster report? This is where I saw the 404 error on my site.
WPBeginner Support says
yes you should be able to see your sitemap file in Webmaster Tools
Administrador
Eric Kuhn says
I replaced the edit files with the XML sitemap fix and completely removed what was there initially. Google webmaster tools has accepted the sitemap however, my sitemap doesn’t show a 404 or anything. Does that mean everything is ok?
WPBeginner Support says
Yes, everything looks OK.
Administrador
Melissa says
I tried fixing the 404 error code and now I get the following messege:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at artattackfx.com Port 80
I cannot access the WP Admin Site… How can I revert to before I added this code :
# WordPress SEO – XML Sitemap Rewrite Fix
2
3
RewriteEngine On
4
RewriteBase /
5
RewriteRule ^sitemap_index\.xml$ /index.php?sitemap=1 [L]
6
RewriteRule ^([^/]+?)-sitemap([0-9]+)?\.xml$ /index.php?sitemap=$1&sitemap_n=$2 [L]
7
8
# END WordPress SEO – XML Sitemap Rewrite Fix
to the htacess code in YOAST? Please Help.
WPBeginner Support says
As the tutorial suggests you added the code in .htaccess file on your webserver? If yes, then simply edit the .htaccess file and remove the code you added.
Administrador
Remi says
I thought I followed to the letter your second suggestion but have the same issue as Melissa. Now waiting for the Webhost for a solution. What about adding a warning in your second solution that it can lead to a 500 Internal Server Error.
WPBeginner Support says
You can also revery back by editing the file your modified through FTP. Connect to your website using an FTP client. Locate the file you modified (.htaccess or class-sitemaps.php) and remove the code you added. Alternately, you can also delete the WordPress SEO folder from your wp-content/plugins/ directory through FTP.
Todd says
Thanks a lot. The first fix worked for me as well.
icejava says
Thanks, I had to apply both fixes to get mine too work! Job well done.
Andy says
Thank you very much for this. Works perfectly!
Toni says
Can anyone advise on how to delete the post-sitemap.xml as I cannot find it in my root directory! I have turned of the generate sitemap in Yoast.
Koen says
Hi,
I have wordpress 3.6 with Avada theme and WordPress SEO by Yoast plugin.
First I got the 404 error page.
Then I applied the .htaccess fix without any result.
Then I applied the class-sitemaps.php fix, now the sitemap returns a blank page.
What to do?
Please help. Avada isn’t a crappy theme, I think.
Cheers, Koen
Frank says
Koen,
I’m having the same problem I was thinking it was a Nginx issue because I’m not hosting on an Apache server.
are you hosted on a Apache server?
glowzar says
I know more than 1 with avada theme an the same problem.
Gbenga Adebayo says
Hi,
Appears i still have a few issues to sort out. Google webmaster reporting http 403 errors with my sitemap. I can’t find the sitemap anymore in my root folder. I can navigate to the sitemap using my browser without getting a 404 error message.
Any suggestions or help is appreciated.
Gbenga Adebayo says
Many thanks! .htaccess addition fixed the error for me
Madhu says
Phew … Thanks again!
I updated my SEO pluggin and the sitemaps had the same issue.
I had to incorporate both the fixes.
Rajesh Thakur says
Thanks First one did worked for me need to clear w3 cache after that and wait a little also disable XML sitemap checkbox and check it again
Erica says
I tried the second set of instructions and it resulted in a “Fatal Error” message and I was unable to access my WP site, or even the login page. Scary!
Nyla says
Hi all
I’m an very frustrated to say that I am too getting 404 error, I’m using kriesi replete theme.
I have tried both options however nither worked
I’m not sure if I’m doing it write, can somebody explain…. In simple terms are we deleting and replacing the existing code on both options? Or just adding? It’s not clear or does it make a difference if the prexisting remains
Thanks in advance
Jonny R says
Awesome thanks, implementing both worked perfectly!
Fin O'Suilleabhain says
Worked like a charm. Grateful for the helpful post.
Ahmed Alahdal says
Thanks for the fix
Joyce says
Thank you so much!
this worked — had to make both changes, (edited the class-sitemaps.php file).
Anudeep says
Thanks a lot!
It worked
Rohin says
Damn helpful.
One of my clients had this problem and just took 5 minutes to solve the issue. Just because of this post.
Thanks a lot.
Ron MacGregor says
I am new to WordPress and have only begun a using the Canyon theme. I got the 404 message as I was attempting to install a “contact info” plugin. Does anyone know if I just begin at the very beginning again, i.e. go through my GoDaddy account to reinstall WordPress and then reinstall the Canyon theme – might that solve the 404 problem?
Editorial Staff says
It is probably the issue with that other plugin.
Administrador
Ricky says
Thanks for the fix!
Jack Logan says
I have two sets of websites (WordPress Multisite installs) and I have no issues with sitemaps on one of them and I get a 404 error with category_sitemap.xml on the other one.
I tried both fixes suggested in this post, but they don’t solve the issue. The only thing that works is going to Posts -> Categories – Edit and changing from “Auto detect” to “Always include” on all categories.
The issue here is that I have over 200 sites, and about 8 categories per page, so it would take too long to do it just to get category sitemaps, even though I could use it….
Is there any way to mass change all the categories on WP Multisite to “Always include”. I think this would be a solution that would work for everyone.
Thank you.
Jacques Karsten says
If none of this works try create a file named sitemap_index.xml on your html root through ftp and make sure the permissions are set and the plugin should then take care of the rest.
Kevin says
Thanks!! your suggest worked perfectly!
John says
I did both and it started working. It sounds pretty obvious, but make sure if you copy and paste that you take the line numbers out. I forgot to and broke my .htaccess file for a few minutes.
Hector Torres says
Hi, just wanted to give my thanks, used the second option suggested ad it fixed my 404 error. Thanks!
Adam says
I’m not sure which part worked for me, but I found this page because I was getting the 404, too. I disabled the XML Sitemaps in the plugin, then enabled it and checked the boxes to exclude posts (since I only have pages). Now, it is working perfectly.
Prashant says
Thanks Mate Perfect ! Suggestion for Me !!!!!!!!!!!!!!!!!! Really Greatful Thanks
Ov3rfly says
During research about a similar 404 sitemap xml feed problem, I found a different reason which I would like to share:
WordPress adds a 404 header to all feeds if no posts exist in a site.
More details and a hotfix here:
http://wordpress.org/support/topic/sitemap-xml-feed-is-shown-but-404-header-added-by-wordpress-if-site-has-no-posts
Brad Dalton says
I think there are other issues with this plugin as well.
The attachment pages aren’t all redirecting to the parent page which is something i noticed today.
Editorial Staff says
Create a ticket in the support forum. We haven’t tried that feature yet.
Administrador
Michi says
No other comment since April. That has been 5 months since. I have the 404 still in Sept 2012! Was able to fix it with the .htaccess fix. Thanks for posting
Just wondering why this is STILL an issue.
Sandie Wright says
It worked for me! Open the class-sitemaps.php file located in plugins > wordpress-seo > inc folder. then find the code around line 79 and replace the old code with this new code:
/**
* Initialize sitemaps. Add sitemap rewrite rules and query var
*/
function init() {
global $wp_rewrite;
$GLOBALS[‘wp’]->add_query_var( ‘sitemap’ );
$GLOBALS[‘wp’]->add_query_var( ‘sitemap_n’ );
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’ );
$wp_rewrite->flush_rules();
}
Then, go back to your WP admin page and then go to the SEO plugin > XML sitemaps, and then click the button again (XML Sitemap). The 404 should be replaced with your sitemaps! Easy peasy.
Boah says
@SANDIE WRIGHT: I followed your instructions but it did not solve my 404 problem.
raviteja says
thanks you, the rewrite rule itself cured the problem of 404 not available sitemap
Jody says
Thanks for jacking up my site! i tried your code and now i got a 500 internal service error i have been trying for hours to fix! thanks for making my little problem into a HUGE problem!
Editorial Staff says
If you are getting a 500 internal service error, you can simply undo the changes. Not sure why you would get that.
Administrador
Brad Dalton says
I’m finding my sitemap gets removed everyday and then indexed again. Here’s what i get every day. http://postimage.org/image/3rb3d8qsr/932c5815/
I don’t think it’s my theme as i’m using Genesis.
Not sure but it may be the way my server is configured.
Editorial Staff says
Has to be a conflict with something else (another plugin or server settings). We are using Genesis on this site as well and do not have that issue.
Administrador
Eva says
Hi!
Thank you so much for posting this article! With the first fix, I managed to solve the 404 issue for most sitemaps, though there’s still 1 that is showing the error… Any suggestions of what to do?
I thought about exporting the Yoast SEO settings and reinstalling the plugin to see if that does the trick. Just to be on the safe side: does exporting literally export all settings, even the page/article level SEO customizations OR only the general settings?
Thanks!
Eva
Sara says
Thanks so much – this worked for me.
I know you said the plugin is good, and the problem is in the theme or other plugins, but I tried disabling all plugins and switching to the twenty eleven theme, and the sitemap still gave a 404 error. The only thing that worked for me is editing the htaccess file.
Boah says
… and I tried the same thing. Removed all the plugins, all the themes, and tried it again: 404 error. To make it worse: I’d have an .htaccess file because of IIS. Which options are there for me?
Boah says
Typo: ‘I’d have an’ must be ‘I don’t have an htaccess file’
Rusty Solomon says
I guess SEO Yoast recent update have sitemap problem as I cant see any sitemap on the URL the plugin provide. Let me know if any one has the same issuee and Fix.
Also is there any good plugin avaialble as same as SEO Yoast.
Thanks & Regarsd
Jay Wylie says
Hi, I have tried the first fix, but broke my site in the process. Is there anyway to re-edit my htaccess file, to stop it causing a 500 internal server error?
thanks
Editorial Staff says
You can simply take the code out. Use FTP <
Administrador
Boah says
Hi!
I have edited the plugin as suggested but don’t have a .htaccess file. I still do receive a 404 error.
I’ve also add message on the plugin forum. No replies yet. Suggestions are more than welcome!
http://wordpress.org/support/topic/plugin-wordpress-seo-by-yoast-404-when-viewing-xml-sitemap-1
Colin says
Hi Joots, I’m using the latest version of the SEO plugin. I’m going over previous posts and completeing the various fields, “Focus Keyword”, “SEO Title”, etyc, etc but after I update the post and then go back to “Edit” those fields are then blank again. I wondered how I could rectify this?
Thanks,
Colin
Liverpool, UK
Saki_Kawa says
The solution doesn’t resolved my issue.. I still have a blank page at post-sitemap.xml
Does someone have a solution?? Or I need to unistall this plugin and find another one for my sitemap..
Adam Parnala says
Hi, I don’t have any problems with yoast seo plug in as I’m currently using it. I just I want to ask if it is better than the all in one seo plug in? I’m just curious because I found out that a lot of blogs in my niche uses it. Which is better? the all in one seo or yoast seo? (I’m already used to yoast). Oh, can I also ask how to set multiple focus keyword in Yoast seo? because there is only one field and I can’t figure out how to set a few more keywords for it. Sorry for my questions I hope you can answer me. Thanks!
Editorial Staff says
Yoast’s plugin is a more complete SEO plugin.
Administrador
yoast says
Anyone here who’s willing to test another (and better) fix with me?
Craig says
I’d be willing to test a better fix for this issue but I’m reluctant to commit to a timeframe as I’m not really good at keeping on top of my todo’s since my stroke. (This is one of the reasons I haven’t returned to work as a PHP coder yet.)
And I’d be *very* interested in helping if I happen to be experiencing any of the issues cited above.
Craig
Shawn Poole says
Hi,
Yoast, if the offer is still good, I would LOVE too! I am not to savvy with all of this but would be willing to allow you to guide me
Boah says
Sure, send me an email!
zifana says
thanks..i use wordpress seo,but not with sitemap,because have no idea to fix this error
Stephen Cronin says
Hmm, I think the second part is going to cause the rewrite rules to be flushed on every page load, which <a href=”http://codex.wordpress.org/Rewrite_API/flush_rules”>the Codex</a> warns not to do due to performance issues:
<blockquote>Because this function can be extremely costly in terms of performance, it should be used as sparingly as possible – such as during activation or deactivation of plugins or themes. Every attempt should be made to avoid using it in hooks that execute on each page load, such as init.</blockquote>
I’m guessing that’s why Joost isn’t doing that by default
Of course, I could be wrong because I don’t know his plugin well enough.
jonbish says
I was under the same impression when this article came through my RSS. I’m pretty sure going to your permalinks settings page would accomplish the same thing without having to flush the rewrite rules every time the page loads.
yoast says
@jonbish Unless you’re running a crappy plugin or theme that DOES flush on every pageload before this plugin gets a chance to get its rewrites in.
wpbeginner says
@yoast @jonbish Yes we understand that this is probably a compatibility issue. Yoast sitemaps work fine on our sites. We had to do this on a client’s site.
yoast says
@wpbeginner @jonbish I know YOU understand, question is: do your readers
We’re working on a fix for these kinds of issues in core btw: http://core.trac.wordpress.org/ticket/18450
wpbeginner says
@yoast @jonbish Added a note at the beginning of this article, so users understand as well
yoast says
You’re 100% right Stephen. Something else *is* doing it on each pageload, which forces this “fix”, which isn’t a fix but a workaround for a broken theme or other plugin…
Boah says
And now? It seems a lot of people can’t use your plugni as intended.
JustinVelthoen says
Thanks! I was about to switch to All-In-One because I kept getting sitemap issues.
DrorBekerman says
Do you know what to do when the sitemap returns a blank page?
icejava says
Its probably not blank, just how your browser renders XML (maybe Chrome, mine does it too). View the source code of the page and you shall see the light
Editorial Staff says
This happens for a few reasons. Either you’re running low on memory. Two the file that generates the visual layout in your /wp-content/ directory is not working properly. Perhaps because you blocked the php execution?
Administrador