Which one to manage first - the article's accompanying image is directly displayed on other sites

The article's illustration is directly displayed on other sites, which one to manage first, bandwidth or watermark? Manage bandwidth first. When the image is directly referenced by an external site, the request is sent to the source site, and the traffic and server load are borne by the source site, which is an access-level issue; watermark management deals with attribution, even if the watermark is intact, the traffic that is referenced still counts on your account. So the sequence is to first use source verification to block invalid references, and then on the publishing side, use watermarks and titles to automatically match illustrations to leave clear identification.

What exactly does hotlinking consume?

The hotlink consumes not the storage space, but the bandwidth, connection count and response time with every request: when the external page is opened, the browser takes the image address back to your site to fetch the image.The parties involved have a very direct approach when clarifying such behaviors, Patchstack discusses the WordPress image hotlinking guide, writing 'Hotlinking steals your bandwidth' and 'increasing your server load', what it takes is bandwidth, and what it raises is the server load, not storage.

A single image referenced once or twice does not show much difference, but when collected collectively, it is different: a site that moves popular images in bulk will amplify the request volume of the same image to a peak on the access curve of the source site. When troubleshooting, do two things first, put the traffic curve of the past seven days and the access source of the images together, and confirm which sources are not your own domain name.

How to add source verification?

The source verification checks the referrer page address in the request header. The Web server layer adds a rule: allow referrals from this site, and return a forbidden access status code for other sources.That Patchstack article on WordPress防盗链指南 states, “if the request comes from an invalid referer, the server responds with a 403 Forbidden status code.” The page returns a forbidden access according to the invalid reference.

Configure blocking at both the CDN and caching layer; if only the source station is blocked, the request will still return to the source station before being interrupted, and the consumption has already occurred. Third-party edge blocking also has ready-made capabilities; in the Cloudflare console, such settings can be placed under Scrape Shield and blocked unauthorized site references using its 'disallow hotlinking' option.

It is necessary to be clear about two costs:

• The reference page address can be forged, and source verification cannot be regarded as the only defense line; it blocks direct references that do not modify the code.
• Blocking will interrupt legitimate references. Partners in accordance with the agreement to reference, readers forwarding the page to social platforms, will all see invalid images, so a whitelist needs to be left.

The watermark solves the issue of ownership.

Watermark management does not handle traffic, it handles the issue of 'who is this image of.' Adding a watermark will change the image itself, and sometimes it will make the image larger and slower to access, so it should not be used as a means to save bandwidth. Its true value is in collection disputes: after the content is moved, it is difficult for the forwarder to cleanly remove the identification.

AnQiCMS divides its capabilities on this line into three parts: watermark management is responsible for adding identifiers to published images; anti-crawling interference codes are used to protect content from being bulk-crawled, and are combined with automatic image matching according to the title content to allocate images for articles, in order to avoid confusion of source when the same image is reused repeatedly; the full-site replacement tool can change keywords or links within the site in one go when batch errors are found, reducing the cost of manual page-by-page modification. These three things are on the publishing side, cannot block requests, but can still make the content carried away carry the source.

The division of labor between image matching and caching

Separate the two types of actions:

1. Perform interception: Source verification rules, edge layer reference restrictions, whitelist list, these three determine whether the traffic is still being consumed.
2. Then mark: The position and depth of the watermark, whether the rule for automatic title image matching is reasonable, this determines whether the source can be identified after it is taken away.
3. Finally, check: After a week, pull the visit source again to see if there are any external site domains in the new sources.

The common consequence of reversing the order is: The image is added with a heavy watermark, the traffic is still taken away, and the page becomes slower.

Common questions

Can adding only a watermark prevent hotlinking?No. The watermark does not change the request target, the image is still loaded from the original site, and the traffic consumption still occurs.

After returning 403, will the search engine not receive the image?It is possible. You need to allow image crawling for search engines in the rules, and at the same time, normalize the image addresses within the site to avoid treating legitimate crawling as invalid references.

What should you do if a split image appears on the historical page after interception?There are two methods: replace the blocked source with a substitute image with an identifier; or rewrite the image addresses on the historical page in bulk to new addresses. This step can be done with a site-wide replacement tool, which is faster than page-by-page editing.