Prompts are questions you choose to monitor. Their results do not show how often real people ask those questions in private AI conversations or provide search-volume estimates.
Start with useful questions
- Open the Project, then Dashboard → Prompts → Library.
- Review the Active and Suggested tabs before adding more. Look for repeated wording and gaps in the customer journey.
- Choose a few questions that represent each important product or customer need. Include an early research question and a more specific comparison or buying question where relevant.
- Write each Prompt as a customer would ask it, in the language and Market you intend to measure. Keep a stable core of Prompts so later Analyses are easier to compare.
Plan a small, balanced starting set
Suppose a supplier serves small teams that need regional delivery and an accounting integration. A starting set could cover different decisions without repeating the same question:
Adapt the wording to your customers and Market. Use Tags for a second grouping, such as a campaign or audience, if you need to review those Prompts together. Keep Topic and Search Intent distinct: the Topic describes the subject, while Search Intent describes the kind of decision. Do not add many near-identical phrasings just to fill the Plan allowance; each Active Prompt changes the set measured in future Analyses.
Review suggestions and remove overlap
- Open the Suggested tab. Read each question alongside the Prompts already in Active; suggested wording is a candidate, not a measured customer question.
- Accept a suggestion only when it represents a relevant customer need that the Active library does not already cover. Reject irrelevant or overlapping suggestions. Check the available Prompt capacity before accepting a group.
- Search the Active library for questions with the same underlying need, even when their wording differs. Keep the clearest customer-style version and archive an Active Prompt you no longer want measured. Use Delete only when you intend to remove the Prompt instead of retaining it for later review.
- Confirm the Active tab contains the intended questions. Compare later Analyses with care after changing this set.
Add Prompts
Select Add in the Prompt Library. The current add flow offers these methods:Import a prepared list
- Select Add → Bulk upload. Choose Paste for one question per line with shared Topic, Tags, and Language, or File for a CSV or Excel sheet with different values per row.
-
For a file, include a header row and a column containing Prompt text. A useful starting structure is:
- Upload the file and check Map columns. Confirm which column supplies Prompt text, Topic, Language, Tags, and Search Intent. A Tags cell can contain multiple tags separated by a semicolon. For Paste, enter a Topic and choose the shared defaults below the text box.
- Set defaults for missing file values. Values supplied by the file win for their rows. Check that the Prompt Language fits the Project’s Market; a display translation does not change the wording measured by an Analysis.
- Select Preview prompts. Review the proposed rows and the counts for new, duplicate, invalid, and over-limit Prompts. Preview does not save the batch.
- Import only when the preview matches your intended library. Return to Active and confirm the new Prompts, Topics, and Tags.
Organize and maintain the library
- Topic groups a Prompt by subject, product, service, or use case. It is required when you write a Prompt and should not be a Search Intent label.
- Search Intent classifies the question as Informational, Commercial, or Transactional. Use it to compare questions at different decision stages.
- Tags let you group Prompts for your own workflow. Add them in the import defaults or file, edit the Tags cell afterward, or use the available bulk action for selected Prompts.
- Source tells you how a Prompt entered the library. A generated question is a candidate for your review, not proof of real-world demand.
