Q&A: reviewing and approving your questions
From 2.0, the questions and answers AISA generates do not go live the moment they are created. Every pair carries a status, and only the ones you approve get published. The reason is simple: a model that lacks a fact is tempted to invent one, and an invented answer about your address or your opening hours does more harm than a missing answer.
The product rule, which holds across the whole plugin, is this: if AISA has the information it writes it, otherwise it writes nothing. An answer that should say where you are, on a site where your address is not configured, is born empty with a note saying what is missing.
The three states
Every question sits in one of three states. You see them as badges on the row, in the set editor.
Approved — badge online. The answer exists and you have approved it. It goes on the site, into the FAQPage schema and into llms.txt.
To approve — badge to approve. The answer exists but you have not confirmed it yet. It appears nowhere. This is the normal state of a freshly generated answer when automatic approval is off, or of an answer the fact check has left a warning on.
To complete — badge to complete. The answer is empty because a fact was missing. The question stays: it is still a question your customers ask, and it is worth answering. What is missing is the fact, not the question.
Only the first state produces anything visible. The other two stay in the dashboard.
What goes live and what does not
| Where | What appears |
|---|---|
| The Q&A block or shortcode in your pages | approved only, and only with an answer |
| The FAQPage schema in the structured data | approved only |
| llms.txt | approved only |
| The set editor in the dashboard | all of them, with their status |
There is no route by which a question still to be completed reaches a page. That is deliberate.
What happens to FAQs that were already live
On the first load after the update AISA goes through the sets you already have, once, and deletes nothing.
- Answers that contained a placeholder — the ones that read on your site as "we are located in [TO BE VERIFIED]" — move to to complete and leave the site immediately. That is the intended effect: that text was never meant to be public. The original text is not lost: it stays on the row, under the line explaining that it was removed because it contained a placeholder, and you can read it or recover it whenever you like.
- Every other answer becomes approved and stays visible exactly as before. If your set was clean, nothing changes for your visitors after the update.
If an FAQ page looks shorter to you after updating, open the set editor: the missing questions are there, with a note saying which fact they need.
Reviewing a set
Open the set from the Q&A menu. Above the list you get the filters with their counters:
- All — everything
- Approved — the ones that are live
- To approve — they have an answer and are waiting for you
- Suggested — they are waiting for a fact
Every row has an Approved checkbox. It is disabled while the answer is empty: a question without an answer cannot be approved, and there is no sense in wanting it to be.
Where a fact is missing, the row shows the Missing fact field — "opening hours", for instance — with a direct link to the field you need to fill in the AISA settings. Fill in the fact, come back and press Regenerate answer: AISA rewrites that single answer using the fact it now has. The button is only active once the fact is actually there; while it is missing, the advice is to enter it first.
The fact-check warning
While generating the answers, AISA also runs a check with no AI involved: it looks for opening hours, phone numbers and country names in the text and compares them against the business details you configured. Anything it cannot confirm is not blocked — it may well be right and simply not configured — but it leaves a warning on the row and keeps the question among the ones to approve.
The warning means "check this before publishing it", not "this is wrong". Questions carrying a warning are also excluded from automatic approval: if you switched that option on, they still wait for your eyes.
Approving in bulk
Reviewing thirty questions one at a time is tedious, so there are two shortcuts.
From the set editor. The Approve all complete button approves every question that has an answer. While a filter is active the button becomes Approve all shown and acts only on the rows in front of you, so you can approve one group at a time. When something is left out AISA says so and takes you to the first one excluded — empty answers and answers with a warning to check are left out. If every complete question in that group carries a warning, nothing is approved and AISA states it: that is not an error, it means they need looking at.
Until you save you have an Undo: it reverses the approvals you just made and saves nothing. The reminder under the button is explicit — Save the set to publish them — because an approval only becomes public when the set is saved.
From the list of sets. The Q&A sets list carries the bulk action Approve complete questions: select the sets, apply it, and the complete questions in each one are approved. It only changes the status, does not touch a single word of the text, and running it twice does no harm. The Status column on each row also holds a Review and approve link, which opens the editor already on the group you care about.
The dedicated page, and the three choices after creating it
From the set editor you can create the FAQ page with Create dedicated page. Until 2.0 the page was created and then sat there with nothing linking to it: a page that exists and nobody reaches.
Now, as soon as the page exists, AISA offers three routes:
- Add it to a menu you already have. You pick the menu; AISA never creates a new menu by itself.
- Append the Q&A to an existing page. The page content is not replaced: the Q&A goes at the end, and before writing AISA saves a revision and asks you to confirm.
- Nothing, for now. A legitimate choice. In that case the audit will flag that there is a Q&A page nothing links to, so you do not forget about it.
The page is created with a slug in the language of the set — frequently-asked-questions, domande-frequenti, preguntas-frecuentes and so on — and with the language assigned. With Polylang or WPML the pages of sibling sets are linked to each other as translations. The slugs of pages you already had are never renamed.
If you use Elementor or another page builder
With a page builder active the FAQ page is created without builder mode, so the content renders normally and the questions show up straight away. The panel still hands you the shortcode to copy, in the form , for the day you open that page with the builder.
There is one case where AISA stops and explains what to do instead of acting: when you ask it to append the Q&A to a page already built with Elementor. On those pages the content visitors see comes from the builder, not from the WordPress text field, so writing there would produce nothing visible. The message tells you as much and points you to the right route, which is to add a Shortcode widget where you want the questions, carrying the set's shortcode.
If your site still prints the old shortcode as plain text, the update fixes it by itself: where needed it is rewritten in the current form, and where the Q&A block was already present the duplicate is removed. A revision is saved before every change, and the log of what was touched is visible in the AISA dashboard.
Frequently asked questions
Can I approve everything and stop thinking about it? There is an option, in AISA Premium: on the One-Click SEO page, under the Q&A set checkbox, you will find Automatically approve complete and verified questions. It is off by default and, even when on, it never approves the questions still to be completed nor the ones carrying a fact-check warning. It applies to the Generate Q&A button of the Q&A panel as well.
I filled in the missing fact. Do I have to regenerate the whole set? No. Press Regenerate answer on the row and AISA rewrites that one answer. Regenerating the whole set would cost more and would also rewrite what is already fine.
Why does a question with no answer stay in the list? Because the question is useful. The fact that customers ask it is information, and deleting it would lose you the reminder. If a question does not interest you, delete it yourself from the row.
Do the questions waiting for approval weigh on the site? No. They are not printed, they do not enter the structured data and they do not reach llms.txt. They exist in the dashboard only.
How do I know how many are pending? The Q&A menu entry carries a badge with the number of questions to deal with, the Q&A card on the dashboard has a status line per set, and the sets list has a Status column. There are no global WordPress notices: the flags stay inside the AISA screens.