When search traffic to an article from last year declines, you may wonder whether to write a new article on the same topic. Editing the existing one can feel risky too, particularly if you worry about losing rankings. But the age of an article alone cannot tell you which option is better.
If the question the existing article answers is still the same, consider updating it first. If the task the reader wants to complete has changed, consider a new article. Before looking at the publication date, I write one sentence stating what the reader should be able to do after reading. If that sentence is unchanged, I reconsider whether there is a sufficient reason to create another URL.
1. Separate four options: keep, update, consolidate, or write a new article
Thinking only in terms of “write something new” or “update” can lead you to change articles that do not need work. Start by sorting existing articles into four groups. The table below provides editorial decision criteria, not Google's ranking formula.
| Option | Decision criterion | Illustrative example |
|---|---|---|
| Keep | The question and answer remain valid, with no clear gap | A method and worked examples for converting product units |
| Update | The core question is unchanged, but the interface, procedure, conditions, or evidence has changed | Instructions for a tool whose menus have changed |
| Consolidate | Several articles answer the same question, with unique information scattered between them | The same account deletion process split across two articles |
| Write a new article | The reader's purpose or circumstances differ enough to require a separate explanation | Creating an account versus designing permissions for multiple employees |
Having several articles on a topic is not inherently wrong. “How to write meeting notes” and “How to track actions agreed in a meeting” are related, but people read them for different purposes. If someone who reads the first immediately needs the second, you can link them. Looking at whether the reader's next action differs is more accurate than counting how many words the articles share.
2. Compare the task the reader wants to finish, not just the keywords
Suppose you already have an article called “Creating UTM Links for a Newsletter,” and the new candidate is “How to Set Up Newsletter UTM Tags in 2026.” If only the year has changed, the reader's task is the same, and the required setup is largely unchanged, updating the existing article is the natural choice. “Why Newsletter Visits Appear but Purchases Do Not,” however, addresses a measurement problem after the link has been created and can be a separate article.
If the decision is unclear, hide the existing article's title and read its first paragraph, subheadings, examples, and final action. If these largely overlap with the new article's outline, question whether it really addresses a different problem. When changing only the words in the title leaves essentially the same body, readers have little reason to read both.
If Search Console data is available, also examine the queries for which the page appears. Comments, inquiries, and recurring questions within the company provide other clues. A single query appearing in the report does not by itself require a separate article. If one short paragraph can answer it, adding that paragraph to the existing article may be more convenient for the reader.
3. Start an update with the parts that prevent readers from completing their task
An update is more than polishing wording or adding length. First, check whether a reader following the article can still achieve the same result in the current interface. For tool instructions, review menu locations, account requirements, the boundaries between free and paid features, and how to verify the result after saving. For a product explanation, check that the described features and support remain accurate.
Suppose a hypothetical draft ends with “Click Connect in Settings, and you are done.” If the reader cannot verify a successful connection, it needs another step, such as “On the connection status screen, confirm the target account name and check that one test item appears correctly.” Use menu names verified in the actual tool. Filling in a missing step like this is different from merely replacing sentences.
I divide the update list into factual errors, missing explanations, and structures that are difficult to read. Correcting an inaccurate feature description takes priority over changing a transition word. If the core answer is buried after the introduction, I also change the order. I do not lengthen sections that already explain enough. Google's people-first content guidance likewise asks whether readers receive enough help to achieve their purpose and cautions against changing dates without substantive changes.
4. Check each article's distinct role before combining similar posts
Do not delete a low-traffic article simply because its title resembles another. One may explain how beginners can get started, while the other troubleshoots a problem for people already using the service. Even with less traffic, the latter may deserve to stay if it answers an important work-related question.
Place the two consolidation candidates side by side and mark their shared answers and unique information. If the actual procedure is the same and the only difference is an outdated interface, consolidation may make sense. If they cover different plans or product versions, however, consider whether combining them could cause readers to misunderstand which conditions apply to them.
Google's canonical URL guidance explains how to indicate a preferred URL for duplicate or very similar pages. It does not mean that articles with somewhat similar topics must always be combined. Choose consolidation when it gives readers a more complete answer. Do not turn it into a blanket rule that removing low-click articles raises rankings across the site.
Once you choose articles to combine, record how you will select the URL and content to keep. Consider existing shared links, completeness, and the topic you intend to maintain, as well as traffic. Simply joining two bodies together often leaves repeated introductions and conflicting conditions. Explain shared material once and move each article's unique examples to the right places. Then check whether readers familiar with either original can still find the answer they need, whichever route they take.
5. Decide separately whether to edit the body and change the URL
When updating an article that answers the same question, keeping its existing URL is a reasonable default. Changing the title's wording does not necessarily require changing the address. Keeping readers' saved links and links from other articles connected to the same explanation also makes maintenance easier.
If you combine two articles and retire one URL, decide where that address will lead. Choose a relevant replacement page rather than simply sending it to the home page. For a permanent move, you can consider a permanent redirect such as 301 or 308 in line with Google's redirect guidance. Check separately how to configure it on the platform you manage.
For a normal update, distinguish the publication date from the modification date. Preserving the original publication record and showing the date of a substantive update helps readers understand the article's history. A brief note such as “Updated pricing and interface examples to reflect the current version” is also useful. If dates appear both on the page and in structured data, they should match, as explained in Google's date guidance.
Articles whose year-specific record matters are an exception. Overwriting last year's event recap or a particular year's research results with this year's content confuses readers looking for the historical record. Keep the original as a record of that time, create a separate article for the new research or event, and link them.
6. Record the original question and how you will verify the update
Before starting, record the URL, core question, problem, scope of the update, and result to verify. For example: “The signup interface has changed, so readers can no longer follow step 3. Replace the example with the current screen and check whether another team member can complete the process from the beginning.” This provides a clear acceptance criterion. Even if search clicks do not increase, you can verify the instructions' accuracy immediately.
If many articles need attention, do not try to review them all on the same day. Start a list with articles containing incorrect information and articles that are frequently shared. Prioritizing the risk of readers making a wrong decision or being unable to proceed is more useful than sorting solely by age. Recording the next review date and the responsible person can also reduce the burden of researching everything from scratch when the same issue returns.
Assess search performance on a separate timeline. First, check that the updated page opens correctly and that relevant internal links and necessary settings remain intact. Then observe queries, clicks, and readers' subsequent actions. Google's recrawl request guidance explains that a request does not make changes appear in search immediately or guarantee indexing. Repeated requests for the same URL do not make the process faster.
Instead of declaring success or failure from one or two days of clicks, choose a comparison period that accounts for existing traffic volume and topic seasonality. If several changes were made together, also record that attributing the result to any one change is difficult. At the next editorial meeting, alongside “How many new articles did we publish this week?”, consider “Which obstacle did we remove for readers in an existing article?” New articles and updates are both choices for solving that problem.