After the garbage update, the fluctuation of rankings, first check which groups of site data
Rubbish update after ranking fluctuations, first check which groups of site data? First check the收录面, then check the content, finally check the word ranking. First look at the two things verified that day. One, the garbage update in September is still fermenting in October, and the site master reported it as the main change this period; two, Google is contributing to the pilot settlement for artificial intelligence, about a hundred publishers get a return on the ad revenue of about one percent. After the two things are added together, the reasons for the fluctuations are divided into two categories: 'judged low quality' and 'display form changed', and the data needs to be checked separately.
First clarify the two reasons for the fluctuations.
The garbage update action targets low-quality and manipulative behavior. After being hit, the performance is a decrease in page index or the visibility of the entire site decreases, not that a word has dropped two places. The change in display form is different: the answer position, artificial intelligence summary, and reference links increase, but the page is still indexed, but the clicks are absorbed by the upstream.
The entry points for the two types of reasons are different. The former needs to check the health of crawling and indexing, and the latter needs to check the coverage of references and original content. It is easy to draw the conclusion that 'the algorithm has punished me' when mixed together, but in fact, it may just be a change in the display structure.
The first group of data to check: inclusion and crawling
View the four items in order:
Is the crawling status abnormal. Has the robots.txt configuration been changed recently, and have the rules mistakenly sealed the directory; can the addresses in the sitemap still be accessed normally?
The proportion of invalid addresses. Error pages and redirect addresses mixed into the sitemap will unnecessarily consume crawling quotas, pushing the pages that truly need to be recrawled to the end of the queue. This is especially important during the garbage update period, as crawling allocation is already compressed.
The difference between the index volume and the submission volume. The number of submitted addresses is much greater than the number of indexed pages, indicating that a large number of pages have been deemed of low value; the difference suddenly expands, usually corresponding to the time point when content is batched online.
The structure of internal entry. Anchor text management is responsible for automatic linking of keywords within the site, if the word table points a large number of words to the same few pages, the rest of the pages become islands, and the natural distribution of crawling decreases.
The data group checked again: content and words
The keyword library is the destination for this step. The keyword library management focuses on maintaining SEO keywords, and the volatility analysis needs to return to this table: first, see which type of words have dropped, whether it is brand words, general words, or long-tail problem words; then see if the landing pages corresponding to these words are still the same article.
Three types of situations are worth paying attention to. The loss of brand words indicates the visibility problem of the entire site; the loss of general words indicates that the page has lost its competitiveness among similar content; the loss of long-tail problem words often means that the page is folded into the abstract, and the display layer is replaced.
The self-inspection actions on the content side are concentrated in three places: merge or rewrite pages with high repetition, pull back the content that has been launched in bulk to a controllable rhythm, and change the expressions with old criteria. If the site has recently done a full-site replacement, it is also necessary to confirm that the rewritten text is still consistent with the word list.
How to deal with the changes on the artificial intelligence side
About one hundred publishers are settled on a small-scale ad revenue sharing settlement in the pilot, signaling that the traffic brought by artificial intelligence displays is beginning to be formally measured. The actual significance for content sites is not equal sharing, but rather that the source of citation becomes more important.
Two things that can be done: use llms.txt to explicitly list pages worth reading, so that large language models do not have to find the focus in the whole site themselves; write the paragraphs on these pages in a self-contained Q&A form, which is convenient for extraction and citation. These two actions do not change the authorization layer, and authorization is still decided by robots group.
Rankings are last looked at.
Ranking is the result, crawling, indexing, and content quality are the reasons. When the cause layer is not clear, look at the ranking, and only repeatedly adjust the title and description, and such changes are exactly the most easily misjudged actions during the garbage update period.
The criteria for recovery should also be placed at the cause layer: the number of failed crawls decreases, the index difference converges, and the display positions of long-tail problem words reappear. The ranking usually recovers after these three.
Common questions
Question: Can a large amount of content be released during the garbage update period?It is not recommended. Batch going online will change the crawling allocation and quality impression of the site, and it is more important to maintain the original update rhythm during the fluctuation period.
Question: How to judge whether it is a penalty or a display change?Check the index volume. A significant reduction in the index is closer to low-quality judgment; stable index with a downward click is mostly a change in display form.
Question: Should we change the title and description first?Don't change it yet. Changing the title when the cause layer is not clear will mix two variables together, making it impossible to attribute later.
Question: Does llms.txt help with fluctuations?It solves whether the model can read the key page, without changing the search side index judgment, and belongs to the complementary action of the display side.