Feature preview
The function of anti-crawling interference code is to increase the cost of the whole transfer, it inserts noise characters that do not produce semantic meaning for readers and layout, does not change the structure of the text and the page address, and therefore does not change the search engine's understanding of the page topic. This article explains the position of interference code insertion, the type of collection it can prevent and cannot prevent, and the way it coordinates with sensitive word filtering and content review level.
Will the anti-capture interference code in the text affect the search engine's understanding of the content of the page? It will not change the outward theme expression of the page. The method of interference code is to insert noise characters that do not contribute to reading and semantics in the text, and the page title, paragraph structure and address will not change accordingly. The SEO configuration within the site also works normally. AnQiCMS's anti-capture ability is implemented according to this idea, with the goal of not allowing clean text to be copied in one piece.
It acts on the text rendering process, appearing between paragraph text, not adding a new paragraph of explanation or changing the tag structure. The criteria can be looked at in three layers: the address does not change, the title does not change, and the paragraph order does not change. Any method that maintains these three layers is consistent with the original expression of the page to the outside; if a scheme hides an entire paragraph of text to prevent collection, it already belongs to another type of change and requires separate evaluation.
There is also a robots configuration within the site that is used to agree on the crawling scope, it acts on 'which paths are allowed to be crawled', and it is a different matter from 'what is included in the text after crawling', the two should not be substituted for each other.
The interference code is aimed at bulk搬运: the program directly takes the page text into the database, without cleaning and publishes it. For such behavior, noise characters will be moved together, and the transporter either has to manually clean page by page or write targeted cleaning logic, the cost will increase significantly.
It does not target two categories. One is the citation of excerpts with注明出处, which should not be blocked; the other is the directional collection after cleaning, where any character-level interference can be removed by the rules. Therefore, the positioning of interference codes is to increase costs, not to block access.
On the content security side, there is also sensitive word filtering and keyword replacement, content review, which manages whether the content entering the library is compliant, interference code manages whether the content going out is easy to be taken away, the direction is opposite and they are not interchangeable. There are also JWT authentication and protection against SQL injection and XSS in the security layer, which belong to the boundary of access and input.
The meaning of stratification lies in the controllability of collateral damage. If a segment of content is rewritten by sensitive word filtering, both the version seen on the front end and the version taken away by the collection party will be the rewritten version, at this point it is not necessary to add interference code; conversely, normal extraction usually only takes a sentence rather than a whole paragraph, the probability of noise characters falling into a segment is relatively low, which is also one of the reasons why the interference intensity is controlled at the text level.
Question: Do you need to resubmit the sitemap after enabling interference code?Answer: No. The address and structure have not changed, and the sitemap and link push remain the same.
Question: Will it affect the background text editing?Answer: No. Interference occurs during the rendering process, the saved text in the background is still the original text, and editing and republishing are not affected.
Question: In which cases is it recommended not to open?Answer: Pages mainly with data tables and short lists, as well as scenarios providing text interfaces to the outside, noise characters will make structured data acquisition difficult. This type of content is more suitable for using permission and frequency control processing.
Question: Do there conflict between anti-crawling and content review meetings?Answer: No conflict. The review acts on the incoming text, and the anti-crawling acts on the out-of-station rendering. Both are two stages of the same piece of content.
Preview
When importing historical content in batches, archives with text and pictures are suitable for entering as compressed packages, and neatly formatted plain text content is suitable for entering as tables. The choice between the two entry methods depends on the proportion of resources and fields in the source. This article explains the fields that need to be checked before and after batch import, the arrangement of the status of importing drafts first and then publishing, and the method of rolling back after importing incorrectly, with the help of the recycle bin and interface query.
Preview
Documents can be recovered after being deleted because the deletion of formal documents is executed by moving them to the recycle bin instead of a physical deletion. The document status of AnQiCMS is divided into four types: formal documents, drafts, pending publication, and recycle bin, each corresponding to different visibility and flow paths. This article summarizes the conversion between the four states, the differences between draft previews and public releases, and the usage of scheduled release at a point in time.
Preview
After replacing the link using the background full-site replacement, whether to rebuild the statically generated pages that have already been created depends on whether the site has enabled staticization. The replacement action falls on the data layer, the front-end address is determined by the pseudo-static rules and caching, and there is no need to rebuild for pure dynamic rendering. After staticization is enabled, it is necessary to rebuild during off-peak hours and perform sampling verification, and a 301 redirect should also be set up as a fallback.
