An online catalogue means hundreds of pages to write, and each one needs a title, a description, filled-in attributes, variants to spin out. The hard part is not writing one page: it is writing three hundred and keeping them up to date. So new references sit in draft for weeks for lack of time, and the ones that do go live often carry the supplier's description pasted in, which is the exact same text as ten other stores.
That copied text costs you twice. Google treats it as duplicate content and ranks the page lower, and the visitor reading it finds nothing that would tip them into buying. An AIOS connected to your catalogue writes each page from the supplier data and what you know about the product, in your brand voice, structures it for search, spins out variants and translations, and keeps the whole catalogue consistent. You move from writing every page to reviewing and publishing.
The problem
- Every new reference needs a title, a description, attributes and tags, and it sits in draft for weeks because writing it well takes time you do not have
- The supplier description pasted in is the same text as ten other stores: Google penalises it as duplicate content and it does not convert
- The catalogue is inconsistent, the same information written differently from one product to the next, missing fields, materials and sizes phrased ten ways
- Size and colour variants and translations multiply the work: one product becomes twenty pages to write and keep aligned
How the AIOS handles it
It writes each page in your voice, from your data
You give it the supplier spec sheet, your notes on the product, a few photos: the AIOS turns them into a clear title, a description that leads with the benefit and not just the list of specs, and fills in the attributes. It is not a spec sheet copied over, it is a page that makes people want to buy, written in your brand tone. Show it three or four pages you like and it picks up their length, level of detail and style.
It structures the page for search
For each product the AIOS writes a clean title and meta description, fills the structured attributes (material, dimensions, weight, compatibility), adds the questions buyers actually ask and links the page to its related products and its category. The text is unique from one product to the next, to avoid duplicate content, and built around the words your customers really type, without keyword stuffing that rings false.
It handles variants and translations
A product spun into five sizes and three colours shares a consistent base, without you rewriting the same thing twenty times or variants contradicting each other. And if you sell abroad, the AIOS translates each page into your target markets keeping the tone, not a machine word-for-word, with units and sizes converted locally. One source, cleanly spun out and translated.
It keeps the catalogue consistent and current
The same fields filled the same way across the catalogue, pages missing a description or an attribute spotted and flagged, texts updated when the supplier changes a spec. The AIOS works with Shopify, WooCommerce and PrestaShop: it prepares the pages in your store, as drafts, and you publish them in one click once reviewed. The catalogue stops drifting as items pile up.
A concrete example
We just got 40 references from the winter collection, the supplier file is in the folder. Prepare the pages.
Forty pages prepared as drafts in the store from the supplier file and the photos. For each one: a title, a description of about a hundred and fifty words in the tone of your current pages, filled-in attributes (material, fit, care, dimensions), a meta description, and two frequent questions. Size and colour variants are attached to the parent page, and I prepared the English version of each page for your UK store, sizes converted. Four points for you before publishing. Three references have no composition in the supplier file: I left the field empty rather than invent it, it needs asking. Two references look like the same product under two different codes, the ecru roll-neck jumper in 4831 and 4907, worth checking before creating two pages. One reference is a 390 euro coat, well above your usual range: I wrote the page but I leave the positioning for you to confirm. The rest is ready to review.
Other use cases: Handling first-level customer service
Main page: E-commerce