So Outside Technology Security CMS
AnQiCMS
Online Demonstration

The page shows that it has been crawled but not indexed, is it a broken link or a quality demotion?

📅 2026-11-01 👁️ 0

The page status shows that it has been crawled but not indexed. Is there a problem with the indexing link or the quality has been demoted? First, state the conclusion: The 'has been crawled' in the status itself indicates that the crawling link is working, the crawler can come in and read the content, and the problem is mostly not with the link, but with the selection side of the inclusion - When the system doubts the quality of the entire site, it will actively reduce the number of pages indexed. Therefore, the investigation should shift from 'whether it can be caught' to 'whether it is worth including', and then分流 along with the batch pages.

Separate the two links first

Crawling and indexing are two independent pipelines; do not mix them into one for diagnosis. The crawling process looks at accessibility: whether robots have opened the corresponding directory, whether the detail page is listed in the sitemap, and whether the server returns a normal page or an error response to the crawler.As long as the log leaves a record of crawling, the link is working. The collection process focuses on selection: within the same batch of addresses, the system evaluates whether the topic is repeated, whether there is independent information increment, and whether it is worth occupying the index space.The majority of cards that are 'already indexed but not yet included' are stuck in the latter rather than the former. The starting point of the judgment is to confirm in the index statistics and site map report that this address has indeed been indexed and fully indexed, first excluding the possibility of incomplete reading due to deep script rendering or redirect chains, and then discussing quality.

The scope of quality impact

Why quality concerns can affect indexing, the official has spoken quite directly in a recent public statement: If the system is seriously concerned about the quality of a website, it will reduce the number of pages it indexes.This sentence is worth experiencing word by word—it is not scored page by page, but treats the quality of the entire site as a prerequisite; once the prerequisite is questioned, the performance is that a large number of pages have been indexed but stopped outside.Fall into self-check, in fact, there are only two criteria: first, whether these pages that have not been included are highly similar to each other, and second, whether the new content provides additional information compared to the existing pages.When the overall dimension of the website is questioned, it is more effective to first converge the low-quality clusters than to催 a single address.

How to分流batch pages

Export the addresses that are stopped at 'Already crawled but not indexed' in batches, and examine them with three rulers: thematic repetition, information increment, and whether the source is content collection. Content collection is an efficiency tool, but pages collected in batches often carry identical wording and structure to the original, and are most likely to be trapped outside of indexing. Pay attention to this type first. The results of the three rulers determine the direction of action.

Symptoms Check first Handle
List multiple items under the same theme Thematic repetition Merge into one page
The page only changed the title Information increment Supplement unique content
Batch source consistent Whether content collection Withdraw or redo
Normal crawling but zero collection Overall site quality Convergence of low-quality aggregation

Disposal order and record keeping

The order is more important than strength. The first step is to subtract: withdraw or merge pages that are purely collected and have zero increments first, so that they do not continue to drag the overall impression of the entire site;The second step is to organize, gather similar requirements scattered across multiple pages into a few carrying pages, and conveniently clean up keywords in the keyword library that point to duplicate targets, avoiding the same word directing access to several similar pages.Step three involves creating links, reviewing the anchor text destinations, and consolidating excessive anchor text to specific landing pages to ensure clear weight distribution rather than dilution. After making the changes, resubmit in batches, recording the addresses, actions, and submission dates for each batch, and check the indexed numbers after a period of time.The records are kept to be able to review which type of action truly took effect.

Common questions

Question: If the content collected has not been indexed for a long time, do I need to催收录催 every day?

Answer: No. Urging indexing does not solve the problem of selection and rejection. What is truly effective is to first reduce the theme repetition, supplement information increment, and pull the overall site quality back, and the indexing will naturally relax.

Question: Should the pages collected by content collection be deleted all at once?

Answer: Not necessary. Do not cut all at once. Keep and observe those with independent information, localized rewriting, and incremental supplement; withdraw or redo those that are identical to the original text and have zero collection in batches, so that they do not stop at the index and drag down the overall site judgment.

