solutions · ecommerce stores

Buying guides written from your catalogue, linked to your products

A product grid does not answer the question a shopper asks first. IT Master writes the guides and comparisons that do, grounds them in your own product data, and links each one to the products it recommends.

reviewed 2026-09-02 · by the IT Master editorial team · how we check facts

what usually goes wrong

Our category pages are two lines of copy above a product grid, and nothing on the site answers the questions shoppers ask before they choose.
Every buying guide we have paid for reads like the manufacturer's brochure rewritten, because the writer never saw our stock, our prices or our returns.
The blog posts we do have never link to the products they discuss, so an article that ranks sends the reader nowhere.
We tried an AI writer and it stated a specification our product does not have, and nobody caught it before it went live.
When the range changes, last year's guides quietly go out of date because nobody has time to revisit them.

what changes

Shoppers who search a question land on a page that answers it and links to the product.
Every guide links to the products and the category it discusses.
Specifications come from your catalogue rather than a model's memory.
Guides are rewritten when demand or the range moves.
Spend follows articles that publish rather than a subscription.

The question a category page cannot answer

A category page has one job: show the range and take the click. It rarely ranks for the question a shopper asks before they get that far, because a grid of products is not an answer to “which 4K camera actually sees at night” or “what size dehumidifier does a three-bedroom house need”.

That is where most of the demand sits, and it is measurable. IT Master reads it from DataForSEO and from your own Search Console, groups the queries under the categories you already sell, and writes three shapes of page against them:

Buying guides that take a shopper from a need to a shortlist of products you stock.
Comparisons between two models, or two approaches, using the specifications held in your catalogue.
Category-supporting articles that answer the long-tail questions around a category and point down into it.

Each article publishes with JSON-LD schema, an FAQ block, a hero image and internal links, on a steady cadence rather than in a batch. Together they catch the informational search and hand the shopper on to the page that takes the order.

Your catalogue is the part a competitor cannot copy

Research that reads only the pages already ranking produces a competent summary of pages that already exist, and Google has no reason to rank an eleventh.

IT Master reads the competitors too, but the facts in the article come from your side of the fence. Before a word is written, the engine retrieves whatever first-party material the store holds:

product data: titles, variants, specifications, what is in the box;
supplier datasheets and manuals for the lines you sell;
support Q&A and returns notes, where you keep them, which record the questions buyers actually asked and why things came back.

A comparison built on that can say which of two models has the wider field of view, and which one buyers returned over a firmware fault. Those sentences are on no competitor page, because no competitor holds the data. That is what a novelty check rewards, what an AI assistant has reason to quote, and what a rival cannot reproduce by rewriting your page. Where the data is thin the article stays inside what can be verified instead of filling the gap. First-party data explains the retrieval side.

in one sentence

First-party grounding means an article's facts are retrieved from the store's own product data, datasheets and support answers before a word is written, so a rival cannot reproduce the page without the same data.

Links that point down into the catalogue

A guide that ranks but does not link to the products it recommends is a leak. IT Master places internal links from the same retrieval layer that grounds the article, so the link to a product page goes in where that product is named, not into a footer block of related posts.

They run in three directions:

down to the product pages the guide names;
across to the category the guide supports, so that category collects a link from every article in its cluster;
sideways to sibling guides and comparisons, which builds a topic cluster instead of a pile of orphaned posts.

New articles link back into earlier ones in the same cluster, so the cluster thickens as it grows and nobody edits old posts by hand. Article and FAQ schema ship in the same payload, and IndexNow pings the search engines as soon as the page is live rather than waiting for a crawler to find it.

Why a wrong specification does not ship

For a store, a false spec is worse than a dull paragraph. It is a return, a chargeback, and a customer who does not come back. So the check is structural rather than a promise: the model that writes is never the model that checks.

Writers are Claude models. Once a draft exists, judges from a different vendor, Gemini and GPT, run four checks in parallel: a fact-check against the retrieved catalogue and datasheet material, a novelty score against every competitor page pulled during research, an E-E-A-T critique, and an AI-tell detection pass. A draft that fails any of them goes back to the writer with the specific objections, for up to three revision rounds, and is rejected if it still fails.

The numbers are worth stating plainly. Across 186 Standard-tier runs, 51% of drafts passed every check first time; the rest were revised or rejected. Pro-tier judges are stricter: 25% first-pass, across a small sample of 16 runs. The rejects are the point. How it works walks the full pipeline.

