AI replies with inline source links to your actual articles
SleekAI matches each visitor question to articles in your WordPress library, then formats the answer with inline links whose anchor text and URL come directly from wp_posts. Use your own OpenAI, Anthropic, Google, or OpenRouter key.
Why answers need inline links, not just citations
A citation at the bottom of a reply is fine. An inline link inside the sentence is better. Visitors do not always read past the first line, and a citation tucked underneath often gets ignored. When the link sits inside the phrase that triggered curiosity, click-through to your real content jumps and the bot starts acting as a guide instead of a dead-end answer.
SleekAI builds inline source links from your WordPress data. Anchor text comes from post_title or a custom display field. The URL comes from the permalink stored against the post ID.
The hard part is balance. Too few links and the bot reads like a sealed paragraph. Too many and the reply becomes a sea of underlined fragments. Generic chatbots cannot tune this because they have no concept of your post taxonomy, no view of which articles already cover the topic, and no way to vary anchor text based on what the visitor actually asked.
Features
Inline anchors, not footers
Links appear inside the sentence that mentions the topic. Visitors do not have to scroll past a citation block to find the source, so click-through rises and the bot reads more like a knowledgeable colleague.
Pulled from your library
Every link points to a real WordPress post you have already published.
Scoped by taxonomy
A docs bot links only to docs, a blog bot links only to articles, and you avoid embarrassing cross-links between unrelated content areas.
Where source-linked answers earn their keep
Onboarding tutorials
Walk new users through setup by linking each step to the matching tutorial. The bot becomes a guided table of contents that adapts to whatever question the visitor actually asked.
Editorial sites
When readers ask about a topic, the bot points at your strongest article on it and adds related coverage as secondary links. Page views rise without resorting to clickbait recommendation widgets.
Internal knowledge bases
Employees ask process questions and the bot replies with inline links to the matching internal docs. Cuts the time spent searching SharePoint or Confluence-style sites for the right page.
How the source-link pattern works
Map your articles
Choose which post types and taxonomies the bot can see. Titles come from post_title in wp_posts. Permalinks come from the same post IDs. Taxonomy filters scope which posts are eligible per chatbot.
Set the link rules
The system instruction defines anchor format, max links per reply, and what to do when no source matches. You can also require that each reply contain at least one link if your editorial policy demands it.
Map your data
Choose the posts, fields, taxonomies or users the bot should know and reference them in the instruction.
Set display conditions
Decide which pages, post types, roles or logged-in states show the chatbot.
Why inline links beat footer citations
Visitors do not read chatbots the way they read documentation. They skim the first line and act on it. A citation tucked at the bottom of a reply often goes unread. An inline link sits inside the sentence that hooked their attention, so the click happens at the moment of peak curiosity.
That click is the difference between a chatbot that closes conversations and a chatbot that opens them. A closed conversation ends in the chat window. An open conversation lands the visitor on your article, where they can keep reading, sign up for a newsletter, or buy something. Inline source links also reframe what the bot is doing.
It is no longer pretending to be the encyclopedia. It is acting as a librarian who points at the right shelf. That posture is honest about what the model can and cannot do, and it builds trust faster than confident summaries ever will. Operationally the pattern protects your content strategy too.
Every link the bot inserts is one your team controls. You wrote the article, you chose the URL, you can edit it later. Generic chatbots that quote external URLs send traffic away from your domain. Source-linked replies keep visitors moving through your library and turn the chat widget into a discovery surface that complements search.
Frequently asked questions
How does the bot decide which article to link?
Mapped posts are visible to the model in the prompt along with their titles and permalinks. The system instruction tells the model to pick the most directly relevant article, prefer canonical pages over tangential ones, and avoid linking the same article twice in one reply.
Can I customize the anchor text?
Yes. By default the anchor text matches post_title. You can map a custom field like seo_anchor instead, or instruct the model to use a short rephrased anchor while linking to the canonical URL stored against the post.
Does this support custom post types?
Any post type registered in WordPress is fair game. Docs, courses, recipes, case studies, knowledge-base entries. Map their permalink and title as visible variables and the bot will link to them inline like any other source.
How many links per reply is sensible?
Two or three inline links per reply is a strong default. More than that starts to read as link soup and click-through actually drops. The system instruction can enforce a cap, and you can adjust it per bot if a topic genuinely needs more sources.
Will the bot ever link off-site?
Only if you map external URLs into the data the bot can see, for example a postmeta field with a partner link. Default behavior is your own domain. Off-site links happen only when you deliberately expose them.
Will the bot work with my own AI provider?
SleekAI uses your API key for OpenAI, Anthropic, Google, or OpenRouter. The link-formatting logic lives in the prompt and the data mapping, not the model. Any reasonable instruct-tuned model can produce inline links reliably.
Which AI providers does it support?
OpenAI, Anthropic, Google and OpenRouter, plus custom OpenAI-compatible endpoints. You bring your own API key and the provider bills you directly.
Where does the chatbot get its answers?
From the WordPress data you map into its instruction: post titles and content, post meta, ACF and Meta Box fields, taxonomies, terms, users and user meta, or a WP_Query. Values resolve on every request.
Pricing
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
…or get the Bundle Deal
and save €250
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
SleekAI
SleekByte
SleekMotion
SleekPixel
SleekView
SleekRank
SleekTrack