Hi Matt,

Yes, this seems to be something which has been occurring on one of our 
repositories. I have observed three separate flags within Google Search Console 
in as many weeks. This never used to be a problem in the past so I can only 
assume Google has changed its security metrics. 

> If you've also dealt with something like this, how did you end up handling it?

But in terms of handling it, I didn't! 😉 I have simply provided feedback to the 
Search Console team via the 'reconsideration request' feature. Each time Google 
has lifted the flag (presumably following investigation by a real human...). 
So, rather than handling it locally, I'm hoping that Google simply modifies 
their security/spam checking algorithms because a lot of services must be 
getting flagged and I don't think it is reasonable for Google to expect the 
changes they are seeking.

Cheers

George
--
George Macgregor
Scholarly Publications & Research Data | IS Information Management
University of Strathclyde
Tel: 0141 548 3496 | Web: https://purl.org/g3om4c  | Twitter: @g3om4c
https://orcid.org/0000-0002-8482-3973
--
--
The University of Strathclyde is a charitable body, registered in Scotland, 
with registration number SC015263

-----Original Message-----
From: Code for Libraries <[email protected]> On Behalf Of Krc, Matthew
Sent: 11 December 2019 16:07
To: [email protected]
Subject: [CODE4LIB] "Content Injection" warnings from Google

NONCONFIDENTIAL // EXTERNAL
Hi,

I was wondering if any other institutions that serve up PDFs in their digital 
libraries ever have had to deal with Content Injection errors from Google 
Search Console. This seems to be the case with a number of our documents - when 
Google indexes the text layer of our PDFs they seem to be interpreting 
imperfect OCR as spam content and flagging it as a potentially hacked page 
(we've done thorough investigations and they're not).

If you've also dealt with something like this, how did you end up handling it?

Thanks,
Matt

Matthew Krc
Senior Digital Projects Librarian
Federal Reserve Bank of St. Louis
(314) 444-0836

Reply via email to