AI Share Buttons is a WordPress plugin from BeeClear – an agency focused on website visibility in search engines and in answers generated by language models. It adds a row of buttons to your content that open ChatGPT, Claude, Perplexity, and other AI systems. What sets it apart is its own prompt with placeholders for the current page. The visitor doesn’t paste a link or come up with a question, because the instruction is already sitting ready in the chat window. See how this mechanism works and how to craft prompts for your own content.
Table of contents
- Why isn’t a plain share button enough in the age of AI assistants?
- What is a prompt element in AI Share Buttons?
- How do the %url%, %host%, and %title% placeholders point to the current page?
- What prompts should you prepare for different types of content?
- Which AI systems accept the prompt straight from the button?
- Does the prompt in the button send your page content to the AI provider?
- How does the label next to the buttons preview what the prompt will do?
- How do you check which prompt readers click most often?
- How do you set up your first prompt in AI Share Buttons?
Why isn’t a plain share button enough in the age of AI assistants?
A plain share button just passes along the page address, and that’s the end of its job. Someone who wants to discuss the article with an AI model has to copy the link and write their own question. Not everyone bothers. The rest ask in their own way. The answer then ends up generic, or misses the point of the text.
As the author, you have no say in what the model actually gets asked. You can’t suggest that the article is worth summarizing, translating, or comparing to the reader’s own situation. AI Share Buttons closes that gap. The plugin hands the model not just the address, but a whole instruction written by you. You decide what question kicks off the conversation about your content.
What is a prompt element in AI Share Buttons?
An AI Prompt is an element in the AI Share Buttons dashboard that stores the wording of a prompt and the settings for one set of buttons. You write the prompt in it once, and the plugin uses it across many pages at the same time. In that same place, you choose the AI systems, their order, the label next to the buttons, and how they get inserted. Each element also has its own shortcode.
You can create several such elements and assign them to different parts of the site. A button only shows up when the prompt is active, has content, and the given system is enabled for it. An inactive prompt renders nothing at all, even through the shortcode. That means you can switch the whole thing off with one move, without having to hunt for it inside your posts.
How do the %url%, %host%, and %title% placeholders point to the current page?
The %url%, %host%, and %title% placeholders point to the current page because the plugin substitutes its data in for them at render time. One prompt can then serve hundreds of posts, and each link tells the chatbot exactly which page it’s about. Here’s what fills in for each placeholder:
- %url% inserts the permalink of the page being viewed,
- %host% gives just the host name, i.e. the site’s domain,
- %title% adds the page title.
The plugin encodes the finished text and appends it to the chosen AI system’s URL. Addresses with parameters reach their destination intact, with no garbled characters. A sample prompt might read: “Summarize the article %title% from %url% in five bullet points.” On every post, the reader sees a different title and a different link in the chat window, even though the instruction was only written once.
You can combine placeholders freely with your own text and drop them anywhere in a sentence. A prompt for a knowledge base might read: “Read the page %url% and answer my questions about its content.” Meanwhile, %host% comes in handy for something like “What other materials on this topic does %host% publish?” The plugin doesn’t dictate the language or the form of the prompt – you decide the tone of the conversation.
What prompts should you prepare for different types of content?
It’s worth preparing prompts separately for each type of content, because a blog visitor and a documentation user need different things. On a blog or a content portal, a request for a summary, a translation, or a discussion of the article works well. In documentation and knowledge bases, an instruction that opens the help page for further conversation works better. The visitor will then ask for details in their own words.
You can insert each AI Prompt element in two ways. The shortcode places it anywhere in the content. Automatic insertion adds it before or after the content – on individual posts and on pages with selected templates. That way, a blog post gets a different prompt from a help page, with no manual work needed for each publication. Developers can extend automatic insertion to custom content types with the beeclear_ai_share_auto_post_types filter.
Which AI systems accept the prompt straight from the button?
The prompt goes straight from the button into six of the seven built-in AI systems. The exception is DeepSeek, which doesn’t offer a parameter to prefill the chat via the URL. Clicking it opens an empty conversation there, and the question has to be pasted in manually. Here’s how it plays out for each system:
| AI system | Does it receive the ready-made prompt? |
|---|---|
| Google AI Mode | yes |
| Copilot | yes |
| ChatGPT | yes |
| Claude.ai | yes |
| Perplexity | yes |
| Grok | yes |
| DeepSeek | no – opens an empty conversation |
For each prompt, you only enable the systems you want and set their order by dragging them. If an empty conversation in DeepSeek doesn’t work for you, just turn it off. A developer can also redirect it elsewhere with the beeclear_ai_share_systems filter. Each system gets either a text label or an image, with optional width and height.
Does the prompt in the button send your page content to the AI provider?
The prompt in the button doesn’t send your page content to the AI provider, because your server never connects to it at all. The mechanism relies on a plain link with the instruction text embedded in the URL. The visitor’s browser opens it in a new tab, with the rel attribute set to noopener noreferrer nofollow. The provider only sees what the browser sends after the click.
The plugin makes no outgoing HTTP requests and doesn’t store any visitor data. It also doesn’t change posts in the database, since everything is appended at the moment the page renders. Once deactivated, the buttons disappear without leaving any trace in the content. That matters if you care about user privacy and keeping your database clean.
How does the label next to the buttons preview what the prompt will do?
The label next to the buttons previews what the prompt will do, because the visitor only sees the actual instruction after clicking. A short label like “Summarize this article with AI” tells them what to expect. You set the text separately for each AI Prompt element. By default it reads “Summarize this content with AI,” so it’s worth writing your own to match your site’s voice.
You choose the label’s position from three options: to the left of the button set, above it, or not at all. On top of that, there are three button sizes – small, medium, and large. Keeping the label consistent with the prompt’s content builds trust. Someone who clicks “Translate this text” should get a translation, not a summary.
How do you check which prompt readers click most often?
You can check which prompt gets clicked most often in Google Tag Manager, since every click pushes an ai_share_click event to the dataLayer. The event carries the name of the AI system, the prompt, and the button’s position. The position tells you whether the click came from the row at the start of the content, at the end, or one inserted via shortcode. A trigger based on this custom event in GTM is all you need for a report.
Data like this lets you compare different instructions. You can see whether readers prefer a summary over a translation, and which AI system attracts them the most. Based on that, you adjust the prompt’s wording, the order of the systems, or where it’s inserted. The prompt stops being a one-off piece of text and becomes a tool for deliberate improvement.
How do you set up your first prompt in AI Share Buttons?
You can set up your first prompt in AI Share Buttons in a few steps, starting from the “AI Prompts” submenu in the WordPress dashboard. The plugin requires WordPress 6.3 and PHP 7.4 or newer. Here’s the sequence:
- add a new AI Prompt element and mark it as active,
- write the instruction using the %url%, %host%, or %title% placeholders,
- enable the AI systems you want and arrange their order,
- set the label text and its position – next to the buttons, above them, or not at all,
- choose the shortcode or automatic insertion before or after the content.
You can move your finished settings and all your prompts to another site by exporting and importing a JSON file. You can adjust the look with your own class and global CSS, or with a stylesheet assigned to a single prompt. Want help matching prompts to your own content? You’ll find details and contact information about implementation on the AI Share Buttons plugin page.
