Ilaiyaraaja’s 50-Year Run Proves Brands Need a Back Catalog People Can Still Find

Ilaiyaraaja’s 50-year run is a better SEO lesson than any one-hit success story

BBC World’s report on Ilaiyaraaja’s 50-year career makes a simple point with unusual force. He still matters because people keep referencing, performing, and reinterpreting his work. That is what staying power looks like: a body of work that keeps finding new listeners instead of one loud moment that burns bright and fades.

That is the cleaner lesson for ecommerce content. A brand does not need one viral page that spikes, gets shared, and then disappears from search behaviour. It needs a back catalogue that keeps surfacing when shoppers, editors, and answer systems look for a specific problem, comparison, or clear explanation.

Durable discovery comes from pages that stay retrievable and citeable after the launch rush fades. If a size guide, fabric guide, or returns explainer can still be found six months later, it keeps doing work. If it cannot be found, it was never an asset; it was a traffic burst with a byline.

The real divide in content strategy is whether a page wins once and then disappears from search behaviour or keeps being referenced as part of the site’s working memory. A page that disappears from search behaviour is a dead asset. A page that keeps being referenced becomes the place people return to when they need an answer without starting from scratch.

This article takes that idea seriously and applies it to ecommerce library planning. The practical goal is to build pages that hold up as search shifts toward answer layers, internal linking, and reused citations. Stores that do this keep getting found long after launch noise has faded.

Why one-off hits stop paying rent

Content built for a single ranking moment usually pays once and then decays. It is tied to a narrow query, a temporary trend, or a page structure search systems cannot reuse cleanly. The traffic arrives, then the page slips because nothing in the site keeps pulling it back into view.

In ecommerce, this shows up in familiar ways. A product launch post gets clicks for a week, then ages out when the range changes. A generic blog post about winter boots never earns links, so it sits there looking busy while doing very little. Seasonal articles disappear every year because no category page, guide, or related article points back to them.

Lean teams pay for that mistake in time. They keep rewriting the same topics, cleaning up duplicated briefs, and trying to rescue orphan pages nobody can reach from the homepage or collection pages. The site fills with content that exists, but does not connect to anything useful.

Google Search Central is clear that helpful, people-first content wins over pages made to chase search systems, and its scaled content abuse policies exist for a reason. The practical reading is simple: write for a real shopper and make the page useful enough to keep. A return policy explainer for “can I return opened skincare” has a better chance of lasting than a thin post stuffed with keywords and no clear answer.

Search now rewards reuse. Pages that can be cited in answer layers, linked from related content, and referenced externally have a better chance of staying visible than pages written for one keyword match. A hit song can fade from rotation, but a catalogue keeps getting sampled, covered, and searched. Ecommerce content works the same way.

What makes older content still findable

Retrievability is plain enough. Older content stays findable when the topic is clear, the URL is stable, the page is linked from somewhere else on the site, and it answers a job that still exists. If a shopper still needs to know whether a jacket runs small, that page can keep earning its place.

Structure does a lot of the heavy lifting. Descriptive headings tell both readers and machines what each section covers. A concise summary near the top helps people decide quickly if they are in the right place, and subheadings let them jump straight to sizing, materials, shipping, or returns without wading through filler.

Language matters because people scan before they read. Nielsen Norman Group’s research on web reading behaviour shows users pick out headings, highlighted phrases, and the opening lines of sections first, which is why clear layout wins attention, source. Google Search Central says helpful content should satisfy the reader’s need with clarity, source. The lesson is simple: write the page so a hurried shopper can spot the answer within seconds.

Answer systems also prefer pages that are easy to quote. Short definitions, direct answers, and clean sectioning give machines a neat passage to pull, and they give humans the same clarity. A paragraph that says, “This backpack fits a 15-inch laptop and has a padded sleeve” is easier to reuse than a wall of copy that buries the fact in brand language.

Freshness helps when it is about upkeep rather than churn. Update examples, tighten explanations, fix broken links, and keep product references current. That keeps a guide useful without turning it into a different article every time someone opens the editor.

Older pages fail when they go vague, run too long, or get stuffed with loosely related keywords. A returns article that starts talking about delivery windows, payment methods, and styling advice has lost its purpose. The pages that last are the ones people can still find, read, and use without extra effort.

Build pages around jobs, not topics

Topic-first planning sounds organised, but it usually produces broad pages that try to speak to everyone and end up helping no one. A page about “running shoes” is easy to write and hard to use because the shopper still has to work out whether they need width, cushioning, stability, or another feature.

Job-first planning starts with the decision a shopper needs to make. That might be choosing between cotton and merino, checking whether a jacket runs small, comparing two product types, figuring out how to care for leather boots, or deciding if a feature is worth paying for.

