Why is the search console collection report inaccessible, and where is the difference between being crawled and indexed?
Crawling and indexing are two separate processes, not the same thing, a large number of pages displayed in the Search Console inclusion report show that they have been discovered but not yet indexed. The issue is usually not whether you can get the page, but whether it is worth including in the results.The issue resolved by being caught is accessibility, the issue resolved by indexing is value judgment: an address must first be retrieved by the crawler, be able to respond normally, and the main text can be read, before it is eligible to enter the second door;The second door looks at whether this page has independent information compared to the existing content on the site. Therefore, when the report shows a result of no access, it is not necessary to first suspect the server, but to separate the two links and check them first, and then decide whether to repair the content or the path.
Being caught and selected are two different links
The status in the collection report is misleading because it puts two things together: whether the search engine has obtained the page, and whether it is willing to put the page into the results.Crawl to solve reachability, index to solve value judgment, an address must pass through these two doors one after another. The report shows that a large number of pages have been found but not indexed, which exactly indicates that the crawl channel is not broken - the spider has already found them following the links or site map, and what is stuck is the latter link.When judging, break the link: first confirm whether the response code and the content are complete, and then see what incremental content this page provides relative to the existing content on the site. If the address can be obtained and the content can be read, but it still does not enter the index, the problem lies in the content itself, not in the technical channel.
What kind of handling does each report status correspond to
Different status text points to different causes. The page has been crawled but not indexed, usually due to poor page quality or insufficient repetition; The page has been found but not indexed, more often due to low link weight, or the page is not in the crawling queue.Duplicate web page has not selected a standard address, the direction of the standard is not clear; if the server returns an error or a soft 404, it is a response layer issue. What is most easily ignored here is the redirect link: old addresses left after the revision or adjustment of columns. If the 301 redirect is not properly configured, the crawler will repeatedly back and forth between the old address and the new address, and the new page will not receive the appropriate weight.Translate 301 redirect, it is more useful than submitting ten more links.
Which section does the sitemap and link submission manage
The sitemap is responsible for full disclosure. After the Sitemap is automatically generated, search engines can visit according to the list, so that historical pages and content that is updated infrequently are not completely disconnected; link push is responsible for timely informing Baidu, Bing and other engines of the newly added and modified addresses, which belongs to a queue shortcut channel. Both solutions are to make it know that there is a page, but they cannot solve the problem of 'whether this page is worth including'. Pushing acceleration does not guarantee inclusion. This sentence is more practical in reverse: if the inclusion rate is low for a long time, re-pushing is just to resubmit the same rejected answer again.
| Link | Responsible link | Can solve | Cannot solve |
|---|---|---|---|
| Site map | Discovery and revisit | Page lost and checklist missing | Content deemed duplicate |
| Push manually | Accelerate discovery | New content queued at the back | Value judgment of thin text |
| 301 redirect | Weight bearing | Old address invalid, link detour | No increment on the page itself |
Action sequence: repair content first, then repeat
Check and sort by cost from low to high. The first step is to count the parameter links and list pages, and gather the combination addresses that only change sorting, pagination, and filtering from the crawling to avoid them taking up the entire site's quota.Check whether the same topic page has been written as multiple variants of the same content, merge what can be merged, and use anchor text to direct scattered entry words back to the retained page;Step three requires additional content, including template sentences, padded paragraphs, and pages with only images to be updated. The keyword library here is used to assign tasks to a batch of pages: only one core keyword is assigned to a single page to avoid competing with oneself.Edit the content and send the link push again, wait for the next round of report refresh.
How long to come back for review
The index update has a delay, and looking at it too early will only lead to the conclusion that 'nothing has changed.' It is recommended to leave regular content for one to two weeks for observation, and for batch updates, leave for four weeks. During this period, keep an eye on three numbers: the proportion of items found in the report that have not yet been indexed, the actual landing traffic corresponding to the indexed pages, and the number of successful entries in the sitemap submission records. If only a few tens of pages have been processed, the proportion not moving is normal, and it is more reliable to check each item on the page list.
Common questions
Question: The page shows that it has been crawled but not indexed yet, should I resubmit?Do not submit yet. This status indicates that the crawling is complete, but what is missing is the indexing intention. Check if the content has independent information, if it is highly similar to existing pages within the site, and submit it after making changes.
Question: Why is the new site收录收录 so slow, is there a problem with the crawling channel?The new site is more about low link weight, the address is found but not included in the indexing queue. Make sure the sitemap is ready, use active push to submit core pages, and at the same time, make the hierarchy from the homepage to inner pages as shallow as possible, which is more effective than repeatedly checking the server.
Question: Should parameter pages be prohibited from crawling uniformly?All variations that are easy to block and obscure normal ones should be blocked. A more stable approach is to normalize the combined address with parameters and then only restrict the forms without content in the robots configuration.
Question: Will the deleted page still occupy the index?It will remain for a while. After deletion or merging, give it the correct 301 redirect or an explicit out-of-stock response, and the entries in the report will gradually disappear.
Question: How can you determine whether it is a content issue or a technical issue?Compare a rejected address and an included address in the same list: response code, body length, unique information volume, number of internal links. Only when the last item is significantly different, the problem is in the content.