# igeo.ai Documentation # Welcome to igeo.ai > Understand how your brand shows up in AI-assisted discovery-and what to do next. Canonical URL: https://app.igeo.ai/docs/welcome ## Overview Your audience asks AI assistants for product recommendations, comparisons and practical answers. igeo.ai helps you understand how your brand appears in those conversations, research the sources behind them and turn what you learn into content, publishing and optimization work. Connect that work to observed citations, crawler activity, website visits and search performance. ## What is igeo.ai? igeo.ai is an AI visibility and optimization platform for marketing teams and agencies. Track prompts, mentions, sentiment, position and share of voice; inspect competitors, sources and cited pages; then use recommendations, page analysis, content workflows and agents to decide what to create or improve. Brand Hub and audiences ground your workspace in a consistent brand context. Content Studio, agents, calendar and the enabled publishing tools help you produce and review content. AI Search Console, AI Traffic, AI Crawlers and connected Performance data help you assess what happens after publication. Optional capabilities include Articles Marketplace, Content, Ads, project management and generated website editing, depending on the workspace. ## What you'll find in these docs - [Quickstart Guide](https://app.igeo.ai/docs/quickstart) - [Sidebar navigation](https://app.igeo.ai/docs/navigation) - [Features and workspace access](https://app.igeo.ai/docs/feature-availability) - [Brand profile](https://app.igeo.ai/docs/brand-profile) - [Brand voice and audiences](https://app.igeo.ai/docs/brand-voice-and-audiences) - [Setting up prompts](https://app.igeo.ai/docs/setting-up-prompts) - [Competitors](https://app.igeo.ai/docs/competitors) - [Understanding your performance](https://app.igeo.ai/docs/understanding-your-performance) - [Understanding chats](https://app.igeo.ai/docs/understanding-chats) - [Visibility](https://app.igeo.ai/docs/visibility) - [Share of Voice](https://app.igeo.ai/docs/share-of-voice) - [Sentiment](https://app.igeo.ai/docs/sentiment) - [Position](https://app.igeo.ai/docs/position) - [Sources](https://app.igeo.ai/docs/sources) - [Pages and citation research](https://app.igeo.ai/docs/pages) - [Recommendations](https://app.igeo.ai/docs/recommendations) - [Page Scan](https://app.igeo.ai/docs/page-scan) - [Content Studio](https://app.igeo.ai/docs/content-studio) - [Blog briefs, drafts and publishing](https://app.igeo.ai/docs/blog-workflows) - [Social content and variants](https://app.igeo.ai/docs/social-content) - [Content publishing workspace](https://app.igeo.ai/docs/content-workspace) - [Ads workspace](https://app.igeo.ai/docs/ads-workspace) - [AI content agents](https://app.igeo.ai/docs/ai-agents) - [Reddit GEO](https://app.igeo.ai/docs/reddit-geo) - [Publishing calendar](https://app.igeo.ai/docs/publishing-calendar) - [AI Search Console and content tracking](https://app.igeo.ai/docs/content-tracking) - [Articles Marketplace](https://app.igeo.ai/docs/articles-marketplace) - [Generated website editing](https://app.igeo.ai/docs/website-editor) - [AI Traffic](https://app.igeo.ai/docs/ai-traffic-analytics) - [AI Crawlers](https://app.igeo.ai/docs/ai-crawlers-analytics) - [Search and traffic performance](https://app.igeo.ai/docs/performance) - [Reports and exports](https://app.igeo.ai/docs/reports-and-exports) - [Connect integrations](https://app.igeo.ai/docs/integrations) - [MCP](https://app.igeo.ai/docs/mcp) - [Public API](https://app.igeo.ai/docs/public-api) - [Manage your project](https://app.igeo.ai/docs/manage-your-project) - [Team members and workspace roles](https://app.igeo.ai/docs/team-and-roles) - [Project details, assets and access](https://app.igeo.ai/docs/project-management) - [Billing, plans and usage](https://app.igeo.ai/docs/billing-and-plans) - [Email and Slack notifications](https://app.igeo.ai/docs/notifications) - [Video tutorials](https://app.igeo.ai/docs/video-library) - [Next steps](https://app.igeo.ai/docs/next-steps) ## What igeo.ai does Start by measuring how often AI answers mention your brand, where it appears, how it is described and how it compares with competitors on the same prompts. Research the evidence in Sources and Pages, use Recommendations and Page Scan to prioritize work, and create or improve content through Content Studio, agents and your connected publishing destinations. Track published URLs, compare search and traffic outcomes, and share results through reports, MCP or the Public API. These metrics build on Sources - the sites and pages models reference when they discuss your space. When visibility or position shifts, it is often tied to which sources show up and how your category is described. Explore sources to find practical levers for improvement. Read more about the main metrics: Visibility, Share of Voice, Position, and Sentiment. - Visibility - How often your brand is mentioned across AI responses to the prompts you track - like share of conversation in AI discovery. - Share of Voice - How your mention rate compares to the competitors you configure on the same set of prompts. - Position - How prominently you rank when you appear alongside competitors in an answer. - Sentiment - Whether the model's language frames your brand positively, neutrally, or negatively when it mentions you. ## How igeo.ai collects data We run the prompts you define across the AI platforms and models your plan includes, on a schedule that fits your workspace. Prompts are phrased like real questions buyers ask - conversational and specific to your industry - rather than isolated keywords. Because model answers are not fixed, we focus on patterns over time so you can trust directionally correct trends and comparisons. For what to expect on variability and freshness, compare metrics with the same time range and filters, and use the Core Metrics articles in this help center for how each score is defined. ## Why answers can differ from a single API call A one-off answer from an API does not always match what a user sees in a product experience - wording, ordering, browsing, and model routing can all differ. igeo.ai is built to reflect how your audience encounters AI-assisted answers in the flows we measure, while still emphasizing trends rather than any single snapshot. Details that matter for your contract or region are best confirmed with your team's admins. ## How igeo.ai helps Continue to Next steps for FAQs, support, and pricing, or return to the Dashboard anytime. - Track AI visibility - See when you are mentioned in relevant conversations across the models you monitor. - Monitor competitors - Compare share of voice, position, and sentiment on the same prompts. - Understand citations - Use Sources to see which domains and pages appear alongside answers in your space. - Spot gaps - Pair metrics to find where you are visible but not preferred, or cited without a strong brand presence. - Track trends over time - Watch how your metrics move as models and markets evolve. - Decide what to do next - Ground strategy in Recommendations and your dashboard, not guesswork. ## Video walkthroughs - [Introduction to igeo.ai](https://www.youtube.com/watch?v=3kqdTQEED3s) --- # Quickstart Guide > The fastest way to get your workspace tracking real buyer questions and see your first trends. Canonical URL: https://app.igeo.ai/docs/quickstart ## Overview This guide gets you oriented fast: define what you track, compare your brand to key players, read the dashboard, then connect citations to action. Setup is mostly a matter of minutes; meaningful trends appear after your prompts have run enough times — often over a few days depending on your plan and schedule. If you still need workspace setup, finish onboarding first. Refine Brand profile and workspace settings (Manage your project) when you want suggestions to match your positioning. ## Step 1: Setting up prompts Prompts are the questions you want visibility for when people ask AI about your category. We run them across the engines your workspace monitors so you can see mentions, positioning, and sentiment over time. Your task Add a solid starter set on Prompts: group prompts under topics in the sidebar so reporting stays structured, then add conversational questions (not single keywords). When igeo.ai suggests new topics or prompts, review and accept the ones that match how buyers really talk — wording does not need to be perfect up front. Quick tip Ask “What should we be found for?” Reframe keywords you already trust (for example from Search Console) into full questions buyers would paste into ChatGPT-style tools. "What's the best CRM for small marketing teams?" "Which project tools work best for agencies managing ten-plus clients?" "How do you compare analytics platforms for B2B SaaS?" More patterns and examples in Setting up prompts. ## Step 2: Identifying competitors While prompts run, igeo.ai can surface brands that appear alongside yours. Adding the competitors you care about makes share-of-voice and position comparisons meaningful everywhere in the app. Open Competitors. Switch to Suggested competitors when you want to approve auto-detected brands, or add players manually when you already know who you benchmark against. Important: Use short, recognizable brand names — the way customers say them — not full marketing legal names or raw URLs if that would confuse tracking. Match spelling consistently; if variants matter for your space, configure them alongside the primary name in the product. Details: Competitors (docs). ## Step 3: Understanding your dashboard The default Dashboard is your orientation screen once prompts have produced enough answers to chart. Spend a few minutes mapping the layout: Use the dashboard's time range controls and any engine / provider filters your header exposes to focus on a period or on the models that matter most — especially when comparing week over week. - AI engines — Cards per model/provider showing how often your tracked space gets responses there. - Competitors — Who appears next to you and rough visibility ordering for the current period. - Visibility trend — The main line chart for mention patterns over the selected dates. - Top sources — Domains AI answers lean on as citations for your prompts. - Recent agent posts — Latest agent-generated content tied to your workspace, when enabled. ## Step 4: Understanding your sources When models browse or cite the web, those URLs and domains show up under Sources. They are usually the strongest lever for improving what AI says next — often more direct than tweaking a single prompt sentence. Start from the domains list, then drill into URLs for any domain to see specific pages that surface often. Compare competitors' recurring domains against yours and note gaps. Give prompts a little time to accumulate before treating Sources as definitive — early days can swing as engines refresh and your prompt mix stabilizes. Deeper guide: Sources (docs). - Domains where rivals appear repeatedly → similar themes or partnerships worth exploring. - Industry publications you never appear on → outreach or editorial opportunities. - Your own URLs showing up → double down on those content formats or internal linking. ## What's next? - Go deeper on prompts: Setting up prompts. - Get oriented on how prompts run and why answers vary: Welcome to igeo.ai. - Turn signals into actions: Recommendations and your Dashboard filters. ## Video walkthroughs - [Get started with igeo.ai](https://www.youtube.com/watch?v=7mmvpPieLyo) --- # Sidebar navigation > Where each area lives in the sidebar, what it’s for, and what you’ll see depending on your workspace and role. Canonical URL: https://app.igeo.ai/docs/navigation ## Overview The left sidebar follows the same order as product navigation: Dashboard first, then grouped sections for monitoring, brand, analytics, and optimization, plus in-app documentation. Labels (Monitoring, Brand, Analytics, Optimization) organize related items — exact wording may follow your workspace language settings. For setup depth on prompts and topics, see Setting up prompts. ## Where everything lives Dashboard — High-level performance and recent activity. Use it for orientation and shared time-range filters across the workspace. ## Monitoring Prompts — Create and manage the questions you track, organized by topics and tags. Refine wording as you learn what matches real buyer questions. Mentions — How AI responses reference your brand and competitors across monitored prompts. Doc: Understanding chats. Sentiment — Tone of language when your brand is mentioned in scoped answers. Competitors — Configure and compare the market players you care about for share-of-voice and position views. Sources — Domains and URLs cited in model answers. Pages — How your site's pages relate to AI visibility and citations. This item appears only when your workspace has page data available; if you do not see it, your account may not have connected pages yet. ## Brand Brand Hub — Central place for brand guidelines and assets so your team stays aligned with how you want to show up. Docs: Brand profile · Manage your project (workspace and account basics). ## Analytics AI Traffic — On-site visits and attribution from AI-related referrers (provider cards, trend chart, top pages and sources for your traffic) — separate from prompt-based visibility on the Dashboard. AI Crawlers — Crawler-oriented analytics on its own screen (how bots map to providers). Doc: AI Crawlers. Docs: AI Traffic · AI Crawlers. ## Optimization Recommendations — Prioritized suggestions from your data. A small dot can appear next to this item when there are weekly insights you have not opened yet (based on your last visit). Agents — Create and manage igeo.ai agent–driven content tied to your strategy. ## Documentation Documentation — This in-app help center (including metrics guides and how-to articles). ## System Admin For system administrators, an expandable System Admin section lists shortcuts such as Insights preview, LLM usage, admin tools, account emails, subscriptions, and HTML preview. It is visible only to users with system admin access. ## Who sees what Viewer accounts are limited to items explicitly allowed for viewers (such as Dashboard, Prompts, Mentions, Sentiment, Competitors, Sources, AI Traffic, AI Crawlers, and Documentation). Sections like Brand Hub, Pages (when shown), Recommendations, and Agents are hidden. Section labels only appear when at least one item underneath is visible to you. Full workspace roles see the complete menu according to plan and data (for example, Pages only when page data exists). Billing and some account tools may live outside the core sidebar — use Account when you need subscription or team settings. Next: Quickstart Guide · Visibility. --- # Features and workspace access > Find the right workflow and understand why a feature or integration may be unavailable in your workspace. Canonical URL: https://app.igeo.ai/docs/feature-availability ## Choose the workflow for your goal - Monitor AI answers: Dashboard, Prompts, Mentions, Sentiment and Competitors show your brand's presence across the engines configured for the workspace. - Research evidence: Sources and Pages explain which domains and URLs appear in monitored answers. Page Scan analyzes a specific page for improvement opportunities. - Take action: Recommendations, Content Studio, Agents and Reddit GEO connect your findings to content work. Calendar organizes scheduled and published posts. - Measure outcomes: AI Search Console tracks individual content URLs; AI Traffic measures visits; AI Crawlers measures bot access; Performance uses connected search and analytics properties. - Coordinate work: Brand Hub, Team, Integrations, project management and Billing keep the workspace configured for the people doing the work. ## What controls availability The sidebar and actions depend on your workspace role, plan, account status and enabled capabilities. A page described here may be hidden or read-only for your membership. Workspace owners and admins can review access and integrations. Articles Marketplace, Content, Ads, project management and other optional modules can depend on workspace configuration. The generated website editor applies to workspaces with a generated site and an active editing session. Documentation does not enable those capabilities. Customer documentation covers customer-facing workflows. Internal administration and experimental screens are outside the supported customer workflow. ## If a page is empty or blocked 1. Check the selected workspace first; prompts, connections, content and settings belong to that workspace. 2. Check the date range, topics, prompts and engine filters. A narrow selection may have no completed responses. 3. Follow any integration setup message and finish selecting the correct property, page, board or site. 4. Ask a workspace owner or admin to review your role, enabled features or subscription when the page reports an access restriction. ## Related guides - [Sidebar navigation](https://app.igeo.ai/docs/navigation) - [Team members and workspace roles](https://app.igeo.ai/docs/team-and-roles) - [Connect integrations](https://app.igeo.ai/docs/integrations) - [Billing, plans and usage](https://app.igeo.ai/docs/billing-and-plans) --- # Brand profile > Define how igeo.ai understands your brand in Brand Hub so prompts, topics, and outputs stay aligned with how you show up. Canonical URL: https://app.igeo.ai/docs/brand-profile ## Overview Your brand profile is the structured story igeo.ai uses to stay aligned with how you position the business, who you serve, and what you offer. You edit it in Brand Hub on the Brandbook tab; optional Audiences work lives on a second tab in the same place. Keep it accurate when your positioning changes — prompt suggestions and downstream views stay more relevant when the profile matches reality. ## What's in Brandbook The Brandbook tab groups fields so you can refine identity, messaging, and guardrails without hunting through unrelated settings. Typical areas include: - Basics: core identity, regions, languages, sites you care about, and who you consider the audience. - Descriptions & positioning: short and long copy that explains what you do and how you differ. - Personality & tone: how the brand should sound when referenced or quoted in generated context. - Offerings: products, services, or pillars you want emphasized when relevant. - Knowledge sources: references the workspace can lean on so answers stay grounded. - Content guidelines: do's and don'ts for how your brand should appear in suggested or agent-driven output. ## During onboarding and after If your flow includes a brand step, treat it as the first serious review — then revisit Brand Hub whenever messaging, segments, or offerings shift. Saving meaningful updates helps topic and prompt suggestions stay in sync with your strategy. ## Why it matters A precise profile reduces generic suggestions: igeo.ai can steer prompts and themes toward the buyers, industries, and offers you actually care about. Pair updates with a pass over Prompts — accept or refine suggestions after you change the profile so tracking reflects the new story. Accurate brand profile → more relevant suggested topics and prompts → metrics that reflect the market you are really in. ## Related documentation Connect brand context to workspace setup and monitoring: Manage your project Account, team, billing, and switching workspaces. Setting up prompts Organize conversational questions with topics and tags. Quickstart Guide Fast path from setup to meaningful dashboard views. Sidebar navigation Where Brand Hub and the rest of the app live in the sidebar. ## Video walkthroughs - [Review your brand book](https://www.youtube.com/watch?v=CzWsB_D4GzY) --- # Brand voice and audiences > Give content workflows a consistent brand foundation and a clear audience in Brand Hub. Canonical URL: https://app.igeo.ai/docs/brand-voice-and-audiences ## The two parts of Brand Hub Open Brand Hub at /brand-book. The Brandbook tab holds your brand foundation; the Audiences tab holds the people you want to reach. These are workspace records that can be reused when configuring content generation. Brandbook includes brand identity and positioning, tone of voice, visual identity, products or services, and knowledge sources. Review generated suggestions against your actual offering before saving them. - [Open Brand Hub](https://app.igeo.ai/brand-book) - [Open Audiences](https://app.igeo.ai/brand-book?tab=audiences) ## Set a useful brand voice 1. Start with an accurate company description, website and the products or services you sell. 2. Describe how the brand should sound. Use concrete examples of approved language, terminology and claims rather than broad instructions such as 'be engaging'. 3. Review the visual and knowledge sections so the content team can work from the same brand context. 4. Save changes and choose the appropriate brand kit in a Content Studio workflow when that option is available. ## Create and maintain audiences Use the Audiences tab to review, generate, add and edit the audience records for the workspace. Describe the buyer's context and needs so content can answer a specific person's question. An audience can guide the language and emphasis of generated content; it is not a guarantee that an AI engine will show an answer to that audience. Prompt monitoring still measures responses to the questions and engines you track. - Keep distinct buyer groups in separate audience records when their needs differ. - Revisit audiences when you enter a new market or change the product positioning. - Choose the audience in a content workflow alongside its topic, prompts and instructions. ## Video walkthroughs - [Create and configure audiences](https://www.youtube.com/watch?v=WCD9BPDmufk) ## Related guides - [Brand profile](https://app.igeo.ai/docs/brand-profile) - [Content Studio](https://app.igeo.ai/docs/content-studio) - [Blog briefs, drafts and publishing](https://app.igeo.ai/docs/blog-workflows) - [Team members and workspace roles](https://app.igeo.ai/docs/team-and-roles) --- # Setting up prompts > Build conversational questions, organize them with topics and tags, and keep tracking aligned with how buyers really use AI. Canonical URL: https://app.igeo.ai/docs/setting-up-prompts ## Overview Prompts are the foundation of what igeo.ai measures. Every conversational question you add is run across the AI surfaces your workspace monitors, then rolled up into visibility, share of voice, sentiment, and position. This page explains how to think like a buyer, organize work with topics, and use the tools on Prompts at scale. New to the product? Start with the Quickstart Guide. ## Keywords versus conversational prompts Classic SEO often targets short keywords. AI assistants are tuned for full questions: intent, constraints, and context in one utterance. Tracking real prompts means writing the way people actually ask — not only the head terms you already bid on. - Keyword-style: "best CRM software" - Prompt-style: "What CRM would work best for a ten-person sales team that mostly works remotely?" ## Intent, context, and stability Models infer what you are trying to accomplish (intent) and the situation you describe (context). Different intents produce different answers; similar intents tend to stabilize over time even when wording changes. You usually do not need many near-duplicate questions — capture the intent and the constraints that matter for your category. ## Anatomy of a strong prompt Most effective prompts combine a clear ask with specifics that narrow the answer. Example: "What's the best project management tool for creative agencies with remote teams under twenty people?" Intent: recommend a project management tool. Context: creative agencies, remote teams, small team size. Pure how-to questions sometimes yield generic instructions with few brand names. If you need commercial visibility, phrase prompts so tool or vendor comparisons are natural — for example ask which products or stacks fit a scenario, not only how a task is done in the abstract. ## Prepare your topics Topics group related prompts so reporting stays structured and suggestions stay on-theme. Think in clusters (product lines, audiences, or use cases) rather than one giant list. On Prompts, use the topics panel to pick a theme, add topics, and when available review topic suggestions — generated ideas you can accept into your setup so downstream prompt generation stays aligned with those themes. A practical starting point is three to five broad areas where you care about AI visibility, then refine as you see which clusters produce the strongest signal. ## Creating and managing prompts Open Prompts. Use Manage Prompts in the toolbar for the main actions — Generate Prompts, Prompt Suggestions, Add Prompt(s), and for workspace admins Export as CSV. ## Generate Prompts Opens the generator dialog. Pick a topic and how many prompts to create. Configure Intent Type (Informational, Navigational, Commercial, or Transactional), then Prompt Type (Organic, Branded, or Competitor Comparison). Add region and language, optional additional instructions, and optional words to exclude. Use this when you want a structured batch aligned to a topic instead of typing each line by hand. ## Prompt Suggestions Opens a dialog where you review model-generated suggestions: accept those that match real buyer language and reject the rest. Accepted prompts join your tracked set according to your workspace rules. ## Add Prompt(s) Add one or more prompts in a single flow. Each entry needs a topic and region so runs are attributed correctly. If a prompt already exists for the same region, the product surfaces a conflict so you can adjust wording or geography instead of creating silent duplicates. ## Tags Tags layer flexible labels on top of topics — for example funnel stage, persona, or campaign. From the prompts table, open tagging on a row to assign tags or manage your tag list. Tags flow through to filtering in other parts of the product where supported. ## Export as CSV Workspace admins can export prompts to CSV for backup, QA, or offline planning. igeo.ai does not ship a bulk CSV import on the Prompts page; bring changes back by adding or generating prompts in the app. ## Prompt volume Prompt volume estimates how much discovery demand sits behind a prompt's themes. In the product, volume appears as a numeric score with a five-segment bar: more filled segments indicate higher estimated volume. The product describes volume as: "Estimated AI search volume based on related topic space," with supporting text such as "Estimated search volume by the AI models" — matching what appears in tooltips when you hover volume in the app. Use volume alongside judgment: prioritize prompts that combine healthy demand with strategic importance for your brand. ## Limits and regions The Prompts toolbar shows how many prompts you use versus your workspace prompt limit. When you reach the cap, creating or accepting additional prompts may require freeing space (for example by removing prompts you no longer need) or upgrading your plan if your organization supports it. Regions control where each prompt is executed. Your account may cap how many distinct regions you can use; if you exceed that allowance, reduce regions or adjust the prompt set before retrying. ## Related documentation Prompts connect directly to how you read the dashboard and competitive landscape: Quickstart Guide End-to-end workspace setup so your first prompts and dashboard views are meaningful. Visibility How often your brand appears in AI answers to the prompts you monitor. Share of Voice Compare your mentions to tracked competitors on the same prompts. Sidebar navigation Where Prompts, competitors, and sources live in the app. ## Video walkthroughs - [Set up AI prompts](https://www.youtube.com/watch?v=RN86g8Rgf8A) - [Choose the right prompts to monitor](https://www.youtube.com/watch?v=s2_cDfZBqIA) - [Review topics and competitors](https://www.youtube.com/watch?v=HUIh2p11IGs) --- # Competitors > Choose who you compare against so share of voice, position, and sentiment stay grounded in the market you actually compete in. Canonical URL: https://app.igeo.ai/docs/competitors ## Overview Tracked competitors anchor your benchmarks. Share of voice, position, and comparisons in sentiment all depend on who you include: the same prompts and time range, compared across you and the market players you define. This page walks through Competitors — the Overview and Suggested tabs, manual add, and how to open a competitor for citations and detail. If you are just getting started, follow Step 2: Identifying competitors in the Quickstart Guide first. ## Why competitors matter Competitors turn raw visibility into context. Seeing that you appear in 15% of answers means more when you also know a peer appears in 45% for the same prompts — it shows both upside and what is realistic in your category. - Benchmarks: Anchor share of voice and position against brands you actually compete with. - Ambition: Decide whether to match, beat, or lead specific peers on the same questions. - Gaps: Spot prompts or periods where others consistently rank ahead of you. - Metric quality: Share of voice divides mentions among tracked brands — an incomplete set can skew who looks strong or weak (see Share of Voice). ## Where to configure competitors In the sidebar under Monitoring, open Competitors (/competitors). For how the sidebar is organized, see Sidebar navigation. ## Overview tab The Overview tab is your home base: a share-of-voice snapshot, a trend chart for appearances over time, and a full table of market players (including your workspace brand where applicable) with performance fields such as visibility, rank, and sentiment — aligned with your dashboard time range and filters. ## Open a competitor for detail Select a competitor from the table to open a dedicated view at /competitors/<name> (or an id when needed). There you get citation-level breakdowns, charts, and back navigation to the main Competitors list. Use it to see which sources and responses sit behind the rollups you see on Overview. The topic-level analysis view at /competitors-analysis also provides ranking cards, a topic selector and a paginated prompt table for comparing the available competitor data. ## Suggested competitors tab Switch to Suggested competitors to review brands igeo.ai proposes for tracking. In English, the in-app tooltip describes suggestions as driven by your website's content — treat that as the product definition of how candidates are chosen, rather than a manual rule you configure. ## Each suggestion card - Shows the suggested name and, when available, a link from the candidate data. - Shows a count so you can see how strongly that name surfaced in the suggestion set. ## Actions Use Add competitor on this tab to create a competitor manually instead of starting from a suggestion (see below). - Add: Adds the brand as a tracked competitor. If the suggestion has no website on file, the app asks you to confirm a valid website URL before completing the add. - Merge: Use when the suggestion should map to your workspace brand (for example when a variant name still refers to you). The merge flow ties that candidate to your account — not to another competitor row. - Reject: Dismisses the suggestion so it no longer appears in the suggested list. ## Manual add Add competitor opens a form to create a competitor directly. You enter a name, a website URL (must be valid to save — this grounds logos and classification), and optionally a logo URL. That matches what the product collects today: there is no separate “display name vs tracked name” step in this dialog — keep the name short and recognizable (see naming below). ## Naming that keeps metrics honest Use the shortest, clearest label people use in conversation — “Acme,” not “Acme, Inc.” — so tables and comparisons stay readable. When several spellings appear in AI answers, prefer one primary competitor row that matches how you think about the brand; if detection drifts, adjust your set over time as you review mentions and citations. ## Ambiguous or generic names Some names double as common words. If counts look wrong, spot-check Mentions and citations on the competitor drill-down before adding duplicate or overly narrow entries. The product does not expose a regex or pattern editor in the standard competitor form — stick to clear names and validate what you see in the data. ## Related documentation Competitors connect prompts, dashboards, and competitive metrics: Quickstart Guide End-to-end workspace setup so your first prompts and competitor set are meaningful. Setting up prompts Build conversational questions and organize them with topics and tags. Share of Voice How your mentions compare to every tracked competitor in the same AI answers. Sidebar navigation Where Prompts, Competitors, and Sources live in the app. ## Video walkthroughs - [Review topics and competitors](https://www.youtube.com/watch?v=HUIh2p11IGs) --- # Understanding your performance > Use the dashboard, filters, Prompts, and Mentions to see rolled-up visibility, competitors, and sources. Canonical URL: https://app.igeo.ai/docs/understanding-your-performance ## Overview The Dashboard (home) is your primary hub for how you and competitors trend over time, how sources show up in answers, and — when enabled — quick signals by AI provider or recent agent activity. It complements Mentions, where you inspect raw responses in depth (Understanding chats). Metric definitions: Visibility, Share of Voice, Sentiment, and Position. ## What you see on the Dashboard The layout can include a visibility trend chart comparing how often brands appear across your filtered time range, a competitors table with visibility, share of voice, sentiment, and position-style columns, and a top sources card listing domains most frequently cited in responses. Depending on your workspace you may also see provider-level mention summaries and recent agent posts — these are not the same as raw model chats; use Mentions when you need answer-level detail. ## Filters in the toolbar On most monitoring pages, the sticky subheader hosts shared filters so every chart and table stays in sync. Typical controls include: AI Traffic AI Traffic measures visitors to your site from AI-related sources — different from Dashboard metrics built from monitored prompts. It uses its own filters (providers, countries, granularity) tuned for traffic charts. Crawler-focused analytics live on /analytics/crawlers; see AI Traffic (docs) for the tracker snippet, traffic view, Settings, Cloudflare, and roles. - Date range: focus on recent days or a custom span; reset returns to defaults. - Regions: narrow to where prompts were executed. - Topics and tags: slice reporting to the prompt groups you care about. - Prompt types and providers (models): compare ChatGPT, Perplexity, Gemini, Claude, and other engines you track. - Branded: limit to prompts that include your brand in the question versus those that do not — useful when you separate branded and non-branded demand. ## Prompts Prompts lists everything you monitor, grouped by topic, with usage against your plan limit. From here you open a prompt to see its response history and metrics for that question alone — similar mental model to the main dashboard but scoped to one line item. For prompt mechanics and limits, see Setting up prompts. ## Brand mentions versus domain citations A strong dashboard story often mixes two ideas: your brand named in an answer, and your website or content cited as a source. You can be cited without a brand mention, or mentioned without your domain appearing — both matter for strategy. Use Sources and Mentions together to close those gaps. Start from Understanding chats when you need to verify what a single model actually said before changing prompts or competitors. ## Related documentation Go deeper on metrics and evidence: Understanding chats Read individual AI responses before interpreting aggregate metrics. Visibility How often your brand appears in AI answers to monitored prompts. Share of Voice Compare your mentions to tracked competitors on the same prompts. Sources Domains and URLs cited when models answer your prompts. ## Video walkthroughs - [Track AI citations, mentions, and clicks](https://www.youtube.com/watch?v=S-PBHE7Rbfw) --- # Understanding chats > How to read individual AI responses-the raw material behind visibility, sources, and competitive views. Canonical URL: https://app.igeo.ai/docs/understanding-chats ## Overview Each chat here means one stored AI response to a prompt your workspace monitors — the atomic unit behind mentions, visibility, sources, and competitive views. Reading a single response carefully explains what the dashboards are aggregating over time. Use Mentions (and recent-answer cards on the dashboard when shown) to open prompts, scan the response list, then open a row for the full breakdown. ## Anatomy of a response The detail drawer pairs your user prompt with the model's answer. Above the body, a metadata strip summarizes that run: - Provider: which surface produced the answer (for example ChatGPT, Gemini, Claude, Perplexity) — shown with the model's icon. - Model: the specific model identifier for that run. - Sentiment: how the answer talks about your brand when scored for that response. - Visibility score: a radial chart summarizing visibility for that answer. - Sources preview: favicons for URLs associated with the run (more load in the body or via load-more when the full list is longer than the first page). ## Regions Prompts run in the regions you configure for your workspace; each stored response carries a region when present. Geography matters for comparability — compare runs that use the same prompt and region when you judge wording or sourcing differences. ## Main answer and brands The body renders the model's text with markdown-style structure (headings, bullets, paragraphs, inline links). When structured brand data exists for the run, you also see ranked companies with short reasons — useful for seeing how the model ordered players in that specific answer, which feeds ideas about position at the aggregate level. ## Sources and links in the text A response may include URLs inline in the narrative and a broader set of URLs attached to the run. Inline links reflect what readers see in the prose; the full source list can be longer or paginated — use Load more sources when available so you review everything the run captured, not only what appears in the excerpt. Model behavior varies by provider: some runs surface many sidebar sources but fewer explicit in-text citations. Track trends across weeks rather than fixating on a single volatile day. ## Related documentation Move from single responses to workspace-level metrics: Visibility How often your brand appears in AI answers to the prompts you monitor. Sources Domains and URLs tied to how models answer your prompts. Sidebar navigation Where Mentions, Prompts, and Sources live in the app. Mentions Open the workspace view where you browse responses by prompt. --- # Visibility > How often your brand appears in AI-generated answers to the prompts you monitor. Canonical URL: https://app.igeo.ai/docs/visibility ## Overview Visibility measures how often your brand is mentioned in AI-generated answers to the prompts you track. When a model responds in your category, we check whether your brand appears in that response - and how that rate changes over time and across engines. Scores reflect your monitored prompts and respect the date range and filters you apply in the app (for example time period and provider). Use visibility to answer: "Are we showing up in AI answers?" and "Is that improving or slipping versus earlier periods?" Pair it with competitors on the same prompts to see share of conversation in AI discovery. Higher visibility means models mention your brand more often when discussing your tracked topics - a direct signal of presence in AI-assisted discovery before you layer in share of voice or sentiment. ## How visibility is calculated The percentage summarizes how often your brand appears in the set of model answers igeo.ai counts for your workspace. Conceptually: Visibility (%) ≈ (Responses that mention your brand ÷ Responses in scope) × 100 "In scope" means the answers included for your configuration (tracked prompts, selected period, filters). Exact aggregation rules can differ by plan and product version - use trends for direction, not a single point in time as a guarantee. For variability and how to read charts responsibly, see Welcome to igeo.ai. ## Reading visibility in igeo.ai On the Dashboard and other views that surface a visibility score or chart, use the time range control to compare weeks or months, and apply any engine / provider filters your header or page exposes so you are comparing like with like. Wording in individual answers will vary; rely on smoothed trends and your chosen window rather than one response. ## Brand recognition Visibility reflects whether models “know” your brand for the questions buyers ask. Low visibility on core prompts is a signal to revisit prompts, content, and sources-not just paid placement. ## Competitive context On the same prompt set, a competitor can dominate mentions. Visibility shows whether you appear at all; Share of Voice and Position show how that presence splits and ranks. ## Strategic prioritization Use visibility to prioritize topics where you are absent or fading, then connect those patterns to Sources and Recommendations for concrete next steps. ## Related metrics Visibility pairs with these metrics on the same underlying answers: ## Share of Voice How your mention share compares to the competitors you track on the same prompts. ## Position How prominently you rank when you and competitors appear in the same answer. ## Sentiment How positively or negatively the model frames your brand when it mentions you. --- # Share of Voice > How your brand’s mentions compare to every tracked competitor in the same AI answers. Canonical URL: https://app.igeo.ai/docs/share-of-voice ## Overview Share of voice compares how often your brand is mentioned versus all mentions of brands you track - you and your configured competitors - across the same prompts and time window. It answers “Of the branded mentions in this slice, what portion is us?” rather than “In how many responses did we appear?” Use the same date range and filters as elsewhere so SoV stays comparable to visibility and position. Configure who counts as competition in Competitors; incomplete competitor sets can skew share. High visibility but low share of voice usually means others earn more mentions in the same conversations - you show up, but they own more of the named-brand airtime. Higher SoV means you capture a larger fraction of brand mentions among tracked brands in scope. It is not the same number as visibility % (responses) and can move differently when one answer mentions multiple competitors multiple times. ## How share of voice is calculated SoV summarizes your share of brand mentions among you and the competitors you track. Conceptually: SoV (%) ≈ (Mentions of your brand ÷ Mentions of all tracked brands) × 100 “Tracked brands” includes your workspace brand plus the competitors you added. Which responses and mentions enter the numerator and denominator follows your workspace rules and plan - use SoV for relative comparison over time, not as a literal audit count. For interpretation and variability, see Welcome to igeo.ai. ## How Share of Voice differs from Visibility Visibility is about responses: what share of answers mention you at least once. Share of voice is about mentions: how your brand's mention count compares to the total mention count split across tracked brands (multiple mentions in one answer count toward SoV). The two metrics can diverge when competitors rack up repeated name drops in the same chats where you appear once. - Visibility - If your brand appears in 6 out of 20 scored responses, your visibility for that slice is 30%. - Share of voice - If those answers contain 9 mentions of your brand and 27 mentions of tracked competitors combined, your SoV is 9 ÷ (9 + 27) × 100 = 25%. ## Split of influence SoV shows who occupies the branded portion of AI answers in your niche. It complements Visibility by revealing whether you are a footnote or a leading voice when models discuss your category. ## Competitive pressure A rival can drive down your SoV while your visibility stays flat if they earn more mentions per answer. Pair SoV with Position and Competitors to see who benefits from the same prompt mix. ## Where to invest next Use SoV trends to prioritize narratives, pages, and partnerships: connect shifts to Sources and Recommendations when you need concrete plays, not just score watching. ## Related metrics Interpret share of voice alongside: ## Visibility How often your brand appears in AI answers to your tracked prompts-not relative share. ## Position How prominently you rank when you and competitors appear in the same answer. ## Sentiment How positively or negatively the model frames your brand when it mentions you. --- # Sentiment > The tone of model language when your brand is mentioned-in answers scoped to your prompts, date range, and filters. Canonical URL: https://app.igeo.ai/docs/sentiment ## Overview Sentiment measures the overall tone of AI-generated answers when they mention your brand, on a scale from 0 to 100. It answers whether models frame you favorably, neutrally, critically, or with mixed signals-not only whether you appear. Scores reflect your monitored prompts and respect the date range and filters you apply (for example time period and provider). Use sentiment alongside visibility: a brand can be visible often yet described in lukewarm or negative terms when mentioned. A score near 50 means positive and negative classifications in scope balance out; higher values tilt toward relatively more positive language. Read trends and comparisons rather than a single snapshot - see Welcome to igeo.ai. ## How sentiment is measured igeo.ai classifies how your brand is portrayed when it appears in an answer (or aggregated slice of answers), using discrete labels: Positive - Language that favors trust, strength, or recommendation when your brand is discussed. Negative - Critical, cautionary, or unfavorable framing. Neutral - Factual or descriptive tone without a clear positive or negative lean. Mixed - Both supportive and critical signals in the same context; for scoring, this is split between positive and negative (see below). ## How sentiment is calculated The headline score summarizes classified mentions in your scope. Conceptually, each mixed label contributes half toward positive and half toward negative when computing the balance; neutral increases the denominator and tends to pull the score toward the middle. In closed form: Sentiment (0–100) ≈ 50 + ((adjusted_positive − adjusted_negative) ÷ total) × 50 Here adjusted_positive and adjusted_negative incorporate that split for mixed labels; total is the count of classified items in the aggregation. Exact rules can vary by view and product version - use direction and relative changes over time. For variability and interpretation, see Welcome to igeo.ai. ## Reading sentiment in igeo.ai Open Sentiment from the sidebar (see Sidebar navigation) for breakdowns tied to your workspace. Use the same time range and engine / provider filters as on the Dashboard so period comparisons stay fair. Individual answers will vary; rely on smoothed trends in your chosen window rather than one response. ## Brand reputation Tone shapes whether buyers trust you when models cite you. Persistent negative or mixed sentiment on core prompts is a signal to revisit messaging, sources, and factual gaps-not only mention volume. ## Competitive comparison On the same prompts, compare how you and tracked competitors are described. Pair with Share of Voice and Position to see whether you win mentions but lose the narrative. ## Strategic insights Track sentiment over time to spot drift after launches or news, prioritize topics where tone slips, and align improvements with Sources and Recommendations. ## Related metrics Sentiment reflects tone on the same answers where you measure visibility, share of voice, and position. Compare those metrics, then ground trend reads in methodology: ## Visibility How often your brand appears in AI answers to your tracked prompts-not relative share. ## Share of Voice How your mention share compares to the competitors you track on the same prompts. ## Position How average rank among brands works in the same prompts and slice as sentiment. --- # Position > How your brand ranks among names the model surfaces when you appear in AI-generated answers. Canonical URL: https://app.igeo.ai/docs/position ## Overview Position measures the average rank of your brand when it appears in answers-whether you are named first, second, or deeper in the list of brands the model surfaced (1 is best). It complements Visibility (whether you appear at all) with order and prominence when you do. Scores reflect your monitored prompts and respect the date range and filters you apply (for example time period and provider). Compare position over time and across views to see whether you are earning preferred placement in recommendations and comparisons. Being mentioned first or early among extracted brands usually indicates stronger topical authority and relevance for that answer-before you layer in share of voice or sentiment. ## How position is measured When models generate responses, they often mention multiple brands. igeo.ai scores each tracked response using structured extraction: an ordered list of companies with optional rank values. Your workspace matches your domains to entries in that list; we use the supplied rank when present, otherwise the ordinal position among companies we can resolve (first match = 1). Responses where you do not appear do not contribute a rank. The headline position value is an average of those ranks across answers where you appear. Lower averages are better (closer to 1). Exact aggregation can differ by view and product version-use trends for direction, not a single snapshot as a guarantee. ## How position is calculated Conceptually, position summarizes where you sit in the ordered brand list per answer, then averages across the responses that mention you: Position (avg rank) ≈ mean(rank in each response where your brand appears) Ranks are taken from structured companies data for each scored response; views that show averages (for example by prompt or competitor) apply the same idea over the slice they aggregate. For variability and how to read charts responsibly, see Welcome to igeo.ai. ## Reading position in igeo.ai Use the Dashboard and Competitors views that surface average rank or position alongside visibility-always align the time range and any engine / provider filters with other metrics so comparisons stay fair. Where prompts or recommendations show rank for a prompt, drill down to see whether you are consistently first or fluctuating across answers. Individual answers will vary; rely on smoothed trends in your chosen window rather than one response. ## Brand authority A better position (average closer to 1) suggests models treat your brand as a primary reference for the topic-listed before alternatives when they enumerate options. ## Competitive advantage You can have solid visibility yet appear after competitors in the same answers. Position shows whether you win order, not only presence; pair it with Share of Voice to see mention volume versus listing order. ## Topic relevance Position can vary by topic and prompt-revealing where you lead on authority versus where you need stronger content or prompts. Tie shifts to Setting up prompts and Sources when you turn insight into action. ## Related metrics Position sits alongside these metrics on the same underlying answers: ## Visibility How often your brand appears in AI answers to your tracked prompts-not relative share. ## Share of Voice How your mention share compares to the competitors you track on the same prompts. ## Sentiment How positively or negatively the model frames your brand when it mentions you. --- # Sources > See which domains and pages AI cites for your prompts so you can close citation gaps and shape what models treat as evidence. Canonical URL: https://app.igeo.ai/docs/sources ## Overview Sources shows which domains and URLs appear when AI models cite the web in answers to your monitored prompts. It complements brand metrics — visibility, share of voice, and sentiment — by revealing the evidence stack behind those answers: who earns citations, where you show up, and what to publish or pitch next. Use Sources alongside Pages when you tie citations back to owned URLs. New to the workflow? Read Step 4: Understanding your sources in the Quickstart Guide. ## Why sources matter Models lean on cited pages when they explain categories, compare options, or list “best” picks. Knowing which domains dominate citations in your slice tells you where narrative and SEO effort pay off — and where competitors earn airtime you do not. - Citation benchmarks: See which sites models treat as authoritative for your prompt mix. - Gaps: Spot domains rivals earn repeatedly versus your properties or industry coverage. - Action: Prioritize content formats, partnerships, and technical fixes that move the URLs you care about into the citation set — often a stronger lever than tweaking a single prompt line. ## Where to open Sources In the sidebar under Monitoring, open Sources (/sources). For the full sidebar map, see Sidebar navigation. ## Filters and time range Sources uses the same workspace filters and date / time-range controls as the rest of the dashboard (aligned with how you scope prompts and reports). Change the slice here and the domains, counts, and chart update to match. Filter and date controls align with other monitoring views — see Sidebar navigation for where those live. ## Top of the page: score card and trend The top row pairs a score card with a trend chart. The card highlights total citations and how they break down. On the all-domains view (/sources), the breakdown uses domain types from the product — Reference, Corporate, UGC, Editorial, Institutional, and Other — so you can see whether models lean on encyclopedic sites, brands, forums, publishers, or other buckets for your current scope. The trend chart summarizes citation activity over time for that same scope. When you drill into a single domain, both widgets reflect that narrower slice. ## Domain list The main table lists domains ranked for your filters, with pagination so you can move through large result sets. Select a domain to open its detail view. ## Open a domain Choosing a domain navigates to /sources/<domain> (the domain is URL-encoded in the path). That screen keeps the score card and trend focused on that host while the table shows the specific URLs cited under it — again with pagination and the search and sort controls shipped in the product. ## URL grouping in the UI You may see labels that group URLs (for example article versus listicle-style paths). Those groupings come from lightweight URL heuristics in the interface to help you scan long lists — they are a convenience for reading the table, not a guarantee of a fixed editorial taxonomy on the backend. ## Domain drill-down and navigation On a domain's page, review which exact URLs surface most often. Use Back (or equivalent navigation) to return to the full domain list at /sources. ## When counts still look noisy Give prompts time to accumulate before treating Sources as definitive — early days can swing as runs refresh and your prompt mix stabilizes. Pair this view with prompt quality and Competitors so citation patterns match the questions you really care about. ## Related documentation Sources ties prompts, metrics, and site work together: Quickstart Guide Includes Step 4: Understanding your sources — domains, URLs, and competitive gaps. Setting up prompts What you monitor determines which citations appear in Sources. Sidebar navigation Where Sources, Prompts, and Competitors live in the app. Welcome to igeo.ai How monitored prompts and patterns over time relate to citations and dashboard views. ## Video walkthroughs - [Track AI citations, mentions, and clicks](https://www.youtube.com/watch?v=S-PBHE7Rbfw) --- # Pages and citation research > Explore the individual URLs surfaced in AI answers and connect page-level evidence to content work. Canonical URL: https://app.igeo.ai/docs/pages ## Move from domains to individual pages Sources helps you understand domains used as evidence across monitored answers. Pages at /pages lets you inspect individual URLs and their citation activity. Both views reflect the selected workspace and the monitoring data available for it. Use page research to find content formats that models repeatedly surface, check whether your own pages appear, and identify pages worth improving. A citation is evidence in an answer; it does not by itself establish that a person visited the site. - [Open Pages](https://app.igeo.ai/pages) - [Open Sources](https://app.igeo.ai/sources) ## Research a page 1. Open Pages and use the search, filters and sort options to focus on relevant URLs. Available sorts include citations, trend, branded status and alphabetical order. 2. Select a page to open its detail drawer. Review its citation count and trend, the provider breakdown and the prompts that surfaced it. 3. Open the original URL to check the actual content and context. Compare recurring themes with your brand's own coverage. 4. When a source-page content action is available, use it to start content work from that evidence. Otherwise record the opportunity in your editorial workflow. ## Interpret page activity carefully Compare pages using the same period and prompt scope. A page can be heavily cited for one narrow topic and absent elsewhere. Check the underlying answers before treating a trend as a market-wide change. Use AI Search Console for the lifecycle of a URL you publish, AI Traffic for visits to your site, and AI Crawlers for crawler requests. These are related observations with different data sources. ## Related guides - [Sources](https://app.igeo.ai/docs/sources) - [Understanding chats](https://app.igeo.ai/docs/understanding-chats) - [AI Search Console and content tracking](https://app.igeo.ai/docs/content-tracking) - [Page Scan](https://app.igeo.ai/docs/page-scan) --- # Recommendations > Prioritized actions from your workspace data: the recommendations list and insight tracking in one place. Canonical URL: https://app.igeo.ai/docs/recommendations ## Overview Recommendations lives under Optimization in the sidebar. It turns your monitored prompts, mentions, and competitive context into a prioritized workspace for action — so you can go from seeing metrics elsewhere in the app to deciding what to do next. Open Recommendations in the product anytime. If you are still setting up tracking, start with Quickstart Guide and Setting up prompts first — recommendations become richer as your prompt mix and history grow. ## Why use Recommendations Dashboards and detail views explain what models say and how you compare. Recommendations focuses on what to do about it: ordered items you can work through with your team, tied to the same filters and time ranges you use elsewhere when filters apply. - Action: Move from insight to a concrete next step without exporting screenshots or maintaining a separate task list by hand. - Consistency: The same workspace configuration that powers visibility and share of voice also grounds what appears here — fewer mismatched stories between tabs. - Discovery: Surfaces ideas you might miss when jumping between Mentions, Sources, and the Dashboard alone. ## Two tabs inside Recommendations The header uses two tabs. Labels match the rest of the app — the first tab is your primary recommendations list; the second is for insight tracking over time. Recommendations — The default view lists actionable items for your workspace (your todo-style backlog). Work through items, apply filters when shown, and use this tab when you want the current prioritized set. Tracking — Switch here to follow insight-tracking oriented views and trends configured for your workspace (how items evolve and what you have already reviewed). Exact columns and charts follow the product version you use. ## Sidebar badge A small indicator can appear next to Recommendations in the sidebar when there are weekly insights you have not opened yet, based on your last visit. It is a gentle nudge, not a blocking gate — open the page when you are ready. ## Where to open it In the sidebar under Optimization, go to Recommendations. For how the menu is organized, see Sidebar navigation. ## Filters on the page When filters are available in the subheader (for example topics, prompt types, or specific prompts), they scope the same way as on other monitoring-style pages — keep slices aligned when you compare this view with Prompts, Mentions, or the Dashboard. ## Who sees Recommendations Viewer roles do not see Optimization sections such as Recommendations and Agents. Full workspace roles see them according to plan and workspace settings. See Sidebar navigation for the full “who sees what” breakdown. ## Related documentation Connect recommendations to how you read metrics and navigate the app: Quickstart Guide Get tracking in place so suggestions reflect real buyer questions. Understanding your performance How the Dashboard, filters, and rollups relate to what you do next. Sidebar navigation Where Recommendations sits next to other Optimization items. --- # Page Scan > Analyze a specific web page and turn its findings into concrete content and technical improvements. Canonical URL: https://app.igeo.ai/docs/page-scan ## Run a page analysis 1. Open Page Scan at /page-scan in the workspace you want to improve. 2. Enter the page URL in the scan launcher and start the analysis. Wait for the scan status to complete before reviewing results. 3. Review the recommendations and open an item to see its explanation, severity, category, evidence and proposed fix. 4. Use the competitor gaps section, when returned by the scan, to compare coverage and decide which missing information is relevant to your audience. - [Open Page Scan](https://app.igeo.ai/page-scan) ## Prioritize the findings Start with findings that affect whether the page is accessible and understandable, then address clarity, evidence and missing coverage. The scan's severity labels help triage work; review each proposed change against the purpose of the page. A recommendation is a proposed improvement, not a promise of indexing or citation. Keep important facts accurate and preserve useful content while making changes. ## Measure after making changes Publish approved changes in your website's own editor or publishing workflow. Re-run Page Scan to review the updated page, and track the URL in AI Search Console to follow subsequent crawl and citation signals. Use Sources, Pages and the original AI responses to see whether the page later appears as evidence. Keep the monitored prompts and comparison period consistent when evaluating a change. ## Related guides - [Recommendations](https://app.igeo.ai/docs/recommendations) - [Pages and citation research](https://app.igeo.ai/docs/pages) - [AI Search Console and content tracking](https://app.igeo.ai/docs/content-tracking) - [Blog briefs, drafts and publishing](https://app.igeo.ai/docs/blog-workflows) --- # Content Studio > Create and manage content workflows from a template, topic and monitored prompts through review, publishing and tracking. Canonical URL: https://app.igeo.ai/docs/content-studio ## A workspace for content work Content Studio at /content-studio brings content workflows into one list when available for your workspace and role. Each workflow connects a content template to workspace context such as topics, prompts, AI platforms, cited pages, brand kits, audiences and instructions. The list includes draft, in-review and published status filters. Open a workflow to continue work, inspect its metrics when available, or use available scheduling and tracking actions. Existing agent generations can also be brought into content workflows. - [Open Content Studio](https://app.igeo.ai/content-studio) ## Create a workflow 1. Select the new-content action to open the template picker. Search templates, browse onsite or offsite categories, and choose an available template. 2. Choose a topic first, then select the monitored prompts the content should address. The available prompts and cited pages depend on that topic. 3. Choose the relevant platforms and, where offered, cited pages, brand kit and audience. Add instructions for facts, constraints and the intended outcome. 4. Follow the workflow stages to generate and review the content. Save edits before moving on or publishing. ## Keep generation and publication separate Blog workflows support titles, a brief and a draft; social workflows support variants and a compose step. Review facts, links, images, tone and brand claims before using the publishing action. The publish dialog shows the destinations available for that workflow. Publishing requires the relevant connection and destination selection. Export remains useful when you want a separate editorial or publishing process. An unavailable template or destination should not be treated as a connected publishing channel. ## Close the loop with tracking After publication, use the workflow's tracking view to review the available visibility, mentions, citations and position data. Interpret results alongside the tracked prompts and publication timing. Content metrics can take time to accumulate. A generated draft or a successful publication does not guarantee that an AI engine will crawl, cite or recommend it. ## Related guides - [Blog briefs, drafts and publishing](https://app.igeo.ai/docs/blog-workflows) - [Social content and variants](https://app.igeo.ai/docs/social-content) - [Publishing calendar](https://app.igeo.ai/docs/publishing-calendar) - [AI Search Console and content tracking](https://app.igeo.ai/docs/content-tracking) - [Brand voice and audiences](https://app.igeo.ai/docs/brand-voice-and-audiences) --- # Blog briefs, drafts and publishing > Build an article from monitored questions, edit its content and metadata, then publish to a connected site or export. Canonical URL: https://app.igeo.ai/docs/blog-workflows ## Choose the evidence and article direction 1. Create an available blog workflow in Content Studio. Select its topic and one or more prompts, then choose the relevant AI platforms and cited pages. 2. Add a brand kit, audience and clear instructions when needed. Include approved facts and constraints so generated text has useful context. 3. Generate title options and review the proposed direction and outline. Select a title before generating the brief. - [Open Content Studio](https://app.igeo.ai/content-studio) ## Review the brief and edit the draft The brief is a planning document for the article. Review its scope and structure before generating a full draft. The workflow sidebar lets you return to the relevant stage as the work progresses. Use the draft editor to revise the article and its metadata. Check the title, URL slug and search description where shown, and inspect headings, links and images. Use draft and review status to communicate editorial readiness. Generated statements still need editorial review. Check source relevance, product details and any quantitative claim before publishing. Save changes using the workflow's save controls. ## Publish or export the article 1. Choose Publish or export after reviewing the saved draft. 2. For WordPress publishing, connect a site in Integrations and select the required site/category offered in the dialog. 3. Review the selected destination and timing. Use scheduling only when the destination and workflow offer it. 4. Use MDX export when you want to publish through another content system or complete an external review. An exported file is not a live publication. 5. After publication, open tracking and inspect the live URL before evaluating subsequent citations. ## Related guides - [Content Studio](https://app.igeo.ai/docs/content-studio) - [Connect integrations](https://app.igeo.ai/docs/integrations) - [AI Search Console and content tracking](https://app.igeo.ai/docs/content-tracking) - [Reports and exports](https://app.igeo.ai/docs/reports-and-exports) --- # Social content and variants > Create channel-specific social drafts, compare variants and publish or export through the destinations available to your workspace. Canonical URL: https://app.igeo.ai/docs/social-content ## Start with the right channel and context Content Studio has social workflows for LinkedIn, X, Facebook, Instagram, Pinterest and Reddit. The available templates determine the formats you can create. Choose a template that matches where the post will be used. Configure the topic, tracked prompts and any brand or audience context. Add instructions that explain the post's purpose and the evidence it should use. Channel-specific formats and image support vary. ## Compare variants and compose a post 1. Generate the available variants and read them side by side. Compare the central claim, opening and fit for the channel. 2. Choose a variant and continue to compose. Edit the body, images and any channel-specific fields offered by the workflow, such as hashtags or the first comment. 3. Preview the final post and save your edits. Check the destination's format and length requirements before publishing. ## Use the actual destination status The publish dialog resolves the destinations and connections available for the workflow. Connect the relevant social account in Integrations and select the correct page, profile, board or subreddit when required. A destination shown as unavailable cannot be used to publish. Use the export action offered by the workflow for manual publishing or an external approval process. Confirm that a scheduled or published status is shown before assuming a post is live. Reddit engagement has an additional research and review workflow in Reddit GEO. Review the community context and the specific approval checks there before posting comments. ## Related guides - [Content Studio](https://app.igeo.ai/docs/content-studio) - [AI content agents](https://app.igeo.ai/docs/ai-agents) - [Publishing calendar](https://app.igeo.ai/docs/publishing-calendar) - [Connect integrations](https://app.igeo.ai/docs/integrations) - [Reddit GEO](https://app.igeo.ai/docs/reddit-geo) --- # Content publishing workspace > Manage publishing profiles, posts, approvals, drafts, inbox activity and social analytics in an enabled Content workspace. Canonical URL: https://app.igeo.ai/docs/content-workspace ## Open the enabled Content workspace Content at /content is an optional workspace capability with its own publishing and engagement tools. It complements the staged article and social workflows in Content Studio. Access depends on your account's enabled features and workspace permissions. Its tabs include Posts, Social profiles, Inbox, Approvals, AI drafts, Analytics and Notifications. Select the correct workspace before connecting a profile or working on a post. - [Open Content](https://app.igeo.ai/content) ## Prepare, approve and publish 1. Use Social profiles to connect or manage the publishing identities available to the workspace. 2. Create a post in the composer or start from AI drafts. Choose the relevant target and review the generated text and media in the editor. 3. Use the available approval workflow when another team member needs to review the post. Inspect items pending your approval and those waiting on someone else. 4. Choose the destination and timing in the publishing or scheduling dialog, then check the saved post's status and details. ## Review engagement and analytics Inbox brings together the messages and mentions available from connected profiles. Review the original context before replying or taking an action, and check which channel is selected. Analytics includes account and post views for the selected time range. Metrics depend on provider support, connected profiles and available data. Use Notifications to review the available content-workspace activity. Publishing analytics and social engagement are different from citations in monitored AI answers. Use AI Search Console, Sources and AI Traffic to investigate AI discovery outcomes. ## Related guides - [Content Studio](https://app.igeo.ai/docs/content-studio) - [Social content and variants](https://app.igeo.ai/docs/social-content) - [Publishing calendar](https://app.igeo.ai/docs/publishing-calendar) - [AI Search Console and content tracking](https://app.igeo.ai/docs/content-tracking) - [Features and workspace access](https://app.igeo.ai/docs/feature-availability) --- # Ads workspace > Connect advertising accounts, inspect imported performance and create supported paused image ads in an enabled Ads workspace. Canonical URL: https://app.igeo.ai/docs/ads-workspace ## Connect an advertising account Ads at /ads is an optional workspace capability. The workspace includes Home, Recommendations, Campaigns, Creative library, Billing & caps and Ad accounts. Availability depends on the enabled account features and your permissions. The connection catalogue supports OpenAI, Meta, Google, LinkedIn, TikTok, Pinterest and X advertising accounts, subject to provider access. OpenAI requires a ChatGPT Ads Manager key. X also requires the brand's X publishing account to be connected in Content's Social profiles. - [Open Ads](https://app.igeo.ai/ads) ## Read imported performance Totals and local filters reflect the currently loaded page of ads. Keep currencies separate and check pagination and the reporting range before comparing totals. - Home summarizes the available spend, impressions, clicks and connected networks. - Campaigns provides paginated ads, search, platform and status filters, details, creative previews, CSV export and native ad-manager links. - Creative library shows copy and images returned with the loaded ads. It is not a separate uploaded asset library. - Billing & caps shows reported spend and budgets, grouped by platform and currency. Use the native ad manager for platform-level financial controls. - Recommendations surfaces connection suggestions and rule-based performance flags such as reported spend without reported clicks. ## Create an ad where supported The workspace does not provide automatic campaign activation, automatic pausing or enforcement of a shared workspace spend cap. Disconnecting an advertising connection does not stop campaigns already running on the platform. 1. Connect an eligible advertiser account and open the new-ad flow. 2. Select a supported creation destination: OpenAI, Meta, LinkedIn or Pinterest. Other connected networks use their native ad manager for creation. 3. Enter the required image-ad, traffic destination and campaign details. Review the creation summary before submitting. 4. Created ads are paused. Review and activate them in the native platform's ad manager when ready. ## Related guides - [Content publishing workspace](https://app.igeo.ai/docs/content-workspace) - [Search and traffic performance](https://app.igeo.ai/docs/performance) - [Reports and exports](https://app.igeo.ai/docs/reports-and-exports) - [Features and workspace access](https://app.igeo.ai/docs/feature-availability) --- # AI content agents > Generate, review and manage channel-specific content with workspace agents and connected publishing accounts. Canonical URL: https://app.igeo.ai/docs/ai-agents ## What agents do The Agents area at /igeo-agents provides content generation and post history for the workspace. Supported social destinations include Facebook, Instagram, LinkedIn, X, Pinterest and Reddit; blog workflows use the publishing integration available to the workspace. Agents use workspace context and the generation options available in the product. Use them to create a draft from a topic, prompt or recommendation, then review the output before publication. - [Open Agents](https://app.igeo.ai/igeo-agents) ## Work with a generated post 1. Choose the relevant agent or generation flow and supply the requested content context. 2. Wait for generation to finish, then open the resulting post. Review and edit its text and any image assets. 3. Connect the publishing account in Integrations and choose the required destination before using a publish or scheduling action. 4. Review post history and the available analytics, comments or reactions to see what happened after publication. ## Use Content Studio for a staged editorial workflow Content Studio adds a workflow around content planning, drafting, review, publishing and tracking. Use it when you want to keep the topic, prompts, draft and measured results together. The Team area can also display configured AI agent profiles alongside people. A profile describes an agent's role and brand voice; it does not by itself establish a connected publishing destination or grant access to an external account. ## Related guides - [Content Studio](https://app.igeo.ai/docs/content-studio) - [Social content and variants](https://app.igeo.ai/docs/social-content) - [Connect integrations](https://app.igeo.ai/docs/integrations) - [Team members and workspace roles](https://app.igeo.ai/docs/team-and-roles) --- # Reddit GEO > Research Reddit opportunities, prepare relevant drafts and review comments before publishing through a connected Reddit account. Canonical URL: https://app.igeo.ai/docs/reddit-geo ## Connect and research Reddit GEO has Overview and Drafts views at /reddit-geo. Complete the Reddit integration and any required subreddit selection first. Setup status must be ready before the connected workflow can proceed. Overview brings together subreddit intelligence, relevant source posts, opportunities and available account or posted-comment statistics. Use the original Reddit thread and community context to judge whether a contribution would be useful. - [Open Reddit GEO](https://app.igeo.ai/reddit-geo/overview) - [Connect Reddit](https://app.igeo.ai/integrations?highlight=reddit) ## Prepare and review comments 1. Open Drafts and inspect the available comment targets. Generate a draft for a relevant target or use batch generation when offered. 2. Read the original post and edit the suggested response. Keep the comment relevant, accurate and appropriate for the community. 3. Open the review before approval. Check its eligibility, blockers, warnings, subreddit policy and account limits. 4. Acknowledge the review and approve the post only when eligible. Check the resulting published URL and status. Pending, published and discarded drafts are available in separate filters. ## Understand posting controls Reddit GEO exposes safety settings such as daily caps, cooldowns and subreddit policies. The review can block a post or show when it becomes eligible. Changing a draft does not bypass those checks. Use the opportunity and citation information as research context. Publishing a comment does not guarantee a new AI citation, traffic or visibility improvement. Follow the available metrics over time and inspect actual answers. ## Related guides - [Sources](https://app.igeo.ai/docs/sources) - [Social content and variants](https://app.igeo.ai/docs/social-content) - [Connect integrations](https://app.igeo.ai/docs/integrations) - [AI Search Console and content tracking](https://app.igeo.ai/docs/content-tracking) --- # Publishing calendar > Review scheduled and published content, plan timing and open posts from the workspace calendar. Canonical URL: https://app.igeo.ai/docs/publishing-calendar ## Review the content schedule The Calendar at /calendar shows workspace content around its scheduled or published dates. It helps you see how activity is distributed and inspect the posts associated with a day. Select a day or event to inspect the available post details and provider. Use the schedule actions from Content Studio or agent post flows when you want to put content on the calendar. - [Open Calendar](https://app.igeo.ai/calendar) ## Schedule content deliberately 1. Review and save the content before opening the scheduling or publishing dialog. 2. Confirm the connected account and selected destination. Choose a future time when scheduling is available. 3. Read the date and time shown by the scheduling control and confirm the action. 4. Return to Calendar to verify the planned post. After the scheduled time, check the post's actual publication status and destination. ## Separate the schedule from the outcome A calendar event records planned or past content activity. Confirm publication in the post history or live destination if an integration expires or a publish attempt fails. Use AI Search Console and the workflow tracking view to assess subsequent content pickup. Calendar itself is not a measure of indexing, citations or on-site visits. ## Related guides - [Content Studio](https://app.igeo.ai/docs/content-studio) - [Social content and variants](https://app.igeo.ai/docs/social-content) - [AI content agents](https://app.igeo.ai/docs/ai-agents) - [AI Search Console and content tracking](https://app.igeo.ai/docs/content-tracking) --- # AI Search Console and content tracking > Follow published URLs from publication and crawler access to citations in monitored AI answers. Canonical URL: https://app.igeo.ai/docs/content-tracking ## Track a published URL 1. Open AI Search Console at /ai-search-console and select the correct workspace. 2. Choose the track-results action and enter a valid public HTTP or HTTPS URL for the content you want to follow. 3. Review the tracked-content list and open the URL's detail view to inspect the available signals and trend. 4. Use the status groups, content type and available filters to focus on published content that needs attention. - [Open AI Search Console](https://app.igeo.ai/ai-search-console) ## Read the lifecycle status Tracked items can be blog posts, website content or social posts. The status describes observed data for that item, not a guarantee about every search engine or AI product. - Published: the URL is recorded as published; later pickup may not yet be observed. - Crawled: crawler access has been observed for the tracked content. - Cited: the page has appeared as a citation in monitored AI answers. - No pickup: the content has not gained the expected subsequent pickup in the available observations. - Lost: previously observed citation activity has dropped out of the relevant tracking window. ## Evaluate results with the right evidence Open details to compare the available citation and visibility signals over time, and inspect the prompts or providers associated with pickup. Content Studio also has a per-workflow tracking view with available mentions, visibility, citations and position metrics. Crawler access, citations and visits answer different questions. A bot request does not prove a citation; a citation does not prove a click. Use AI Crawlers, Sources and AI Traffic together to understand the sequence. ## Related guides - [Content Studio](https://app.igeo.ai/docs/content-studio) - [Pages and citation research](https://app.igeo.ai/docs/pages) - [AI Crawlers](https://app.igeo.ai/docs/ai-crawlers-analytics) - [AI Traffic](https://app.igeo.ai/docs/ai-traffic-analytics) --- # Articles Marketplace > Find available publication sites, compare them with your cited sources and manage article publication with marketplace credits. Canonical URL: https://app.igeo.ai/docs/articles-marketplace ## Check marketplace access and credits Articles Marketplace is an optional capability. When enabled, open /articles-marketplace to see publication sites, the workspace's article-credit balance and publication history. Marketplace credits are separate from an AI visibility metric. Review the credit requirement shown for a site and the publication details before starting a paid publication action. - [Open Articles Marketplace](https://app.igeo.ai/articles-marketplace) ## Choose a relevant publication 1. Browse the available sites and use the filters for site categories, origins and source mentions. 2. Inspect the site's details, available traffic or authority information and credit requirement. Missing data is not proof that a site has no audience. 3. Use source matches to compare marketplace sites with sources appearing in your monitored AI answers. 4. Choose a publication because it is relevant to the audience and article, then review the proposed content and publishing action. ## Follow publication status Use the create-post flow to prepare the publication for the chosen site. The publication list and article detail page provide the resulting status and publication information. After a publication is live, inspect the original page and follow its URL in AI Search Console. A paid publication or a site's presence in Sources does not guarantee future AI citations, ranking or referral traffic. ## Video walkthroughs - [Publish content through the marketplace](https://www.youtube.com/watch?v=lSznsBJEK9A) ## Related guides - [Sources](https://app.igeo.ai/docs/sources) - [AI Search Console and content tracking](https://app.igeo.ai/docs/content-tracking) - [Billing, plans and usage](https://app.igeo.ai/docs/billing-and-plans) - [Video tutorials](https://app.igeo.ai/docs/video-library) --- # Generated website editing > Request changes to a website created through the no-website onboarding flow and review the completed rebuild. Canonical URL: https://app.igeo.ai/docs/website-editor ## Who can use the editor The generated website editor at /website-editor is for workspaces with a website created by the no-website onboarding flow and an available editing session. It requires a selected workspace and is not a general-purpose editor for any external website. If your company already publishes through WordPress or another content system, use that system or the connected publishing workflow to update the live site. - [Open generated website editor](https://app.igeo.ai/website-editor) ## Request and review a change 1. Open the editing session for the selected workspace and read the existing conversation. 2. Describe one concrete change, including the page or section and the exact copy or intended result. 3. Send the request and wait while the site change is processed. The editor prevents overlapping requests while a change is running. 4. Once processing finishes, review the updated site or preview. Send a follow-up change if necessary; if a request fails, review the failure state before retrying. ## Work in reviewable steps The editor applies requests through a rebuild process, so changes are not instantaneous visual edits. Make related requests small enough that you can assess the result clearly. Review business facts, links, layout and mobile presentation after a rebuild. Use Page Scan and content tracking to assess the page once it is ready for discovery. ## Related guides - [Quickstart Guide](https://app.igeo.ai/docs/quickstart) - [Brand profile](https://app.igeo.ai/docs/brand-profile) - [Page Scan](https://app.igeo.ai/docs/page-scan) - [AI Search Console and content tracking](https://app.igeo.ai/docs/content-tracking) --- # AI Traffic > On-site visits from AI-related sources: embed our lightweight tracker, see dashboards at /analytics-separate from prompt monitoring in Mentions. Canonical URL: https://app.igeo.ai/docs/ai-traffic-analytics ## Overview AI Traffic is your workspace view of on-site visits tied to AI-related discovery — not the same story as Dashboard or Prompts (those track model answers to monitored questions). Here, “top sources” means referral and path patterns in your traffic data — not citation domains from AI answers; for those, use Sources and Mentions. - /analytics — visits, trends, and breakdowns (pages, referral-style sources, geography, device, browser) for sites you connect. - /analytics/crawlers — crawler-focused analytics (AI Crawlers doc). - Prompt monitoring — see Understanding chats and Understanding your performance. ## Embedding the tracker Prompt monitoring shows what models say. AI Traffic shows who actually lands on your site from AI-led discovery — only after your pages send events to igeo.ai. Your production snippet — with real workspace id and API host — is always shown under AI Traffic → Settings. Example below: replace YOUR_ACCOUNT_ID; collect URL may match your deployment (e.g. https://api.igeo.ai/analytics/collect). - data-account-id — binds hits to your workspace. - data-endpoint — posts to /analytics/collect on the API. - Hosted script — loads https://public.igeo.ai/tracker/v1/tracker.min.js in the document head. ```html ``` ## What each event includes - Page context: URL, path, time; optional session and landing hints. - Attribution: referrer when available — links visits to AI surfaces. - Environment: user agent; browser, OS, device, language where derivable. - Human vs bot: classification and crawler name when relevant. - Location: coarse geography (e.g. country or region) from IP when present. ## Privacy Read the Settings tab on AI Traffic for EU storage, minimizing identifiable data, and wording to review before you deploy on customer-facing sites. ## Traffic view On the default view at /analytics you get: - Providers — LLM-related breakdown plus an aggregate TOTAL. - Volume & trends — visit counts with period-over-period context and a chart for your date range. - Tables — top sources, pages, locations, devices, browsers (AI-attributed traffic — not share of voice from prompts). ## Filters - /analytics — analytics toolbar: providers, countries, shared date picker. - /analytics/crawlers — adds crawler-focused filters when relevant. - Monitoring pages (Prompts, Mentions, etc.) — different controls: regions, topics, tags, branded toggles. ## Why on-site traffic matters at igeo.ai Much of igeo.ai explains what models say about your brand. AI Traffic answers whether real visitors arrived via AI-led discovery. - Close the loop — see if interest in assistants and AI search surfaces turns into actual site visits. - Measure pathways — referrers, landing paths, geography, devices, trends — how people move from AI contexts to your pages. - Prioritize work — pair “signal in chat” with traffic on owned properties for content, attribution, and ROI — not leaderboard metrics alone. ## Related documentation Keep monitoring metrics and site analytics in separate mental buckets — and bookmarks. AI Crawlers Crawler analytics on a separate screen at /analytics/crawlers. Sidebar navigation Where AI Traffic, AI Crawlers, and the rest of the app live in the sidebar. Understanding your performance The home dashboard, filters, and prompt-based monitoring — separate from on-site traffic. Sources (monitoring) Domains and URLs cited in model answers to your prompts — not the same as top sources in traffic tables. AI Traffic Open the product view this page describes. ## Video walkthroughs - [Track AI citations, mentions, and clicks](https://www.youtube.com/watch?v=S-PBHE7Rbfw) --- # AI Crawlers > Cloudflare-backed bot analytics at /analytics/crawlers-which LLM crawlers hit your site, top paths, and why it matters for GEO. Canonical URL: https://app.igeo.ai/docs/ai-crawlers-analytics ## Overview AI Crawlers (/analytics/crawlers) shows how automated bots tied to AI companies request your pages — distinct from human visitors in AI Traffic (site tracker on /analytics). Availability can depend on your subscription (for example starter plans may not include this screen). - Crawler view — which bots hit your site, how activity trends over time, and which URLs they fetch most often. - AI Traffic — real people arriving on your site (referrers, pages, geo, devices) after AI-led discovery. - Together — compare what models pull from your domain with what real users actually visit. ## Cloudflare and this screen Crawler charts and breakdowns are powered by data from Cloudflare for the zone you connect to igeo.ai. At the edge, Cloudflare sees requests from named bots (for example GPTBot, ClaudeBot, PerplexityBot) — igeo.ai maps those signals to LLM providers and surfaces volume over time, top paths, and top crawlers. ## Where to connect Open AI Traffic (/analytics) and use the Cloudflare integration tab to link your account and choose the site (zone) you want analyzed. Until Cloudflare is connected and data is flowing, crawler analytics may be empty or minimal — the product may note when collection starts after the next scan cycle. This is separate from the site tracker script on AI Traffic → Settings; that script targets human page views. Crawler analytics here come from edge visibility into bot traffic. ## What you're seeing LLM operators send crawlers to fetch and refresh content that can flow into answers and citations. In the product you typically get: Use the crawler filter in the toolbar to narrow to specific bots when you want a focused slice. - Provider-oriented cards — bot volume grouped toward familiar LLM brands (plus a total). - Trends over time — how crawler requests move across your selected date range. - Top paths — URLs on your site that receive the most crawler requests. - Top crawlers — which bot identities drive the most traffic. ## Why it matters If models use what they can retrieve from your site, pages crawlers hit most often are strong signals for where to invest — content quality, structure, freshness, and technical basics (not blocking crawlers you care about). - Prioritize URLs — top-path lists highlight where bots concentrate; align those pages with your GEO and editorial priorities. - Understand bot mix — see which assistants or ecosystems pull from your domain most aggressively. - Contrast with AI Traffic — crawler demand vs human visits tells you whether edge interest converts into real sessions. ## Filters - Shared with AI Traffic — date range and (where applicable) provider and country controls match what you use on /analytics. - Crawler filter — on this route, narrow to specific AI crawler identities when you need a targeted view. ## Related documentation Use bookmarks to separate monitoring (prompts and answers), human site traffic, and edge crawler analytics. AI Traffic Human visits from AI-related discovery: tracker snippet, dashboards at /analytics — not crawler requests at the edge. Sidebar navigation Where AI Traffic, AI Crawlers, and the rest of the app live in the sidebar. AI Crawlers Open the product view this page describes. --- # Search and traffic performance > Connect Google and Bing data to compare traffic lift, keywords and traffic sources alongside AI visibility. Canonical URL: https://app.igeo.ai/docs/performance ## Connect the correct search and analytics properties Performance at /performance uses connected Google Search Console, Google Analytics 4 and Bing Webmaster Tools data. Finish the account connection and select the appropriate site or property in Integrations first. Readiness is checked separately for Search Console, Analytics and Bing. A connected identity without the required selected property can still leave part of the dashboard unavailable. Follow the setup or pending message shown in the app. - [Open Performance](https://app.igeo.ai/performance) - [Connect analytics integrations](https://app.igeo.ai/integrations) ## Use the three Performance views - Traffic Lift compares the available search and traffic metrics across periods. Check which connected data source supplies each metric. - Keywords shows available search-query performance and movement. Use the displayed comparison controls to investigate gains, declines and important terms. - Traffic Sources breaks down the available acquisition data so you can examine how people arrive at the website. ## Compare with AI monitoring without mixing the metrics Use Performance to understand measured search and website activity, then compare it with AI answer visibility over a relevant period. Search clicks, impressions and visits are different measurements from mentions and citations. A change after publishing content can have several causes. Use consistent dates, inspect the underlying pages and prompts, and avoid attributing every traffic change to an AI citation. If a view cannot load, check the integration status and retry. Data availability and freshness depend on the connected source as well as the workspace. ## Related guides - [Connect integrations](https://app.igeo.ai/docs/integrations) - [AI Traffic](https://app.igeo.ai/docs/ai-traffic-analytics) - [Understanding your performance](https://app.igeo.ai/docs/understanding-your-performance) - [Reports and exports](https://app.igeo.ai/docs/reports-and-exports) --- # Reports and exports > Generate a monthly PDF summary, retrieve prior reports and choose an export method for content or application data. Canonical URL: https://app.igeo.ai/docs/reports-and-exports ## Export a monthly summary report 1. Select the workspace whose results you want to share. 2. Use Export report in the application header when available to open Export Summary Report. 3. Choose the month and year. The selector offers supported historical periods and excludes future months. 4. Start the User Summary PDF export and wait for completion. Open or download the generated report using the result action. 5. Review the report before sharing it, especially its workspace and reporting period. ## Retrieve previous reports The export dialog loads report history for the selected workspace. Use a saved report's download action to retrieve the corresponding PDF, rather than generating the same period again solely to find a previous file. The summary export uses its selected month and year. Do not assume that all filters on the page behind the dialog apply to the PDF. ## Choose the right export for the task API and MCP access follow workspace membership, key scopes and supported operations. The API documentation lists private capabilities that are not exposed through the public interface. - Editorial handoff: use the blog workflow's MDX export or the social workflow's available text/asset export. - Application integration: use the Public API for supported workspace data in dashboards, scheduled jobs and data pipelines. - Assistant-led analysis: connect an MCP client and request the supported workspace information conversationally. ## Related guides - [Understanding your performance](https://app.igeo.ai/docs/understanding-your-performance) - [Blog briefs, drafts and publishing](https://app.igeo.ai/docs/blog-workflows) - [Public API](https://app.igeo.ai/docs/public-api) - [MCP](https://app.igeo.ai/docs/mcp) --- # Connect integrations > Connect analytics, crawler data, communication tools, social accounts, publishing destinations and MCP clients to a workspace. Canonical URL: https://app.igeo.ai/docs/integrations ## Find the integration for your workflow Integrations at /integrations is the central catalogue for workspace connections. Search by tool name or use the Analytics, Communication, Social Media, Publishing and MCP categories. Choose the correct workspace before connecting an external account. Integration setup and management depend on your workspace access, the provider's permissions and the feature's availability. - [Open Integrations](https://app.igeo.ai/integrations) ## Connect analytics and crawler sources Check the status after connecting. Some flows require property selection or processing before a page is ready. Use the integration's manage action to inspect or change the selection. - Google: authorize the account and select the appropriate Search Console site and/or Analytics 4 property for Performance. - Bing: connect Bing Webmaster Tools and select the relevant site for the Bing data shown in Performance. - Cloudflare: follow the connection card's configuration to supply crawler analytics for your website. ## Connect publishing and social accounts 1. Find Facebook, Instagram, LinkedIn, X, Pinterest, Reddit or Blog in the catalogue and open its connection flow. 2. Complete the provider authorization and return to the application. Select the page, profile, board, subreddit or site when the flow requires it. 3. Check the connected status, then confirm the intended destination again in the content publishing dialog. 4. If publishing fails or a connection expires, revisit the integration and reconnect before retrying the post. ## Connect communication and AI tools Slack has a connection card for workspace communication. Email digest and competitor-alert settings are managed in Preferences. The MCP category includes setup cards for Cursor, Claude, Google Sheets, Lovable, ChatGPT and n8n. These cards lead to MCP and API key management; a card's active-key status does not independently verify that a particular external client has completed its configuration. Use the MCP guide for the server URL and credentials. Use the Public API guide for deterministic REST integrations, scopes and the supported route catalogue. ## Related guides - [Search and traffic performance](https://app.igeo.ai/docs/performance) - [AI Crawlers](https://app.igeo.ai/docs/ai-crawlers-analytics) - [MCP](https://app.igeo.ai/docs/mcp) - [Public API](https://app.igeo.ai/docs/public-api) - [Email and Slack notifications](https://app.igeo.ai/docs/notifications) --- # MCP > Connect igeo.ai to AI assistants via Model Context Protocol-query prompts, mentions, and workspace data without leaving your editor. Canonical URL: https://app.igeo.ai/docs/mcp ## Overview Model Context Protocol (MCP) lets compatible AI assistants and agents talk to igeo.ai using a standard interface — so you can ask questions about your prompts, mentions, sentiment, competitors, and sources without copying exports or switching tabs all day. Think of MCP as a bridge: your AI tool stays in the editor or chat, while igeo.ai supplies the live workspace context behind the scenes. ## What is MCP? MCP is an open protocol for connecting AI applications (Claude Desktop, Cursor, Windsurf, and others) to tools and data sources. Instead of each vendor inventing a custom plugin format, MCP defines how clients discover tools, call them, and read structured resources — so integrations stay consistent and easier to maintain. igeo.ai exposes an MCP endpoint over HTTP (JSON-RPC). Connect with a workspace-scoped API key or a supported OAuth flow. Available tools include workspace analysis and supported content or configuration actions; the server enforces your workspace access and granted scopes. ## Why MCP matters for AI visibility GEO and AI visibility work is iterative: you tune prompts, watch competitors, and react to how models answer. MCP keeps that loop inside the workflow you already use — your coding agent or assistant can pull the latest igeo.ai state on demand instead of you manually reconciling screenshots or CSVs. - Faster decisions — Compare “this week vs last week” or “this topic vs that topic” with natural language instead of rebuilding the same filter sets by hand. - Shared context — The same workspace rules (membership, roles and granted scopes) apply through MCP, so answers stay aligned with what the dashboard would show for that workspace. - Automation-ready — Agents can chain steps (fetch prompts → summarize weak spots → draft follow-up actions) using structured tool results. ## How MCP makes igeo.ai easier to use Without MCP, jumping between igeo.ai and an AI assistant means re-explaining filters, pasting tables, and risking stale numbers. With MCP connected, you keep one thread of conversation and let the client fetch fresh workspace data when it needs it. ## Examples of what you might ask “Run prompt_work_priorities and tell me which prompt to maintain and which to improve this week.” “Which tracked prompts had the lowest visibility in the last seven days?” “Summarize sentiment for our brand vs the top two competitors this month.” “What allowlisted read routes exist for this workspace?” (discovery via MCP tools/resources) Exact tool names and capabilities evolve with the product; your client will list what the connected server exposes after setup. ## Copy-paste prompts (weekly planning) Paste one of these into Claude, Cursor, or ChatGPT after connecting igeo.ai MCP. Or fetch the full JSON playbook via MCP resources/read on igeo://mcp/playbooks/prompt-prioritization. ## Weekly planning (recommended) You are connected to igeo.ai via MCP. 1) Call the tool prompt_work_priorities with recentDays=30 (visibility uses the last 7 days by default). 2) Summarize: total prompts, how many had post activity in 30 days, visibilityRangeDays, and thresholds (maintenance ≥50, improvement ≤49 by default). 3) Present MAINTENANCE (maintenancePick) and IMPROVEMENT (improvementPick) with rationale and one concrete next action each. 4) If a pick is null, use the best alternate from alternates. Use only MCP tool results — do not guess. ## Audit recent work Using igeo.ai MCP: 1) Call prompt_work_priorities with recentDays=14. 2) List recentlyWorked sorted by lastPostAt (newest first) with topic, post count, and avgVisibility. 3) Flag high-visibility prompts with only one post in the window. ## Deep dive on improvement pick Using igeo.ai MCP: 1) Call prompt_work_priorities with recentDays=30. 2) Use improvementPick.promptId with prompt_responses (query.range=30). 3) Explain why visibility is low and propose 3 content actions. ## How to connect MCP and API keys are available to active workspace members. Select the correct workspace before creating a key. If the setup page is unavailable, check your membership and account status with a workspace admin. 1. Sign in to igeo.ai, select the workspace and open MCP & API keys. 2. Create a key — The app generates a server URL and client configuration (JSON) you can paste into your MCP client. Some clients accept a single URL with token query parameters; others want headers (Authorization, X-Workspace-Id) — use the snippet that matches your tool. 3. Point the client at the igeo.ai MCP server — Requests go to your environment's API base with the /mcp path (for example the same host your app already uses for VITE_API_URL, plus /mcp). 4. Start a session — Initialize the MCP connection in the client, run tools/list (or the equivalent in the UI), then ask questions that trigger tool calls. Use only the tools and operations permitted for your credentials. The api_get tool is read-only; supported write tools also require the appropriate role and scopes. ## Connect with supported OAuth clients When a compatible client starts an OAuth connection, follow its sign-in flow, select the intended workspace and review the permissions requested. Approve only the workspace and scopes required for that integration, then return to the client and verify the available tools. If a Claude connection link is invalid or expired, restart the connection from Claude. API keys are shown in full only when created. Store the secret securely, use the configuration supplied by the app and revoke a key when it is no longer needed. Client cards with an active-key status do not independently verify that every external client is connected. For workspace switching, billing, and team roles, see Manage your project. ## Data use and license The same data-use license that applies to the Public API applies to MCP. You may use data lawfully retrieved through MCP for any lawful purpose of your choosing. See Public API — Data use and license. ## Related Public API Build direct REST integrations with the same workspace API keys. Manage your project Workspace settings, team, billing, and where account-level tools live. Quickstart Guide Get prompts and workspaces set up so MCP-backed questions return meaningful data. Sidebar navigation Find Account, analytics, and monitoring areas in the app. ## Video walkthroughs - [Connect igeo.ai MCP to Claude](https://www.youtube.com/watch?v=YcLvqjPPEMc) --- # Public API > Integrate igeo.ai directly into applications, scheduled jobs, dashboards, and data pipelines with the public REST API. Canonical URL: https://app.igeo.ai/docs/public-api ## Overview The Public REST API lets your software call igeo.ai endpoints directly. Use MCP when an AI assistant should discover and operate igeo.ai tools conversationally. Both interfaces use the same igeo.ai data and business rules, but REST is the better fit for deterministic application integrations. ## Choose REST for application integrations Use the Public API for scheduled jobs, dashboards, data pipelines, and product features where your code controls the exact request. For agent-led workflows and natural-language tasks, use MCP. ## Data use and license Subject to your valid and authorized access to the relevant workspace, IGEO AI LTD (“igeo.ai”) grants you a non-exclusive, worldwide, royalty-free, fully paid license to use, reproduce, store, process, modify, combine, analyze, display, export, distribute, and otherwise exploit the data, metrics, insights, and other outputs returned to you through the Public REST API and MCP (together, “API Data”) for any lawful purpose of your choosing, including internal reporting, customer-facing products, automations, and other downstream systems. This license is irrevocable as to API Data you have already lawfully retrieved. You retain all right, title, and interest in content you submit to igeo.ai (“Customer Content”). igeo.ai does not claim ownership of Customer Content, or of API Data, merely because such data is delivered through the Public REST API or MCP. You are solely responsible for ensuring that your use of API Data complies with applicable law (including privacy, confidentiality, and intellectual-property laws) and with any third-party terms that apply to content included in API Data. This data-use license is in addition to, and does not replace, our Terms and Conditions, Privacy Policy, and Fair Use Policy. If there is a conflict between this section and those policies solely regarding your right to use API Data you have lawfully retrieved, this section controls. ## Enable and authenticate Public API access is included for every workspace. You must be an active workspace member to manage API keys. Public API requests use the same API keys as MCP. Treat every key as a secret and never expose it in browser code or a public repository. Create or manage a key on the MCP & API keys page. Copy a new key when it is shown; the secret cannot be retrieved later. ## Required headers Authorization: Bearer igeo_live_... X-Workspace-Id: your workspace ID ## Permissions and scopes Restrict each key to the smallest set of actions its integration needs. The request method determines the required scope. read — GET requests. write — POST, PUT, and PATCH requests. delete — DELETE requests. mcp:full — all supported operations; use only when necessary. Keys inherit the creator's current workspace access. Write and delete operations require an owner, admin, or editor role. ## Rate limits and errors Limits are applied per workspace. Avoid bursts, cache stable responses, and use exponential backoff with jitter when retrying. Inspect X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset. Monthly variants use the -Month suffix. ## Common responses 401 — the API key is missing, invalid, expired, or revoked. 403 — the workspace, role, scope, path, or HTTP method is not permitted. 429 — a rate limit was reached. Wait for the Retry-After interval before retrying. ## Route catalog Search the customer-facing REST surface by path, description, group, or HTTP method. A path can support more than one operation. ## Not exposed by the Public API The catalog above is the source of truth for supported public paths and methods. Billing, Content Studio, Articles Marketplace, AI Assistant, account and workspace lifecycle, member and role management, onboarding, and system administration remain private. Outbound webhooks or event subscriptions. Internal, administrative, and support-only endpoints. MCP protocol endpoints; connect through an MCP client instead. API-key lifecycle endpoints through Public API authentication. Cross-workspace agency operations without explicit membership. OAuth client registration and authorization flows. ## Related documentation MCP Connect AI assistants to igeo.ai tools and workflows. Manage your project Learn about workspace roles, access, settings, and API keys. ## Make your first request ```bash curl --request GET \ --url "https://api.igeo.ai/accounts/{accountId}" \ --header "Authorization: Bearer $IGEO_API_KEY" \ --header "X-Workspace-Id: {accountId}" ``` ## Accounts API routes - GET /accounts — List accounts. - GET, PUT /accounts/{accountId} — Get or update Brand Hub account details. - GET /accounts/{accountId}/ai-engine-exposure — Get visibility broken down by AI provider. - GET /accounts/{accountId}/ai-exposure — Get the account visibility score. - GET /accounts/{accountId}/appeareance — Get account appearances across AI responses. - PUT /accounts/{accountId}/brandbook/visited — Mark the account brandbook as visited. - GET, PUT /accounts/{accountId}/competitors-alt-names — List and update competitor alt names. - GET /accounts/{accountId}/competitors-referrals — List competitor referrals. - GET /accounts/{accountId}/limits — List limits. - GET /accounts/{accountId}/pages — List pages. - GET /accounts/{accountId}/pages/detail — Get page detail. - GET /accounts/{accountId}/pages/prompts — List page prompts. - GET /accounts/{accountId}/pages/v2 — List account pages using the v2 response format. - GET /accounts/{accountId}/provider-mentions — List provider mentions. - GET /accounts/{accountId}/provider-mentions/{provider}/prompts — List provider mentions prompts. - GET /accounts/{accountId}/scanned-prompts — List prompts included in the account's latest scan. - GET /accounts/{accountId}/sources/detail — Get source URL details. - GET /accounts/{accountId}/sources/domain-drill-down/{domain} — Get detailed source metrics for a domain. - GET /accounts/{accountId}/sources/domains — List source domains for the account. - GET /accounts/{accountId}/sources/domains-page — List source domains with pagination. - GET /accounts/{accountId}/sources/domains/{domain}/urls — List source URLs for a domain. - GET /accounts/{accountId}/sources/summary — Get the account's source summary. - GET /accounts/{accountId}/sources/url-type-summary — Get source counts grouped by URL type. - POST /accounts/{accountId}/update-ai-providers — Update ai providers. ## Content Agents API routes - GET /accounts/{accountId}/agents/blog/sites — List connected blog sites. - DELETE /accounts/{accountId}/agents/blog/sites/{siteId} — Delete agent blog site. - GET /accounts/{accountId}/agents/blog/sites/{siteId}/categories — List agent blog site categories. - GET /accounts/{accountId}/agents/blog/sites/{siteId}/pages — List agent blog site pages. - GET /accounts/{accountId}/agents/dialog-init-data — List agent dialog init data. - GET /accounts/{accountId}/agents/downloadImage/{postId} — Download agent image. - POST /accounts/{accountId}/agents/generateContent — Generate agent content. - GET /accounts/{accountId}/agents/posts — List generated agent posts. - GET /accounts/{accountId}/agents/posts/{generationId}/detail — Get details for a generated agent post. - GET /accounts/{accountId}/agents/posts/{postId}/analytics — List agent post analytics. - GET /accounts/{accountId}/agents/posts/{postId}/comments — List agent post comments. - POST /accounts/{accountId}/agents/posts/{postId}/generateShareLink — Generate agent post share link. - GET /accounts/{accountId}/agents/posts/{postId}/reactions — List agent post reactions. - POST /accounts/{accountId}/agents/publish — Publish a generated agent post. - GET /accounts/{accountId}/agents/reddit/account-stats — List agent reddit account stats. - POST /accounts/{accountId}/agents/reddit/approve-comment — Approve agent reddit comment. - GET /accounts/{accountId}/agents/reddit/comment-review/{postId} — Get agent reddit comment review. - GET /accounts/{accountId}/agents/reddit/comment-targets — List agent reddit comment targets. - GET /accounts/{accountId}/agents/reddit/drafts — List agent reddit drafts. - POST /accounts/{accountId}/agents/reddit/generate-comment — Generate agent reddit comment. - POST /accounts/{accountId}/agents/reddit/generate-comment-batch — Generate agent reddit comment batch. - POST /accounts/{accountId}/agents/reddit/post-comment — Post agent reddit comment. - POST /accounts/{accountId}/agents/reddit/regenerate-comment — Regenerate agent reddit comment. - GET, PUT /accounts/{accountId}/agents/reddit/safety-settings — Get or update Reddit agent safety settings. - GET /accounts/{accountId}/agents/reddit/setup-status — List agent reddit setup status. - GET, PUT /accounts/{accountId}/agents/reddit/subreddit-policies — Get or update subreddit policies for the Reddit agent. - POST /accounts/{accountId}/agents/reddit/subreddit-policies/refresh — Refresh agent reddit subreddit policies. - GET /accounts/{accountId}/agents/reddit/subreddits/intelligence — Get agent reddit subreddit intelligence. - POST /accounts/{accountId}/agents/reddit/sync-metrics — Sync agent reddit metrics. - GET /accounts/{accountId}/agents/selectedPage — Get agent selected page. - POST /accounts/{accountId}/agents/selectPage — Select agent page. - PUT /accounts/{accountId}/agents/updatePost/{postId} — Update agent post. - POST /accounts/{accountId}/agents/updatePost/{postId}/addImage — Update agent post add image. - POST /accounts/{accountId}/agents/updatePost/{postId}/removeImages — Update agent post remove images. ## Audiences API routes - GET, POST /accounts/{accountId}/audiences — List and create audiences. - GET, PUT, DELETE /accounts/{accountId}/audiences/{audienceId} — Get, update, and delete audience. - POST /accounts/{accountId}/audiences/generate — Generate an audience with AI. ## Competitors API routes - GET, POST /accounts/{accountId}/market-players — List competitors with filters and pagination, or create one. - PUT, DELETE /accounts/{accountId}/market-players/{competitorId} — Update and delete market player. - GET /accounts/{accountId}/market-players/{competitorId}/citations — List market players citations. - GET /accounts/{accountId}/market-players/{competitorId}/citations/aggregates — List market players citation aggregates. - GET /accounts/{accountId}/market-players/{competitorId}/citations/page — Get market players citation page. - GET /accounts/{accountId}/market-players/company-data — List market players company data. - POST /accounts/{accountId}/market-players/delete-nominee — Delete market players nominee. - POST /accounts/{accountId}/market-players/merge-candidate — Merge market players candidate. - GET /accounts/{accountId}/market-players/nominees — List suggested competitor candidates. - GET /accounts/{accountId}/market-players/optional-grouping — Get the current competitor entity grouping. - POST /accounts/{accountId}/market-players/optional-grouping-generate — Generate a proposed competitor entity grouping. - GET /accounts/{accountId}/market-players/page-data — List market players page data. - GET /accounts/{accountId}/market-players/ranking — Get competitor performance rankings. ## Tracked Recommendations API routes - GET, POST /accounts/{accountId}/monitored-proposals — List monitored recommendations with filters and pagination, or create one. - PUT, DELETE /accounts/{accountId}/monitored-proposals/{trackedRecommendationId} — Update or delete a monitored recommendation. - GET /accounts/{accountId}/monitored-proposals/analytics — Get analytics for monitored recommendations. - GET /accounts/{accountId}/monitored-proposals/overview — Get the monitored recommendations overview, optionally paginated with page and pageSize (newest first). ## Page Scans API routes - GET, POST /accounts/{accountId}/page-scans — List page scans or start a new scan. - GET /accounts/{accountId}/page-scans/{scanId} — Get page scan. - GET /accounts/{accountId}/page-scans/competitor-suggestions — List page scans competitor suggestions. - GET /accounts/{accountId}/page-scans/remaining — Get the number of page scans remaining. ## Prompts API routes - GET, DELETE /accounts/{accountId}/prompts — List account prompts or delete prompts in bulk. - PUT, DELETE /accounts/{accountId}/prompts/{promptId} — Update and delete prompt. - PUT /accounts/{accountId}/prompts/add-batch-suggestions — Add prompt batch suggestions. - POST /accounts/{accountId}/prompts/batch-by-topic — Create prompt batch by topic. - GET /accounts/{accountId}/prompts/responses — List prompt responses with filters and pagination. - GET /accounts/{accountId}/prompts/responses/{responseId} — Get a prompt response by ID. - GET /accounts/{accountId}/prompts/responses/{responseId}/sources — List sources cited by a prompt response. - GET /accounts/{accountId}/prompts/responses/chart-data — Get chart data for prompt responses. - GET /accounts/{accountId}/prompts/responses/llm-mentions-count — Get the LLM mention count for prompt responses. - GET /accounts/{accountId}/prompts/responses/presign-image — Get a presigned URL for a response image. - GET /accounts/{accountId}/prompts/responses/sentiment — List prompt responses with sentiment data. - GET /accounts/{accountId}/prompts/responses/sentiment/historical — Get historical prompt-response sentiment data. - GET /accounts/{accountId}/prompts/responses/source-domains — List source domains found in prompt responses. - GET /accounts/{accountId}/prompts/stage-visibility — Get prompt stage visibility. - GET /accounts/{accountId}/prompts/suggestions — List prompt suggestions. - POST /accounts/{accountId}/prompts/suggestions-generate — Generate prompt suggestions. - PUT /accounts/{accountId}/prompts/suggestions/{promptId} — Update prompt suggestion. - GET /accounts/{accountId}/prompts/work-priorities — List prompt work priorities. ## Recommendations API routes - GET, POST /accounts/{accountId}/proposals — List recommendations with filters and pagination, or create one. - GET, PUT, DELETE /accounts/{accountId}/proposals/{recommendationId} — Get, update, and delete proposal. - PUT /accounts/{accountId}/proposals/{recommendationId}/status — Update proposal status. - POST /accounts/{accountId}/proposals/generate — Generate proposals. - GET /accounts/{accountId}/proposals/live — List active recommendations. - GET /accounts/{accountId}/proposals/meta — Get recommendation filter metadata. - GET /accounts/{accountId}/proposals/remaining — Get the number of recommendations still available. - GET /accounts/{accountId}/proposals/visibility — Get recommendation visibility settings. ## Scans API routes - GET /accounts/{accountId}/scans — List account scans. - GET /accounts/{accountId}/scans/last — Get the date of the latest scan. ## Tags API routes - GET, POST /accounts/{accountId}/tags — List and create tags. - GET, PUT, DELETE /accounts/{accountId}/tags/{tagId} — Get, update, and delete tag. - POST, PUT, DELETE /accounts/{accountId}/tags/batch — Create, update, or delete tags in bulk. - GET, POST /accounts/{accountId}/tags/prompts/{promptId} — List or assign tags for a prompt. ## Topics API routes - GET, POST /accounts/{accountId}/topics — List and create topics. - PUT, DELETE /accounts/{accountId}/topics/{topicId} — Update and delete topic. - GET /accounts/{accountId}/topics/{topicId}/prompts — List topic prompts. - PUT /accounts/{accountId}/topics/{topicId}/prompts-transfer — Move prompts to or from a topic. - GET /accounts/{accountId}/topics/ai-score — Get visibility scores by topic. - GET /accounts/{accountId}/topics/analyse — Get aggregated topic appearance analysis. - POST /accounts/{accountId}/topics/batch — Create topic batch. - GET /accounts/{accountId}/topics/suggestions — List topic suggestions. - POST /accounts/{accountId}/topics/suggestions-generate — Generate topic suggestions. - PUT /accounts/{accountId}/topics/suggestions/{topicId} — Update topic suggestion. ## Dashboard Data API routes - GET /accounts/{accountId}/ui-pages/dashboard — Get data for the account dashboard. - GET /accounts/{accountId}/ui-pages/dashboard/top-source-domains — Get the dashboard's top source domains. ## AI Traffic Analytics API routes - GET /traffic/{accountId}/ai-dashboard-data — Get AI traffic dashboard data. - GET /traffic/{accountId}/cloudflare/analytics — List cloudflare analytics. - GET /traffic/{accountId}/cloudflare/crawler-analytics — List cloudflare crawler analytics. - GET /traffic/{accountId}/cloudflare/crawler-logs — List cloudflare crawler logs. - GET /traffic/{accountId}/cloudflare/zones — List cloudflare zones. - GET /traffic/{accountId}/events — List AI traffic events with filters and pagination. - GET /traffic/{accountId}/has-events — Check whether the account has AI traffic events. - GET /traffic/{accountId}/stats — List stats. --- # Manage your project > Workspace-centric settings: account preferences, team, billing, and switching between workspaces. Canonical URL: https://app.igeo.ai/docs/manage-your-project ## Overview igeo.ai is workspace-centric: what you configure applies to the currently selected workspace (account). Day-to-day product work — prompts, mentions, competitors — uses that same context. Administrative and personal controls sit under Account, Team, and the workspace picker in the shell, rather than a separate “projects table” per brand. Billing and subscription management typically open from the profile menu when your role allows it; keep your plan current so limits and schedules match how you operate. ## Account settings Use Email notifications for email digest and alert settings; Account for connected social accounts and billing-related actions; and MCP & API keys for MCP and Public API integrations available to active workspace members. ## Multiple workspaces If you belong to more than one workspace, switch from the workspace / account control in the app header before changing settings — each workspace keeps its own prompts, competitors, and billing relationship where applicable. ## Team Use Team to manage who can access the workspace and how roles map to features (for example which sidebar areas viewers see versus full participants). Align invites with how your org wants to share dashboards and monitoring work. ## Billing and subscription Plan changes, invoices, and payment methods are handled through your billing flow — often opened from the profile menu as Manage billing or similar when you have access. If you do not see billing actions, ask an admin on the workspace to adjust the subscription or seat model. Prompt limits, schedules, and feature availability follow your subscription; when in doubt, check your plan details alongside how many prompts you run on Prompts. ## Related documentation Tie workspace setup back to brand context and navigation: Public API Authenticate REST integrations and browse every exposed route. Brand profile How Brand Hub captures the story igeo.ai uses for alignment. Sidebar navigation Where Prompts, Account access, and other areas live. Quickstart Guide End-to-end setup through your first useful views. Next steps Support, exports, and where to go after the basics. ## Video walkthroughs - [Get started with igeo.ai](https://www.youtube.com/watch?v=7mmvpPieLyo) --- # Team members and workspace roles > Manage the people, profiles, reporting relationships and access roles associated with your workspace. Canonical URL: https://app.igeo.ai/docs/team-and-roles ## Open the workspace team Team at /new-team shows the people associated with the selected workspace. Open a member to review their profile and available access controls. Member profiles can include role information, reporting relationships, an avatar and voice context. Configured AI agent profiles are displayed separately from people. They help describe the roles and destinations of agents used by the team. - [Open Team](https://app.igeo.ai/new-team) ## Understand workspace access Roles affect which pages and actions are available. Project vault rights and public API key scopes are additional controls for their respective features; a team profile is not a substitute for those permissions. - Owner: retains ownership access; ordinary member access controls do not change or remove the owner's role. - Admin: manages team members and workspace settings within their authorized workspace. - Editor: creates and edits workspace content. - Member: participates in the workspace with the access allowed for that role. - Viewer: has read-only access, with some optimization areas and actions unavailable. ## Add or update a member The interface prevents ordinary role changes to yourself or the owner. If a control is missing or disabled, ask the workspace owner or admin to review the membership. 1. With a workspace-management role, use the add-member action and enter the required person and access details. 2. Open the saved member to update supported profile fields, reporting relationships or photo. 3. Use Workspace access to change an eligible member's role and save the change. 4. When removing a member from the selected workspace, review the confirmation carefully. Their other workspace memberships are separate. ## Set up your personal voice Members can edit their own biography and personal voice. Workspace owners and admins can edit other members' profiles. Open your member profile in Team and choose Edit profile & voice or Edit voice to work on the available settings. Saved personal voice settings help generated comments sound like the person who owns the connected personal social account. This member voice is separate from the company-wide brand context in Brand Hub. 1. Choose a Professional, Balanced or Casual preset, or describe a Voice style that fits you. 2. Adjust the four sliders: Formal to Casual, Concise to Expansive, Analytical to Story-led, and Reserved to Bold. Each slider runs from 0 to 100. 3. Paste an authentic Writing sample to guide vocabulary, rhythm and phrasing. Use Always and Avoid for specific writing instructions. 4. Review your job title, department, Personal positioning and Content pillars. Enter each content pillar on its own line. 5. Try a reply preview, then choose Save profile & voice to make the settings available for subsequent generated comments. ## Preview your reply before saving Use Preview my reply with a sample post to generate a draft reply from your current voice settings, including unsaved edits. The preview does not publish a comment or save your profile. Read the draft for your natural tone and adjust the voice or sample post as needed. Changing either marks the previous result as an earlier preview; use Update my reply preview to hear the current version. Save profile & voice separately when you are satisfied. ## Learn your voice from LinkedIn posts Analyze LinkedIn voice proposes settings from at least three distinct original LinkedIn posts with at least 300 characters in total. These posts must already have been published through your explicitly owned personal LinkedIn connection in this workspace. The analysis does not import earlier LinkedIn history or use company posts, comments or source articles. If the workspace does not have enough qualifying posts, paste an authentic writing sample instead. 1. Choose the personal LinkedIn account to analyze when an account selector is shown, then select Analyze LinkedIn voice. 2. Review the number of posts analyzed and the suggested voice summary. Your existing saved voice stays unchanged during analysis. 3. Choose Apply suggestions to draft if you want to use the proposal, or Dismiss suggestions to leave it aside. 4. Review and adjust the draft settings, preview a reply if useful, then explicitly choose Save profile & voice. Applying a suggestion alone does not save it. ## Related guides - [Manage your project](https://app.igeo.ai/docs/manage-your-project) - [Project details, assets and access](https://app.igeo.ai/docs/project-management) - [Features and workspace access](https://app.igeo.ai/docs/feature-availability) - [Public API](https://app.igeo.ai/docs/public-api) --- # Project details, assets and access > Maintain company details, engagement information, domains, brand files and controlled credential access in an enabled project workspace. Canonical URL: https://app.igeo.ai/docs/project-management ## A shared project record Project management is an optional workspace capability. Its sections include Details, Credentials, Domains, Brand assets, Team access and Access log. The record belongs to the selected workspace. Details brings together company, billing and contact information. Engagement settings describe deliverables, commitments, quotas and meeting cadence when you have permission to maintain them. - [Open project management](https://app.igeo.ai/project-management/details) ## Manage domains and brand files 1. Open Domains to review or maintain the project's domain records. 2. Open Brand assets, choose the appropriate category and upload a supported file. The upload size limit is 4 MiB per file. 3. Use the individual file download actions to retrieve saved assets. Adding another attachment keeps prior files in the category. 4. Keep authoritative company facts and brand assets current so collaborators can use the same project information. ## Use credential access controls Credential lists contain metadata rather than plaintext secrets. Revealing or copying a secret requires the relevant access and a reason; the interface limits how long a revealed value stays visible. Use access requests when you need a credential you cannot currently reveal. Authorized managers can review requests and manage vault rights or category scopes in Team access. Access log provides the saved audit history. Workspace membership and project vault rights serve different purposes. Owners and admins retain the full standard rights defined by the project, and their membership roles are managed in Team. ## Save and resolve changes Save each edit and check the result before switching workspaces. If an engagement has changed while you were editing, review the latest saved version before replacing your draft. A permission restriction or an unavailable module requires a workspace owner or admin to review access. Never paste secrets into public documentation or content workflows as a workaround. ## Related guides - [Team members and workspace roles](https://app.igeo.ai/docs/team-and-roles) - [Brand profile](https://app.igeo.ai/docs/brand-profile) - [Manage your project](https://app.igeo.ai/docs/manage-your-project) - [Features and workspace access](https://app.igeo.ai/docs/feature-availability) --- # Billing, plans and usage > Review the workspace subscription, available plan changes, payment details and billing history. Canonical URL: https://app.igeo.ai/docs/billing-and-plans ## Read the workspace billing overview Open Billing at /billing after selecting the correct workspace. The overview shows the subscription and billing information available for that account, including plan, status, billing interval, renewal timing, payment information and recent payment history when applicable. Plans, trials, negotiated subscriptions and AppSumo entitlements can have different billing arrangements. Use the values shown for your workspace instead of assuming a public price or a fixed quota from documentation. - [Open Billing](https://app.igeo.ai/billing) - [Review available plans](https://app.igeo.ai/pricing) ## Review a plan or payment change 1. Use Pricing to compare the plans and options currently offered to the selected workspace. 2. Use the available manage-plan or payment-method action in Billing. Some actions require an authorized billing role and a managed subscription. 3. Review the amount, interval and effective timing shown by the confirmation or billing portal before completing a change. 4. Return to Billing and verify the subscription and payment state after the action finishes. ## Understand limits and cancellation Tracking capacity, included AI engines and other entitlements depend on the plan and workspace configuration. Check plan details and in-product limit messages before expanding your prompt set or enabling another workflow. If cancellation is available, the cancellation dialog explains the impact and available choices. Read the effective date and consequences shown there before confirming. Use support if your billing arrangement does not expose the required action. Marketplace publication credits and content publishing status are separate from subscription status and AI visibility results. ## Related guides - [Manage your project](https://app.igeo.ai/docs/manage-your-project) - [Features and workspace access](https://app.igeo.ai/docs/feature-availability) - [Articles Marketplace](https://app.igeo.ai/docs/articles-marketplace) - [Next steps](https://app.igeo.ai/docs/next-steps) --- # Email and Slack notifications > Configure weekly digests and competitor alerts for the right workspace roles, and manage the Slack connection. Canonical URL: https://app.igeo.ai/docs/notifications ## Choose email notifications 1. Open Preferences at /preferences for the selected workspace. 2. Enable or disable the weekly digest. When enabled, choose its weekday and the workspace roles that should receive it. 3. Enable or disable competitor alerts and select the recipient roles for those alerts. 4. Save the preferences and check for the saved confirmation. An enabled notification needs at least one recipient role. - [Open notification preferences](https://app.igeo.ai/preferences) ## Connect Slack Open Integrations and find Slack in the Communication category. Use its connection and management actions to configure the workspace's available Slack integration. Email recipient roles and a Slack connection are separate settings. Check the product's current configuration rather than assuming every email event is also delivered to Slack. - [Manage Slack integration](https://app.igeo.ai/integrations?highlight=slack) ## Use notifications as a starting point Open the workspace to inspect the prompts, answers and date range behind an alert. Compare the underlying evidence before changing your content strategy. The Recommendations sidebar may also show an unread-insight indicator based on your last visit. Opening Recommendations lets you review the current actions and their tracking context. ## Related guides - [Connect integrations](https://app.igeo.ai/docs/integrations) - [Recommendations](https://app.igeo.ai/docs/recommendations) - [Competitors](https://app.igeo.ai/docs/competitors) - [Team members and workspace roles](https://app.igeo.ai/docs/team-and-roles) --- # Video tutorials > Watch official igeo.ai walkthroughs and continue with the written guide for each feature. Canonical URL: https://app.igeo.ai/docs/video-library ## Official product walkthroughs Watch official igeo.ai product walkthroughs, conversations and short videos. Continue with the related written guides for current setup steps and feature details. - [Watch the igeo.ai YouTube channel](https://www.youtube.com/@igeo-ai) ## Introduction to igeo.ai Start with an overview of igeo.ai and the shift from search results to answers in AI search. - [Watch Introduction to igeo.ai](https://www.youtube.com/watch?v=3kqdTQEED3s) - [Welcome to igeo.ai](https://app.igeo.ai/docs/welcome) ## Get started with igeo.ai Follow the onboarding walkthrough before setting up your brand, project, and monitored prompts. - [Watch Get started with igeo.ai](https://www.youtube.com/watch?v=7mmvpPieLyo) - [Quickstart](https://app.igeo.ai/docs/quickstart) - [Manage your project](https://app.igeo.ai/docs/manage-your-project) ## Set up AI prompts Watch the prompt setup tutorial, then use the written guide to configure the questions you want to monitor. - [Watch Set up AI prompts](https://www.youtube.com/watch?v=RN86g8Rgf8A) - [Setting up prompts](https://app.igeo.ai/docs/setting-up-prompts) ## Choose the right prompts to monitor Learn about choosing prompts for tracking your brand's performance in AI search. - [Watch Choose the right prompts to monitor](https://www.youtube.com/watch?v=s2_cDfZBqIA) - [Setting up prompts](https://app.igeo.ai/docs/setting-up-prompts) ## Review topics and competitors Review the topics and competing brands that shape your AI search monitoring project. - [Watch Review topics and competitors](https://www.youtube.com/watch?v=HUIh2p11IGs) - [Competitors](https://app.igeo.ai/docs/competitors) - [Setting up prompts](https://app.igeo.ai/docs/setting-up-prompts) ## Review your brand book Watch the brand book walkthrough and review the brand information used across your project. - [Watch Review your brand book](https://www.youtube.com/watch?v=CzWsB_D4GzY) - [Brand profile](https://app.igeo.ai/docs/brand-profile) ## Create and configure audiences See the audience configuration walkthrough, then connect it to your brand voice and content workflow. - [Watch Create and configure audiences](https://www.youtube.com/watch?v=WCD9BPDmufk) - [Brand voice and audiences](https://app.igeo.ai/docs/brand-voice-and-audiences) ## Publish content through the marketplace Explore the marketplace introduction for publishing content on third-party sites. - [Watch Publish content through the marketplace](https://www.youtube.com/watch?v=lSznsBJEK9A) - [Articles marketplace](https://app.igeo.ai/docs/articles-marketplace) ## Connect igeo.ai MCP to Claude Watch the MCP connection walkthrough and use the current setup guide for endpoint and authentication details. - [Watch Connect igeo.ai MCP to Claude](https://www.youtube.com/watch?v=YcLvqjPPEMc) - [MCP integration](https://app.igeo.ai/docs/mcp) ## Track AI citations, mentions, and clicks A brief introduction to tracking citations, brand mentions, and clicks in AI search. - [Watch Track AI citations, mentions, and clicks](https://www.youtube.com/watch?v=S-PBHE7Rbfw) - [Sources and citations](https://app.igeo.ai/docs/sources) - [Understanding your performance](https://app.igeo.ai/docs/understanding-your-performance) - [AI traffic analytics](https://app.igeo.ai/docs/ai-traffic-analytics) ## Can AI really understand you? An igeo.ai podcast conversation about AI understanding and its implications for brands. - [Watch Can AI really understand you?](https://www.youtube.com/watch?v=CjDQfRnGQdg) - [Welcome to igeo.ai](https://app.igeo.ai/docs/welcome) ## Can automation help your brand get found in AI search? An igeo.ai podcast discussion about automation and brand discovery in AI search. - [Watch Can automation help your brand get found in AI search?](https://www.youtube.com/watch?v=CDFmLYyY3aM) - [AI agents](https://app.igeo.ai/docs/ai-agents) ## Can AI agents replace your marketing team? An igeo.ai podcast conversation about AI agents and marketing teams. - [Watch Can AI agents replace your marketing team?](https://www.youtube.com/watch?v=KeJujGuA3YQ) - [AI agents](https://app.igeo.ai/docs/ai-agents) - [Content studio](https://app.igeo.ai/docs/content-studio) ## Faster marketing insights and analytics A short podcast clip about using AI for marketing insights and analytics. - [Watch Faster marketing insights and analytics](https://www.youtube.com/watch?v=37rzzY1Ts4E) - [Understanding your performance](https://app.igeo.ai/docs/understanding-your-performance) ## Add your voice and stories to AI content A short clip about bringing your own voice and stories into AI-generated content. - [Watch Add your voice and stories to AI content](https://www.youtube.com/watch?v=_52CqDzgdms) - [Brand voice and audiences](https://app.igeo.ai/docs/brand-voice-and-audiences) ## Claude and Meta Ads for lead generation analysis A short discussion of Claude and Meta Ads analysis. See the integrations guide for connections supported in igeo.ai. - [Watch Claude and Meta Ads for lead generation analysis](https://www.youtube.com/watch?v=uybhf06Yoj0) - [Integrations](https://app.igeo.ai/docs/integrations) ## When people ask AI, does your brand show up? A short igeo.ai podcast clip about brand visibility in AI answers. - [Watch When people ask AI, does your brand show up?](https://www.youtube.com/watch?v=j9MgztRB5-k) - [Visibility](https://app.igeo.ai/docs/visibility) ## Faster marketing insights A short igeo.ai podcast clip about marketing insights. - [Watch Faster marketing insights](https://www.youtube.com/watch?v=zN1yQrSO2oo) - [Understanding your performance](https://app.igeo.ai/docs/understanding-your-performance) ## Can AI help small teams? A short igeo.ai podcast clip about how small teams work with AI. - [Watch Can AI help small teams?](https://www.youtube.com/watch?v=b1rTWgJkK1s) - [AI agents](https://app.igeo.ai/docs/ai-agents) ## Video walkthroughs - [Introduction to igeo.ai](https://www.youtube.com/watch?v=3kqdTQEED3s) - [Get started with igeo.ai](https://www.youtube.com/watch?v=7mmvpPieLyo) - [Set up AI prompts](https://www.youtube.com/watch?v=RN86g8Rgf8A) - [Choose the right prompts to monitor](https://www.youtube.com/watch?v=s2_cDfZBqIA) - [Review topics and competitors](https://www.youtube.com/watch?v=HUIh2p11IGs) - [Review your brand book](https://www.youtube.com/watch?v=CzWsB_D4GzY) - [Create and configure audiences](https://www.youtube.com/watch?v=WCD9BPDmufk) - [Publish content through the marketplace](https://www.youtube.com/watch?v=lSznsBJEK9A) - [Connect igeo.ai MCP to Claude](https://www.youtube.com/watch?v=YcLvqjPPEMc) - [Track AI citations, mentions, and clicks](https://www.youtube.com/watch?v=S-PBHE7Rbfw) - [Can AI really understand you?](https://www.youtube.com/watch?v=CjDQfRnGQdg) - [Can automation help your brand get found in AI search?](https://www.youtube.com/watch?v=CDFmLYyY3aM) - [Can AI agents replace your marketing team?](https://www.youtube.com/watch?v=KeJujGuA3YQ) - [Faster marketing insights and analytics](https://www.youtube.com/watch?v=37rzzY1Ts4E) - [Add your voice and stories to AI content](https://www.youtube.com/watch?v=_52CqDzgdms) - [Claude and Meta Ads for lead generation analysis](https://www.youtube.com/watch?v=uybhf06Yoj0) - [When people ask AI, does your brand show up?](https://www.youtube.com/watch?v=j9MgztRB5-k) - [Faster marketing insights](https://www.youtube.com/watch?v=zN1yQrSO2oo) - [Can AI help small teams?](https://www.youtube.com/watch?v=b1rTWgJkK1s) ## Related guides - [Quickstart Guide](https://app.igeo.ai/docs/quickstart) - [Brand voice and audiences](https://app.igeo.ai/docs/brand-voice-and-audiences) - [Setting up prompts](https://app.igeo.ai/docs/setting-up-prompts) - [MCP](https://app.igeo.ai/docs/mcp) --- # Next steps > Find support, answers to common questions and the next workflow for your workspace. Canonical URL: https://app.igeo.ai/docs/next-steps ## Overview Next steps Browse FAQs for common questions, contact us for support, or review pricing if you're evaluating plans. Use the in-app feature request and bug report forms to share product feedback. Return to the Dashboard anytime.