TheSmartOne

Correct, you are right, I was talking about the exclusion I made in robots.txt before
Since I was lucky to have 2 patterns in the spam links I used *u_b*, instead of .jp* there.

So for the redirection rule, I also opted to just use your regex for u_b, which works flawless.

I’m pretty sure your solution of jp will work too, just haven’t tested it yet.
Thinking about writing an article about it ??

Hi @cbrandt

Working like a charm mister!!
I used the u_b since the .jp was excluding .jpg and .jpeg

As a reference for others I chose:
SOURCE URL: /.*u_b.*
TITLE: (optional) My China sucks redirect
MATCH: URL only
WHEN MATCHED: Error (404) WITH HTTP CODE: 410 – Gone
GROUP: Redirections (or any other group name you chose/created) POSITION 0

I already had added a redirection for all spam URLS (+- 300), and just noticed that slowed down my site up to getting a timeout. So I disabled those, keeping just 1 rule.

Result: see server response check below

I chose 410 – Gone since 404 can be a temporary error, and 403 might mean the page exists, but google has no access. With 410 I’m indicating this spammy link is Gone – forever.

I have removed the *.u_b* from my robots.txt so google can crawl all spam links and see they dont exist, and remove forever from index and cache.

I’ll donate for this kick-ass plug-in. Thanks guys.

Server response check using https://tools.seobook.com/server-header-checker

> GET https://www.mysite.com/?jsdfjfdfu_bdsdd.jp HTTP/1.1
> Host:
> User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.246
Response
< HTTP/1.1 410 Gone
< Date: Tue, 05 Feb 2019 18:05:38 GMT
< Server: Apache/2
< Pragma: no-cache
< Expires: Wed, 11 Jan 1984 05:00:00 GMT
< Cache-Control: no-cache, must-revalidate, max-age=0
< X-Redirect-Agent: redirection
< Link: ; rel=shortlink
< Set-Cookie: PHPSESSID=e3ptr3b73a84deo4qbpvv2h6m6; path=/
< Vary: Accept-Encoding,User-Agent
< Transfer-Encoding: chunked
< Content-Type: text/html; charset=UTF-8

My other pages nicely show a 200 OK response

Final response
< HTTP/1.1 200 OK
< Date: Tue, 05 Feb 2019 18:05:38 GMT
< Server: Apache/2
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Pragma: no-cache
< X-Pingback:
< Link: ; rel=shortlink
< Set-Cookie: PHPSESSID=kp1nrjh7d7ehap936b5md6nl34; path=/
< Vary: Accept-Encoding,User-Agent
< Transfer-Encoding: chunked
< Content-Type: text/html; charset=UTF-8

• This reply was modified 5 years, 9 months ago by TheSmartOne.

So anyone that understand regex to exclude urls with the word u_b ?

Hi Milan

Thanks. Yeah could be one of the plugins conflicting

I’ll give it a try without plugins and report my findings.

Regards
Michael

The search on my main menu suddenly started to work – showing a list of topics when I use keywords from my site. Not sure if it was because the indexing finished?

Exactly what I wanted. Nice, thank you. The widget therefore is less necessary – at least for me.

Keep up the good work. don’t let google buy you ??

Cheers
TSO

Thanks for the fast reply.

On my page I have a search entry after the main menu, and – for now – one as a widget on the right.

The first one doesn’t do this instant searching, that’s why I tried to get it working with a widget.

So I understand the first search entry should also be capable of doing this?

If you could point me in the right location how I can change this, that would be nice.
The search page itself works flawlessly so far.

Thanks

Deactivating / reactivating plugin did the trick. Thx

Just happened to my site.
Home page was fine but some pages were down.

Disabled jetpack and all functioning again.

Thanks! ??

Thanks. I’ll look into the thread, and see what is possible.

Hey Jack

I see you got the plugin working again. Cool!
Any chance you would want to share the updated version of wp-statsmechanic.php?

Me no speak PHP ??

And there are no similar plugins around.

Bedankt ??

I have the same question. I had hoped this plugin might fix this but it didnt.

Any workaround or idea?

I tried to fix it with this aticle but couldn’t
https://googlewebfonts.blogspot.com.br/2010/09/optimizing-use-of-google-font-api.html

Closing topic.

Thanks for the nice clarification.

The plugins don’t all offer the same functionality, and that a good thing too.

I think it’s also great users can switch without much hassle between great plugins.

Cheers!