Ask: How can you distinguish between link and quality issues?

Answer: Check the crawling records. Only check robots, sitemaps, and accessibility if there are no crawling records; if there is crawling but no inclusion, prioritize processing batch pages according to the quality criteria.

Related articles

The active push protocol is only supported by a few search engines, does another one count as a push?

The active push protocol informs search engines about which URLs have changed, requests priority crawling, but only a few participate. The one that does not participate will not change the crawling and inclusion judgment just because you have sent a notification. You need to separate discovery and inclusion, follow the engine's分流 actions, let the sitemap be responsible for the bottom line, push for incremental, and then use each result to check whether it has really entered the index after the push.

2026-11-01

When the sitemap exceeds the limit, it can only be split into files, and before splitting, you need to clear which type of address.

The site map exceeds the single file limit and must be split into multiple files using an index file for aggregation, but before splitting, it is necessary to clean up three types of addresses: pages with error status codes, redirect addresses, and pages with屏蔽 marks that are written into the map. The cleaning order is wrong, and the each file after splitting is still wasting crawling quota, the collection efficiency will not improve.

2026-11-01

Several thousand articles need to be moved, should it be imported using a compressed package or a table?

When moving thousands of articles, the basis for choosing between compressed package import and table import is not the quantity but the material form: batch import using ZIP compression packages for text with attachments and rich text, and batch import using Excel tables for neatly organized fields. First align the content model and custom fields, and then use the import interface for title duplication check to control duplicates, and only the failed batches can be safely rerun.

2026-11-01

When starting a site with a container image, should the default port and background address be changed together?

When starting a station using a container image, whether to change the default port and backend address at the same time depends on where the traffic comes from: After the site is behind the reverse proxy, the container listening on port 8001 only needs to match in the mapping, the default port does not need to be changed; what needs to be received is the exposed surface of the backend address. Before going online, enable the built-in protections such as JWT authentication, sensitive word filtering, captcha, and rate limiting first, and then verify it once from the external network.

2026-11-01

How to plan the column structure and classification for a single backend to manage multiple sites without conflict

When managing multiple sites with a single backend, the place where column structure and classification are most likely to interfere with each other is when reusable definitions and isolated data are mixed together. This article explains by separating the shared layer and the isolation layer: the definition of the content model can be reused across multiple sites, the classification tree, column aliases, and visibility range should be planned independently for each site, batch operations at the whole-site level are disabled by default and explicitly enabled per site, and a landing sequence and a corresponding table are provided.

2026-11-01

Can deleted articles be retrieved, and how are drafts, pending publication, and recycling stations divided?

Deleted articles can usually be retrieved: In the AnQiCMS backend, deleting formal documents is not a physical deletion, but moving them to the recycle bin, from which they can be restored. Each of the four document statuses has its own boundaries - formal documents are visible to the public, drafts are only in the background and preview links contain the preview tag, pending publication waits for the set time to take effect, and the recycle bin accommodates deleted content. This article explains the appropriate operations for each and the safe sequence for bulk cleaning.

2026-11-01

How to import articles from the old station table once, if the fields do not match

The order of handling the mismatch of fields when importing the exported table of the old station to the new system is: first select the channel and then discuss mapping, the three columns of fixed title, alias, and category must be mapped, then determine the default value strategy for custom fields, and finally use title search to check if it already exists to avoid repeated imports and sample check the import results

2026-11-01

On the day of replacing the host, the domain resolution needs to be moved, and how long in advance should the cache time be reduced to be safe.

The key to migrating domain name resolution is not on the day of the switch, but in advance, by lowering the caching time of the resolution to make both new and old sides converge to the same record as soon as possible. Generally, adjust the cache value one to two days in advance, let the old environment run for a few days after the switch, and hand over the redirection and site map to the new address. Email records are easiest to miss, the effective window is uncertain, and after the switch, you need to check the inclusion status with each search engine separately.

2026-11-01