How would that help? Wouldn't the copier simply sign with their own key?
Maybe Google should run a timestamping service. It could be stateless: send an hash of the content, get it back timestamped and signed, then include it in the page before publishing it.
- create signature
- post signature, possibly publicly, (wow, maybe an actual use for a blockchain)
- post content
Anybody copying it could be proven to be a copyist.
Actually secure timestamping is already used by Windows to verify software signatures, even when the signing key expires: https://security.stackexchange.com/questions/47289/how-is-an...
Heck, you can even use Roughtime [0] to achieve secure timestamping as it uses digital signatures and allows you to provide a nonce. Even the design doc [1] mentions this use case:
> This means that Roughtime replies can be used as a time-stamping service, and thus that Roughtime servers can be used to check each other.
Content creators signing their content with a private key would be a better idea.