Update an Old Post or Write a New One? A Decision Rule

Update the old post when Search Console shows it already gets impressions for the search you care about. Write a new one only when none of your pages appears for that search, or when the page that appears is about something else. When two of your posts appear for the same queries, merge them into one and redirect the weaker URL.

Get the three numbers

Open the Search Console Performance report and set the date range to the last three months. That help page defines the metrics: impressions are how many times your site appeared in Search results, and average position is the average position of your topmost result.

For the post you are deciding about:

1. Add a Page filter with the post's exact URL.
2. Switch on Clicks, Impressions and Average position above the chart.
3. Open the Queries table and export it.

Then do the reverse for the topic. Remove the Page filter, add a Query filter containing the main phrase, and open the Pages table. This shows every URL on your site that appears for that phrase. If more than one does, note them. You will need that list in the merge section.

Before you conclude that a post has declined, widen the date range. Google's guide to debugging traffic drops recommends looking at 16 months so that a seasonal pattern is not mistaken for a drop.

The decision rule

Find the first row that matches what you see.

What Search Console shows	Decision	First action
The post has impressions for the target query at an average position of roughly 8 to 20	Update	Improve the answer for that query. See "What to change" below
The post is near the top, with many impressions and few clicks	Update the title only	Rewrite the title to say what the page answers. Leave the body alone
The post gets impressions mostly for a query it does not really answer	Write new	Create a page for that query and link to it from the old post
Two of your posts appear for the same queries	Merge	Combine into the stronger URL and redirect the other
The post has no impressions for anything after several months	Neither, yet	Check that it is indexed and that the topic is one people search
The post ranks and brings visits, and one fact in it is out of date	Correct in place	Fix the fact. Do not restructure a page that works
No page on your site appears for the query	Write new	Confirm the query matters to buyers first

The 8 to 20 range is a working threshold of ours, not a Google rule. The reasoning: a post in that band has been understood as relevant and is being outranked, so improving it starts from an existing position. A new URL starts from none. Average position is an average across searches, so read it as a band and not as an exact rank. Google's traffic-drops guide also notes that positions are not fixed in place.

For the "many impressions, few clicks" row, Google's documentation on title links recommends titles that are descriptive and concise. Compare your title with the query. If the query is "PP vs PET bottles for essential oils" and your title is "Material Guide", the title is the problem.

What to keep when you update

An update that throws away what was working can lose the position you had. Before you edit, list what stays.

Keep:

• The URL. Changing it turns an update into a move.
• The sections that match your top queries. In the exported Queries table, mark the five queries with the most impressions. Find the section that answers each one. Those sections may be improved but not removed.
• Links pointing in. Check which of your own pages link to the post and what their link text promises. The updated post must still deliver that.
• Anything first-hand: your own measurements, photos and process notes. This is the hardest material to replace.

Change:

• The opening. Put the direct answer to the main query in the first two or three sentences.
• Outdated facts. Check standards editions, regulations, specifications and prices against their sources.
• What the top results have and you lack. Search the main query, read the pages above yours, and add what a buyer would miss on your page. Add from your own knowledge. Do not paraphrase theirs.

The date. Change the visible date only when the content has really changed. Google's helpful content guidance lists changing the date of pages to make them seem fresh, when the content has not substantially changed, as a warning sign. The same list questions adding or removing a lot of content mainly because you believe it will make the site seem fresh.

Write down the date of the update and the three numbers from before it. Without a baseline you cannot tell later whether the update did anything.

When to merge, and when to redirect

Two posts overlap when the Pages table for one query lists both of them, or when their exported query lists share most of their top entries.

Example. A fictional closure supplier has these two posts:

	Post A: "How to choose a lotion pump"	Post B: "Lotion pump buying guide"
Impressions for "how to choose lotion pump"	More	Fewer
Links from other pages on the site	Several	One
Unique content	Output table	Section on neck finishes

The steps:

1. Pick the URL to keep. Choose the one with more impressions and more links pointing in. Here that is A.
2. Move the unique content. Copy B's neck-finish section into A where it fits. Drop what duplicates A.
3. Redirect B to A with a permanent redirect. Google's page on redirects says a permanent redirect tells Google to show the new target in search results, and a temporary one keeps the source page.
4. Update internal links that pointed to B so that they point to A. Google's page on consolidating duplicate URLs says to link within your site to the canonical URL.
5. Check after a few weeks. Inspect B's URL in Search Console and confirm it is reported as a page with a redirect.

When not to merge: the two posts serve different searches even though the words overlap. "Lotion pump vs spray pump" and "how a lotion pump works" share a phrase and answer different questions. Keep both and link them to each other.

When to redirect without merging: a post is obsolete, has no unique content worth keeping, and another page covers the subject properly. Redirect it to that page. If no page covers the subject, let the old URL return a not-found status. Do not redirect it to the home page. A visitor who lands on the home page after clicking a specific result has been sent to the wrong place.

When a new post is the right answer

Write new when one of these is true:

• The Pages table for the query is empty. Nothing on your site appears.
• A page appears, and it is a product or category page that should stay a product or category page.
• The old post would have to change its subject to answer the query. That is a new article with an old URL, and it will stop serving the queries it serves today.

Link the new post from the old one and from the relevant product page on the day you publish it.

What a tool can and cannot do here

Blogo does not have an automated workflow for refreshing existing posts. It creates new drafts and does not edit or overwrite pages that are already live, so the update and merge steps above are manual work in your CMS.

What it does cover is the question before this one. When you connect Search Console, Blogo's plan reads your queries and existing pages and recommends what to write next, with the evidence shown so that you can accept the pick, change it or choose another.

None of this guarantees a better position. It makes sure that the hours you spend go to pages with evidence behind them.

Once the decision is "update", the content refresh checklist covers the revision itself.