Refreshing and Pruning Old Posts
Audit your old posts with written rules, decide to keep, refresh, redirect or remove each one, build a redirect map without chains or loops, and refresh posts honestly.
In this lesson you will
- Audit posts with written rules
- Choose keep, refresh, redirect or remove
- Build a redirect map without chains
- Refresh a post honestly
About 24 minutes
Priya looks back
After a year, Priya has fifty posts. A few still bring most of her readers. Some are out of date, one is a rant she regrets, and two cover the same ground as newer, better posts. Leaving old posts alone is easy, but a blog full of stale pages is harder to trust and harder to maintain. Advanced bloggers run a regular content audit: a list of every post with a decision beside it.
Four possible decisions
- Keep. It still works. Leave it alone.
- Refresh. The topic is good but the post has slipped. Update facts, fix links, improve the photos and answer the question better.
- Redirect. A better page now covers the topic. Send the old address to it with a permanent redirect.
- Remove. The post has little value and nothing replaces it. Take it down.
Write the rules down
A rule helps you decide the same way every time. The program below audits seven made-up posts. If a replacement exists, it redirects. Otherwise, if visits fell by 40 per cent or more, it refreshes. Otherwise, if the post has under 50 visits and no inbound links, it removes it. Anything else is kept. The numbers 40 and 50 are my choices for the example, and you should pick your own.
# MADE-UP audit: (slug, visits this year, visits the year before, inbound links, replacement)
posts = [
("start-seeds-windowsill", 2400, 2300, 6, None),
("best-spade-2022", 90, 400, 2, "tools-guide"),
("slug-rant", 20, 25, 0, None),
("compost-basics", 800, 1500, 3, None),
("seed-saving-old", 60, 70, 1, "seed-saving"),
("allotment-history", 15, 18, 0, None),
("mulch-myths", 300, 310, 1, None),
]
def decide(visits, before, links, replacement):
if replacement:
return "redirect"
if visits / before - 1 <= -0.4:
return "refresh"
if visits < 50 and links == 0:
return "remove"
return "keep"
tally = {}
for slug, now, before, links, repl in posts:
action = decide(now, before, links, repl)
tally[action] = tally.get(action, 0) + 1
print(f"{slug}: {action} ({now / before - 1:+.0%})")
print("tally:", dict(sorted(tally.items())))
redirects = {"best-spade-2022": "tools-guide", "seed-saving-old": "seed-saving",
"tools-guide": "best-spade-guide"}
def follow(url):
seen, hops = [url], 0
while url in redirects:
url = redirects[url]
hops += 1
if url in seen:
return None, hops
seen.append(url)
return url, hops
long_chains = [u for u in redirects if follow(u)[1] > 1]
print("chains over one hop:", long_chains)
flat = {u: follow(u)[0] for u in redirects}
print("flattened:", flat["best-spade-2022"])
redirects["a-loop"] = "b-loop"
redirects["b-loop"] = "a-loop"
print("loop found:", follow("a-loop")[0] is None)
start-seeds-windowsill: keep (+4%)
best-spade-2022: redirect (-78%)
slug-rant: remove (-20%)
compost-basics: refresh (-47%)
seed-saving-old: redirect (-14%)
allotment-history: remove (-17%)
mulch-myths: keep (-3%)
tally: {'keep': 2, 'redirect': 2, 'refresh': 1, 'remove': 2}
chains over one hop: ['best-spade-2022']
flattened: best-spade-guide
loop found: True
The tally is {‘keep’: 2, ‘redirect’: 2, ‘refresh’: 1, ‘remove’: 2}. The compost post is the one to refresh: its visits fell 47% on last year, but the subject is still useful and had three links pointing to it. The old spade post fell 78% and has a replacement, so it is redirected. Two posts with almost no visits and no links are removed. The best-performing post is left completely alone. Notice that the rules protect the posts that other sites link to. Even weak pages that have links are better redirected than deleted.
Redirects done properly
A redirect sends a visitor and a search engine from an old address to a new one. Use a permanent redirect, usually called a 301, when the move is for good. Google describes a 301 as a strong signal that the new address should be treated as the main one. Redirect to the closest match, not always to the home page, since sending everything to the home page confuses readers.
The second part of the program checks a redirect map. It finds that ‘best-spade-2022’ goes to ‘tools-guide’, which itself goes to ‘best-spade-guide’, so a reader makes two hops. Chains like that are slow and fragile, so the program flattens the map and sends the old address straight to the final one. It also builds two entries that point at each other and proves it can detect the loop. A loop makes a page fail to load, so always test redirects after you set them.
When to remove a page
If nothing on your site replaces the page, let it return a not-found message, called 404, or a gone message, called 410. Google treats the two the same, so do not spend time choosing. What matters is that the server tells the truth. A page that says ‘not found’ on the screen but quietly returns a success code is a soft 404 and confuses search engines. Make a helpful not-found page that links to your best posts so a lost reader can find their way. If a page will come back soon, do not use either code.
Refresh honestly
- Read the post as a new reader would. What is out of date or missing?
- Update the facts, steps, photos and links. Check each link still works.
- Improve the title and opening if readers are not clicking, as lesson 17 showed.
- Add a line saying when it was last updated, and only change that date when you really did update the post.
- Link to it from your newest posts and note the date to check results in a month.
Deleting posts without a redirect or a check for links. You lose readers who arrive from other sites, and the sites that linked to you end up with broken links.
The posts, visits and rules are made up. Search engines may take weeks or months to notice changes, and nobody can promise a result from a refresh. Check Google Search Central for its current guidance on redirects and removed pages.
Practice for this lesson
Check what you learned
Five quick questions. Pick an answer and you will see straight away whether it is right and why.
What does a permanent redirect do?
- Deletes the page
- Sends readers and search engines to a new address for good
- Hides the page
- Speeds up photos
A 301 says the page has moved for good.
Why flatten a redirect chain?
- To create a loop
- To delete links
- Fewer hops are faster and less fragile
- To raise ads
Sending the old address straight to the final one is cleaner.
How does Google treat 404 and 410?
- About the same
- 404 is banned
- 410 gets a prize
- Neither is ever used
Google treats both as the page being gone.
Why were posts with inbound links protected?
- They are always best
- They have no text
- Other sites link to them, so removing them breaks those links
- They are free
Redirecting keeps those readers and links useful.
When should you change the last updated date?
- Only when you really updated the post
- Every day
- Never
- When you add ads
A false date misleads readers.
Summary
- Audit regularly and decide with written rules.
- Redirect to the closest replacement and avoid chains and loops.
- A removed page can return 404 or 410; Google treats them alike.
- Refresh for real and update the date only when you did.
Questions
How often should I audit?
Once or twice a year is plenty for most blogs. Use your search report and visitor numbers to spot the posts that have slipped.
Should I delete thin posts?
Not by reflex. First ask whether you can improve or merge them. Remove only the ones with little value, little traffic and no links.
Do refreshed posts rank higher?
Sometimes, but there is no promise. A refresh helps readers first, and any search benefit is a bonus.
