• Resolved jetxpert

    (@jetxpert)


    Hi there,

    We love your plugin but, due to conflicts, deleted it some time ago.

    Here’s our problem: After we deleted your plugin, iThemes Security plugin is capturing numerous 404s (via Google bot) related to your plugin. It appears many other ex-plugin users have reported the same or similar problem.

    Click here: https://prntscr.com/p4b8bb

    We followed your past recommendations to no avail. Not only did we purge all of our cache, we also checked our file directory for “plugin remnants.” None found.

    Can you think of anything else? Google bot shouldn’t be searching for this plugin (files) anymore.

    • This topic was modified 5 years, 2 months ago by jetxpert.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter jetxpert

    (@jetxpert)

    *** Update | Temporary Fix ***

    Based on the file directory (path) given in the above link, we have added the following to our robots.txt file:

    Disallow: /wp-content/uploads/fvm/ #block access to deleted plugin (fast velocity minify)

    Not sure the above will work, but time will tell as Google bot crawls our site.

    Still, need to understand better why this is happening. It shouldn’t. Not happening with any other plugins we’ve deleted in the past.

    Thank you!

    G

    (@gnetworkau)

    Unfortunately thats how Google works, and there is not much you can do about it.
    Expect any temporary type files to remain indexed by Google for months after they have been deleted.

    Plugin Author Raul P.

    (@alignak)

    @jetxpert the robots rule is wrong.

    You cannot / should not block google from accessing your js and css files, else think your styles are broken.

    The behaviors you describing is perfectly normal.
    If you purge the cache, you are deleting the cache.
    If you delete the cache, it will trigger a 404 for that specific file, not the page where it belongs.

    Having 404 for those files, is irrelevant for seo.
    But if it’s annoying to see, checkout the settings.
    There is a setting to preserve cache files, so that thing won’t happen…

    Thread Starter jetxpert

    (@jetxpert)

    All:

    Above worked, but we went ahead and removed the robots.txt line entry as suggested by @alignak. Let’s see what happens when Googlebot recrawls our website.

    PS: We deleted FVM over 10 months ago and was still getting 404s from your plugin. No other cache plugin has done this before so suggest checking into your code to eliminate this condition.

    Cheers!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Post Deletion | Plugin Generating 404s’ is closed to new replies.