Search Engine Rankings and CPU Resource Over Usage

  • Resolved truebird

    (@truebird)


    6 years ago

    Hi,

    Regarding this site http://bit.ly/2rR0WtS

    Will this plugin OR the FULL CODE .htaccess code found here https://perishablepress.com/6g/
    effect any search engine bots and therefore rankings at all?

    I am trying to narrow down what may have effected us to drop off bing, yahoo, duckduckgo, and some others (but Google is fine). Our host, siteground, added some other .htaccess entries and I blocked a few ip addresses before and we had the FULL CODE https://perishablepress.com/6g/ I have sense totally removed every adjustment done recently to identify what may be causing good search bots from seeing us and dropping us out of rankings out of the blue. So, we are starting over.

    Now, we just have wordfence and and pretty much clean .htaccess and we removed all prior IP deny addresses too.

    I wanted to try to either use your plugin OR the FULL CODE alone from your site (purpose is the try to reduce CPU usage (see here https://www.screencast.com/t/hcaUbaOK7Rw and https://www.screencast.com/t/HZDe3aHNQo but at they same time not mess up our search rankings on any search engines, even smallers search engines too, we don’t want to block any good search engines at all and get back our ranking standings.

    For example, we are on the first page of Google for “wall street” and should be on all other search enginesites too like yahoo, bing, duckduckgo, baidu, ask, and many others but we dropped off after doing some .htaccess adding siteground added and IP blocks (both of which we removed and now starting over).

    So, my questions are:

    Will your plugin and/or full code version block any kind of good search engines at all (not matter how small they are etc)?

    and

    Do you have any recommendations?

    🙂

    Greg

    • This topic was modified 6 years ago by truebird.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Jeff Starr

    (@specialk)

    6 years ago

    Glad to help:

    1) “Will your plugin and/or full code version block any kind of good search engines at all (not matter how small they are etc)?”

    Nope, they are designed to NOT block legit requests and good (compliant) search engines.

    2) “Do you have any recommendations?”

    I’m not sure, but keeping a close eye on site error and access logs is going to provide information about how traffic (of all kinds) is being handled behind the scenes.

    Let me know if I can provide any further infos, glad to help however possible.

    Thread Starter truebird

    (@truebird)

    6 years ago

    @specialk

    Cool deal. Ok. I will let you know how it goes and appreciate the fast response!!!

    🙂

    Plugin Author Jeff Starr

    (@specialk)

    6 years ago

    Anytime, truebird! 🙂

    Thread Starter truebird

    (@truebird)

    6 years ago

    @specialk

    Looks like I had one other thing to maybe ask you.

    On the left of diffchecker is what was our old code we had implemented a while back (few months). On the right is your fresh code from your site https://www.diffchecker.com/SYecNlHl

    Do you think lines 4 – 9 are a good idea?

    Should I stick with the old code we had or use your fresh code a best you can tell?

    I also notice that lines 54 – 64 are different. Use them or keep the old?

    Lastly, regarding this:
    HTTP Auth

    If your site is using any HTTP authentication, you will need to comment out (or remove) the following lines:

    Allow from all
    Require all Granted

    These lines are located in the User Agent section. Thanks to Tomas for reporting this.

    >>>Is this something I can disregard on our site or do I need to comment out both? I don’t see these on the right of diffchecker (old code) but on on your new one here https://www.screencast.com/t/jM2Yp7whrOK on the left.

    🙂

    P.S. OR, should we just use the plugin only https://wordpress.org/plugins/block-bad-queries/ ya think (if so, if we disable it then the code just removes itself from .htaccess and any related file adjustments right)?

    P.S.S Any other thoughts before we add it back in on anything else at all you may notice?

    • This reply was modified 6 years ago by truebird.
    • This reply was modified 6 years ago by truebird.
    Plugin Author Jeff Starr

    (@specialk)

    6 years ago

    Glad to help:

    1) “Do you think lines 4 – 9 are a good idea?”

    Not in general, which is why they are not included in 6G.

    2) “Should I stick with the old code we had or use your fresh code a best you can tell?”

    I can only speak for my own code, so would always recommend no modifications, unless you know and understand what you are doing.

    3) “I also notice that lines 54 – 64 are different. Use them or keep the old?”

    As above, keep the original code always unless you know what you are doing.

    4) “Is this something I can disregard on our site or do I need to comment out both?”

    It sounds correct, but proper testing will need done as there always are other variables in play.

    5) “OR, should we just use the plugin only https://wordpress.org/plugins/block-bad-queries/ ya think (if so, if we disable it then the code just removes itself from .htaccess and any related file adjustments right)?”

    The choice is yours. 6G is more comprehensive than BBQ. And no, the plugin does not remove anything from anywhere. It does not assume anything (like 6G or anything else).

    6) “Any other thoughts before we add it back in on anything else at all you may notice?”

    Yes, always test thoroughly, keep a close eye on logs, and for any further questions about 6G, please contact me directly (the forums here at WordPress.org are for free plugins only). Of course, any questions specifically about BBQ (free version) are welcome here.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Search Engine Rankings and CPU Resource Over Usage’ is closed to new replies.