• Hello,

    We have the paypal ipn for wordpress version 1.1.0 installed on our website. It is also running woocommerce Version 3.0.5 on a theme called “Pluto”.

    Recently we’ve been getting error notifications from Google Search Console. The Google bot is detecting 404s from a directory on our website called “paypal_ipn”. This directory does not exist because when I log into our ftp, I don’t see it. I’m assuming it is generated from the plugin since the transaction ID of each customer purchase is showing up as separate links in that directory.

    Is it possible to get rid of this directory or at least hide it from the public?

    Thanks,
    Karen

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi Karen,

    Sorry for the delay, I have created an issue for this in our Git repo and I have assigned it to a developer. We’ll review this and get back to you ASAP!

    HIi @karenfan73,

    After careful testing, we conclude that It is not an issue with the plugin, though. It only comes when the search engine is indexing the site or crawling the site. Sometimes our site URL in the WordPress is like https://www.domain.com/custom_post_type and it is considering as the directory name. In our case, paypal_ipn is custom post type. and because of that crawlers may be showing them as a directory.

    We can remove that by adding special code in the wordpress plugin file / functions.php page

    function noindex_for_paypal_ipn()
    {
        if ( is_singular( 'paypal_ipn' ) ) {
            echo '<meta name="robots" content="noindex, follow">';
        }
    }
    
    add_action('wp_head', 'noindex_for_paypal_ipn');

    Alternatively, you can make a robots.txt file at the base of your domain which tells them also not to index said page (crawlers are supposed to look for this file):
    User-agent: * Disallow: /company-name

    Please Let me know if you have any further questions/concerns on this.

    Cheers.

    Plugin Contributor angelleye

    (@angelleye)

    @angelleyesupport, That code snippet you provided here is something we should probably just add to the plugin by default. Please get back to TJ within the BitBucket issue that was created for this and see if he thinks there’s any reason we shouldn’t do this in the plugin core code.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘paypal_ipn directory’ is closed to new replies.