Live example: cctvmaster.co.uk

cctvmaster.co.uk sells CCTV to UK trade and retail buyers, and it runs this engine against its own catalogue. The store holds what the approach needs: specifications for cameras, recorders, cabling and kits, supplier datasheets for its main lines, and a history of buyer questions.

So a guide to choosing a recorder can quote channel counts and storage figures from the datasheet the store already holds, and a comparison between two camera lines can use the specifications of the exact models on the shelf and link straight to them. Nothing in either article depends on a model remembering a number.

The sibling sites cctvline.co.uk and eurocctv.co.uk run the same pipeline against their own catalogues, each with its own brand voice and its own retrieval collection, kept apart from one another. What is shared between them is the method, never the content or the data. The security and CCTV page goes through that in more depth for the trade.

Delivery, cost, and the loop that runs after publishing

Articles arrive on whatever the store runs. On WordPress, install the plugin, paste one key, and posts appear with the Yoast or Rank Math fields filled. Next.js storefronts use @itmaster/sdk; anything else can read the REST pull feed or take a signed webhook. Shopify and Webflow we connect for you on request; Wix and Squarespace get a copy-paste queue your team posts from.

You pay per published article from a prepaid balance, with no subscription, and a draft that fails the checks is not charged at the full rate. Four tiers, Lite, Standard, Pro and Premium, differ in the writer and the strictness of the judges. Figures are on pricing.

Publishing is not the end of the job. A nightly loop reads Search Console per article, spots pages that have started to decay and queues a refresh, which runs the research and grounding stages again against the catalogue as it stands then. The same loop tracks whether GPT and Perplexity cite you. Start with the free site check.

questions people ask

Does this work with Shopify?

Yes, with a setup step on our side. There is no self-serve Shopify plugin yet, so we connect the store for you on request, and articles then arrive as blog posts with schema and internal links already in place. WordPress stores install the plugin and paste one key. Next.js storefronts use the @itmaster/sdk package. Anything else can pull the REST feed or receive a signed push webhook to its own endpoint. Wix and Squarespace are served through a copy-paste queue that someone on your team posts from.

What does the engine need from my catalogue?

Whatever you already have, in the format you already have it. At minimum, product titles, descriptions and specifications. Results improve with supplier datasheets and manuals, and improve again with support Q&A or returns notes, because those hold facts your competitors cannot see. Nothing needs rewriting or reformatting first. Where a product's data is thin, the article leans on the research stage and stays inside what can be verified rather than inventing the missing detail, which is also what the fact-check judge is looking for.

Will the articles just be rewrites of what competitors already published?

That is checked rather than promised. During research the engine fetches the pages currently ranking for the topic. After writing, a judge from a different vendor scores the draft's novelty against all of them, and a draft that reads as a blend of the top ten fails and goes back for revision. Grounding is what makes a good score achievable in the first place: a comparison citing your own datasheet figures and your own returns reasons contains sentences that appear on no competitor page, because no competitor holds the data.

What happens when a product sells out or is discontinued?

Articles are not written once and abandoned. The nightly loop reads Search Console for every published page, flags the ones losing impressions or position, and queues a refresh. A refresh runs the research and grounding stages again, so it reads the catalogue as it stands that night rather than as it stood when the guide was first written. Internal links are placed from the same retrieval layer, so a refreshed guide points at products the store currently lists, and the revised article reaches your site by the same route the original did.

How do I pay, and what if a draft fails the checks?

You pay per published article from a prepaid balance, and there is no subscription. A draft that still fails validation after its revision rounds is rejected rather than published, and a draft that fails the checks is not charged at the full rate. Four quality tiers are available, Lite, Standard, Pro and Premium, which differ in the writing model and how strict the judges are. Per-tier prices are on the pricing page. The free site check costs nothing and needs no balance, so it is the cheapest place to start.

How does it decide what to write about?

From demand rather than from a topic list someone typed up. The engine pulls keyword and question data from DataForSEO and from your own Search Console, then groups those queries under the categories you sell, so each article supports a category or product page that can convert. Articles publish on a steady cadence instead of arriving as a batch, which is safer for a young site. The nightly loop re-reads Search Console to see which topics are gaining and which published guides have started to slip.

See what search engines and AI assistants find on your site

Free, no account. Type your address and we show you what is missing and what we would write first.

Check my site See pricing