So Outside Technology Security CMS
AnQiCMS
Online Demonstration

The natural flow decreases week by week, when should we go back and modify the old article?

📅 2026-11-01 👁️ 0

The natural flow decreases week by week, how long should we go back and modify the old article? The judgment line should not be determined by the calendar, but by the decline of a single page: The review criteria on the day are that a page's natural flow decreases by more than 20% within 90 days, indicating that it is losing relevance or ranking ability, and it should be changed at this time, rather than waiting for the unified inventory at the end of the quarter. The cumulative decline week by week is normal fluctuations; when a content item drops below this line, it is the effect of content decay.

Why is the rate of decay easily underestimated?

The same statistics show that the average article loses 1.21% of its traffic per week, and it will be halved in about 57 weeks. The number of less than 1% per week looks small because it is multiplication rather than addition at work, and the decline will become very noticeable when the ranking drops from the first page to the second page.

Another set of numbers explains why it is worth scheduling the revision of old articles: the search engine research cited in the same statistics shows that the monthly average of natural browsing has increased by 106% after updating and republishing old articles. This means that the return on investment of revising the article is usually faster than writing a new one.

What signals mean it's time to revise

Sort by trigger strength, first look at these four signals:

  • Natural traffic on a single page has dropped by more than 20% in the past ninety days, which is the most direct signal;
  • The ranking position has not changed, but the click-through rate has dropped, indicating that the summary is out of sync with the needs, or has been overshadowed by new answer-type content;
  • The facts and numbers on the page are outdated, and the competitors are using data from the current year;
  • The search intent has drifted, and the people coming in are doing something else, for example, the page originally written for decision-makers is now full of steps to find.

The first two are signals of quantity, and the last two are signals of quality. Only when there are signals of quantity, check the technical aspects (collection, availability, experience indicators) first, and the signals of quality need to be adjusted in the text.

How should the text be reordered?

The text should not start from the latest article, but from the article with the greatest loss. The recommended screening criteria: sort the absolute values of natural traffic loss in the past three months, take the batch that is closest, and then exclude those that have already repeated the content on the current network.

In order, first fill in facts and numbers, then fill in the structure, and finally change the title and description. The reason is that the most common cause of attenuation is outdated content, and structural changes will trigger crawling and understanding again, so it should be done after filling in the facts, so that the effect of one revision can be fully reflected in the same round of observation.

During the revision process, two things should be handled concurrently. First, the in-site keyword library: Go over the core and related keywords of this article, check if the words registered in the library still match the page intent, and also see which words have been occupied by other content to avoid self-collision. Second, duplicate content: If only one article of the same theme is revised, the other will continue to分流, and the whole-site replacement tool is more efficient in this kind of batch unification than manual revision, for example, replacing expired product names and old activity slogans all at once.

Leave traces after the revision is done.

After the revised release, make sure that both search engines and readers can see this change. Within the site, separate the update time from the release time and record them separately. The time factor plays a role here: scheduled publishing controls when the content is visible to the public, and the update time indicates when it was reviewed. Both are documented, providing readers with a basis for judging credibility and allowing you to distinguish which fluctuations correspond to which changes when reviewing the data later.

Do not release all the old articles at the same time during batch revisions. Use scheduled publishing to distribute them over different time periods, which can observe the effect of individual articles while also avoiding a queue caused by submitting too many addresses to the push interface at once.

Review the cycle on a weekly basis instead of daily. After going live, at least two complete weeks should be observed, and then the decline line within ninety days should be checked to determine if a second revision is needed.

Common questions

Do all old articles need to be updated regularly?No need. The frequency of updates for evergreen content (such as tool usage, concept explanations) is low, and pages with time and numbers are the high-risk areas for decay.

Will changing the title cause the original ranking to be lost?There is a risk, and it is worth making changes only when the intent is changed rather than the wording. Simply changing the title text without moving the main content often only brings a waiting period for re-examination.

How long will it take to see the effect?The effect of re-launching after a revision is usually seen in clicks and impressions within one to two weeks, but ranking recovery takes longer, it is more稳妥 to evaluate according to a quarter.

