• Resolved Anonymous User 14284321

    (@anonymized-14284321)


    I am having an issue with entries such as this:
    http://{DOMAIN}.net/wp-admin/admin-ajax.php?action=wordfence_logHuman&hid={CODE}
    showing up in Google search results, despite having wp-admin explicitly blocked in my site’s robot.txt file.

    User-agent: *
    Disallow: /wp-admin/

    I do realize this is probably just from Live Traffic view, but I don’t understand why Google is ignoring the robots.txt setting.

    Has anyone else seen this issue before? It’s disconcerting to see anything from wp-admin in search engine results.

    https://wordpress.org/plugins/wordfence/

Viewing 15 replies - 1 through 15 (of 17 total)
  • Thread Starter Anonymous User 14284321

    (@anonymized-14284321)

    Update: I checked in URL Parameters within Google Webmaster Tools, and set the “action” parameter to “No URLs”.

    I’ll updated when I know whether or not this fixes the issue πŸ™‚

    Thread Starter Anonymous User 14284321

    (@anonymized-14284321)

    Update #2: Nope, didn’t fix the issue. I explicitly set the URL Parameters to “No URLs” and submitted remove requests for the existing link, and it’s still showing up.

    Hopefully Google has some sort of answer on this.

    Plugin Author WFMattR

    (@wfmattr)

    You might try the
    Google Webmasters Forum — Wordfence itself wouldn’t cause this link to be indexed, so they may be able to help more.

    @Sduibek We discussed this earlier (I haven’t had a chance to talk to MattR yet). We think there may be a way for us to fix this but we’re testing it right now. Hopefully it will be out in the next release or so. The internal ticket is FB835 and it is being actively worked.

    Resolving ticket for now since it has been entered.

    tim

    Hi,
    is there any news about this issue?
    I’ve just been informed by our SEO admin that “google search console” started some days ago to find hundreds of 404 like This:
    http://www.domain.com/wp/?wordfence_logHuman=1&hid=2B4928F91501E8B7051FAEF85711D07D

    I’ve also found this post https://wordpress.org/support/topic/loghuman-call where a wordfence’s member suggested to just disable Live Traffic but it’s 2 years old.

    Thanks,
    Nowherelab

    Plugin Author WFMattR

    (@wfmattr)

    This issue is fixed for most users, but when WordPress is installed in a subdirectory, it still happens.

    If you do not use the Live Traffic page in Wordfence, you can disable it, which does take the “logHuman” link out of your pages, and Google should not report new 404’s. Sometimes it takes a few days for Google to catch up with pages it had crawled, but they should stop relatively soon after the option is disabled.

    -Matt R
    FB862

    Hi Matt,
    thanks for your reply.
    Actually I always install WP in a subfolder so I’ll go on and disable Live Traffic.
    Hope it works.

    Thanks

    Hey, I’m doing some maintenance/SEO on a site of mine and ran into this as well. Hundreds of Wordfence links in the Crawl Errors. Yes, I’m installed in a subdirectory and always do that with WP. Is the fix still to simply disable Live Traffic? Any update on a fix?

    Thanks!

    Well, actually for me disabling live traffic solved the issue.

    hope it helps

    Cool. Just switched that, then marked the errors on Search Console to fixed. Hopefully that’s that. πŸ™‚

    Plugin Author WFMattR

    (@wfmattr)

    @nowherelab: Thanks for following up!

    @fastasleep: There was an update in version 6.0.16 that should fix this on subdirectory installations, though Google sometimes hangs on to old links and re-checks them for a long time. Some of these might still appear for a while because of that, but the number of these links that Google checks should decrease.

    -Matt R

    Sorry, I didn’t note when the 404’s ended, but I assume they probably stopped around the time of that release. The Search Console has months of history of crawl errors, so that’s likely what I was clearing out. Thanks for letting me know! So, it’s safe to turn on the live traffic feature again? πŸ™‚

    Plugin Author WFMattR

    (@wfmattr)

    I believe it is safe to use on subdirectory installations again — we have had a couple people report issues, but they sounded like they may be the same case, where older errors are still in the list.

    If you do have trouble with it after re-enabling live traffic, please do let us know. Thanks!

    -Matt R

    I am also facing exactly the same issue with 2,461 errors. I disabled live traffic and I have also set the url parameter to no urls, still facing the same issue.
    Please assist to resolve this issues.

    Plugin Author WFMattR

    (@wfmattr)

    @alimraan: There was an update to Wordfence that fixed this issue, so make sure you are running the current version.

    If you still have trouble, please make a new post using the form at the bottom of the Wordfence forum here, since this one was already resolved. Thanks!

    -Matt R

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Wordfence logHuman in Google search results’ is closed to new replies.