The blog lives inside Maho: how it works and what you can do with it
The Maho blog is in the core since 25.9.0, not bolted on: posts, categories, SEO, sitemap, search suggestions, a widget and an API.
A blog does two quiet things for a store: it gives people another reason to arrive on the site, and it keeps that content where the store already lives. The second part is the one that usually costs. A separate blog means a second theme, a second image pipeline, a second sitemap, and every colour change done twice.
In Maho the blog is a core module, and that is the practical difference: posts sit in the store database, they answer on the store URLs, and they use the same theme, the same media library and the same cache. This deep dive covers what it is made of, where it came from and what you can do with it today.
When it arrived
The Maho_Blog module shipped in 25.9.0, published on 7 September 2025: it is not in 25.7.0
and it is in 25.9.0, so that is the first release that carries it. It was version 1.0.0 and did the
essentials: posts, an entry in the menu, the sitemap and search suggestions. The module is at 2.0.0
today and has added categories, attributes, a preview and the API.
What a post is made of
A post is an EAV entity, the same shape as a product: static fields for what everybody needs, and attributes for what you add yourself. The fields you always find are the title, the url key the address is built from, the publish date, the content, the image, the meta title, description, keywords and robots, the active flag and the store view assignment.
The url key can be edited, and the publish date decides when the post is visible: a post that is not published yet is not in the listing and has no public address.
Categories
Blog categories are a tree, and the address follows it:
/blog/category/<category>/<subcategory>/<post>, with a category prefix you can change. A post can
belong to several categories, and every assignment carries a position, so you decide the order of the
posts inside a category.
Categories are off by default: when you turn them on, the breadcrumbs appear on the post too.
Where it is managed
The blog has its own entries in the admin: the post grid, the edit page, and the content editor the rest of the admin uses. The preview is the same as the CMS pages: you open a post from its address and see what a visitor will see, without publishing it.
One detail you notice while writing is that the content runs on the same engine as the store content.
Template directives such as {{media url="..."}} and widgets work here too, images go through the
media library, and a change to the store design reaches the posts without touching blog templates.
On the storefront
The listing lives under the configured URL prefix, blog by default, and shows the published posts of
its store view with the pagination you choose (20 per page if you leave it alone). The menu entry
appears by itself when the setting is on and at least one post is published: an empty blog does not
leave a link that goes nowhere.
Then there are the points that make the blog part of the store instead of an appendix:
- the sitemap includes the posts, with frequency, priority,
lastmodand images; - the store search suggests posts too, up to the number you pick;
- the Blog Recent Posts widget brings the latest posts into a CMS page or a column, optionally from one category and its subcategories, with a cache that refreshes when a post is saved.
All of it is governed from System > Configuration > Blog, with the General, Search and Sitemap groups, per store view: two stores can have a different prefix and a different number of posts per page.
The API
Since 26.7.0 the blog posts and categories are resources of the new API, over REST and GraphQL, in the
Content section. There is read, create, update and delete, plus two operations for the image: an
upload that saves it under media/blog in place of the current one, and a delete.
The GraphQL read accepts the filters that matter to whoever builds an external storefront: the url
key, a search in the title and the body, the category, the creation and update dates, and a scope
that, with backend access, returns the records of every store view too, disabled and unpublished ones
included, the way the admin grid does. A post write accepts the categories as a list of ids or as id
and position pairs, and the image has to be a path relative to media/blog.
Where to start
If the store does not use the blog, the first step is a small test: one post published in one category, the menu entry on, and a CMS page with the latest posts widget. That shows whether the storefront theme has the styles for the blog, and if it needs a touch, you touch it where you already touch the rest of the store.
A store with a blog somewhere else does not have to move it in one night: posts have a url key and meta fields, so they can be brought over one category at a time while watching the sitemap for redirects, without switching the old blog off on day one.
Text prepared with the help of AI and checked against the source before publication. It can still contain mistakes: if you find one, report it.Read the manifesto
Source: Release 25.9.0
Does your store still sell?
Tell us where you are starting from: we reply with a first assessment, no strings attached.
Ask for the store assessment