GhostClick · Guide

Understanding Reports

Read a journey report or a page report, see what passed as well as what failed, and share it.

Two Shapes of Report

A journey report is a story: what the agent did, step by step, and where it got stuck. A page report is an inspection: what's on one page, what's wrong with it, and what to change first. They answer different questions, so they look different. Both are covered below.

One thing is true of every report: it shows what passed as well as what failed. A list of only problems tells you nothing about how much of your site was actually looked at, so each section says what was checked and how much of it was fine, with the failures expanded and the rest there when you want it.

The Journey Report

When a journey audit completes, you get a report showing what happened at every step of the simulated journey: an overall pass/fail status, an AI-written assessment, detected issues, and a full screenshot replay.

Summary Card

At the top of the report you'll see:

  • A large PASS or FAIL status badge, per device
  • Your journey goal as the title
  • Stat pills showing device mode, step count, duration, date, and URL
  • Issue count pills — e.g. "1 critical", "2 warnings"
  • An AI-written assessment of what happened and why
Report Header
PASSFAIL

Each device mode (desktop/mobile) gets its own pass/fail result, based on goal verification — whether the completion signal for your journey actually appeared, not just whether the agent stopped moving.

Issue Severity Levels

Every issue GhostClick finds is categorised into one of three severity levels:

CRITICAL

Blocks the journey. The customer cannot proceed — e.g. a broken checkout button, a form that won't submit, a 404 in the flow.

WARNING

Significantly degrades the experience. The customer might still complete the journey, but with friction — e.g. confusing navigation, hidden CTAs, slow-loading images.

INFO

Minor observations. Not blocking, but worth addressing — e.g. missing alt text, inconsistent spacing, small text on mobile.

Steps & Issues Tabs

The report body has two tabs:

  • Steps — an expandable timeline of every action the AI took. Open a step to see the screenshot, the AI's reasoning, what it observed, and the page URL. Steps flagged as obstacles (cookie banners, newsletter popups, and similar interruptions the agent had to click through) are marked separately from the happy path.
  • Issues — issue cards with severity badges, descriptions, screenshots, and metadata (device, step number, issue type).

Issue Types

  • Blocked — something completely prevents progress (broken link, error page, disabled button)
  • Constraint violated — the AI noticed a violation of a constraint you set (e.g. "don't create an account", but a signup wall appeared)
  • UX problem — poor experience that hurts conversion (confusing layout, unclear CTAs, aggressive popups)
  • Performance — slow loading, large images, render-blocking resources

The Page Report

A page audit reports on one URL rather than a path through the site, so it's organised as tabs. You only get the tabs that report actually has — a page audit run without the AI review has no AI review tab.

Summary

The headline scores, the top fixes, and the annotated screenshot.

First impression

The first screen scored out of 100, judged on what a visitor sees before scrolling.

CRO & usability

All 48 checks by category, each with the verdict, the evidence and the fix.

AI review

The open-ended read of the page, when you asked for one.

Findings

Everything flagged, gathered in one list by severity.

Links

Every link checked, with what each one returned.

Images

Missing, oversized, and images without alt text.

SEO

Title, description, headings and social preview tags.

Forms

Fields, labels, and whether the form is set up to submit.

The Annotated Screenshot

If the audit included a review, the report carries a screenshot of the whole page with the findings drawn on it as numbered pins, sitting where the problem actually is. Click one and a card opens beside it with the evidence and the suggested fix, plus a way to jump straight to that check in the checklist. Open large blows the screenshot up when a pin sits on something small.

It's the quickest way in: scan the picture, click what looks wrong, read the fix.

Tip

Don't skip past the passes. "38 of 41 links are fine" is the context that tells you three broken links is a small job — and a section reporting that nothing was checked is telling you something too.

The Friction Report

From a completed journey audit, click Friction report to open a focused, presentation-style view of every friction point found during the run — built for sharing with people who don't need the full technical replay.

Sharing is the same control on every report, with three settings: private, anyone with the link, or public. See Sharing a report for what each one means and when to use it.

Info

Reports are private until you say otherwise, and setting one back to private takes any link you handed out offline immediately. A shared report never exposes your account, your billing, or any of your other audits.

Re-Running and Saving

From the report page you can:

  • Re-run — test the same journey again to see if a fix worked
  • Save as journey — save the audit configuration as a reusable, monitorable journey (or jump to View journey if it's already saved)
  • Delete — permanently remove the audit and its data