For ecommerce
The blog around the catalogue.
A shopper reads before they buy: which one, what size, whether it is worth it. Xt4b writes those posts on your own domain and links them into the products you already sell. It does not touch product pages, category copy or prices.
Catalogue untouchedNothing to installNo per-article quotes
What the posts answer.
Not another product listing. The questions a shopper puts to a search engine in the days before they add something to a cart.
- The comparison before the cart
- Two products, two approaches, two price points — a post that helps the shopper choose rather than a listing that repeats both descriptions back at them.
- What the product page cannot say
- Sizing, materials, care, compatibility, what happens after the order. A product page has to sell; a post can explain, including the parts that argue against the upgrade.
- The price and timing question
- What it costs, when it ships, whether there is a cheaper route to the same outcome — answered in a post, because a product page that talks about alternatives is a page that loses its own sale.
- The category you sell but have not explained
- A cluster of posts around a product type you stock: the demand is being searched before the page that deserves it exists.
- Links into the pages that sell
- Every post links to product and category URLs taken from your own sitemap, so the blog pushes readers — and authority — at the catalogue instead of competing with it.
- Answers in the language they buy in
- Each language is its own plan built from that market's own searches, not the English posts translated. A Dutch shopper searching in Dutch is planned for separately.
The steady version of a shop blog.
Five steps, and only one of them is yours to repeat. The rest happens on the calendar, in the background, whether trading is quiet or busy.
- 01
Scan the shop
The free scan reads your homepage, your headings and your sitemap — product and category URLs included — and shows what your site already answers and what it misses.
- 02
Connect the domain
One DNS record and the blog answers on a domain you own, usually a subdomain. Nothing is installed on the store, and the catalogue keeps serving exactly as it does today.
- 03
Check the plan against the catalogue
Read the entries and discard anything you would not want a buyer to find — a comparison against a product you have dropped, a guide for a category you no longer stock.
- 04
Posts publish on their dates
Written to the plan entry it belongs to, checked before it publishes, then live with images, metadata and internal links to the product pages it discusses.
- 05
See which queries appear
Connect Search Console read-only and each site reports the clicks, impressions and average position its posts earn, per query.
What stays with the merchandiser.
What a post cannot know is what your margin is, which line is about to be replaced, or which claim your supplier will not stand behind. Those stay on the product page, where they belong.
What it can do is keep answering the questions your catalogue raises — and link the answers to the products, so a guide written this month is still sending shoppers into the shop next year.
- Product titles, descriptions, category copy and the prices themselves
- Which lines are worth pushing this quarter, and which are being retired
- Stock, shipping, returns and the offer
- Photography of the actual product
- The claims a product page can stand behind
Six posts in the first month, or one every publishing day.
Both start the same way. Only one of them is still linking into the catalogue next year — and a shopper can tell which is which.
The blog nobody keeps up
- Six posts in the first month, then nothing until next year
- Buying guides written by whoever had a spare afternoon
- Posts that chase the same query as the category page they sit next to
- Recommendations with no link to the product being recommended
- No idea which queries bring traffic, let alone orders
A blog that feeds the catalogue
- One post per publishing day, on the dates it was planned for
- Queries taken from what shoppers type before they choose
- Every post links into the product and category pages you already have
- A generated cover and in-article image for each post
- Clicks and impressions reported beside the calendar, per site
What a blog does not fix
Conversion rate, delivery times, returns, reviews and price still decide whether a shopper buys. A blog earns the visit — it does not improve the checkout, and it will not rescue a product page that loses the sale.
And rankings, traffic and orders are not guaranteed — no honest supplier can promise them, and our terms say so. What you get is a growing set of pages on your own domain, publishing on a schedule, each one pointing at the products it discusses.
Costed per site, not per post.
20€ per website, per language, per month. The scan comes first and costs nothing — you see the queries your shop is missing before you decide anything.
That is the whole invoice: no per-article rate, no minimum number of posts, no separate charge for images, metadata or hosting the blog. A shop selling into two languages is two lines, each with its own plan and calendar.
The blog sits on a domain you already own, so the archive is an asset of the business rather than a channel you rent from somewhere else — and the API can feed it into whatever you already run.
- The plan: queries, intents, outlines and dates
- Writing, with the review pass before publishing
- Cover and in-article images, in your brand colour
- Hosting the blog on your own domain
- Canonical URLs, sitemap and structured data
- Search Console reporting, per site
More on content
- For local businesses
Answer the question before they call.
- For hotels & travel
Answer the guest in the language they searched in.
- For restaurants
The question that ends in a table — menus and prices stay yours.
- For dentists & clinics
Answer the treatment and cost questions, with clinical review.
- For law firms
Clients search the situation, not the practice area.
- For publishers
Archive depth under the news: the long tail a desk cannot reach.
- For WordPress sites
A blog for WordPress without a plugin or a theme edit.
Questions shops ask.
Including the one that decides the whole thing: whether product pages are included.
Will it write my product descriptions?
No. Product titles, descriptions and category copy stay yours: they are the pages that sell, and a generated paragraph dropped into a price table is not an improvement on what you wrote. Xt4b writes the posts around the catalogue — comparisons, sizing, care and buying-guide queries a shopper searches before they are ready to buy — and links to the product URLs in your sitemap instead of replacing them.
Where do the posts actually live?
On a blog on your own domain, usually a subdomain like blog.yourshop.com. Not on a marketplace, not on a directory and not on Xt4b's own site, so the archive belongs to the shop: if the subscription stops, the posts and their URLs stay where they are.
Does it integrate with Shopify, WooCommerce or a custom storefront?
It does not need to. Nothing is installed, and the blog is served from your own domain, so it does not matter what the catalogue runs on. If you would rather the posts land in the store's own blog, the read-only API returns every post as markdown or as rendered HTML and you can publish it through whatever you already use.
What about the pages my shoppers already find me on?
Every URL in your sitemap — product and category pages included — is recorded before anything is planned, so new posts target searches your shop does not answer yet rather than competing with pages that already rank. That is also what keeps a post about a product from cannibalising the product page itself.
Does it understand the difference between a buyer and a browser?
Each planned post carries one intent — research, comparison or purchase — and a different search, so the research posts do not read like landing pages and the purchase-stage posts are not buried in a beginner's guide. You see every entry, with its intent, before one word is written.
What does it cost for a shop selling in two markets?
A line is one site in one language: 20€ per website, per language, per month. A shop selling in German and Dutch pays for two lines, each with its own plan, its own target searches and its own calendar, and each planned from that market's own searches rather than translated. There are no per-article quotes and no charge for the scan, which needs no account.
Will it bring more orders?
No ranking, traffic or revenue is guaranteed, and any supplier who promises one is guessing. What the blog does is give your own domain more pages answering more of the questions shoppers ask before they buy, publishing on a schedule, with reporting that shows which queries the site is beginning to earn impressions for.
Start with your shop
Answer the question before the cart.
Connect your domain and read the plan: the queries your shop is missing, the first entries, and dates you can move before anything is written.
Product pages stay yours20€ / site / language / month3 days free, no card