Manage AI Visibility

Manage AI Visibility Tracking lets you define the buyers, questions and AI platforms Wheremore should monitor. Each configuration represents a specific audience and business problem, rather than a generic list of keywords.

Overview

Setup has four parts:

Build an audience profile — describe the person you want to reach and the problem they are trying to solve.
Choose conversations — select suggested buyer questions or write your own.
Launch the configuration — choose the tracked brand or website, project, AI platforms and processing days.
Manage monitoring — review, edit, pause or remove the saved configuration.

Wheremore processes the selected questions in the background on the chosen days. Saving a configuration does not produce every result immediately.

Access and scope

AI Visibility configurations are workspace-aware.

The active workspace controls which projects and websites are available.
Each configuration belongs to one project.
The tracked website or brand provides the subject whose AI visibility is measured.
Only users with access to the relevant resources can view or change the configuration.
Changing workspace reloads the available configurations.

Before you begin

Decide:

which buyer or stakeholder you want to understand;
the industry, organisation size and geography that shape their needs;
the problem that causes them to search;
the alternatives or competitors they may consider;
the website or brand you want to track;
which AI platforms matter to your audience; and
how frequently monitoring needs to run.

Specific audience information produces more useful questions than broad descriptions such as “business owners” or “people who need software”.

Quick start

Open Manage AI Visibility Tracking.
Confirm the active workspace.
Answer the Audience Profile Builder’s questions.
Review the completed audience profile.
Select the suggested conversations you want to monitor.
Add any important question that is missing.
Optionally enrich the question set with real search data.
Select Confirm & Launch.
Name the configuration.
Confirm the tracked website or brand and project.
Select one or more AI platforms.
Choose the processing days.
Confirm the configuration.
Expand the saved row to review its setup.

Build the audience profile

The Audience Profile Builder asks a short sequence of questions. Answer in the language you would use internally; Wheremore turns the answers into a structured profile.

The profile can include:

Role — the job or stakeholder being represented.
Industry — the market in which the audience operates.
Company size — startup, small, mid-size, large or enterprise.
Geography — the region or market that affects the decision.
Core problem — the immediate problem the buyer needs to solve.
Alternatives — existing tools, suppliers or approaches they may compare.
Brand tracking — the company, product or website whose visibility is being measured.

Additional context can include budget, priorities, personal stakes, trigger moments and important product features.

Write useful answers

Prefer concrete answers:

UK marketing directors at mid-size B2B SaaS companies who need to connect fragmented search and revenue data.

Avoid answers that are too general:

Marketing people who need analytics.

The profile card updates while you answer. Review it before continuing, as this context shapes the suggested conversations.

Choose the conversations to monitor

Wheremore generates bespoke questions from the completed profile. They are not a shared question library.

Questions are grouped by buyer-journey phase:

Awareness — discovering and naming the problem.
Consideration — evaluating approaches and comparing options.
Decision — choosing a provider or solution.

Select the questions that reflect genuine buyer searches. A balanced configuration should cover more than one phase where appropriate.

Write your own question

Use Write your own question when an important scenario is missing.

Good questions:

sound like something a buyer would naturally ask;
contain enough context for a meaningful answer;
focus on one decision or problem;
do not force the tracked brand into every question; and
include branded or competitor comparisons only when those are genuinely useful scenarios.

Every saved generated or user-written question receives its own stable identifier within the configuration.

Enrich questions with real search data

The enrichment option can add search evidence to the suggested questions, including available search volume, People Also Ask and AI Overview signals.

You can provide competitor domains where requested. The interface shows the supported maximum and any applicable credit estimate before the enrichment runs.

Enrichment helps prioritise questions, but a low-volume question can still be strategically important in a specialist or high-value buying journey.

Launch the configuration

Select Confirm & Launch after choosing at least one question.

Configuration name

Use a name that distinguishes the audience and purpose, such as:

CMO — UK B2B SaaS
PR Manager — Media Monitoring
Ecommerce Director — Data Integration

Track results for

Confirm the company, product, brand or website Wheremore should look for in AI answers.

Use the real public identity that buyers and AI platforms are likely to recognise. Avoid internal project names.

Project

Select the project that owns the configuration. A project is required and must be available in the active workspace.

AI platforms

Select one or more available platforms. These can include standard and search-enabled variants of:

ChatGPT;
Claude;
Gemini; and
Perplexity; plus
Google AI Mode.

Search-enabled variants can return web-grounded answers and citations when the provider makes them available. Results and citations vary by provider.

Each selected question/platform combination creates monitoring work. Choose the platforms that matter rather than selecting everything by default.

