Pluma
Docs index

Get started

What Pluma is Concepts First 5 minutes

Guides: the 5 steps of every site

Step 1 · Create the site Step 2 · Invite your agent Model your content Create and publish content Step 3 · Connect the MCP Images and files Step 4 · Invite your team Step 5 · Deploy on Netlify Deploy on Vercel Generic webhook deploy Composable pages Migrate from repo files Staging and previews Languages Migrate from Contentful · pending Billing · pending AI visibility Analytics AI answers Search Console and Bing Site preview

API

API · conventions Delivery API Preview API Management API Agents Webhooks

MCP

MCP MCP tools MCP OAuth

Reference

Rich text

Errors

Errors Error: check_unavailable Error: invalid_body Error: invalid_key Error: invalid_parameter Error: invite_expired Error: invite_used Error: key_cannot Error: missing_key Error: not_found Error: rate_limited Error: translation_unavailable Error: validation_failed Error: version_conflict Error: wrong_space

Frameworks

Astro Plain fetch
docs/guides/ai-answers.md View markdown →

AI answers

What do ChatGPT and Gemini say when a customer asks for what you sell? AI answers, in Visibility, asks them every week and tells you, for each:

  • in how many answers your business is mentioned, and in what position when the answer is a list;
  • in how many it cites your site as a source;
  • which competitors show up in the answers (only the ones the answers name: Pluma doesn't ask about competitors on purpose);
  • anything it says about you that contradicts your own content in Pluma (hours, prices, address, products).

Your agent reads the same with get_answers and changes the questions with update_questions (MCP tools); the API has them at GET /api/v1/spaces/:space_id/answers and PATCH /api/v1/spaces/:space_id/questions (Management API).

Nothing to set up

You don't configure anything. As soon as the site has its live address and some published content, Pluma prepares the first report by itself: it guesses where your customers are (from your domain, like .gt, or from where the site was created), picks the questions from real searches, asks ChatGPT and Gemini, and reads your site. It takes a few minutes; the site's Overview shows "preparing" meanwhile. After that it refreshes every Monday.

Overview is the first thing you see: in how many answers each assistant mentions you, who they recommend instead, what they get wrong about you, where they get their facts, your visitors from AI and whether AI can read your site.

There's nothing to adjust in the dashboard: no questions to write and no place to pick. Pluma picks them from what people really search and refreshes them on its own. An agent can still replace them with update_questions.

Your questions

Up to 30, the way a customer would ask, without your business's name. They start from what people actually look for, not from what your site says:

  1. Your own searches first. If the site has Search Console or Bing connected, Pluma starts from what people searched before they found you. When they connect for the first time, Pluma picks the questions again from them (unless an agent set its own with update_questions); the next Monday run asks the new ones.
  2. Real Google searches for your category. From your content Pluma takes only your category and place ("pastelería", "milhojas" + "zona 14", "guatemala") and gets the Google searches that contain them in your country, with how many times a month people search each one (DataForSEO). Most searched first.
  3. Google's autocomplete adds the local and product searches the first two miss ("milhojas zona 14 a domicilio").
  4. It leaves out searches that name a business (yours or others'), and turns the rest into questions a person would ask ChatGPT. Each question keeps the search it came from, its source (search_console or google), its Google volume (search_volume) and how often people ask it to AI assistants (ai_volume).

If none of these give enough, Pluma writes them from your content instead and marks them "suggested".

They're asked from your customers' place (country and city), because assistants answer differently in Guatemala City than in Madrid. Pluma guesses it from your domain (.gt), from where the site was created, or from your content.

How it's measured

  1. Every Monday, Pluma asks each question to four assistants through DataForSEO: ChatGPT and Gemini as they answer in their apps, and Claude and Perplexity through their APIs with web search on (marked "API": close to their apps, not identical). All from your country. It keeps each answer, its sources, the brands it names and the searches the assistant ran behind the scenes.
  2. Competitors are the businesses the answer names, minus yours. Cited means one of the answer's sources is your live site's domain.
  3. A smaller model reads each answer and says whether you're mentioned, where, the tone, and which statements contradict your published content.
  4. Each question shows how many times a month people ask AI assistants that search (AI search volume), so the list is ordered by what matters most.

Everything is stored in Pluma: the page, your agent (get_answers) and the API read the stored results, and the weekly run refreshes them. Without DataForSEO configured, Pluma asks ChatGPT through OpenAI's API instead.

Things to know:

  • Answers change from one day to the next. Read the trend over weeks, not one run.
  • One call per question per week. Each run shows what it cost.
  • What's sent: to DataForSEO, only the questions and your country; to OpenAI, the answers to read, your business's name and your published content. Nothing about your visitors. See the Pluma privacy policy.