Feature preview
The difference between articles collected and self-written articles in inclusion comes from the page repetition rate and information increment, rather than the source itself. The crawling and indexing judgment is what new content this page provides, and if the collected text is highly similar to existing pages on the entire network, it is likely to be considered of low value. The available processing order is to go through content review and sensitive word filtering first, then decide the scope of publication, and finally enter the sitemap.
Do collected articles and self-written articles have differences in inclusion? Differences exist, but the determining factor is not whether it is collected or written, but the repetition degree and information increment of this page relative to the existing content on the entire network. The crawling system makes an independent judgment for each page, if the self-written page is empty, it will not be included, and if the collected page supplements the structure, data and localization information, it can also be included. The real risk lies in large collection volume and low value per page.
The indexed object is the page itself: whether the text is available, how much difference there is from existing pages, and whether this page has an independent entry and a stable address. The source is collection or editing, which is not included in the judgment items.
Therefore, the collection content usually encounters three types of inclusion issues. The first type is duplication: the same article already exists on multiple sites across the network, and your page is just a copy. The second type is low quality: the text is short, the structure is chaotic, and images are missing, and it is considered to have no display value after being crawled. The third type is out of control during crawling: a large amount of imports at one time, a large number of similar pages suddenly pour into the site map, and the overall quality impression of the site is lowered.
The most direct consequence of the repetition issue is that the page is not selected as a display result. It is indexed but not recognized as a separate page by the indexing layer, resulting in a long-term mismatch between the number of收录 and traffic.
Low-quality issues are manifested as collection without traffic or significant delay in collection. These pages often lack subheadings, lack conclusion sections, and still contain the original site's copyright notice and irrelevant links in the main text.
The risk of losing control of the crawling scope lies in the rhythm. A large amount is released at one time, which does not match the original update frequency of the site, and the crawling distribution will be tilted towards new pages, while the re-crawling cycle of old pages will be prolonged, giving the impression that the entire site is deteriorating.
The collected main text should not be directly entered into the formal document. The available processing chain consists of three steps.
The first step is content review. The system supports content collection from other websites automatically and provides content security settings: sensitive word filtering and keyword replacement, content review. Documents that do not pass the review remain in the draft or draft status, the draft link with preview=true is only visible to internal users, does not participate in the site map, and will not be indexed.
The second step is to supplement the increment. Change the collected text into a page with independent value: add your own conclusion section, add subheadings, replace generalized statements with specific ones for the local or industry, and supplement missing images and tables. Pages without information increment can stay in the recycle bin - deleting formal documents is to move them to the recycle bin rather than physical deletion, and mistakes can still be recovered.
The third step is the control of the publishing scope. Low-value batches are not placed on the site map first, use the time factor - scheduled release at a controllable pace to go online, to avoid a large number of similar pages flooding in on a single day.
The purpose of the sitemap is to inform the crawling system which pages are worth capturing, therefore it should only carry addresses that have already gained independent value.
There are three conditions to determine whether a page should be included in the sitemap: the content has been reviewed and passed an artificial check; it does not duplicate the theme of existing pages within the site; and this page has an internal entry, not just a standalone link. If all three conditions are met, the sitemap is automatically generated, and if not, it remains in draft status first.
AnQiCMS's sitemap supports automatic generation. After the collection batch goes online, it is recommended to observe the crawling results by category: first, check if the crawling volume has increased, then see if the index volume keeps up, and finally check if the traffic appears. Only an increase in crawling without an increase in indexing is usually a repetition issue; if both crawling and indexing increase but the traffic is zero, it is usually a value issue.
Two types of content play different roles on the site. Self-written pages are responsible for establishing citable in-depth content, while collection pages are responsible for filling in the coverage of long-tail issues. Treat collection as a source of quantity and self-written as a source of quality, and the performance of inclusion is expected to be easier.
At the same time, anti-collection protection should be done. The system provides anti-collection interference codes to prevent your main text from being moved in bulk by downstream and becoming someone else's page, thereby diluting your inclusion value.
Question: Will articles collected be considered cheating?The function itself is not a cheating item, the object of judgment is the page quality. Large amounts of repetitive and non-incremental pages will bring quality risks to the entire site.
How many collections are safe at one time?Follow the original update rhythm of the site to increase the number of new pages per day, so that it matches the scale of existing content, which is more important than a specific number.
If the collected page is deleted after inclusion, will it affect the site?Deleted formal documents go to the recycle bin and can be restored. If the page has been indexed, an invalid address will appear after deletion, and it is recommended to use a 301 redirect to a similar thematic page at the same time.
Will content that has not passed the review be crawled?Drafts and pending release status do not enter the formal index page, and only after being converted to formal documents and appearing on the site map and internal entrance will they participate in crawling.
Preview
Anchor text automatic linking added too much can really mess up the structure of the internal links, the chaos comes from one word pointing to multiple things, repeated stacking on the same page, and conflicts with the replacement of the entire station, rather than the function itself. The criterion for judgment is to see if the target pointed to by the same word is single and if there is an upper limit to the number of times it appears on each page. AnQiCMS manages anchor text according to the keyword library to do automatic internal linking, and is配合 the batch rewriting of the replacement of the entire station, the two have different responsibilities and cannot be mixed.
Preview
When multiple sites share a content model, how to prevent fields from interfering with each other? Limit the common aspects to the structure layer, and leave the differences in the value layer: the model and field names should be consistent across sites, default values and options should be configured separately for each site, and the keyword library should also be maintained separately for each site. Before making changes, confirm which templates and interfaces refer to the fields, and then verify the rendering results separately for each site to avoid affecting multiple brand pages at the same time.
Preview
When the article's accompanying image is directly cited by external sites, traffic and server load are counted on the source site, so bandwidth takes precedence over watermark. Anti-hotlinking relies on source verification to reject invalid reference pages, watermark management deals with ownership rather than traffic, automatic image layout in titles and full-site replacement solve the publishing side identification. This article gives the division of labor and implementation methods of both.
