Ask Clerion questions about your site

Press ⌘K anywhere in the dashboard and type a question in your own words. The answer is written from your own data, with the figures pulled from your account rather than typed by the model. Below are the questions people ask most, grouped by the moment they ask them in, and the answers as Clerion writes them.

Ask Clerion answering a question about the site's traffic

The answers here are from Vesper, the sample store on every account, so they are real product output without being anyone’s private numbers. Yours will be about your site.

Weekly check-in

The questions to ask at the start of the week.

Clerion's live signals on a Monday morning: what moved, and how much of it matters.

What changed since last week?⌘K

Three moves. Sessions 2,140, up 18%, mostly from /collections/summer. Mobile bounce 61%, up 9 points, all of it on /products/linen-shirt-dress. Checkout completions flat at 41. Start with the linen page: it is where the new traffic is leaving.

Where did visitors leave last week?⌘K

/products/linen-shirt-dress lost 312 sessions after landing, more than the next three pages together. Then /cart, 96, and /about, 44. The linen page loads in 4.1 seconds on mobile. That is the leak.

Are we on pace for the month?⌘K

At day 18 you are at 3,860 sessions, projected 6,400 by the 30th. Last month closed at 5,900. Your goal is 7,000. On this pace you land 8% short, unless the summer collection keeps last week’s rate.

Before a campaign

Check the numbers before you spend on ads or email.

The answer to the ads question, written from the regions and landing pages in your own account.

Plan Facebook ads for my weakest regions.⌘K

Weakest region is France, 462 sessions, against 1,382 in the US and 1,043 in the UK. Best landing pages for France by conversion: /collections/summer at 4.2%, then /products/linen-shirt-dress. Watch French checkout completions against your goal of 60 a month.

Which landing page converts best from paid?⌘K

Paid sessions only: /collections/summer converts at 3.8% on 1,140 sessions. The homepage converts at 1.2% on 2,300. The homepage is getting most of your spend and doing the least with it.

Did the newsletter drive any signups?⌘K

Yes. 318 sessions, 27 signups, an 8.5% rate. The last send did 290 sessions and 19 signups. Both times the subject line with a product name in it did better.

When a number looks wrong

Spikes, drops and broken pages.

Clerion checks the date you named, tells you it was the low, and points at the day that actually spiked.

What happened on July 12? Why the spike?⌘K

July 12 was not the spike. It was 53 sessions and 121 pageviews, your lowest day of the period. The spike was July 18: 129 sessions, 376 pageviews, more than double the daily average, after a link from a Shopify community post.

Why did mobile bounce go up?⌘K

Mobile bounce went from 52% to 61%, and almost all of it is one page: /products/linen-shirt-dress, 78% on mobile against 44% on desktop. Its hero image is 2.4 MB. Desktop did not move.

Is checkout broken?⌘K

Partly. “Failed to fetch” on /checkout hit 12 sessions this week, all on Safari 17, all after the shipping step. Nine of the twelve did not complete. The last action in every one was choosing express shipping.

SEO and content

Which fixes matter, and the writing done for you.

The SEO answer comes back as a list you can work through, biggest page first.

Which SEO fixes are worth my weekend?⌘K

Start with /products/linen-shirt-dress: 150 views, no meta description, no OG description. Then /collections/summer, on page two for two terms its title tag does not use. Fixing both touches 40% of your organic traffic.

Which pages get traffic from ChatGPT?⌘K

AI assistants sent 84 sessions this month, up from 31. /about took 39 of them, /products/linen-shirt-dress 22. ChatGPT is quoting the sizing guide on your about page. Nobody else has a page like it.

Write meta descriptions for my top five pages.⌘K

/collections/summer: “Linen dresses, shirts and shorts made in Portugal. Free shipping over $80.” Then four more, each under 155 characters, written from the page’s own copy. Paste them straight in.

For your developer or client

Bug tickets and monthly reports, written for you.

The bug answer names the error, the browser, the cost in sessions, and the likely cause.

Which bug should my developer fix first?⌘K

“Failed to fetch” on /checkout: 12 sessions, 9 lost. A shipping-rates request is timing out. On a Shopify and Next.js setup that is usually a fetch with no timeout. Fix it before the cart quantity bug, which touched 3 sessions.

Write the ticket for that error.⌘K

Title: Checkout shipping-rates fetch fails on Safari 17. Impact: 12 sessions, 9 abandoned, this week. Steps: add a product, go to checkout, choose express shipping. Likely cause: unhandled timeout on the rates request. 12 breadcrumbs attached.

Summarise this month for my client.⌘K

Traffic grew 18% to 6,400 sessions, mostly from the summer collection. Signups held at 210. One thing slipped: the linen shirt dress page loses mobile visitors. Fix its image weight next, then the checkout error.