Ecommerce SEO · October 24, 2026 · 8 min read
Ecommerce Blog Post Ideas Pulled From Your Catalog
Your catalogue already holds around 40 posts: collections become buying guides, attributes become comparisons, support tickets become how-tos.
By FluxWriter
Ecommerce blog post ideas run out at about post four, and they run out because the wrong thing is being asked. Sitting down to think of topics produces four decent ones and then nothing. Reading your own catalogue produces dozens, because a store with 140 SKUs already holds a year's worth of posts or more in its collection names, its product attributes, its support inbox and its seasonal stock. This covers how to pull them out, how to count what you have, and the one filter that keeps the list from filling with things nobody will buy from.
Every Idea Has To Name The URL It Links To
Apply the filter before anything else, because it removes most of what a brainstorm produces. An idea qualifies if you can name the collection page or product page it will send readers to before you write a word. If you cannot name one, what you have is a magazine article hosted on a store domain. It may bring traffic. That traffic has nowhere to go.
The filter sounds restrictive and does the opposite. It changes the question from what should we write about, which has no answer, to which page needs a supporting article, which has about forty. Collection and product pages are the commercial surface of the site. A blog post exists to reach people searching in language those pages do not use, and to hand them over.
It also hands you an internal link before you start. Each post should link to its destination page in the first third of the article, in the words a buyer would use rather than as "click here". One clear link to the right page does more than six sprinkled through the text to look natural.
Collection Names Are Already Buying Guides
Open your collections list. Each name is a category a buyer is choosing inside, which makes each name a buying guide waiting to be written. "Waterproof hiking boots" becomes how to choose waterproof hiking boots. "Ceramic planters" becomes how to pick a planter that will not crack outdoors over winter.
Write the guide as a decision rather than a restatement of the category. The reader arrives not knowing which variables matter, so name three or four and say what each one changes: price, material, size, and the one specification most people get wrong. Then link to the collection and let the filters do the rest.
A store with eight collections gets eight guides immediately. These tend to be the most durable posts on a store blog, because the category outlives the individual SKU. A guide written against the category survives a product selling out, which a post built around that product does not.
Product Attributes Give You The Comparison Posts
Export your products with their attributes: material, size, power source, finish, capacity, compatibility. Any attribute that takes two or more values across your range is a comparison post, because a buyer looking at both options has to choose one and often has no basis for choosing.
Stainless versus aluminium. Corded versus battery. 40cm versus 60cm. Each is a post answering a question the buyer is already asking, and each links to two filtered views of the same collection. Comparison posts tend to convert better than their traffic suggests, because the person reading has already decided to buy and is only deciding what.
Keep them honest by saying which option is wrong for which buyer. A comparison concluding that both are excellent is a weaker post than one saying the aluminium model is lighter, will dent, and is still the right buy for most people. You sell both, so accuracy costs you nothing, and accuracy is what makes the post worth linking to. As a rough rule, six to eight of these exist in a mid-sized range before you start reaching for contrived pairings.
Support Tickets Are The Highest-Intent Source You Have
Read the last two hundred support messages and tally the questions. Not the shipping complaints: the product questions. How do I fit this. Will it work with that. What size for someone 1.8m tall. Which one for a hard-water area. Any question appearing three times is a post, and it is a post you already know has an audience, because those people paid money and still had to ask.
They are also the cheapest posts to produce, because the answer exists already in the reply your support person sends every week. Take that reply, expand it with the context a pre-purchase reader lacks, and link to the products named in the ticket. This source usually yields more usable ideas than any keyword tool, because it comes from people who have actually met the product.
Questions asked on product pages, where your platform or a reviews app collects them, work the same way and sit earlier in the buying cycle. Someone asking on a product page has not bought yet, which puts their wording closer to the search query you want the post to answer.
Counting A Mid-Sized Catalogue Gives You Around Forty Posts
The counts below are illustrative, drawn from a store with roughly 140 SKUs across eight collections. Your own totals will move with how broad the range is and how much of the support history you still have.
| Catalogue signal | Post it produces | Where it links | Illustrative count |
|---|---|---|---|
| Collection page name | Buying guide for that category | That collection URL | 8 |
| Attribute with two or more values | Comparison post | Two filtered collection URLs | 6 |
| Support question asked 3+ times | Troubleshooting or setup how-to | The products named in the ticket | 12 |
| Question asked on a product page | Short answer post | That product URL | 9 |
| SKUs that only sell in one season | Occasion or gift post | The seasonal collection URL | 5 |
| Items customers regularly buy together | Pairing or use-case post | Both product URLs | 4 |
That comes to 44 posts, and not one of them needed an idea. At two posts a month the list lasts close to two years. At one a week it lasts about ten months. It also regenerates on its own: new products bring new attributes, new customers ask new questions, and collections get added as the range grows.
Counting matters more than it sounds like it should. Store blogs rarely stop at post four because writing is hard. They stop because every post starts with a blank search for a topic, and that search gets more demoralising each time you run it. A list of 44 removes the step.
Seasonal SKUs Fill Dates You Already Know
Pull sales by SKU by month, going back two years if you have the history. Products with lumpy demand (everything that only moves in November, or in the first warm week of spring) give you calendar posts with a publication date already attached.
Publish these early. A gift guide going live in the second week of December is competing against pages that have been sitting there since October. As a rough rule, aim to have seasonal posts up six to eight weeks before demand starts, and update the same URL every year rather than publishing a fresh one with the year in the slug.
Seasonal posts are also the easiest thing to schedule ahead, because the dates do not move. If you batch-produce content only once a year, do it for these.
Some Ideas Are Worth Cutting Before You Write Them
Three cuts. First, any two ideas answering the same question with the same intent should be one post rather than two. Two thin articles chasing a single query both tend to underperform the one thorough article you could have written instead.
Second, drop ideas whose destination is out of stock with no restock date, or is a single SKU you may discontinue. Write against the collection instead, so the post outlives the product.
Third, cut anything where your honest answer is "buy ours". A post that only works if the reader accepts your product as the premise is an advert with headings, and it reads that way. The catalogue-derived ideas that earn their place are the ones where a reader who buys nothing still leaves with a usable answer.
FAQ
How many posts does an ecommerce store need before anything happens?
There is no threshold that switches results on, and anyone quoting a specific number is guessing. What does hold up in practice is that one post rarely moves anything measurable by itself, and that gains tend to arrive as slow accumulation across a body of posts. Assume you are judging the exercise at nine to twelve months rather than at post six.
Should the blog sit on the store domain or somewhere separate?
On the store domain, in a subfolder, for the plain reason that the point of each post is to link to a page on that domain. A separate domain turns every one of those internal links into an external one and splits whatever authority you build across two sites. If your platform makes the subfolder awkward, that is worth solving once rather than designing around.
Do comparison posts cost sales by talking people out of the pricier option?
Sometimes, on that one transaction. The trade is that a buyer told the cheaper model suits them returns fewer items and raises fewer support tickets, while the post keeps working for the people the expensive product genuinely fits. When both products are yours, you are choosing between two of your own SKUs rather than between yours and a competitor's.
The Practical Takeaway
This week, do the counting rather than the writing. Put your collections list, your product attribute export and the last two hundred support messages into one spreadsheet, and log every idea that can name the URL it will link to. Expect an afternoon of work and somewhere between thirty and fifty entries. Then order the list by how close each destination page sits to money, with collection guides and comparisons first and general how-tos last, and write the top one. Start by exporting your collections list and writing a single line for each collection naming the guide it becomes.
A spreadsheet of 44 ideas is most of the way to a FluxWriter bulk CSV import, which on the Pro plan queues up to 100 topics and drip-publishes them into the store, so the list you counted this week becomes the publishing order.