Several client brands in one account
Add each client site as its own brand. Open that brand to review its questions, answers and recommended work. For an agency handling different markets, this keeps a retailer's product comparisons separate from a service company's local buying questions. Build each review around the client's actual offer and the decisions its customers make.
Starter, Pro and Max allow unlimited brands, with 60, 150 and 400 active questions respectively, pooled across the account. Each brand can track 25 rivals. The account is single-user. Every plan checks every question daily on AI Overview, ChatGPT, Gemini and Perplexity, collecting answers from the apps people use, with API fallback when an app answer cannot be collected. Dated samples vary by run, location and account; they are not rankings. Before-and-after differences do not prove a fix caused a change.
Questions and rivals for each client
Choose questions about the client's category, common alternatives and specific uses. Review suggested rivals during setup and add the companies that belong in the comparison. Optional Search Console data supplies starting points for questions; you confirm which ones to track. You can also write questions yourself.
SearchSeal saves answers with the brand mentions, positions, other brands named and source links returned. Read the answer behind a result before explaining it to a client. A rival appearing ahead of the client gives you something specific to investigate: what the answer says, which question triggered it and which pages it references. Keep useful questions consistent across reviews.
Plan a weekly client review
Questions are pooled across the account. These examples are not per-brand quotas. Leave room for new questions and follow-ups.
| Plan | Shared questions | Example allocation |
|---|---|---|
| Starter | 60 questions, checked daily | 3 brands × 20 questions |
| Pro | 150 questions, checked daily | 5 brands × 30 questions |
| Max | 400 questions, checked daily | 8 brands × 50 questions |
- Confirm each brand's questions and pages each week.
- Review saved answers, rivals and sources during the week.
- Retrieve reports and fixes through the REST API or MCP tools. Use the client reporting guide to explain the evidence and next edit.
The authenticated owner reviews evidence and decides what to share. Separate client logins and delegated workspaces are unavailable.
Ranked fixes for each client site
Open Actions to review fixes with their reasons, target pages and supporting evidence. A fix can ask you to correct a fact, improve an existing page or write a missing explanation. Review the proposed instruction and draft against the client's actual products before publishing a change on its site.
Optional, read-only Google Search Console and Bing Webmaster connections add search demand. Where a tracked question has a recorded search-query link, impressions help rank its fixes. Search Console also supplies page problems drawn from search performance and index checks. Use the ranked list to choose work for each client, then mark completed fixes done and return to the saved before-and-after observations.
Use the REST API for reporting
Every plan includes API access. Create a read token in account settings and use brand-scoped REST requests to retrieve questions, rivals, answer excerpts, individual answer details, fixes and before-and-after results. Answer details include the question, date, model, brands named and returned source URLs. Fix details include the instruction, draft and evidence.
Export those JSON responses into your own client reporting process. Keep the brand, question and observation date alongside each finding so a reader can understand what was measured. Use the API documentation for authentication, filters and pagination. Decide which evidence belongs in the client's report and add your explanation of the work you recommend next.