Connect your blog to your catalog
Every post links to the product page or category that answers exactly the question it's ranking for. Not a standalone article that ranks, gets visits and leads nowhere: a post that ends where it's supposed to end.
"Connecting your blog to your catalog" means every article links to the product page or the category it actually belongs to — not the homepage, not nothing. It's the catalog interlinking recipe: one pass over the whole blog that maps which post answers which part of your catalog, links each satellite to its pillar post and each pillar to its product page, and leaves the result ready for you to review before it publishes. No generic content tool can do this part, because none of them know your real catalog.
The problem: blogs talking to themselves
Most posts don't link to anything
When we review an ecommerce blog with thirty or forty published articles, it's common to find that most of them have zero links to the catalog. Not a weak or misplaced link: none at all. The post exists, sometimes it ranks, and it leads to no product page and no category.
You can see it without Search Console
It's the standout finding of our free diagnosis, because it takes no special access to
measure: you pull the list of URLs from the blog's sitemap and count how many have at
least one real link to /producto/, /products/ or a catalog
category. The number usually surprises whoever sees it for the first time.
The cost isn't writing, it's not connecting
The blog does its part — it attracts visits — and sends those visits back to Google instead of bringing them closer to a purchase. It's not a content volume problem: it's a problem of where the content that already exists leads.
The recipe: catalog interlinking
Three steps, in this order. None of them rewrites the body of the article: the recipe touches the linking, not the text that already works.
Map what answers what
For every post on the blog, the engine cross-references what that article is about with the real product pages and categories in your catalog, and decides the correct commercial route — if one exists.
one pass over the whole blog, not post by postLink satellite → pillar → product page
Every satellite article gets linked to its pillar post, and the pillar gets linked to the product page or category it corresponds to. Informational content goes to a category; decision content goes to a specific product page.
only the links are touched, never the body textReview as light-touch refreshes
The result arrives as a series of small refreshes, not one massive change all at once. Each one goes through your review before it publishes, just like any other content from the engine.
you approve, nothing publishes on its ownSatellites reinforce the pillar, and the pillar is what finally links to the catalog. That way the link weight of the whole blog converges on the page that has to sell.
Why no generic tool does this
It doesn't know your real catalog
An AI content generator writes text about a topic. It has no way of knowing which product pages exist in your store today, which ones got discontinued last month, or which category each product lives in. Without that data, it can't decide where to link — it can only suggest a generic link or add none at all.
It can't tell a pillar post from a satellite post
Linking well depends on understanding the architecture of the whole blog: which article is the strong piece on a topic and which ones are supporting pieces that should reinforce it. A tool that only sees the article in front of it can't make that call.
It only adds new text, it never revisits what already exists
Catalog interlinking is, above all, a pass over what's already published. A generator that only knows how to write new pieces has no function for going back over the forty posts that already exist and fixing their links.
The engine proposes the mapping and the links. It doesn't publish anything on its own. Every change arrives as a refresh with the previous version saved, and goes through your review before it publishes — exactly like any other content Content Mood produces. If you'd rather do this work manually, the full method, step by step and by platform, is in the guide to linking your blog.
What a product page URL looks like, by platform
The mapping is the same on any platform. What changes is what the destination URL looks like, and that's where it pays to be precise instead of speaking in generalities.
| Platform | What a product page URL looks like |
|---|---|
| PrestaShop | URLs like /12-product-name, with the product ID in front, unless you
have friendly URLs turned on. Worth checking before linking in bulk: that path changes
if the catalog gets reorganized. |
| WooCommerce | Product pages live at /producto/ (or /product/, depending
on configuration). The link finder in the WordPress editor locates the page by typing
its name — the technical part is already solved out of the box here. |
| Shopify | Product pages live at /products/. If a product sits in several
collections, Shopify can generate different URLs for the same page; always link to the
canonical one, without the collection in front, so you don't split signals across
duplicates. |
| WordPress + external catalog | The product page path depends on the store plugin you use. What doesn't change is that the link goes in through the native WordPress editor, just like any other internal link on the blog. |
| Magento | Catalogs of hundreds or thousands of SKUs. There the challenge usually isn't the URL itself, but deciding, among so many possible product pages, which one answers exactly the question the post raises. |
Frequently asked questions
Does this replace the work of an SEO?
No. An SEO decides the architecture, the business priorities and which categories are worth pushing. The engine runs the real mapping of which post answers which product page or category, across the whole blog, and hands it to you for review. It's the mechanical part of the job, not the strategic judgment.
What happens if my product page changes URL?
That's exactly why this pass repeats instead of running once. When a product gets discontinued or its URL changes, the link that pointed there breaks or redirects to the homepage, which is worse. Every new pass also reviews the links that already existed, not just adds the ones that are missing.
Does this work for categories, or only for product pages?
Both. The rule the engine follows: informational content links to a category, because it gives room to a reader who is still comparing and it doesn't expire when stock changes. Decision content, where the reader already knows what they're looking for, links to the specific product page.
How many links does it add per article?
Between two and four per average-length article. Fewer usually means the post has no real commercial route; forcing more than that turns the text into a flyer, and the reader stops trusting the links.
What if a post has no related product page?
No link gets forced where there's no natural route: it shows, and it costs credibility. The mapping marks it as "no commercial route" and leaves it as your call — create the missing product page, adjust the catalog, or leave the post as brand content.
How often does this pass repeat?
It depends on how much your catalog changes. As a reference, once a quarter is usually enough for most stores; if you rotate your catalog heavily by season or trend, it's worth repeating more often.
Start by finding out how many of your posts link today
Your blog's diagnosis is free: how many articles have at least one link to the catalog, which ones have none, and where it's worth starting. Before a single link gets touched.
Get my diagnosisno card · the diagnosis is free · we email you once