Google Search Central’s guidance on helpful content points in the same direction: create pages that satisfy a specific user need source. That is the shape of an evergreen content library strategy that lasts, because each page earns its place by solving a specific job properly.

Compare these two approaches. “Everything about running shoes” is a catch-all article that becomes dated the minute your range changes. “How to choose running shoes for wide feet” gives a shopper a clear decision path, and “what cushioning actually changes” answers one question cleanly.

That difference matters for maintenance too. A job-based page is easier to update when sizes, materials, or features change, easier to cite because the claim is narrow, and easier to fit into internal links because you know exactly where it sits in the site structure.

Build the library as a set of connected answers. Each page owns one job and points to the adjacent pages a shopper is likely to need next. That is how old content keeps earning its place instead of turning into a warehouse of vague advice.

Make the page easy to quote, not just easy to read

Answer layers and AI summaries reward pages with clean passages they can lift without mangling the meaning. If a sentence cannot stand alone, it usually cannot be quoted cleanly either. The page needs to give the answer in pieces that still make sense when taken out of context.

Nielsen Norman Group has long found that users scan rather than read every word, which is why structure matters source. Google says the same thing in its guidance on clear page structure source. Short definitions, direct answers at the top of a section, labelled steps, and plain comparison tables make a page easier to quote and use.

The practical version is simple. Put the answer in the first sentence of a section, then explain it. Use descriptive subheads like “What cushioning changes in a running shoe” or “How to tell if a jumper will shrink” so shoppers and search systems can find the right line fast.

• Short definitions that name the product term plainly

• Direct answers at the top of each section

• Labelled steps for care, sizing, or setup

• Comparison tables with plain labels such as width, weight, and wash care

What hurts citation potential is obvious. Long introductions waste the first screen. Clever copy hides the answer. Paragraphs stuffed with brand language bury the useful line under decoration.

The search query gap here is skimmability for answer engines, and the fix is structure rather than word count. One idea per paragraph, with clear subheads.

Terms a shopper would actually search for, such as “does this coat run small” or “best mattress topper for side sleepers”. A catalogue performs better when individual tracks are easy to sample, and pages work when sections are easy to quote.

Stop publishing orphan pages

Internal linking keeps older pages visible. A page that exists but sits outside the site’s working structure will be hard for users to find again and hard for search systems to treat as part of the active catalogue. Google Search Central says internal links help search engines understand your site structure source.

That means every important page needs a job inside the site. Buying guides should point to category pages and relevant product ranges. Product care articles should point back to the item pages they support. Comparison pages should link to both sides of the comparison, so the shopper can move from decision to purchase without hitting a dead end.

Anchor text matters more than most teams admit. “Read more” tells nobody where the link goes. “See wide-fit trainers”, “compare wool and cashmere jumpers”, and “how to wash suede boots” tell the reader exactly what sits on the other side, which helps users and search systems at the same time.

Older pages need fresh links from newer posts, category pages, and evergreen hubs. Without that, they decay into isolated files that still exist but stop doing useful work. A good library keeps sending traffic back through its older entries, and a well-run shop keeps its best stock on the floor instead of leaving it in the back room.

This is the part many brands miss when they chase volume. They publish a cluster of articles, then move on, leaving older pages stranded. The result is a site full of pages that were written, indexed, and forgotten, which wastes resources that no small ecommerce team can afford.

How to use AI without filling the site with generic copy

The AI question is the wrong place to start. The real issue is whether the finished page contains original judgment, specific examples, and a point of view a shopper can use. If the page reads like it could sit on any store selling any category, it is too generic.

Generic AI copy fails because it irons out the useful differences. It repeats obvious points, strips out the awkward detail that helps people decide, and leaves you with pages that sound familiar in the worst way. That kind of copy is hard to quote, hard to trust, and easy to ignore.

Google Search Central is clear on the risk here. Its spam policies target scaled content abuse, where large volumes of pages are made to manipulate search, including AI-generated pages that exist mainly to flood results. Using AI as a drafting aid is fine. The problem starts when you publish mass-produced pages with no real value, and the policy language says so plainly in Google Search Central spam policies.

A lean editorial standard keeps AI in its place. Start with a human outline that answers one shopper problem, then add source checking, brand-specific examples, and a final edit that removes filler, vague claims, and recycled phrasing.

A page about women’s trail running shoes should explain how a narrow toe box affects downhill stability or how sizing compares with the brand’s other models. A page about leather boots should cover break-in, weatherproofing, and what goes wrong when care advice is too generic.

Use this rule before publishing anything:

• If the page could belong to any store in any category, it is too generic.

• If it names the product type but avoids the buying problem, it is still too generic.

• If a merchant cannot point to a specific shopper question the page answers, cut it.

That standard sounds strict because it is. It also saves time, since you stop polishing copy that never had a reason to exist. The catalogue lesson from the opening holds here too, every track needs a job, or it belongs in the bin.

