What answer engine optimization services should deliver

Whoever you hire, the output should be inspectable. Ask for these by name:

• A question inventory. The real questions your buyers ask, pulled from Search Console queries, People Also Ask boxes and keyword data, not brainstormed in a workshop.
• One page per question, answer first. The opening paragraph answers the question in plain terms; the rest of the page earns the right to be believed.
• A quotable definition on every page. One or two sentences that stand alone when lifted out of context.
• FAQ blocks with FAQPage JSON-LD. Follow-up questions answered in a short paragraph each, marked up so the answers are machine-readable.
• Crawler access. Confirmation that GPTBot, PerplexityBot and Google-Extended can fetch the pages, plus an llms.txt if you want one.
• First-party facts. Numbers and specifics from your own product data, datasheets or support history that no competitor's page can carry.
• A citation report. Which questions were put to which assistant, and whether your site was named.

If a proposal lists "AEO strategy" and "AI readiness" without any of these nouns attached, you are being sold a retainer, not a result. Every item above is a file, a page or a report you can open and check.

Answer engine optimization services are sold three ways, and the billing model tells you what you are really paying for.

Agency retainer. A monthly fee buys a team's time: an audit, a content plan, a fixed number of new or rewritten pages, and a report. You pay whether or not the pages get cited, and output is capped at what people can write and review in a month. Good agencies bring judgement, and you pay for it by the hour.

Software subscription. A monthly licence to a tool that drafts or scores content. Cheaper per page, but briefing, editing, publishing and measuring stay with you, and the bill is the same whether you publish one page or fifty.

Per published article. You pay for finished pages that go live, and nothing for drafts that fail review. That is IT Master's model: a prepaid balance, no subscription, four quality tiers, and a price per published article set out on the pricing page.

None of these is wrong. A retainer suits a business that needs strategy more than pages. Software suits a team with writers and time. Per-article suits anyone who wants checked, published pages at a steady cadence without hiring for it.

Each article runs through one pipeline, with the AEO deliverables built in rather than bolted on.

Discovery pulls real demand from DataForSEO and your Search Console, so every topic starts as a question someone typed. Research reads the competing pages, your first-party data (product records, datasheets, support Q&A) and relevant forum threads, then finds what the competitors left out.

A Claude model writes a question-led article: the direct answer in the opening, a quotable definition, sections that follow the buyer's follow-up questions, and an FAQ block. The draft then enters a validation gauntlet: a fact-check and a novelty score against the competitors by Gemini and GPT judges, plus an E-E-A-T critique and AI-tell detection, none of it by the model that wrote the draft, with up to three revision rounds. 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.

A passing article publishes to your site with JSON-LD schema including the FAQ, internal links into your existing pages, a hero image and an IndexNow ping to the search engines. The full sequence is on the how it works page.

The point of AEO is to be named as a source, so the measurement has to ask the assistants directly. Every night IT Master puts a fixed set of your buyers' questions to GPT and Perplexity and records whether your site is cited, alongside the Search Console clicks and impressions for the same pages. Having both numbers is how you tell a page that ranks from a page that gets quoted.

The same nightly loop watches for decay. When a page's impressions slide or its facts go stale, it is queued for a refresh rather than left to sink.

Two things this measurement will not do. It will not promise a citation: assistants change their sources week to week, and any vendor who promises you placement is guessing. And a week of data is noise; judge the trend over a quarter.

You can run a version of these checks yourself first. The AI visibility checker puts buyer questions to the assistants and shows whether your pages appear as sources, the AEO checker scores any URL on nine deterministic checks, and the AI crawler check reads your robots.txt to show which assistant crawlers you allow or block.

Nothing here requires a new CMS. On WordPress, install the plugin, paste one key, and articles arrive as posts with the Yoast or Rank Math fields filled. On Next.js, @itmaster/sdk renders the feed. Anything else can consume the REST pull feed or receive a signed push webhook at any endpoint. Shopify and Webflow we set up for you on request; Wix and Squarespace get a copy-and-paste queue.

The engine runs today on cctvline.co.uk and cctvmaster.co.uk (UK CCTV trade and retail), eurocctv.co.uk (UK CCTV trade) and 1xai.ir (AI developer tools, in Persian). Each is grounded in whatever first-party data that site holds: product records, datasheets, support questions. Editorial responsibility sits with Editor-in-Chief Rodd Azad, a software engineer and the founder of IT Master and code-nest.dev.

If you want to know where you stand before spending anything, run the free site check. It shows what search engines and AI assistants currently find on your website, and what we would write first. No account, no card.