Your catalogue, audited and cited.
A commerce catalogue is content — usually thousands of pages of it, and almost never audited. Writegarden reads the store you already have through its own API, scores what is wrong, and writes the articles that point back at the products worth selling.
WooCommerce today via the WordPress connection; Shopify with the Shopify connection, coming soon · four category meters · AI Search Readiness checks · product and service cards inside articles.
Why the catalogue is the neglected half of commerce SEO
Most commerce content programmes treat the blog and the catalogue as separate problems. The blog gets a strategy; the product pages get whatever the import script produced. The result is a store where the articles rank and the product pages they point at carry a forty-character description, no structured data, and an image with no alt text. An AI engine answering a buying question reads the product page, not the blog post that linked to it. Auditing the catalogue is not housekeeping — it is the half of the funnel that converts.
What the audit reads
Connect a store and Writegarden scores it across four categories, then lists the specific pages behind every issue.
Metadata
Titles, descriptions and the fields that determine how a product appears in a result or an answer. Missing, duplicated and truncated fields are listed per page rather than counted in aggregate.
Content
Description depth and specificity. Thin product copy is the single most common reason an otherwise healthy catalogue is invisible to an answer engine.
Media
Image coverage and alt text across products and collections — the accessibility requirement and the machine-readability requirement satisfied by the same fix.
Hygiene
The structural drift every catalogue accumulates: duplication, orphaned entries, and inconsistencies between a collection and the products inside it.
AI Search Readiness
A separate pass over schema completeness and answer-readiness — whether a product page gives an AI engine something it can quote and attribute, rather than something it has to paraphrase.
Suggested fixes
For an issue on a product or category page, Writegarden drafts the replacement copy. One-click apply back to the store is in build; today the draft is yours to paste.
Product and service cards inside the article
An audited catalogue only pays if the content points at it. Writegarden keeps a set of product and service offers — imported from the connected store, uploaded as CSV, or detected from your own site — and embeds them into generated articles as branded cards: a banner, a tile, a showcase, a collection grid, or inline links. Each card takes its palette and typography from the brand profile, so it reads as part of the page rather than an advert dropped into the middle of it. Service businesses get the same mechanism with no catalogue at all: offers are detected from your site and rendered as lead-generation cards.
What commerce teams ask.
Which platforms can I connect?
WooCommerce today, through the same WordPress connection used for publishing. Shopify catalogue reading ships alongside the Shopify publishing connection, which is coming soon.
Does the audit change my store?
No. It reads through the platform's official API under the access you grant and writes nothing back. Suggested fixes are drafts you choose to apply.
Is this the same as the website audit?
No. The website audit crawls any site for on-page and technical issues. The store audit reads a connected catalogue through its API and scores the products and collections themselves.
Do the product cards need a store?
No. Offers can be uploaded as CSV or entered by hand, and service offers can be detected from your site — so a services business gets the same in-article cards without a catalogue.