Google AI Mode uses the project's supported target country, defaulting to the United Kingdom when one is unavailable. Its sources can support sections of the overall answer without endorsing a named provider, so a response may contain useful citations even when no structured provider rank is extracted.

Processing days

Choose any combination of Monday to Sunday.

The default is Monday, Wednesday and Friday. Quick-fill options make it easier to select:

All;
Weekdays; or
Mon/Wed/Fri.

The server processing schedule controls the run time. The selected days determine when the configuration is eligible to be queued; there is no separate user processing-time or timezone setting.

Understand the saved configuration table

The table shows:

Configuration Name;
Key Context;
Project;
Status; and
Actions.

Use the expand control to review:

Audience Context;
Business Problem;
Configuration Settings;
Competition;
Key Features; and
Conversations.

The Configuration Settings panel shows the tracked website, selected AI platforms and current processing schedule.

The schedule shown in the expanded table should match the days saved in the edit window.

Enable or disable monitoring

Use the status switch to control future processing.

When a configuration is disabled:

pending jobs are cancelled;
a provider request that is already running may finish;
completed historical results are preserved; and
no new work is scheduled until the configuration is enabled again.

Re-enabling the configuration makes it eligible on its next selected processing day. It does not necessarily run immediately.

Edit a configuration

Select the edit action to update:

configuration details;
audience profile;
questions;
key features;
tracked website or project;
AI platforms; and
processing days.

Save the changes after reviewing each relevant tab.

When the configuration changes, Wheremore cancels its pending jobs so they cannot run with outdated questions or context. Provider requests already running can finish and remain part of the historical record. The revised setup runs on its next selected day.

Edit or remove questions

Editing a question updates that question inside the configuration.
A new question is stored as a custom conversation.
Removing a question stops it from being scheduled again.
Completed historical responses are retained for reporting.
Pending work based on the previous configuration is cancelled.

Remove an AI platform

Removing a platform prevents new work being scheduled for it. Pending outdated work is cancelled, while already-running calls may finish.

Delete a configuration

Delete permanently removes the monitoring configuration and stops future processing.

Before deleting:

Confirm that pausing it would not be sufficient.
Review any historical reporting you still need.
Confirm that you selected the correct workspace and configuration.

Use Disable when you expect to resume monitoring later.

When results appear

AI Visibility monitoring is asynchronous:

The scheduler checks active configurations.
Eligible question/platform combinations enter the queue.
Provider workers process the requests and apply retries where appropriate.
Raw answers are saved.
Wheremore structures the responses for AI Visibility reporting.

The time required depends on queue volume, selected platforms and provider availability. A configuration can be correctly saved even though its latest results are still processing.

Recommended setup

Create separate configurations for meaningfully different buyer groups.
Use a clear core problem and geography.
Keep the question set focused on real buying situations.
Include awareness, consideration and decision questions where relevant.
Track a mixture of unbranded, category, comparison and selected branded questions.
Select only the platforms relevant to the audience.
Start with Mon/Wed/Fri unless daily monitoring has a clear purpose.
Review the expanded row after saving to confirm the schedule and platform selection.

Troubleshooting

No projects are available

Confirm the active workspace.
Confirm the project belongs to that workspace.
Confirm your account has access to the project.

Confirm & Launch is disabled

Complete the required audience profile fields.
Select at least one question.
Complete the required launch fields.
Select at least one AI platform.
Select at least one processing day.

The saved schedule looks wrong

Open Edit and save the intended days again.
Reload the configuration table.
Expand the row and check Configuration Settings.
Legacy schedules can appear as Daily or Mon/Wed/Fri; newly saved custom selections should list their actual days.

A disabled configuration still produced one result

A provider call may already have been running when the configuration was disabled. It is allowed to finish as historical data, but no new work should be scheduled.

Edited questions have not run

The revised configuration becomes eligible on its next selected processing day. Saving an edit does not force an immediate run.

Results are taking longer than expected

Confirm the configuration is active.
Confirm today is one of its selected processing days.
Check that questions and platforms remain selected.
Allow the background queue and response processor to complete.
Temporary provider limits are retried by the worker.

A response contains no providers, sentiment or tone

Occasionally a provider returns malformed or incomplete structured output. Wheremore can retain the recoverable answer while some extracted fields remain unavailable. Later monitoring runs can provide a complete result.

What to do next

After the first monitoring cycle:

Open the AI Visibility dashboard.
Check whether the tracked brand appears in relevant answers.
Compare standard and search-enabled platforms.
Review competitors, sentiment and citations.
Identify questions where the brand is absent or misunderstood.
Use the appropriate specialist content or search tool to improve the underlying evidence.
Keep the configuration stable long enough to measure whether visibility changes.