What an ecommerce content library should contain

A strong content library for a lean store does a few jobs well. It needs buying guides, comparison pages, care and maintenance pages, sizing and fit pages, and problem-solving explainers. Those page types answer the questions shoppers actually type, such as “does this jacket run small”, “best backpack for commuting”, or “how to clean suede trainers”.

Each page type earns its place in the journey. A buying guide attracts the first question, a comparison page supports the decision, a sizing page reduces returns, and a care guide helps after purchase when people want to keep the item in good condition. One page opens the door, another helps the shopper choose, and another reduces friction after checkout. That is how a library keeps working long after the initial publish date.

Product pages and editorial pages need a clear division of labour. Product pages sell the item with variants, price, reviews, shipping details, and the final nudge to buy. Editorial pages explain the decision or the use case, so they should answer questions the product page cannot handle well without turning into a wall of text. If every explanation lands on the product page, it gets bloated and the message gets muddy.

That separation also helps internal linking. A comparison page can link to the relevant product range, a sizing guide can point to the size chart and fit notes, and a care article can link back to the material-specific products. Search engines and shoppers both benefit when the site architecture makes sense.

Pruning matters as much as publishing. Ahrefs has long advised trimming weak pages, and Semrush regularly recommends content pruning and stronger internal linking as part of site maintenance, while Google Search Central warns against thin or duplicate content in its quality guidance and spam policies.

That means some pages should be merged when they overlap, especially if you have two articles saying almost the same thing about fit or fabric care. A smaller set of strong pages beats a large pile of weak ones.

This is where the music analogy earns its keep. A strong catalogue has variety, but every track has a reason to exist. Your store needs the same discipline, with a clear mix of pages that each do one job properly and no filler pretending to be a hit.

How Sprite changes the content library problem

Most content systems still assume a human team will notice the gaps, brief the pages, write the copy, check the facts, add links, and publish on schedule. That works until the team is busy or small. Then the library starts to drift because the work is too repetitive to keep up by hand.

Sprite is built for that exact problem. It analyses your published content corpus before generating anything, so it learns your actual voice, vocabulary, and sentence patterns from the work already on the site. That matters because brand voice is not a style description in a doc nobody opens; it is the pattern your store has already earned.

Voice Modelling keeps each piece inside that established register, and Brand Reflection checks the draft against your patterns before publishing. The result is consistency without flattening the writing into generic ecommerce sludge. The system is reading the store before it writes for the store, which is the part most tools skip.

It also maps category demand and authority gaps, then weights opportunities by what is actually achievable from your current position. The roadmap is sequenced so each piece builds on the last instead of spreading effort across unrelated topics. In practice, that is the difference between a library and a pile of articles with good intentions.

Fact-checking happens after every section during generation, not as a final pass. That matters because errors do not get the chance to compound into the next section. Internal links are built automatically to relevant commercial pages, and existing archive posts are updated to link back bidirectionally, so the site keeps reinforcing itself instead of leaving older pages to drift.

Sprite publishes directly to Shopify or WordPress, either live in autopilot or as drafts in co-pilot for review. On Shopify it injects Liquid templates and creates new blog handles, and every post ships with full JSON-LD schema, including Article, BreadcrumbList, and Organisation. The system runs continuously in the background, tracks what it publishes, and monitors existing content and gaps.

That continuous loop is the point. Content libraries do not fail because one page is weak. They fail because the system stops keeping older pages connected, current, and useful. Sprite is designed to keep the catalogue alive after the first publish, where the real work begins.

What good looks like in practice

The strongest ecommerce content libraries look less glamorous than people expect. They are built from pages that answer one shopper job each, linked tightly to the right products, and updated before they become stale. The value comes from repetition, which is a less glamorous word than “viral” but far more profitable.

Giesswein used automated agentic content to generate €2M in incremental top-line revenue. Nanga saw 250% non-brand organic traffic growth in under 12 weeks without straining internal resources. Whitestep added 142 new pages, increased new content by 62%, gained 90k impressions, lifted organic clicks by 13%, and saved 8 hours a week with one person across three brands in three months.

Kyoto Pearl recovered 100% of traffic and non-brand visibility after a Shopify migration in 90 days, with impressions exceeding pre-migration levels. Asceno got 82% of non-brand impressions from Sprite content, 58% of organic clicks from new content, and improved average search position from 14.1 to 6.5. Those outcomes point to the same principle, the library compounds when the pages are connected and kept in shape.

The lesson is that every store needs better sequencing, stronger structure, and a system that keeps older work useful. One-hit pages are easy to admire and easy to lose. A living catalogue keeps paying because it keeps showing up.

Frequently asked questions

Written by Richard Newton, Co-founder & CMO, Sprite AI.