- Brand
- CrunchJunkie
- Category
- Marketing
- Primary Subcategory
- AI Search & LLM Visibility (AEO/GEO)
Integration details
Description
CrunchJunkie connects your marketing reporting and AI-search visibility to ChatGPT. After you sign in, ChatGPT can read your own team's data — your clients, connected data sources, saved reports and their numbers, and your AI-visibility metrics (how often ChatGPT, Gemini, Perplexity and Google AI Overviews mention your brand). Ask in plain language, like "how did last month's Google Ads report look?" or "what's our AI share of voice this week?", and get answers drawn straight from your live CrunchJunkie account. The connection is strictly read-only and scoped to your workspace: it can fetch and search your data but never change, create or delete anything. Available on CrunchJunkie paid plans.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- AI Search & LLM Visibility (AEO/GEO)
- Secondary Subcategories
- None listed
- Brand
- CrunchJunkie
- Access
- Account required
- First tracked
- 2026-11-20
- Tool count
- 99
- Market
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Not discoverable in ChatGPT yet
ChatGPT now suggests Plugins on its own when they match a user's request, but not every Plugin is being surfaced yet.We haven’t seen CrunchJunkie suggested yet. Sign up and we’ll track it, and your Discoverability Score will appear here once ChatGPT starts surfacing it.
What discovery looks like

