

An AI shopping assistant can help readers choose products using your content. AON connects their buying questions to merchant offers and referral revenue.

A reader finishes your coffee-machine guide and asks a question the article cannot answer for everyone: “Which of these will fit under my kitchen cabinets?”
Your guide explains the options. Choosing for a particular kitchen takes an answer tailored to that space. If the reader leaves to work that out elsewhere, your site loses the chance to help with the final decision.
AON Content Assistant lets that conversation continue on your pages. It combines page context and the visitor’s question to find structured merchant offers. Readers can compare options for their own needs, and qualifying outcomes can generate earnings for your site. AON hosts the assistant, so your team can add this buying help without first building a chatbot.
An assistant needs a reason to be on the page. “We should add AI” is not a sufficient one.
Look for content where a useful answer changes with the reader’s circumstances:
These needs can appear across buying guides, comparisons and reviews. The opportunity is to help visitors apply the content to the decision they are making, wherever that question arises on the relevant pages of your site.
A page without a buying question can keep its editorial purpose. Make the invitation relevant to what readers came to understand or choose.
A strong article explains the options. A useful assistant helps the reader apply that advice to their own needs.
The conversation can ask for the detail that changes the answer, explain a trade-off and help the reader compare suitable options. For the coffee-machine buyer, cabinet space may rule out models that looked equally promising in the article. Personal requirements turn general advice into a more specific buying request. Sometimes the next useful step is a clarification.
Keep buying guidance consistent with the criteria your content explains. The reader’s requirements should remain the reason for a recommendation, with the commercial relationship made clear through a brief disclaimer.
Existing affiliate links can remain useful. They serve readers ready to follow the page’s recommendation. An assistant can help readers resolve the buying questions a static link leaves open. The two experiences address different reader needs.

AON supports different integration routes. The practical choice is how much of the product your team wants to build and operate.
| Route | What your team takes on | Where it can fit |
|---|---|---|
| AON Content Assistant | Configure a placement and add the web integration | A publisher that wants buying assistance on existing pages |
| A custom assistant connected to AON | Build the conversation, query offers and render your own interface | A product team with a distinctive advisor experience or workflow |
A chat interface is only part of the experience. Product discovery needs concrete merchant offers behind the answer. AON provides structured product and commercial information, matches the buying request and connects referrals to reported outcomes.
With AON’s hosted Content Assistant, that commercial connection comes with the conversation. It uses the page and the visitor’s request to find offers from the network. Your team does not need to assemble a separate promotional product list for each article.
If your team already owns an agent, MCP offer discovery may fit its tool workflow. A bespoke website experience can also use the REST API or SDK. That route gives the team more interface responsibility as well as more freedom.
Choose the approach that fits your reader experience and technical resources. The hosted route handles the conversation and offer presentation. A custom route makes sense when the advisor experience is part of the product you want to own.
For the hosted web route, choose a floating entry, an end-of-content entry, or both:
Give that entry a clear purpose in the surrounding article. After a coffee-machine comparison, explain that the assistant can help readers apply the advice to their own kitchen. Keep the article easy to read for someone who does not open the assistant.
Create a Content Assistant placement and add the integration through the shared layout of the relevant public HTTPS pages on your domain. This makes the assistant available across those pages, with each page supplying its own context.
The step-by-step installation walkthrough explains the setup. Use the Content Assistant setup guide for the script and required page marker.
Define what better buying help should achieve for the site. A coffee-machine guide might attract readers who understand the category but still need help finding a model for their kitchen. The goal is to continue helping those visitors before they leave undecided.
Set the goal at three levels:
Identify the question visitors should be able to resolve. A clear goal might be helping them narrow a shortlist using their own requirements, rather than simply increasing how often a chat window opens.
Aim to earn from buying assistance that adds something to the page. Distinguish that opportunity from moving an existing purchase between two links. Consider the audience markets and content topics where the additional help has a clear purpose.
Decide which page groups and time periods you will compare, and which reader and revenue measures matter to your business. Those choices give later results a useful context.
The content should continue delivering the value that earned the visitor’s attention, whether or not they open the assistant.
Judge the complete page over the same period, including existing advertising and affiliate income, reader response and operating effort.
Use your site’s analytics for page visits and assistant-entry engagement. AON’s offer performance reports cover clicks, conversions and estimated earnings. These sources answer different questions: opening the hosted assistant does not tell you everything that happened in the conversation. Its offers and conversation remain inside the panel; the web-plugin reference explains the available host-page events.
If the assistant moves a purchase away from an existing editorial link, that is different from helping a reader who would otherwise leave undecided. Include that overlap when deciding whether the new path adds business value.
Include page integration, editorial review and reporting effort in the business calculation. For a custom assistant, add model and infrastructure costs. Keep estimated earnings, approved commission and payments received separate.
A comparison across similar pages can help you assess the change. Use enough observations to avoid treating a handful of purchases as a stable business model. AON’s attributed earnings show the commercial results of its referrals; the wider page comparison helps you assess the added business value.
Your next revenue opportunity may already be in the questions readers ask after your guides. The visitor with an unresolved requirement has a reason to keep talking to the website that helped them understand the category.
AON Content Assistant gives that visitor a way to continue choosing on your site, backed by merchant options. You can extend the help across suitable pages while your articles and existing links continue serving readers. Your team brings the content and audience relationship; AON hosts the buying conversation and its commercial connection.
Set up AON Content Assistant on your website →
Teams that already operate an advisor can connect it to AON’s shopping MCP server.
Yes, provided each element has a useful role and the page remains comfortable to use. Existing links may serve readers who have already chosen; an assistant can help those with an unresolved requirement. Measure overlap, total page revenue and reader response before deciding whether the new experience adds value.
No, a publisher can use AON Content Assistant without building its own chatbot. AON hosts the Content Assistant conversation and its offer connection. Your team adds the web integration and configures the placement. Building a custom assistant is an option when you want to own the conversation and interface, rather than a requirement for adding buying assistance to your site.
Yes, the AON web integration can be added across the supported public pages you choose. Add the web integration through the shared layout of the supported public pages that should carry it. Each page provides its own subject context, and the visitor’s question adds their requirements. You do not need to create a separate assistant for every article. The installation guide covers page requirements and the required end-of-content marker.
Bring a public example page, the decisions readers need help making, audience markets and the monetization methods you already use. Explain whether you want a hosted experience or already own an assistant. That gives the discussion a business focus: suitable deployment, relevant supply and how to assess the added value.
No, AON Content Assistant discovers offers without a handpicked list for each article. AON Content Assistant matches network offers to the page and to what the reader asks. You choose where to make the assistant available and the supported entry style. The conversation can then help readers apply your advice to their own requirements without a separate curated offer list for every page.
Try live offer search without an account or API key. Start building today — go live when you are ready.