Scrunch
AI search visibility, citations, crawler analytics, and product-level shopping insights
Overview
Scrunch now presents itself as an Agent Experience Platform (AXP) with separate Monitoring & Insights and Content Delivery directions. Its public materials still describe prompt monitoring and citations, AI Search Trends, Insights, Agent Traffic, Site Maps, and product-level Shopping analysis, but the current homepage also promotes autonomous agent deployments, multi-model orchestration, and AI-optimized content delivery. Buyers should distinguish the established monitoring product from newer AXP and infrastructure positioning before treating every homepage capability as available in the same package.
This makes Scrunch different from a prompt-only visibility tracker. It attempts to connect four separate observations: what monitored AI answers say, which sources they cite, which automated clients request site pages, and how products appear in AI Shopping experiences. Those observations should remain separate in reporting. A crawler request is not a citation, a citation is not a click, and a vendor-selected case study is not causal revenue evidence.
- Best for: Ecommerce, SEO, content, and agency teams that need AI-answer monitoring plus crawler and product-level diagnostics.
- Not ideal for: Buyers seeking a low-cost, transparent multi-tier tool, a mature independent review base, or guaranteed traffic and revenue impact.
- Pricing: The current pricing page exposes tier-level model coverage and evaluation positioning but did not return a reliable dollar price in the direct page extraction on September 3, 2026. Third-party pages still show conflicting $250 and $300 starting-price figures; request a current quote.
- Free access: The current pricing page invites teams to evaluate Scrunch and establish benchmarks; trial duration and included limits require confirmation.
- Primary strength: Brings answer visibility, citations, AI-agent traffic, and Shopping into one measurement model.
- Primary limitation: The current page leaves prompt, workspace, seat, and audit quotas unclear; expanded model coverage and API access are positioned as higher-tier requirements.
Who should use Scrunch?
Best for
- Ecommerce teams auditing whether products and attributes appear correctly in AI Shopping answers
- SEO and content teams that need prompt results connected to cited pages and site diagnostics
- Technical marketers investigating which AI agents request which sections of a site
- Agencies that need client workspaces, repeatable prompt panels, and executive AI-search reporting
- Teams willing to validate AI-search observations against server logs, analytics, feeds, and controlled content changes
Not ideal for
- Solo marketers who only need a few manual ChatGPT checks
- Buyers requiring a broad independent review sample before purchase
- Organizations that need fully transparent API, retention, and overage terms before speaking with sales
- Teams expecting crawler access to automatically create citations or conversions
- Product teams without reliable catalog, price, availability, review, and shipping data
Quick facts
| Fact | Details |
|---|---|
| Primary use case | AI-search visibility, citations, crawler analytics, and AI Shopping analysis |
| Main category | Analytics |
| Core price | Not reliably exposed on the current pricing page; verify quote |
| Trial | Evaluation access is promoted; duration and scope require confirmation |
| Prompt, audit, workspace, and seat limits | Current page did not expose reliable quotas; older August snapshot is not assumed current |
| Evaluation LLM coverage | 4 LLMs supported, according to the current pricing page |
| Expanded coverage | 9 LLMs supported, according to the current pricing page |
| Advanced access | Current pricing page references advanced features, API access, and dedicated support; exact entitlement requires confirmation |
| Last reviewed | September 3, 2026 |
AICiteKit editorial verdict
Scrunch is a credible shortlist candidate for teams that do not want to treat AI visibility as a single dashboard score. Its current navigation exposes a useful measurement split: monitoring and citations for answer evidence, Agent Traffic for automated requests, Site Maps for how AI agents consume a site, and Shopping for product-level visibility. The new AXP and Content Delivery positioning broadens the product story, but should be evaluated as a separate implementation decision.
The strongest evidence supports the existence and stated scope of that workflow, not its business outcomes. Scrunch’s homepage displays customer results such as increased brand presence and AI-attributed signups; these are vendor-selected customer evidence and should not be presented as independent or causal proof. Capterra’s current listing reports zero user reviews, so public customer evidence remains thin.
Bottom line: Scrunch is worth testing when crawler behavior and ecommerce product rendering matter alongside prompt visibility. It is harder to justify for a small team that needs a predictable self-serve price, because the current page does not expose a reliable dollar price or complete quota table. During an evaluation, freeze a prompt set, inspect raw answer and citation evidence, compare crawler classifications with logs, and verify that Shopping findings map to real product-data changes.
Core features and practical workflow
Prompt monitoring and citations
Scrunch says its monitoring workflow tracks the prompts that matter, surfaces authoritative citations, and follows brand performance over time. A defensible setup should include branded, category, problem, comparison, alternative, evaluation, regional, and risk prompts. Record the exact prompt, model or surface, country, language, date, answer, mention definition, and cited URL.
Citation data is useful for finding pages and domains that shape an answer. It does not prove that a user clicked the source or that the source was accurate.
Insights and action
The Insights area is positioned as an action layer that provides tips to grow AI presence. Treat recommendations as prioritisation hypotheses. Each recommendation should be traceable to a prompt, answer, source, page, or product fact, then reviewed by an editor or technical owner before publication.
Agent Traffic and Site Maps
Scrunch describes Agent Traffic as analysis of AI website traffic by AI model, page view, and bot type. Site Maps are intended to show how AI agents consume a site and what to fix. These are valuable technical signals when the implementation correctly identifies automated clients, but user-agent strings can be spoofed and infrastructure can hide requests.
A request with a successful status code shows that a client received a response under the measured setup. It does not prove retrieval into an answer, a citation, human attention, or a sale.
Shopping
The Shopping area is positioned as product-level AI-search performance. For ecommerce teams, the useful questions are more specific than “is the brand visible?”:
- Is the correct product or variant recommended?
- Are price, ratings, availability, materials, and use cases accurate?
- Which products or competitors are shown instead?
- Does the answer link to a product page or another source?
- Can a finding be tied to a feed, PDP, review, or shipping-data change?
Ask Scrunch to show the raw answer, source links, timestamp, engine, country, language, and product identifier for any reported observation.
Agent Experience Platform
Scrunch markets AXP as a way to deliver an optimised experience to AI agents, including token-light pages and AI content delivery. This is a materially different product category from monitoring. Buyers should verify how content is selected, cached, rendered, governed, and reconciled with canonical pages, accessibility, SEO, legal requirements, and analytics. Faster or smaller agent responses do not guarantee citations.
AI engine and platform coverage
The current pricing page checked September 3, 2026 continues to present four LLMs for the evaluation tier and nine for organizations requiring expanded model coverage, advanced features, API access, and dedicated support. The direct extraction did not expose the tier names, dollar prices, or a complete list of the nine models; retain the earlier Core/Enterprise details only as historical context until the vendor confirms the current package.
This is a plan-level list, not a complete sampling specification. Before purchase, confirm the exact model/version, consumer or API interaction, search mode, country, language, refresh cadence, history, prompt denominator, and whether Shopping coverage is included in the quoted plan.
Pricing and plan limits
The current Scrunch pricing page was checked September 3, 2026. It presents evaluation and expanded-coverage positioning, including four versus nine supported LLMs, but the directly extracted page did not expose reliable dollar prices, plan names, prompt quotas, trial duration, or the full model list. Older public and review pages report $250 or $300 starting prices and different prompt allowances; those figures conflict and should not populate current schema pricing.
| Plan | Price | Published limits and features |
|---|---|---|
| Evaluation tier | Not exposed | Current page says 4 LLMs supported; confirm prompts, audits, workspaces, users, regions, and trial terms |
| Expanded / enterprise tier | Quote-led / not exposed | Current page says 9 LLMs supported and references advanced features, API access, and dedicated support; confirm names and entitlements |
The current page is framed around evaluation and scaling rather than a clearly documented 7-day Core trial. It does not state every trial condition, data-retention term, overage policy, API quota, Shopping quota, or AXP price. Treat those as open commercial questions rather than assumptions.
Strengths
- Combines answer monitoring and citation analysis with crawler and site signals.
- Product-level Shopping positioning is more relevant to ecommerce than brand-only mention tracking.
- Public Core limits and price make the initial commercial scope inspectable.
- Enterprise page names model coverage, API, integrations, SSO, and dedicated support.
- Agency positioning and workspaces can fit multi-client reporting.
- Separating Monitoring, Agent Traffic, Site Maps, and Shopping encourages better evidence hygiene.
Tradeoffs and limitations
- Current commercial transparency is weaker than the August page snapshot: the new pricing page does not expose a reliable dollar starting price in direct extraction.
- Older public snapshots report 125 prompts, but the current page does not expose a reliable prompt allowance; multi-product, regional, and competitor coverage must be confirmed.
- The current page says evaluation covers four listed LLMs; broader coverage is positioned at nine LLMs.
- Enterprise pricing makes total cost, seats, API, retention, and limits harder to compare publicly.
- Independent reviews specifically evaluating Scrunch’s current platform were not located in this research pass.
- AI crawler traffic does not prove citation, referral traffic, or revenue.
- Vendor-selected customer results do not establish causal business impact.
- AXP delivery needs technical, SEO, analytics, legal, and editorial review before production use.
User reviews and market feedback
Evidence snapshot
| Source | Public signal | What it supports | Confidence |
|---|---|---|---|
| Scrunch product page | Current homepage positions Scrunch around Agent Experience, Monitoring & Insights, Content Delivery, and AI-ready experiences; checked September 3, 2026 | Current product positioning and stated workflow | High for vendor claims |
| Scrunch pricing | Current page says 4 LLMs for evaluation and 9 for expanded coverage, with advanced features/API/dedicated support; dollar prices and detailed quotas were not exposed | Current coverage and commercial-transparency boundary | High for displayed terms; incomplete |
| Capterra Scrunch AI | Listing updated August 26, 2026 reports 0 user reviews, free-trial available, no free version, and a $87 per-user-per-month comparison figure that is not clearly Scrunch’s own price | Absence of attributable user feedback and marketplace context | Medium-low; referral marketplace |
| Rankability Scrunch review | 2026 review describes monitoring, Insights, Knowledge Hub, Journey Mapping, and AXP as limited testing; reports $300/month and 350 custom prompts | Practical workflow and earlier commercial context | Medium-low; independent review, but not current pricing authority |
| Profound Scrunch review | Hands-on comparison reports limited prompt-volume data, weekly rather than daily observations, UI/actionability concerns, and $300/month entry pricing | Concrete usability and workflow caveats from a competitor-authored review | Low-medium; direct competitor bias |
Recurring positive themes
A reliable independent consensus was not established. The clearest positive signal is product breadth: Scrunch explicitly joins answer visibility, citations, automated-agent traffic, site maps, and Shopping rather than presenting them as one metric.
Recurring concerns and tradeoffs
- The lack of a substantial independent review sample limits confidence about usability and support.
- Core’s prompt, engine, seat, and geography limits may be restrictive for agencies or international brands.
- Enterprise-only API, expanded model coverage, and SSO make larger deployments quote-dependent.
- The product spans technically different evidence layers, so teams need a clear reporting taxonomy.
How much should buyers trust the evidence?
Trust the official pages for the displayed price, limits, and positioning, while recognising that they describe vendor capabilities. Treat the absence of independent reviews as meaningful uncertainty. Treat customer outcomes on the homepage as vendor-selected evidence. No public evidence found in this pass proves that Scrunch increases citations, traffic, or revenue causally.
AICiteKit interpretation
Scrunch appears most differentiated when a team needs to connect sampled AI answers with first-party crawler and product data. The evidence is currently stronger for the proposed measurement workflow than for independent satisfaction or business outcomes.
What to verify during a trial
- Can the account export complete answers, cited URLs, timestamps, models, countries, and product identifiers?
- Do the four Core surfaces match the team’s real customer journeys and Shopping use cases?
- How are AI crawlers verified, classified, deduplicated, and separated from spoofed user agents?
- Can Agent Traffic be reconciled with raw CDN, hosting, or server logs?
- Are recommendations linked to a specific missing or inaccurate page or product fact?
- What are the limits for history, API, exports, retention, seats, overages, and Shopping observations?
- Does AXP preserve canonical content, analytics, accessibility, caching, and governance requirements?
Review evidence sources
- Scrunch — current product scope and vendor-selected customer evidence; checked September 3, 2026.
- Scrunch pricing — current model-coverage and evaluation positioning; detailed prices and quotas were not exposed in direct extraction; checked September 3, 2026.
- Capterra Scrunch AI — listing updated August 26, 2026; zero attributable user reviews and referral-marketplace disclosures.
- Rankability Scrunch review — independent 2026 workflow and earlier pricing context; not current pricing authority.
- Profound Scrunch review — competitor-authored hands-on review; useful for concrete workflow caveats, lower confidence because of direct competitive bias.
Last reviewed: September 3, 2026
Data confidence: Medium-low. Official product and pricing claims are directly checkable, but independent feedback and third-party validation of current GEO, crawler, Shopping, and AXP outcomes are limited.
Scrunch compared with other AICiteKit tools
| Tool | Best fit | Main tradeoff |
|---|---|---|
| Scrunch | Answer visibility plus crawler, site-map, and product-level Shopping signals | Higher entry price and limited independent evidence |
| PromptWatch | Prompt monitoring connected to crawler and AI-referral analytics | Different plan structure and implementation requirements |
| Alhena AI | Ecommerce SKU-level Shopping visibility and product actions | More limited independent evidence and public coverage detail |
| Peec AI | General AI visibility analytics and competitive monitoring | Less focused on agent delivery and crawler diagnostics |
| Schema App | Structured-data governance and source-layer changes | Schema is not answer-level visibility measurement |
Recommended workflow
- Start with one market, product family, and stable prompt panel.
- Capture answers, citations, product attributes, model, date, and location.
- Compare answer observations with product feeds, PDPs, reviews, and server logs.
- Classify findings as answer, source, crawler, traffic, or commerce evidence.
- Make one bounded content, feed, or technical change.
- Retest the same prompts and compare detectable analytics separately.
FAQ
Does Scrunch guarantee AI citations?
No. Monitoring can observe citations in a defined sample, but no public evidence supports a guarantee of future citations.
Is an AI crawler visit the same as AI visibility?
No. A crawler request is a technical access event. AI visibility requires answer sampling, and citation requires source evidence in that answer.
Is Scrunch suitable for agencies?
Potentially, especially when client reporting needs answer, crawler, and Shopping context. The current page does not expose workspace or seat allowances; verify the economics for the intended client count.
Does the evaluation tier include all models?
No. The current pricing page distinguishes four supported LLMs for evaluation from nine for expanded coverage. It does not expose the complete current model list or every tier entitlement.
Can Scrunch prove AI-attributed revenue?
No. It may help connect observations with analytics, but revenue attribution requires independent analytics and a defined attribution or experiment design.
Sources and verification
- Scrunch — current product areas, workflow, and customer claims; checked September 3, 2026.
- Scrunch pricing — current model-coverage positioning and evaluation language; checked September 3, 2026.
- Google common crawlers and fetchers — context for verifying crawler identity and access behavior.
- OpenAI GPTBot documentation — example of vendor-specific crawler documentation.
- AICiteKit: AI Crawler Analytics — measurement boundary between requests, citations, referrals, and conversions.
Verification date: September 3, 2026
Scrunch
AI search visibility, citations, crawler analytics, and product-level shopping insights