Home » Blogging » Google webmaster tools access denied error fix

Google webmaster tools access denied error fix

Google Webmaster Tools provides major tools necessary to monitor your website or blog and fix any errors that may interfere with Google indexing your pages and your pages showing up in Google Search results. Recently, I started noticing the notorious Webmaster Tools Access Denied error. Some of the Feedburner related links started showing up under Crawl Errors -> URL Errors of my GWT. All I could get from the error information was that these links were Feedburner related. The problematic links involved URL parameter such as utm_source, utm_medium, and utm_campaign and some Feedburner information. In this post, I will share how I fixed the issue in the hopes that it might help somebody else as well as save some of their time.

Google Webmaster Tools Access Denied Error
Google Webmaster Tools Access Denied Error

In my case, there were two problematic URLs:

<blockquote data-secret="I68nBf0QsS" class="wp-embedded-content"><a href="https://www.htpcbeginner.com/openelec-3-2-1-released-raspberry-pi-update-instructions/">OpenELEC 3.2.1 Released: Raspberry Pi Update Instructions</a></blockquote><iframe class="wp-embedded-content" sandbox="allow-scripts" security="restricted" style="position: absolute; clip: rect(1px, 1px, 1px, 1px);" src="https://www.htpcbeginner.com/openelec-3-2-1-released-raspberry-pi-update-instructions/embed/#?secret=I68nBf0QsS" data-secret="I68nBf0QsS" width="600" height="338" title="“OpenELEC 3.2.1 Released: Raspberry Pi Update Instructions” — htpcBeginner" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>

While you may find fixes that revolve around making Google ignore the links that contain the utm_source, utm_medium, and utm_campaign parameters, they are not the ideal fixes because some may linked to those URLs and you may lose the backlink juice. Searching around, I found several bloggers had this issue but no clear solution available. Fortunately, I stumbled upon <a href="https://wordpress.org/support/topic/403-forbidden-error-on-google-wmt" rel="nofollow" target="_blank">this thread</a> that solved the issue for me. The Google <u>webmaster tools access denied</u> error was caused by the <a href="https://wordpress.org/plugins/bulletproof-security/" target="_blank" rel="nofollow">BulletProof Security</a> (BPS) WordPress plugin I recently implemented. 

[ls_content_block slug="recommended-reading-wordpress"]

The <a href="https://wordpress.org/support/topic/403-forbidden-error-on-google-wmt" target="_blank" rel="nofollow">Webmaster Tools access denied</a> error is caused due to the parenthesis at the end of the links, in this case: (htpcBeginner). BulletProof Security denies access to referrers that contain the parenthesis. The solution is to somehow remove the parenthesis or make BulletProof Security ignore them, the latter being the more practical solution. To make BPS ignore the parenthesis, go to BPS Security plugin settings page from your WordPress dashboard. Then open "Your Current Root htaccess File" under "htaccess File Editor" tab. 

[caption id="attachment_9221" align="aligncenter" width="500"]<a href="https://cdn2.htpcbeginner.com/images/2013/10/gwt_bps_htaccess_editor.png"><img src="https://cdn1.htpcbeginner.com/images/2013/10/gwt_bps_htaccess_editor-500x154.png" alt="BulletProof Security htaccess File Editor" width="500" height="154" class="size-large wp-image-9221" srcset="https://cdn2.htpcbeginner.com/images/2013/10/gwt_bps_htaccess_editor-500x154.png 500w, https://cdn2.htpcbeginner.com/images/2013/10/gwt_bps_htaccess_editor-150x46.png 150w, https://cdn2.htpcbeginner.com/images/2013/10/gwt_bps_htaccess_editor-300x92.png 300w, https://cdn2.htpcbeginner.com/images/2013/10/gwt_bps_htaccess_editor-740x228.png 740w, https://cdn2.htpcbeginner.com/images/2013/10/gwt_bps_htaccess_editor.png 897w" sizes="(max-width: 500px) 100vw, 500px" /></a> BulletProof Security htaccess File Editor[/caption]

Find the following line:

RewriteCond %{QUERY_STRING} ^.*(\(|\)|< |>|%3c|%3e).* [NC,OR] 

Change it to (remove \(|\)|:

RewriteCond %{QUERY_STRING} ^.*(< |>|%3c|%3e).* [NC,OR] 

Update your current htaccess file. BPS should now ignore the parenthesis and Google Webmaster Tools access errors on the Feedburner URLs should go away over the next few weeks when Google finishes re-indexing your pages.

About the author


Anand is a self-learned computer enthusiast, a part-time blogger, and a Food Scientist by career. He has been blogging since 2010 on Linux, Ubuntu, Home/Media/File Servers, XBMC, and related HOW-TOs (read more).


Join the other 110,000 followers