大网数据广告活动
网站运营与故障问答

Does hotlinking image protection hurt search engines indexing?

· 52CE 我爱测

Several websites are hotlinking my images, I want to block and prevent hotlinking to my website images. And, I was going to use standard hotlink prevention code in .htaccess : RewriteEngine on RewriteCond %{HTTP_REFERER} !^$ Rewr…

问题原文

原帖链接 · knilkantha · CC BY-SA 4.0

Several websites are hotlinking my images, I want to block and prevent hotlinking to my website images.

And, I was going to use standard hotlink prevention code in .htaccess:

RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?yourdomain.com [NC]
RewriteRule \.(jpg|jpeg|png|gif)$ - [NC,F,L]

However, some of the blog and forum threads had suggested to separately add search engines in an allow list like the following:

RewriteCond %{HTTP_REFERER}  !^http?://([^.]+\.)?google\.   [NC]
RewriteCond %{HTTP_REFERER}  !^https?://([^.]+\.)?facebook\.    [NC]

Do I need to explicitly add every search engine & social media while applying hotlink prevention code in .htaccess? Does this effect on my website images crawling?

Or, is there any better way to protect images from hotlinking?

已采纳解答

原帖链接 · MrWhite · CC BY-SA 4.0

Do I need to explicitly add every search engine & social media...

Potentially, yes. However, it does depend on how the third party (search engine / social media platform) fetches/caches your images.

If Google image search is a concern then you will need to punch a hole in your hotlinking protection to allow google.com as the Referer. Whilst googlebot will be able to crawl your images initially (because of your first condition that checks for an empty Referer), when a user clicks on an image in "image search", a direct request is made to your site, which sends a Referer of the form https://www.google.com/.

RewriteCond %{HTTP_REFERER}  !^http?://([^.]+\.)?google\.   [NC]

Rather importantly, you are missing the s in https in the above regex, so this negated condition will always succeed and https://www.google.com will be blocked. Google is HTTPS everywhere these days, so you don't need the ? for an optional s. I don't think you need the NC flag either (only malformed bots send uppercase Host headers):

RewriteCond %{HTTP_REFERER}  !^https://([^.]+\.)?google\.

Aside: I have seen http://www.google.com (note HTTP, not HTTPS) used as the Referer by malicious bots, so if anything, these should be blocked.

Or, is there any better way to protect images from hotlinking?

There is no other way. By its very nature, it is unreliable and prone to error.

You should probably only implement hotlinking prevention if it becomes a problem for your site, hampering your site performance or consuming all your bandwidth (or maybe they hotlink everything!). It can even benefit you SEO-wise. I would rather a site hotlinked a few of my images (which I still control), rather than copy and reuse my images without attribution (which I have no control over).

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2019-03-05)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。