<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>sitemaps errors &#8211; blog.bluzz.net | Günlü?üm</title>
	<atom:link href="https://blog.bluzz.net/tag/sitemaps-errors/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.bluzz.net</link>
	<description>halledeceğiz bir şekilde...</description>
	<lastBuildDate>Thu, 22 Nov 2018 08:34:04 +0000</lastBuildDate>
	<language>tr</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://blog.bluzz.net/wp-content/uploads/2014/04/cropped-cropped-The-Afternoon-Ferry-150x150.jpg</url>
	<title>sitemaps errors &#8211; blog.bluzz.net | Günlü?üm</title>
	<link>https://blog.bluzz.net</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>A Strange Sitemap Parsing Error and the simple Solution</title>
		<link>https://blog.bluzz.net/a-strange-sitemap-parsing-error-and-a-the-simple-solution/</link>
					<comments>https://blog.bluzz.net/a-strange-sitemap-parsing-error-and-a-the-simple-solution/#respond</comments>
		
		<dc:creator><![CDATA[Z. Bildirici]]></dc:creator>
		<pubDate>Wed, 21 Nov 2018 20:36:57 +0000</pubDate>
				<category><![CDATA[Genel]]></category>
		<category><![CDATA[google search console xml sitemaps]]></category>
		<category><![CDATA[sitemap error fix]]></category>
		<category><![CDATA[sitemap parsing error]]></category>
		<category><![CDATA[sitemaps errors]]></category>
		<category><![CDATA[wordpress security plugins comparison]]></category>
		<guid isPermaLink="false">http://blog.bluzz.net/?p=4236</guid>

					<description><![CDATA[Notice: My blog is in Turkish, but I wanted to share the solution of the sitemap parsing error problem so this will be a short post. The Problem: Google Search Console shows a &#8220;Parsing Error&#8221; in your Sitemaps section. Already tried: Searched Google, read Common XML Sitemap Errors, Validated your XML and its ok, re-created [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Notice: My blog is in Turkish, but I wanted to share the solution of the sitemap parsing error problem so this will be a short post.</p>
<h3><strong>The Problem:</strong></h3>
<p>Google Search Console shows a &#8220;Parsing Error&#8221; in your Sitemaps section.<br />
<strong>Already tried:</strong> Searched Google, read <a href="https://kb.yoast.com/kb/xml-sitemap-errors/" target="_blank" rel="noopener">Common XML Sitemap Errors</a>, Validated your XML and its ok, re-created your sitemap, then blamed Yoast or security and caching plugins for blocking Google Crawler to reach your sitemap but nothing helped. Bing and Yandex are just ok and shows no errors on your sitemap.</p>
<p><strong>The cause of the problem:</strong> A hacked WordPress website, an unwanted URL injection which affects nearly all pages of your website, so your &#8220;sitemap.xml&#8221; or &#8220;sitemap_index.xml&#8221; or whatever its name has the URL injection too.</p>
<p>The weird thing is that if you go to yoursitename/sitemap.xml and view the source, you cannot see any malicious URL, no hidden stuff, but when I tried &#8220;Fetch as Google&#8221; and Fetch and Render I just saw the weird Asian dating URL&#8217;s at the end of the sitemap! Bang!Â And also there is a &#8220;noindex x-robots&#8221; meta tag inserted. Maybe by Cloudflare or not.</p>
<p>Here is the fetch as google code:<br />
<em>Fetch as Google:</em><br />
<em>http://www.website.com/sitemap_index.xml </em><br />
<em>Indexing requested for URL and linked pages</em><br />
<em>Googlebot type: Desktop (render requested)</em><br />
<em>Complete on Wednesday, October 17, 2018 at 3:08:01 PM PDT</em><br />
<em>Downloaded HTTP response:</em></p>
<p><em> TTP/1.1 200 OK</em><br />
<em>Date: Wed, 17 Oct 2018 22:08:02 GMT</em><br />
<em>Content-Type: text/xml; charset=UTF-8</em><br />
<em>Transfer-Encoding: chunked</em><br />
<em>Connection: keep-alive</em><br />
<em>Set-Cookie: __cfduid=&#8230;&#8230;2a19aa036ae1539814082; expires=Thu, 17-Oct-19 22:08:02 GMT; path=/; domain=.website.com; HttpOnly</em><br />
<em>Cache-Control: no-store, no-cache, must-revalidate</em><br />
<em>Cf-Railgun: 0e497a84f9 0.25 0.498083 0030 cc99</em><br />
<em>Expires: Thu,Â </em><br />
<em>1</em><br />
<em>HTTP/1.1 200 OK</em><br />
<em>2</em><br />
<em>Date: Wed, 17 Oct 2018 22:08:02 GMT</em><br />
<em>3</em><br />
<em>Content-Type: text/xml; charset=UTF-8</em><br />
<em>4</em><br />
<em>Transfer-Encoding: chunked</em><br />
<em>5</em><br />
<em>Connection: keep-alive</em><br />
<em>6</em><br />
<em>Set-Cookie: __cfduid=&#8230;.1539814082; expires=Thu, 17-Oct-19 22:08:02 GMT; path=/; domain=.website.com; HttpOnly</em><br />
<em>7</em><br />
<em>Cache-Control: no-store, no-cache, must-revalidate</em><br />
<em>8</em><br />
<em>Cf-Railgun: 0e497a84f9 0.25 0.498083 0030 cc99</em><br />
<em>9</em><br />
<em>Expires: Thu, 19 Nov 1981 08:52:00 GMT</em><br />
<em>10</em><br />
<em>Pragma: no-cache</em><br />
<em>11</em><br />
<em>Set-Cookie: PHPSESSID=d6XDG0kItbR01S%2Ca4uw-x2; path=/</em><br />
<em>12</em><br />
<em>Vary: Accept-Encoding</em><br />
<em>13</em><br />
<em>X-Robots-Tag: noindex, follow</em><br />
<em>14</em><br />
<em>Server: cloudflare</em><br />
<em>15</em><br />
<em>CF-RAY: 46b614dd70948339-ATL</em><br />
<em>16</em></p>
<p><em>17</em><br />
<em>&lt;?xml version=&#8221;1.0&#8243; encoding=&#8221;UTF-8&#8243;?&gt;&lt;?xml-stylesheet type=&#8221;text/xsl&#8221; href=&#8221;//www.website&#8230;&#8230;xsl&#8221;?&gt;</em><br />
<em>.</em></p>
<p><em>..</em></p>
<p><em>.</em><br />
<em>45</em><br />
<em>&lt;lastmod&gt;2018-01-22T22:32:21+03:00&lt;/lastmod&gt;</em><br />
<em>46</em><br />
<em>&lt;/sitemap&gt;</em><br />
<em>47</em><br />
<em>&lt;/sitemapindex&gt;</em><br />
<em>48</em><br />
<em>&lt;!&#8211; XML Sitemap generated by Yoast SEO &#8211;&gt;</em><br />
<em>49</em><br />
<em>&lt;center&gt;&lt;a href=&#8217;http://www.website/kristen-dating-indonesia/&#8217;&gt;kristenÂ dating indonesia&lt;/a&gt;, &lt;a href=&#8217;http://www.website.com/dating-for<a href="http://www.doyouknowturkey.com/dating-for-drug-addicts/'%3Edating" target="_blank" rel="noopener">-drug-addicts/&#8217;&gt;dating</a>Â for drug addicts&lt;/a&gt;, &lt;a href=&#8217;http://www.website.com/online-dating-advice-chat-room/&#8217;&gt;http://www.website.com/online-dating-advice-chat-room/&lt;/a&gt;&lt;/center&gt;</em></p>
<p><em>Download Time: 0.535 seconds</em><br />
<em>Â© 2018 Google LLC &#8211; Webmaster Central &#8211; Terms of Service &#8211; Privacy Policy &#8211; Search Console Help</em></p>
<h3><strong>Solution:</strong></h3>
<p>Clean up your hacked WordPress. My Favorite plugins are:</p>
<ul>
<li><strong>Anti-Malware Security and Brute-Force Firewall</strong> <a href="https://wordpress.org/plugins/gotmls/" target="_blank" rel="noopener">https://wordpress.org/plugins/gotmls/Â </a></li>
<li><strong>Security &amp; Malware scan by CleanTalkÂ </strong><br />
<a href="https://wordpress.org/plugins/security-malware-firewall/" target="_blank" rel="noopener">https://wordpress.org/plugins/security-malware-firewall/</a>Â  (Be quick to clean up your site before the trial period ends)</li>
</ul>
<p><strong>Other Plugins failed:</strong></p>
<ul>
<li><strong>Wordfence</strong>: Unable to finish a scan, because I am using a dedicated server, even the minimum settings didn&#8217;t help too much server load&#8230;</li>
<li><strong>Sucuri:</strong> The free version has nothing, no malware scan&#8230; Firewall, the famous WAF is not available I free version&#8230; I am still surprised whatÂ people suggest Sucuri so much&#8230;</li>
<li><strong>All in One Security for WordPress:</strong> Not a bad plugin but Malware scanÂ is an externalÂ service not included in free version. They explain it as its a complex and dynamic issue to detect and clean&#8230;</li>
<li><strong>Others</strong>: Lots of time spent, but no luck.</li>
</ul>
<h3>Conclusion:</h3>
<ul>
<li>Anti-Malware Security and Brute-Force Firewall https://wordpress.org/plugins/gotmls/</li>
<li>Security &amp; Malware scan by CleanTalk<br />
https://wordpress.org/plugins/security-malware-firewall/Â  (Be quick to clean up your site before the trial period ends)</li>
</ul>
<p>Both are good plugins,Â Anti-Malware Security and Brute-Force Firewall deserve a Donation &#8211; Sorry Paypal is not available in Turkey. Cleantalk is worth its price, i liked &#8220;Send for Analyze&#8221; option&#8230;</p>
<p>By the help of this combination i was able to scan for malware and injections, a flawless cleaning, then resubmitted the sitemap, when i see that there were no errors i was very happy and also angry for the hours of useless research.</p>
<p>I wrote this blog post because i see many posts about Sitemap parsing error in Google Product Forums and WordPress forums, and you may notice that every WordPress website is under a constant attack and hacked WordPress website numbers are growing very fast.</p>
<p>Take your security measures and try not to be hacked.</p>
<p>&nbsp;</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.bluzz.net/a-strange-sitemap-parsing-error-and-a-the-simple-solution/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
