Tip 10: Recycle Smartly

Your archive already holds your next best page

Most store blogs that have been running for a couple of years contain the same idea written three or four times. A 2022 post on picking the right base layer. A 2023 post comparing merino with synthetics. A 2024 “ultimate guide” that covers both, a little thinner than either. Each one was a sensible brief at the time. Together they split the clicks, the links and the attention that one good page would have kept.

Recycling smartly means treating that archive as raw material. You merge what overlaps, move the useful parts to the pages where buyers actually decide, and update pages in place instead of starting again. It’s the least glamorous tip in this series and often the quickest to pay back, because the research, the product knowledge and some of the authority already exist.

This tip is about what to do with a page once you have decided to work on it. Deciding which pages deserve attention first is a separate job, covered in our guide to content refresh prioritisation.

The wrong kind of recycling

Start with what to avoid, because it is common and it looks productive.

The wrong kind of recycling produces near-copies. The same buying guide republished at a new URL with a fresh date. A “best walking boots for women” post cloned into “best walking boots for men” with the pronouns swapped. A collection intro pasted word for word onto six sibling collections. Every one of these adds a page and subtracts clarity, because search engines now have several similar documents and no obvious reason to prefer any of them.

Google’s spam policies name scaled content abuse: producing lots of pages mainly to catch search traffic, with little added value for the reader. A handful of cloned posts won’t trigger a manual action. It will, however, leave you with pages that compete with each other and a blog that looks bigger than it is useful. We have written about what happens when content volume becomes a liability, and near-duplicates are usually where that story starts.

A simple test. If a reader landed on both versions, would the second one tell them anything new? If the honest answer is no, you’re copying.

Move one: merge overlapping posts into one stronger page

Consolidation is the highest-value form of recycling for most stores. Take a store selling merino base layers with these three posts:

• How to choose a merino base layer (2022, decent backlinks from two outdoor forums)
• Merino vs synthetic base layers (2023, a few clicks a week)
• The complete base layer guide (2024, thin, ranks nowhere in particular)

Open Search Console, filter the Performance report by each URL in turn, and look at the queries. If the same searches (“merino base layer weight”, “is merino warmer than synthetic”) appear under two or three of these URLs, they’re competing. That overlap is your evidence for merging.

How to merge without losing what each page earned

1. Pick the survivor. Usually the URL with the most external links and the cleanest slug. Here that’s the 2022 post.
2. Audit the other two for anything the survivor lacks. The comparison table from the 2023 post and a sizing note from the 2024 one are worth keeping. The generic intro paragraphs are not.
3. Rewrite the survivor as a single page with a clear structure: fabric weights, merino compared with synthetics, fit and layering, care. Bring over the useful sections and write them to fit, rather than stacking three posts end to end.
4. Set 301 redirects from the two retired URLs to the survivor. On Shopify this lives under Navigation, URL redirects. On WooCommerce, a redirection plugin or a server rule does the same job.
5. Update internal links across the site so they point straight at the survivor instead of through the redirect. Check product pages, collection intros and older posts.
6. Request indexing for the survivor in Search Console’s URL Inspection tool.

The redirect matters. Deleting the weaker posts throws away whatever links and history they had. A 301 tells search engines the content has moved permanently, and it sends anyone following an old forum link to the page that now answers their question properly.

Merge only when the intent is genuinely shared. Pages for skiing and running base layers can deserve separate pages if the advice differs in substance: weight, cut, sweat management. If both pages would give a shopper the same advice, merge them. If the advice differs, keep both and link between them.

Move two: turn a buying guide into collection copy and FAQ answers

Your best buying guide probably sits on the blog, three clicks away from the collection where the buying happens. Meanwhile the collection page is a product grid with a single line of copy above it. The thinking you need for that collection is already written. It’s simply in the wrong place and the wrong shape.

Recycling here means extracting and rewriting for a different reader. Someone on a collection page is closer to buying and wants less context. So the guide stays where it is, and you lift its decision points into short, adapted copy.

A worked example

Say the merged guide has sections on fabric weight, fit and synthetics. For the matching collection page you might write:

• An intro of 60 to 120 words above the grid covering the one choice most shoppers get wrong: fabric weight. 150gsm for high-output activity, 200gsm as the all-rounder, 250gsm and up for cold, slow days. Close with a pointer to the full guide for anyone who wants the detail.
• Filter labels that use the same language as the guide, so “Lightweight (150gsm)” means the same thing in both places.
• Four or five FAQ answers below the grid, each rewritten from a guide section into a direct, standalone answer: “Should a base layer fit tight?”, “Does merino smell after multi-day use?”, “How do I wash merino without shrinking it?”

The same material feeds product pages too. The care section of the guide becomes a short care note on each product. The weight explanation becomes one sentence in each description, specific to that item’s weight.

None of this is copy and paste. The guide explains and compares. The collection copy helps someone choose among the products in front of them. The FAQ answers resolve single objections. Same knowledge, three jobs, three different wordings. If you want the reasoning on why collection pages usually need this, see why Shopify collection page SEO is usually broken.

Then close the loop with links. The guide should point to the collection with a descriptive anchor, and the collection intro should point back. That pairing is covered properly in Tip 8: Link the Dots, so it gets no more space here.

Move three: update in place instead of republishing

When a post has aged, the tempting fix is a new post: “Best merino base layers 2026”, published fresh, with the old one left to rot. That creates two pages on the same topic, one of which is now out of date and still indexed. It’s the near-copy problem again, arriving by a different route.

Update the existing URL instead. It keeps its links, its history and its place in your internal linking. A useful update for a store usually involves some of the following:

• Swapping discontinued products for current ones and fixing any links that now hit a 404 or a sold-out page.
• Correcting specifications that have changed, such as fabric blends, sizing charts or care instructions.
• Adding the questions customers have asked since publication. Your support inbox and returns reasons are the best source.
• Cutting sections that no longer help. Shorter and accurate beats longer and partly wrong.

If the URL has a year in it, such as /best-base-layers-2023, you have a choice. Either keep it and accept the slightly odd slug, or move to a year-free URL with a 301 from the old one. Don’t run both.

Be honest with dates. Changing the published date on an untouched post is a small deception that readers notice when the content mentions last year’s range. Show a “last updated” date when you’ve made a substantive change, and leave it alone when you’ve fixed a typo.

A recycling pass you can run this month

Pick one product category. Give it an afternoon.

1. List every blog post, collection page and FAQ that touches that category. A spreadsheet with URL, title, target query and clicks over the last 90 days is enough.
2. Group posts that answer the same question. Any group of two or more is a merge candidate.
3. For each group, choose the survivor, merge, redirect and relink as above.
4. Take the strongest surviving guide and extract collection-page copy and four or five FAQ answers from it.
5. Update anything in the category that mentions discontinued products or outdated specs, keeping the URL.
6. Write down what you changed and when. You’ll want that log for Tip 11: Tinker Constantly, where you check whether it worked.

Most stores end up with fewer blog URLs after this, and better collection pages. That’s the right direction. A smaller archive where every page has a distinct job is easier for shoppers to use and easier for search engines to understand.

If you publish at volume, this discipline needs building into the system from the start. At Sprite, new articles are planned against what a store already has, so a topic that is covered gets an update or a link instead of a second, competing post.

This is Tip 10 in Sprite’s 11-part series on ecommerce content that compounds. Next: Tip 11: Tinker Constantly.

Frequently asked questions