Schema.org markup for Webasyst Hub: discussions in rich results & AI answers

A living community brings customers from search and AI - if machines can understand what happens on your discussion pages. People increasingly ask a search engine or an AI "how to choose", "will it fit", "what is the difference" - and the answer is built from discussions the system can trust. Schema.org markup turns every forum topic into a machine-readable publication: headline, author, date, the gist of the thread. The plugin adds it for you - no code, no theme edits.

68% of Google searches now end without a click (SparkToro, 2026) - being the cited source is the new visibility. A rich result lifts click-through by 25-50% (SEO industry data); in Google Search Central case studies markup gave Nestlé +82% and Rotten Tomatoes +25% clicks. Visitors from AI answers convert 4-9x better (Digital Applied, 2026). The JSON-LD format this plugin uses is officially recommended by Google.

What you get

Three benefits - three reasons each

Discussions stand out in search

A topic shows up as a publication: date, author, breadcrumbs - not a bare blue link.
Rich results lift click-through (Google cases: Nestlé +82%, Rotten Tomatoes +25%).
Freshness is machine-readable: the topic date and the last reply are passed explicitly - and fresh content wins citations (Ahrefs, 2026).

AI understands your discussions

Markup tells the machine directly: this is a discussion, here is the author, the date, the gist - no guessing from raw code.
AI cites explainers and Q&A first: 43.8% of ChatGPT citations are "best / how to choose" content (Ahrefs, 1.4M prompts, 2026).
An author with their own page in the markup is an E-E-A-T signal both search and AI use.

Runs by itself

You write nothing: the markup is built from your topics, authors and community settings.
Discussions, the company card, breadcrumbs, authors, streams and sections - all marked up automatically.
One consistent document with no duplicates - passes validator.schema.org and Google Rich Results.

How search and AI decide what to show

The same discussion - two different endings

When a search engine or an AI prepares an answer, it looks at your discussion topic. The difference is what exactly it sees there - and that decides whose discussion gets cited and whose link gets clicked.

Without markup

The system sees raw code: menus, banners, scripts - and has to guess where the question is, who answered and what it is about.
In search results - a plain blue link with no date, author or breadcrumbs.
The AI is not confident in the data and leaves your discussion out of the answer.

→ the person lands on someone else's site

With markup

The system reads a ready-made discussion card: headline, author, date, section - no guessing.
In search results - a publication with a date, an author and neat breadcrumbs.
The assistant cites your answers and links to your discussion.

→ the person and the lead come to you

Why right now

Google dropped FAQ snippets but doubled down on discussion markup

In spring 2026 Google stopped showing FAQ snippets - the old way to "draw Q&A into the results" no longer works. Yet it expanded forum and discussion markup instead: live community threads are now exactly the format search shows as a rich result (per Google Search Central and Search Engine Land).

For your community that is a direct hit: the plugin marks topics up as forum discussions (DiscussionForumPosting) - the very type in favor now, not the deprecated FAQ. You get the current markup format without a single line of code.

AI search and chat assistants

Markup is the language AI reads your discussions in

An assistant on a phone, in a browser or on a speaker does not carefully parse your site itself - it passes the question to its AI, which builds the answer from AI search. The topic title, the author and the gist of a thread are far easier and safer for AI search to take from structured markup than to guess from raw HTML. Markup is a caption on every page: "this is a discussion, here is who and what about".

ChatGPT
Gemini
Claude
Perplexity
DeepSeek
Alice AI (Yandex)
YandexGPT

In Russia, Alice's AI answers reach tens of millions of people a month, and Alice reads Schema.org markup. The clearer your discussions are to a machine, the better the odds of landing in that answer.

What the plugin marks up automatically

People discuss - the plugin describes it for machines

Discussion topics - headline, author, publish and update dates, image, gist: a complete machine card for every thread (DiscussionForumPosting).
Author - a card linked to the author's own page: an expertise signal for search and AI.
Breadcrumbs - Home → Community → Topic, with working links.
Organization - name, logo, contacts: your company's passport for search and AI.
Sections, tags and the community stream - marked up as collections listing fresh discussions.

Nothing extra leaks out. Only what is already public to a visitor gets marked up: published topics and sections. Drafts and hidden discussions never enter the markup. The built-in checkup shows what is marked up and warns if your theme outputs its own markup (a duplicate hurts).

Stronger together

llms.txt guides AI through the community, markup describes each discussion

These are parts of one system that prepares your site for AI search. llms.txt is the map: it shows the AI where sections and discussions are (where to go). JSON-LD markup is the meaning of each page: what kind of discussion it is, who wrote it, when (what to show). Social preview is a neat discussion card when the link is shared in messengers and social networks, bringing people back to you. Together they give AI a full map, precise facts and live distribution.

llms.txt - where to go JSON-LD - what discussion OG preview - link is shared rich result + AI citation

llms.txtCommunity map for AI →

Social preview (Open Graph)A neat discussion card in chats →

Three plugins of the single KakTak.Net line - map, meaning and preview - prepare your community for AI search together. One style, one support, one ecosystem.

Base and premium edition

Base - one domain, premium - all domains

Base 1 domain

Your community's main domain.
Full markup: discussions, author, breadcrumbs, organization, sections and tags.
Built-in duplicate-markup checkup.

Premium multi-domain

All community sites on different domains - at once, automatically.
Own data for each domain.
For those running several sites from one panel.

How it works

Quietly, in the background, with no effort from you

Turn it on - and the plugin adds correct markup to community pages by itself. No code to write, no theme to touch.
Data stays current: author, dates and sections are taken from the discussions themselves.
No speed impact: the markup lives in the service part of the page and is cached.
The built-in checkup shows what is published and warns if your theme outputs its own markup (a duplicate hurts).

Honest about how it works. Markup is not a direct ranking boost - Google says so plainly. But it is what makes discussions eligible for rich results and lets search engines and AI cite your site with confidence. Without it, rich results and AI recommendations simply do not appear. The effect is greatest paired with the llms.txt map and a rich preview when links are shared.

Smart markup for search and AI (Schema.org) for Hub app

$33.99 per year $6.99 per month $59 forever

$15.99 per year $4.99 per month $33.99 forever