Choosing networks

Networks → Available Networks. Tick the ones you want and use the arrows to put them in order; the order in the list is the order on the page. The arrows work from the keyboard too: focus stays on the arrow you pressed, so moving a network three places is three presses, and a screen reader hears its new position.

Keep the row to the networks your readers use. Look at your dashboard after a few weeks and drop whatever nobody uses.

The floating rail and the pinned bar can each have a list of their own, so the bar on a phone can carry WhatsApp, Copy link and More while the row under a post keeps X, Facebook, LinkedIn and Email. That is chosen under Display → Positions (see Display, below). While either of them has its own list, this screen says so above the tick list, with a link to Display, and what you tick here reaches every other position but not that one.

Three of the buttons are not networks at all:

• Copy link copies the page's canonical URL. It is quietly one of the most used buttons on most sites — people share by pasting into a message far more often than through a share dialog.
• Print opens the print dialog, which recipe and reference sites want.
• More opens the phone's own share sheet, with every app the reader has installed. On a desktop, where no share sheet exists, it copies the link instead of doing nothing.

Email, Copy link, Print and More are ordinary words rather than brand names, so they appear in your site's language. Brand names stay as they are.

Mastodon has no single website, so a reader who uses it is asked which server they are on, with an example in the question. The answer is remembered in their browser and is already in the box the next time, so sharing again is one press of OK, and a reader who gave the wrong server can change it. If what they type is not a server address, they are told and asked again. There is no setting for this: without the question, the button has nowhere to send the share.

Add a Pinterest button to images puts a Save button on the images in a post, so a reader can pin the photo they are looking at rather than the featured image. It is off until you switch it on. The button appears when the image is pointed at or reached with the keyboard, and all the time on a touch screen. It pins that image with its alt text as the description, and each press is counted as a Pinterest share. Only images in the post's own content that are more than 200px wide get one. To leave one out, select it in the editor, open Advanced, and add nopin under Additional CSS class(es); the nopin and data-pin-nopin attributes are honoured too.

Ask an AI about this page#

Networks → Ask an AI. Buttons for ChatGPT, Claude, Perplexity, Google AI Mode and Grok. Each opens the assistant in a new tab and asks it about the page the reader is on. None is ticked to begin with, on a new site or an updated one: tick the ones you want and use the arrows to put them in order. The Dashboard offers them once, drawn in your style, with Add these buttons (all five) and No thanks.

Where they go: in a row of their own under the share buttons, with the heading "Ask AI about this page", or at the end of the share buttons. They appear wherever the share buttons do above and below the content, in the product summary, and in the block, shortcode and template tag. The floating rail and the pinned bar keep to their share buttons. Leave Heading empty for the default in your site's language, or type your own.

Prompt is what the assistant is asked. Left empty, it is "Summarise this page and list its key points: {url}", in your site's language. To write your own, use {url} for the page's address and {title} for its title, for example Explain {title} to a beginner: {url}. Keep {url} in it: without the address, the assistant does not know which page the reader means. With WPML or Polylang, the prompt and the heading are translated like the other words on this screen.

Nothing from these services is loaded on your pages, and nothing is sent to them until a reader presses a button. Then the reader's browser opens the service with the prompt, page address included; no UTM tags are added to it. Each press is counted like a share, under the service's name: on the Dashboard, in the Shares column and in a post's Share buttons box.

What happens next is the service's choice. ChatGPT and Perplexity answer at once, Grok shows the prompt and asks the reader to send it, and Claude asks a reader who is not signed in to sign in first. None of them documents the address it takes a prompt from, so these can change; a button whose service stops reading the prompt still opens that service.