Google Proxy Image Crawler

Hi @123nadav, thanks for your message.

I may need some clarification on your exact question. The %E2%80%A6 characters on the end of the link are the URL-friendly characters to signify an ellipsis (…) character. This is possibly your server using the wrong character encoding where it’s meant to be actually truncating the log entry if it’s over 74 characters long, for example. Are you seeing this formatting in Wordfence’s log, the nginx log or both?

Wordfence will observe Google crawlers and check for their legitimacy. Google are fairly transparent with making their crawlers known so they can be referenced to ensure legitimacy. The link you have provided is for an administrator to whitelist images received from trusted sources in emails on the Gmail platform, so are image URLs from your site being incorrectly interpreted (and therefore broken) when included in mailshots?

Thanks,

Peter.

I saw it in the Nginx log, and you right this issue is familiar:
https://bugsdb.com/_en/debug/019eecc1f845fbaefaf6cad74a097d4d

maybe is because i use base encoding?
screenshot of redirect from an image (i belive the google proxy crawler):
https://ibb.co/KrF3DFS

The Nginx Log and you see it in the wordfance tool ( i belive is wordfance log )
you see these links redirect to the main page ( this because they broke i install 404 plugins to not lose SEO )

HAVE WAY TO FIX IT?
MAYBE HEADER IN NGINX?
MAYBE OFF COOKIES FROM WORDFANCE AND ALLOW SIDE SERVER CACHING? ( VARNISH CACHE? )

WHEN I SAID VARNISH CACHE, I MEAN TO CONNECT A PLUGIN AND ALLOW SERVER SIDE CACHE:
https://ibb.co/d50SVgg

This is another problem i want advise with you but lets will solve the first, and if i need i will open another thread for this, but if server-side can be the issue to the crawler, i be happy to fix both ??

AND HAPPY HOLIDAY
@wfpeter
??

[Moderated: Signature removed]

• This reply was modified 4 years, 2 months ago by t-p.
• This reply was modified 4 years, 2 months ago by t-p.

Side note to @123nadav ,

Please don’t write in caps see Forum Guidelines

@t-p
No problem, i am sorry i didn’t know.

Hi @123nadav, thank-you for the extra information.

You could be looking at a spoofed user agent rather than a Google crawler so you need to look at Live Traffic and do a reverse DNS check of the IP and forward DNS check of the hostname as described by Google: https://developers.google.com/search/docs/advanced/crawling/verifying-googlebot

Your site is 301 redirecting all non-existent URL’s to the home page instead of serving the theme’s 404 page. This is not a Wordfence issue so you’ll need to rectify that, possibly with the help of the theme provider if the problem originates from there.

Thanks again,

Peter.

I did it on purpose if not you get 404… is worst.
I install a plugin to redirect them in the htacsses.

if i do not do it have SEO droping.

Hi @123nadav,

It is not necessarily recommended to blanket-redirect all 404s to the homepage, but this is more for relevancy to the section of your site the visitor was attempting to access than security.

If you were able to verify the Google crawler, and seeing as the image redirect from the log is manual action with .htaccess, I don’t believe I can suggest further Wordfence actions to take. You may need to speak with your host about your Nginx logs if you have concerns about the URL format.

Thanks,

Peter.