Community help center

A help center made of real questions,
answered in public.

Your team answers once, where every customer can read it. Search, categories, tags, and accepted solutions come with it. Live in about five minutes, from $9 one time.

Free for 7 days. No credit card. Live in about five minutes.

demo.myforumcat.com
A customer portal home page: a list of questions with vote counts, solved badges, search, and category and tag filters.
5 minfrom sign-up to a live help center
QAPagestructured data on every answered question
$9one time for a working portal
7 daysfree, no card needed

How it fills up

Four steps, and the help center writes itself

You do not start with a blank page. You start with the question in front of you today.

  1. 1

    A customer searches first

    Search runs over the title and the details of every question, with stemming and ranking. Most people stop right here.

  2. 2

    They ask what is missing

    While they type a title, the form suggests questions that may already answer it. Fewer duplicates get posted.

  3. 3

    Your team answers in public

    A staff reply shows the role next to the name. The asker or your staff marks the reply that worked.

  4. 4

    The answer becomes a page

    The solved thread is a fast public page, with a sitemap entry and QAPage structured data.

Search

Search is the front door

Every question is searchable, by customers and by Google. Nothing is locked behind a sign-in.

demo.myforumcat.com/?q=webhook
Portal search results for a keyword, ranked, with solved badges.

When a search finds nothing, it is written to a log you can read. That log is your list of pages to write next.

Two ways to help

A help center article, and an answered question

Most teams end up with both. They are made in different ways and they age in different ways.

A help center articleAn answered question here
Who writes itSomeone on your team, before anyone asksA customer asks, your team answers
How it startsA planning list and a blank editorA real question from a real customer
How it stays currentSomeone edits it when the product changesA new question shows the old answer is stale
Found byYour site search and GooglePortal search, categories, tags, votes, and Google
Structured dataWhatever your tool addsQAPage structured data on every answered question
Read by AI enginesWhatever your tool exposesA raw markdown view of every thread
Private casesRarely part of the modelPrivate questions and private categories
EditorA full article editorNo article editor. Markdown questions and replies.

Both are useful. Keep the articles you have and put Forumcat beside them.

What this does not do

There is no article editor. Nobody writes a polished article in this tool. The content is questions, replies, and one accepted solution, written in markdown.

There is no importer. Old help docs and old forum threads stay where they are, and the new questions build the archive from today.

Some teams describe a forum as a knowledge base. This is close to that, with the two limits above. It sits beside the help center you already run, and you link both ways.

The solved thread

One answer, marked, and pinned under the question

The reply that worked moves up under the question and the thread turns to solved. A customer reading it does not have to scroll through a debate to find the answer.

Votes show which questions many customers share. Related questions sit in the sidebar, so one answer leads to the next.

Ask, answer and vote →

demo.myforumcat.com/q/105
A solved question: the question at the top, the accepted solution pinned under it in a green block, and related questions in the sidebar.

Found by people and by machines

Sitemaps and structured data, already done

Every portal gets a sitemap, a robots file, and 1200 by 630 preview cards. There is nothing to configure and no plugin to pick.

Every answered question ships QAPage structured data. Every public thread is also served as raw markdown, which is what AI engines and agents read best.

How SEO works here →

demo.myforumcat.com/sitemap.xml
The portal sitemap index, generated automatically.

Naming it

Help center with community, or help center with forum

Teams search for both phrases and mean the same thing. They have docs, and they need a public place where customers can ask the thing the docs do not cover.

That is this. Some teams call it a customer help center forum. Some call it FAQ forum software, because the FAQ page they hand-wrote never keeps up.

The name matters less than the shape. Real questions, public answers, one accepted solution, and a page for each one.

Pricing

Flat, and small enough to sign off alone

$9 one time for a portal on a Forumcat subdomain, or $99 a month on your own domain. The bill does not move with traffic.

Basic

$9 one-time

Create your portal
  • Portal on yourcompany.myforumcat.com
  • 2 team seats
  • 1,000 registered members
  • 10,000 questions
  • 1 GB (≈2,000 images) of media
  • Full SEO and GEO: structured data + sitemap
  • Analytics built in
most popular

Pro

$99 per month

Start with Pro

Everything in Basic, plus

  • Your own custom domain
  • Unlimited team seats
  • 10,000 registered members
  • Unlimited questions
  • 50 GB (≈100,000 images) of media
  • 1,000,000 page views / month

Compare every plan →

FAQ

Fair questions

How fast can we be live?

Answer

About five minutes. Sign in, name your portal, and it is online at yourcompany.myforumcat.com. Nothing to install.

Does this replace our help center?

Answer

No. Keep your articles where they are. This is the public place for the questions those articles do not cover yet.

Do we need to write anything before we launch?

Answer

No. Add a few categories, then answer the first real question. The archive grows from the questions you already get by email.

Can we import our old forum or help docs?

Answer

Not today. There is no importer. Most teams start fresh and let the new questions build the archive, which is live in minutes.

Do customers need an account to read?

Answer

No. Reading and searching are open to everyone. Signing in is only for asking, replying, and voting, and it is passwordless.

Who can see a private question?

Answer

Only the person who asked it and your team. Whole categories can be private too, so every question posted there starts private.

Will the answers show up in Google and AI engines?

Answer

Every answered question becomes a fast public page with QAPage structured data, a sitemap entry, and a raw markdown view. That is what search engines and AI engines read.

Start with the question you answered this morning

Answer it once, in public, and let the next customer read it instead of writing to you.

Create your portal

Free for 7 days. No credit card. Live in about five minutes.