---
name: sitetooling-conversion-friction
description: Find where website visitors get stuck before signing up or buying, using Sitetooling events, heatmaps and session replays. Use when the user asks why people don't sign up, buy, book or get in touch, says "conversion", "people leave the pricing page", "where do visitors get stuck", or wants replays reviewed. Needs the Sitetooling MCP server connected (Pro plan).
---

# Conversion friction review

Find where visitors stall on the way to the goal, with evidence from events, clicks and replays.

## Steps

1. Ask which page or goal matters if the user didn't say (e.g. /pricing, the sign-up button, checkout).
2. Call `get_custom_events` for the last 30 days to see how often the goal event happens (sign_up, purchase, form_submit…) and on which pages.
3. Call `get_heatmap` for the key page: what desktop and mobile visitors click, and what they ignore.
4. Call `list_session_replays` for the same page, with `min_seconds: 20` to skip bounces. Pick the 3 most relevant (long visits that didn't convert).
5. Call `analyze_session` on each of those 3, no more. Before analysing more than 3, tell the user how many more calls it would take and ask.

## What to write

- First line: the site, the page or goal, and the dates.
- **The funnel in numbers**: visits to the page, goal events, and the rate.
- **Where they stall**, ranked by evidence:
  - clicks on things that aren't links or buttons (they expected them to be);
  - rage clicks, or repeated clicks on the same element;
  - long idle gaps, or scrolling up and down without acting;
  - mobile-only problems (desktop and mobile clicks differ a lot).
- **What each replay showed**, one short paragraph per session: path, the friction point, and the likely intent.
- **Fixes to try**: 2–3 specific changes, most likely to help first.

## Rules

- Describe behaviour, never people. Don't quote anything typed; replays only name the fields used.
- Count every `analyze_session` call you make and keep to 3 unless the user agrees to more.
- If a tool needs the Pro plan, say what Pro adds and stop.