How to judge if this has been revised to the end?After two rounds of revisions, if the ranking is still declining and the search intent has been occupied by a new answer form, it is more appropriate to merge the content or rewrite it as another article; continuing to patch only extends the observation period.

Related articles

How much difference is there in the pass rate of mobile performance on mainstream website building platforms?

In the data checked on the day, the difference in the pass rate of mobile performance between the high and low positions is about thirty percentage points. Under the same criteria, the mobile end of the entire station is about nine percentage points lower than the desktop end. This article breaks down the gap into two parts: platform layer and site layer, explains that platform selection determines the baseline, and page optimization determines whether you can reach the top of the platform, and gives the sequence of acceleration actions.

2026-11-01

AI crawlers are not just the leading few, should the budget for crawling be redistributed?

The flow of AI crawlers is no longer concentrated in just a few major ones, the proportion of the part outside the head has increased to about five times the original within a year. This article uses the current day's verified crawling distribution data to explain why assigning robots.txt to just a few old faces is no longer enough, and provides the order of redistributing crawling budgets by crawler group, as well as the division of labor between robots.txt and llms.txt, and the verification method after the modification.

2026-11-01

Major versions should come with a new default theme, what should be tested before the old site is upgraded?

When a major version comes with a new default theme, the template and style references of the old site are the primary test objects. Before upgrading, run the template rendering checklist in the test environment, check if the custom template depends on the style and structure of the old theme; then verify the content fields for renaming or reduction to avoid failure in value retrieval; finally, prepare backups and rollback points that include static files, and confirm that you can roll back to the original version on the same day.

2026-11-01

The open-source program announcement says that the historical version has been hacked, check which directories before upgrading.

When releasing a security announcement for malware released open-source programs, you should check four places before upgrading: the write and cache concentrated running directory, the pseudo-static rules and site rewriting configuration, the abnormal files in the upload and template directory, and the scheduled tasks and background login logs. First collect evidence, then clean up, and finally update the version. Directly covering the upgrade will retain the malware together and also destroy the clues for subsequent investigation.

2026-11-01

How many times is the brand mentioned in AI answers, and how to measure this indicator?

How many times is the brand mentioned in AI answers, which can be measured by three indicators: visibility, average position, and sentiment tendency: Visibility is the proportion of questions mentioned, average position shows which part of the answer it appears in, and sentiment tendency determines whether the mention is positive or negative. This article explains how to conduct a large-scale measurement by fixing the question set and engine range, conducting periodic retests, and explaining how llms.txt and the background GEO module receive the measurement results.

2026-11-01

The proportion difference of AI crawlers in different industries is very large, who should we compare with?

The two groups of data checked on the day illustrate the industry differences in the blocking strategy: less than 20% of the sites in the full-site sample explicitly block at least one type of AI crawler, while the blocking ratio in the news and publishing industry is much higher than that of development tool sites. This article explains that the baseline should be selected with the same industry and purpose, and the training crawler and search crawler should be blocked separately, and the division of labor for content-side anti-collection and access layer rules should be given.

2026-11-01

Can llms.txt replace robots.txt to manage crawling?

llms.txt cannot replace robots.txt in terms of crawling. The division of labor confirmed on the day is: robots.txt determines whether it can be crawled and which paths can be accessed, while llms.txt is about what to look at first after the model comes in. This article explains the levels of solutions provided by the two files, the order of priority when configured simultaneously, and how to verify whether the changes have taken effect.

2026-11-01

Self-hosted content systems need to allocate a few hours for maintenance each month.

The maintenance hours of self-hosted content systems mainly fall on two things: patches and backups. The operation口径 on the day of verification is that critical to high-risk level patches come once every six to eight weeks, with obvious labor costs in addition to the computing power bill. This article divides the monthly maintenance of the small station into two segments: cannot be saved and can be saved, and gives the method of working hours budgeting, and explains which segment can be saved by the technology stack and deployment method.

2026-11-01