Get alerts for CrunchJunkie
Get updates when CrunchJunkie’s Discoverability Score or category rank changes.
Competing in ChatGPT AI Search & LLM Visibility (AEO/GEO)
View Category99 tools agents can invoke
Add a market to a client's AI-visibility project: a country and a language (or a language alone) its prompts are scanned in, with its own prompts and competitors. `prompts` are the reviewed prompt texts (from translate_prompts, edited, or written in that language); without them the market starts empty. Competitors default to the project's list; `competitors` gives the market its own, against which only its share of voice is measured. The preview states what one scan of the market uses (prompts × runs × engines, premium engines counted 3×) and when it is first scanned. Requires MCP write actions; without confirm:true it returns a preview. Writes an internal timeline note.
add_market
Add a manual timeline annotation to a client's AI-visibility project — a dated note that pins onto the charts so metric movements come with their explanation. By default the note is internal (team-only); set showInReports:true to make it visible on shared report charts too. Requires MCP write actions; without confirm:true it returns a preview.
add_annotation
Start tracking keywords for a client, for one place and language. By default Google on desktop and mobile, top 100; Bing and the local lists ("More places", Google Maps) can be switched on with tracks. A keyword that is already tracked for the same place and language is left as it is; a keyword with a search operator (site:, inurl: …) is refused. Tracking runs weekly on the workspace's own DataForSEO account (or, on a Rank Tracker budget, on CrunchJunkie's account, charged to the budget), so every keyword and every engine adds to what is charged: the preview states the most it can cost per month. Get location from find_rank_location. Requires MCP write actions; without confirm:true it returns a preview.
add_rank_keywords
Add a text widget, a free-text block written by the caller, to a report. Deterministic, no AI: the text goes in exactly as given, as HTML (p, br, strong, em, u, s, ul, ol, li, h2–h4, blockquote, a href) or plain text, at most 50,000 characters; scripts, event handlers, javascript: links, frames, images and inline styles other than text-align are removed. Styling is carried by attributes, never inline styles: <span data-tone="muted|accent|positive|warning|negative"> (text colour), <span data-mark="lime|green|amber|rose"> (highlight), <span data-size="small|large">, <div data-callout="note|tip|warning|important"> (a tinted box around one block) and <hr> (a divider); each is painted with the report theme's own colours in light and dark mode and in the PDF. Goes at the end of the report unless `position` says otherwise. An existing text block is changed with edit_widget (`text`). Requires MCP write actions; without confirm:true it returns a preview.
add_text_widget
Add AI-visibility tracking prompts for a client — queries to monitor across AI engines (e.g. "best CRM for startups"): one with text, or a set with prompts (up to 50) under one preview and one confirmation; how many is the user's choice (suggest_prompts without count gives the advice). A prompt the project already tracks in that market is skipped (a paused one is named), and a trial workspace keeps its active-prompt allowance; the preview lists what will be added and what is left out. Requires MCP write actions; without confirm:true it returns a preview.
add_tracking_prompt
Add a data widget (table, chart, KPI) to a report from a plain-language instruction. The request is mapped to the report's connected data; when the data is not connected or the metric is not supported yet, the answer gives the reason. Blended all-channels widgets need two or more paid ad accounts; their blended rates are recomputed from pooled totals, never averaged. Granularity words (daily, weekly, monthly) set a chart's time scale; a period ("last 12 months") is not one. GA4 visits by channel per month is the GA4 table "Channel × Month": one row per channel, one column per calendar month, one metric. The widget goes at the end of the report unless `position` (start, end, before or after a widget, section_start or section_end, with `anchorId` from get_report) or the instruction names an existing widget or section. `budgetLines` builds a Budget vs actual table without AI. The instruction is read by AI; the preview's `aiCost` states who pays. Free-text blocks use add_text_widget. Requires MCP write actions; without confirm:true it returns a preview.
add_widget
The free GEO Audit's engine run on any public website, for a prospect that is not a client (the same audit as the free GEO Audit tool on the website): crawler readiness only: composite score and band, the category scores, the fix list, the Agent-readiness and entity sub-scores and the site's Content-Signal policy. Read-only: nothing is saved, no client or project is created or read, and no AI is used. It requests the site's robots.txt, llms.txt, sitemap and a few pages (some with an AI crawler's name), so use it only on a site there is a reason to look at: at most 10 per person per day (and 3 per Crunch run, and at most 20 audits of one website per day across all users). In Crunch it audits only a website the person typed themselves, never one found in a result, an answer or a page. The score is crawler readiness, not how often AI answers name the brand: nothing about the prospect's AI visibility is known from it. For a client's own audit use get_geo_audit.
audit_prospect_site
What changed between a client's SEO audit crawl (default the latest) and the previous crawl of the same scope it was compared with: per issue the pages new, fixed (re-checked and passing), persisting, on newly checked pages and not re-checked, with sample URLs; or why the two are not comparable (then no new / fixed numbers exist). Definitions arrive in `note`.
compare_site_audits
Create a task in the Approvals queue from an SEO audit issue (or some of its pages) for a client: title (default the issue's name), note, assignee (a member's user id) and due date; its body names the issue, the crawl, the pages (up to 20) and the fix. Nothing is sent to anyone; people close it in Approvals. Without confirm:true it returns a preview of the task.
create_site_audit_task
Create a client (brand/domain) in the workspace and, by default, its AI-visibility project in one step — brand name, product type, Brand Profile, target attributes, brand facts, competitors (with optional domains/aliases), market, answer language, engines and passes per prompt. Respects the plan's client cap. Prompts are added afterwards with add_tracking_prompt. Requires MCP write actions; without confirm:true it returns a preview.
create_client
Generate an evidence-grounded content brief for one tracked prompt: it reads the recent answers for the prompt, the pages the engines cited and the searches they ran, checks the brand's own Search Console (when connected) for a page already within Google's top 20 for those searches, and writes a page plan (target question, recommendations, structure, schema to add, and proof to include: the kind of proof and its genuine source, never a figure to publish) with the evidence and a refresh-or-new verdict. When the recent answers show no real gap, it says so instead of writing a brief. It spends AI on the workspace's own key or Managed AI, not against the scan allowance. Requires write actions and "Allow actions that spend AI"; counts toward 20 assistant-started scans, briefs and rankings refreshes per workspace per day. Without confirm:true it returns a preview. Saved briefs are read with get_content_brief.
create_content_brief
Create a new report for a client. It can be pre-filled from one or more connected data sources' standard templates (e.g. "Google Ads", "Meta", "GA4"), including "All channels", a blended cross-channel section available with at least two paid ad accounts. add_widget and edit_widget refine it afterwards. Requires MCP write actions to be enabled for the workspace; without confirm:true it returns a preview and creates nothing.
create_report
Create, change or revoke a report's share link. `create` makes the link or keeps the existing one and applies the settings given; `update` changes it; `revoke` deletes it so its URL stops working for good (a later create gives a new URL). Settings: `enabled` (false keeps the link, viewers see "not available"), `password` (at least 8 characters; sets or replaces; null removes; stored hashed, never returned; 10 wrong guesses lock the password check for 15 minutes, and setting a new password resets that), `allowDateChange` (true lets viewers pick other periods and see data beyond the report's own range). Anyone with the link can open the report with every widget, its live numbers and the saved AI summaries, after the password if one is set. A report in Deleted cannot be shared. Returns the share URL. It does not e-mail the link (send_report does). Requires MCP write actions; without confirm:true it returns a preview of what becomes public.
create_share_link
Approve or dismiss one item of the Approvals queue, as the Approve and Dismiss buttons on AI Visibility → Approvals do. Approve delivers it: an AI action plan or content brief is e-mailed to the automation's recipients (or the workspace owner); a report draft gets a share link (anyone with the link can then view that report) that is e-mailed to them; a manual task is marked done and nothing is sent. Dismiss closes the item and moves a drafted report to Deleted. Approving spends no AI and starts no scan. It acts on an explicit decision, shows a preview of who gets what, and applies only with confirm:true. Requires MCP write actions.
decide_approval
Edit an existing report widget from a plain-language instruction, validated against the same catalog as add_widget: an impossible change is refused with a reason and nothing changes. Returns a receipt comparing the widget before and after, with the previous configuration for restoring it. `widgetId` (from get_report) pins the target; otherwise it is identified from the instruction. Granularity words (monthly, weekly, daily) set a chart's time scale. Moves (`move`, or an instruction naming an existing widget or section) and section operations are supported; a move result carries `undo`. A text widget is replaced exactly as given with `text` + `widgetId`, without AI. A Budget vs actual table takes `widgetId` + `budgetLines`. An instruction is read by AI; the preview's `aiCost` states who pays. Requires MCP write actions; without confirm:true it returns a preview.
edit_widget
Fetch a single item by the id returned from search (report:<id> or client:<id>). A report in Deleted (the trash) comes back marked deleted: true in its metadata.
fetch
Prompts where the tracked brand is absent from every recent AI answer while competitors are named, the gap definition the in-app Content Brief generator uses, so each gap can become an evidence-grounded brief in CrunchJunkie. Returns the competitors named and the domains the engines cited instead. The gap rule arrives in `howToRead`.
get_content_gaps
Find the place a keyword is searched from, as a person types it: a city, region, postcode or country name. Returns DataForSEO's own places with the locationCode that add_rank_keywords takes. The list does not hold every postcode of a country; a place that is not found can be tracked by coordinates instead ("lat,lng" as the query returns them normalised). bingExact false means Bing cannot be pointed at that place and would search the whole country.
find_rank_location
A project's AI visibility next to the visits and conversions AI assistants send to the client's website, from the client's connected GA4 property: per-day visibility beside AI-referred sessions, conversions and revenue, window totals, the AI-referred conversion rate against the site-wide rate (with a ± of one standard error), and the correlation between visibility and the chosen metric over the days that have both (from 20 such days, with a 95 % interval). `availability` states when GA4 is not connected, not readable or not scanned, and those figures are then null. The GA4 caveats (undercounting, tracking changes, correlation) arrive in `howToRead`.
get_ai_attribution
The workspace's Managed-AI scan allowance for the current billing period: tier, checks included, carried over, used and remaining, overage so far with its price per check in the workspace's billing currency, the fair-use ceiling, checks run on the workspace's own provider keys (BYOK) with an estimated provider cost in USD, where this period's managed checks were started, this month's assistant messages on Managed AI by surface, and when the period resets. A workspace that is not on a metered Managed-AI tier returns no allowance figures. The weighting and cost-estimate notes arrive in `howToRead`.
get_usage
The prioritised actions on the AI Visibility Insights page: citation, content, reputation, technical (llms.txt, AI-crawler access in robots.txt, Organization schema), PR, social and competitive actions (among them one Gap analysis awareness action, `gap`: how many sites AI answers used when they named a tracked competitor and not the client, with the top three, counted by the Gap analysis's own tally over the same 30 days), each with its priority (high, medium, low), the rationale (the observation with the answers behind it and the window), how many tracked prompts it affects, and the domain and engines involved. Worked out at call time from the last 30 whole UTC days of answers plus a live check of the client's website, as the page does. `projectId` or `clientId` selects one brand; without either, the agency page across every brand with a scan (at most 10). Detected changes are in get_signals. Changes nothing. Priority and wording rules arrive in `howToRead`.
get_insights
How visible a project's brand and its competitors are in AI answers over a window of whole UTC days (default the last 30, at most 180; dateFrom and dateTo choose it). `pooled.brands` gives each brand over every answer in the window, pooled as the app's Overview does: visibility with its ± margin, share of voice, sentiment and average position; `pooled.clientByEngine` gives the client per engine; `snapshots` holds the cells behind the pool (one per scan day × engine × market × brand, newest first, at most 500). `source` is blended (default), native or peec. `summary: true` returns the pooled figures without snapshots (a month of a busy project otherwise runs to about 60,000 characters); `limit` and `offset` page the snapshots (`nextOffset`); without them the call returns the newest 500 rows. A model the project has no answer from returns a note naming its engines. Definitions and cautions arrive in `howToRead`.
get_ai_visibility_metrics
The ads people on the team saw in ChatGPT for a client's tracked prompts, from the checks they recorded (no request to ChatGPT, no charge): per advertiser its ads, conversations and prompts, with its newest ad; per conversation the prompt, the date, whether the answer named the client and the ads shown with their turn and whether the answer named that advertiser; the four named-and-paid groups (free, rival, contested, open) counted over every conversation; the client's own ads and the conquest count. One country at a time.
get_chatgpt_ads
The latest technical GEO Audit for a project's domain: composite score and band (crawler readiness: whether AI crawlers can reach, read and parse the site), per-category results, insights and the Agent Readiness sub-score. `firewallAccess` joins robots.txt with a live probe per AI crawler on the homepage and one sitemap content page. `includePages` adds per-page results (capped at 10); `category` returns one part and `fixes: false` leaves out the static fix texts. Counts a check states in its `detail` also arrive as `figures`. The score measures readiness, not how often AI answers name the brand (`scoreNote`); the probe's limits and layer rules arrive in `howToRead`. run_geo_audit creates a new audit.
get_geo_audit
A client's SEO audit (a crawl of the client's own website, AI search first): the latest crawl that ran to the end (or crawlId; a later crawl that did not is named in laterUnfinishedCrawl), its status, Site Health and AI Search Health (pages without errors of pages evaluated, with n and the crawl date), site-wide errors, issue counts by severity and category, the value windows behind the figures, the comparison with the previous crawl of the same scope, a running crawl's progress, the settings and schedule, the page allowance left, and the health of earlier crawls. Reads stored crawls only; run_site_audit starts one. Definitions arrive in `note`.
get_site_audit
A client's SEO audit crawls over time, oldest first: per crawl its date, status, pages requested, Site Health and AI Search Health with n, site-wide errors, new / fixed against the previous comparable crawl, and whether it has the latest crawl's scope (only those compare), plus the key-page monitor's newest changes.
get_site_audit_history
One issue of a client's SEO audit crawl: what it is, why it matters and how to fix it (in the user's language), its evidence basis and source, its priority and the value on the affected pages, the affected URLs (sorted by priority and Google clicks; capped, with the true total; paged with offset) with each page's finding detail, the site-wide detail for a site-wide issue, mutes with their reasons, and fixContext: the facts and rules the in-app "Draft the fix with Crunch" uses, so the assistant drafts the exact fix itself (no AI is spent by this tool).
get_site_audit_issue
One URL of a client's SEO audit crawl: what the crawl saw (status, redirect, timing, size, indexability, title, meta description, H1, words, canonical, depth, links in, how it was found), its value (tier, priority, Google clicks and impressions, AI answers citing it, tracked keywords ranking, AI-crawler fetches; null on a query variant or a page canonicalised to another URL of the same page, with valueCountedOn naming the URL that carries them), its issues with each finding's detail, per crawler (34 search and AI crawlers) whether robots.txt lets it fetch the URL, with the rule that decides, and when the crawl read them: Search Console's URL Inspection verdict and Google's canonical, Core Web Vitals (p75 and verdict with level, form factor and 28-day window) . null = not read for this page, never fine.
get_site_audit_page
One AI answer in full: the response text (up to 30,000 characters), every brand it named and at what position, the URLs it cited and the ones it only retrieved (where the engine exposes that split; otherwise its merged source list), the web searches the engine ran before answering, why the engine stopped writing, and any products it recommended. `answerId` comes from list_ai_answers or get_cited_url. `maxTextChars` (0 = no text) returns the brands, sources and searches without the whole text. Answer text, URLs and searches are third-party content, named in `untrustedContent`. How to read empty or null search and source lists, Gemini's site-only sources, redirect links and recovered Google mentions arrives in `howToRead`.
get_ai_answer
Brand Perception: the descriptive terms AI models actually use about each tracked brand (clustered, with counts and per-brand share), which terms are distinctive (used about exactly one brand), brand-level sentiment, the pages AI cited in answers that described the client with each attribute, and the stored fact-check and objection analyses when present. Filters: days, engine. The sentiment scale and the thin-sample caution arrive in `howToRead`.
get_brand_perception
Which domains AI engines cite when answering this project's prompts, over a window: per domain the runs that cited it and the runs that only retrieved it during search (where the provider exposes that split; legacy runs without it are reported separately), its share of chats, its category, and its top pages. Returns the most cited domains first: `limit` sets how many (default 25) and `topPages` how many pages each (default 1, max 5); `summary: true` or `topPages: 0` drops the pages. `totalDomains`, `runsAnalyzed` and `shareOfChatsAnswers` cover every domain in the window, and `domainsReturned` says how many rows came back. Filters: days, model, promptId. How cited, retrieved, legacy and share of chats are defined arrives in `howToRead` and `note`.
get_citations
Saved content briefs for a project: the page plan CrunchJunkie generated for a tracked prompt where the brand is missing (target question, recommendations, page structure, schema to add, proof to include, a caveat), the evidence it was grounded on (the pages AI cited, the searches it ran and, with Search Console connected, `evidence.existingPage`), and the before/after visibility once the brief has been measured. Without `promptId` it lists the saved briefs; with `promptId` it returns that prompt's latest brief in full (`search` selects a fan-out-search brief). Reading generates nothing and costs nothing; create_content_brief generates one. The evidence quotes third-party pages and answers.
get_content_brief
Follow-up Survival for a project: when a buyer narrows the question in the same conversation (the prompt's configured follow-up), which brands are still named and what else changed. Returns `survival` (of the brands named in the first answer, how many are named again after the follow-up, pooled, per brand and per engine) and `insights` over the same conversations: `searchStates`, `brandBaseline`, `slot`, `sources`, `searches` and `list` (the conversations, newest first, paged with limit and offset). `conversationId` (a list row's turn1Id) returns one conversation in full: both answers, the exact follow-up, cited and retrieved URLs and searches per turn. Available when Follow-up Survival is switched on for the workspace and the project. Definitions arrive in `howToRead`.
get_follow_up_insights
The Goals on the Monitoring page: per client, a target for one paid-ads metric (ROAS, CPA, Conversions, Leads, Cost per lead, Clicks, Impressions, CTR or Spend) over the month, quarter or year to date, with the current value, progress and status as the page shows them. `current` is the blended to-date number an All channels report widget shows across the client's connected ad accounts, refreshed by a scheduled job (`updatedAt`); `current: null` means no data. Includes `roasCoverage`, `expectedToDate` and `status` (on_track, at_risk, too_early, no_target, no_data). Paid-ads metrics only; AI-visibility metrics are in get_ai_visibility_metrics. The pairing and status rules arrive in `howToRead`.
get_goals
Where to start for a client, from its own data. (1) Striking distance — Search Console queries at an average position of 4–20 in the last 30 days (all countries), most impressions first, with the monthly searches already stored for the chosen country and language (a stored lookup, or a Google Ads figure the workspace looked up), and what one lookup of the missing figures would cost. (2) The plain searches AI engines ran for the client's tracked prompts, with runs of n answers and the window. Reads only; lookup_keyword_volumes fetches the missing figures, research_keywords researches a seed.
get_keyword_opportunities
One stored keyword lookup (key) or saved list (listId) with this client's joins, filtered, sorted and paged like the app's table: per keyword the monthly searches (a Google Ads-based model, with its band and date), 12-month trend, difficulty and its step, intent, CPC and bids, SERP features of the dated sample, the AI Overview by its best evidence (the Rank Tracker's newer check where tracked, else DataForSEO's dated sample; source, date, age, stale after 90 days, client cited), how often AI engines ran the search for the client's prompts (runs of n answers, window), and the client's Search Console position. Also the summary of the matching rows (median difficulty with n, AI Overview k of n) and how many rows each view holds (aio_gap, striking, ai_searched). Reads only; nothing is sent to DataForSEO.
get_keyword_research
How keyword research runs for this workspace: which DataForSEO account a lookup would use (the workspace's own, or a Rank Tracker budget) and why, the budget left, DataForSEO's price per request and per keyword with the date it was read, the most a lookup of 100 to 1,000 keywords can cost in USD and EUR (and what a budget is charged), the lookup types, the languages it offers per country (languagesByCountry), row limits and the published difficulty formula. Reads only.
get_keyword_research_setup
The anchor texts of the links DataForSEO found to a client's site, from the STORED answer (no new request, no charge): referring domains, nofollow domains, backlinks, first seen and spam score per anchor, and OUR class (brand, url, generic, descriptive, empty — a heuristic from the client's name and domain, never DataForSEO's). With no stored answer it says so.
get_link_anchors
The weekly spam check of a client's new linking domains: whether it is on, the domain, the account it runs on, its last status (with the next step: confirm_again means the workspace's account type changed since it was switched on, so it waits for a person to confirm it again), the workspace's monthly cap and what this month used, the weekly readings (new and lost referring main domains, newest first) and the link-spam Signal (open, else the latest), and what each cap choice would cover. Reads only.
get_link_monitor
The client's own pages that links point to, from the STORED DataForSEO answer (no new request, no charge): HTTP status DataForSEO last read, title, referring domains, backlinks, broken backlinks and first seen. A page answering with an error (status >= 400) while links point to it is a reclaim candidate (redirect or restore it). With no stored answer it says so.
get_linked_pages
Drill into one page the AI engines use as a source: how many of a project's answers cited it and how many retrieved it during search, its share of chats (answersUsingUrl ÷ answersInWindow), which tracked prompts and engines those answers came from, when it was first and last seen, how often the brand and which tracked competitors were named in the same answers, and the ids of the most recent answers (open with get_ai_answer). Also the page title (Peec AI data), page type, domain category, and a `lifetime` block with the page's citation status, its citation rate before and now, weekly series, per-engine split and evidenced causes. Page URLs come from get_citations or list_citation_lifetimes. The URL matching, Peec AI chat, Gemini site-only and lifetime-frame rules arrive in `howToRead`.
get_cited_url
Full detail for one tracked prompt: per-engine pooled visibility over a window, which competitors the AI named (with counts), the domains cited for this prompt (`runsCiting` = runs that cited it at least once; `citations` = total citations), and the freshest answer excerpt. `promptId` comes from list_prompts.
get_prompt_details
Query fan-outs: the web searches each AI model ran through the provider's official API before answering the project's tracked prompts. One row per distinct search, sorted by answers, with the engines and prompts behind it, its tags, the tracked brands named inside the search string, the client's citation and mention counts, the hosts cited and matching Search Console rows. `limit` sets how many rows come back (default 5, max 200) and, above 10, how long the lists in `signals`, `brandsInSearches` and `sequences` are (default the top 10 of each, with their totals); `summary: true` returns those blocks without rows; `distinctSearches`, the totals in `signals`, `brandsInSearches` and `sequences`, and the per-engine `coverage` describe every search in the window. Filters: days, engine, promptType (shopping or other), tag. fanoutSource "peec" returns the sub-queries Peec AI recorded in its own chats instead, for clients with a Peec AI connection (a separate capture, never pooled with ours). The reading rules for these figures arrive in `howToRead`.
get_query_fanouts
How rank tracking is set up for a client: whether the workspace's DataForSEO account is connected and healthy (the login is masked, the password is never returned), or whether it runs on a Rank Tracker budget (CrunchJunkie's DataForSEO account, charged to the budget; account.source = "managed"), the domains whose positions are read (the client's own site and competitors), the weekly schedule in the client's timezone, which engines and devices are switched on and for how many keywords, the most a weekly run and a month can cost, and what the searches really cost in the last 28 days. It shows the cost ceiling before keywords are added or a refresh is started.
get_rank_tracking_setup
The evidence behind one ranking: the results list the search engine returned for that check with the tracked domains marked, how many results came back against how many were asked for, the link to repeat the same search, every tracked domain's position in that check, the keyword's position history, and what the check cost. It answers "why does it say position 9?" or "why was it not found?".
get_ranking_evidence
A client's keyword rankings in Google and Bing: per keyword the position among organic results and among everything on the page, the change since the last comparable check, the ranking page and whether it is the page the client wants to rank, the local pack position, whether an AI Overview was shown and cited the site, and when it was checked. Also a summary over the keywords of the chosen engine and device (top 3, 10 and 20 with sample size, average position, distribution, movement, and aiOverview.ranked: the keywords whose AI Overview sources could be read split into top 10 and cited, top 10 not cited, cited outside the top 10, and neither), the same per tag and for branded and non-branded keywords, monthly search ranges per keyword, and competitors' positions. Rows are paged and filterable (column, tag, search, branded, within, movement, aiOverview, needsAttention, compareDays). Definitions arrive in `howToRead`.
get_rankings
Get a single report's definition (name, type, widget layout, date-range config) by id.
get_report
Assemble a report's live data (KPIs, charts, tables) for a period, pulled from the connected sources exactly as the app does. `datePreset` and `comparePreset` default to the report's saved config; `widgetIds` (from get_report) limits the result to chosen widgets, which matters for large tables (a 500-row table alone can run to about 90,000 characters); `brandFilter` reads query-based widgets as branded or non-branded only. A widget that could not be read for the period is null, with the reason in `_meta.unavailable`. Third-party text (URLs, domains, page titles, search queries) is named in `untrustedContent`. Notes on donuts, sparklines, margins of error, memory-sourced answers, Peec AI counts and report filters arrive in `howToRead`.
get_report_data
Progress of an AI-visibility scan: its status (queued, running, done, stopped, error), how many of its checks have finished, how many failed for good, when it started and last moved, the last error or budget pause, `waitingToStart`, and `estimatedMinutesLeft` with its `estimateBasis`. `jobId` comes from run_scan; `projectId` or `clientId` selects that project's most recent scan. How the estimate is made, and how background scans advance, arrives in `howToRead`.
get_scan_status
Who advertises on a client's tracked keywords, read from the results pages the Rank Tracker already stored (no new search, no charge): per advertiser the checks it was seen on of all checks in the window, text ads above or below the organic results, whether it is new or stopped against the previous window, its newest ad copy and sitelinks, and the products of its Shopping ads; per keyword how many checks had ads and who; ads on the client's branded keywords; the client's own ads. Needs the Rank Tracker and the Ads area.
get_search_ads
CrunchJunkie ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve CrunchJunkie's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are CrunchJunkie alternatives on ChatGPT?
As of 2026-11-20, CrunchJunkie competes with 212medya Growth Check, 3RD, 8ight SEO & GEO, Abondance, Actionbase, Adzviser Search Console, AEO/GEO by VibeSEO, Aeolo and 119 more in ChatGPT AI Search & LLM Visibility (AEO/GEO), ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.