On this page
A bug report written from a replay should be short and specific: one sentence on what broke and where, the steps to repeat it, what should happen against what did, the device, and where to find the visit. Star the visit first, repeat the visitor's steps on your live site, then send the report to whoever fixes it; on Wix, that's you in the editor, the app's developer, Wix Customer Care or whoever wrote any custom code.
"The site is broken" is hard to act on. "On phones, Add to Cart does nothing on the linen napkins page after choosing a size. See the 2:14 PM visit on October 3, at 1:42" is something you, a developer or a support agent can start on right away. A session replay gives you what you need to write the second kind of report.
Key takeaways
- Star the replay as soon as you spot a bug, and write down the visit's start time from the list and the moment in the replay.
- Repeat the visitor's steps from the Activity list on a phone and a computer before you write anything.
- On Wix, decide who fixes it first: you in the editor, the app's developer, or Wix Customer Care.
- Keep each report to one bug: what broke and where, the steps, what should happen, what happened, the device and where to find the visit.
Is it a bug or a design problem?
It's a bug if something doesn't work the way it was built to, like a button that does nothing. A confusing label or a hidden shipping policy is a design problem, and it needs a different fix, like the ones in the checkout friction checklist. If you're not sure, report it anyway and say so.
These are signs of a bug in a replay.
- Repeated clicks. A Click row with a ×N count, and no change on the page when you watch that moment.
- An error. An error message, or a page that loads only partly.
- A broken layout. Text running off the screen, or buttons on top of each other.
- A sudden exit. A visit that ends right after an action that should have worked.
Find the right visit
If a customer reports the problem, ask when it happened, on what device, which page they were on and what they were trying to do. Then look through the visits from around that time. The replay list groups visits by day and shows each one's start time and length. It marks each visit Mobile or Desktop (tablets count as Mobile) and has a Device filter, but guests aren't identified (the list names each one Visitor plus a short code; only members signed in to your site show by name), so narrow by time and device, then open the likely visits. Phone visits play back in the phone's shape.
If their visit isn't there, they may not have allowed analytics cookies. Why some visits aren't recorded covers that and the other common reasons.
If the problem may be happening right now, watch visits live to catch it as it happens.
Reproduce it yourself
Use the Activity list beside the replay as your script. It lists the visit in order, starting with a Page view row for the page the visitor landed on, then each Click and Typing (masked) row. Watch between the rows to see which pages they moved through. Click a row to jump to it and see exactly what the visitor did.
Then try the same steps on the live site, not in the editor.
- Use the device the visitor used, then the other one. Layout bugs often live on just one.
- Start on the page where the visitor started, if it seems to matter.
- Repeat each action in the same order.
- If it works for you, try another browser, or your phone on a cellular connection.
Write down each step as you go. Those notes become the steps in your report. If you can't make it happen, say so. The replay is still evidence, and some bugs depend on things that are hard to recreate, like an old browser, a browser extension or a weak connection.
Who fixes a bug on a Wix site?
It depends on where the bug lives: click and layout problems are yours to fix in the editor, a widget from an app another company made goes to that app's developer, Wix's own features go to Wix Customer Care, and custom code goes back to whoever wrote it. Working out which one before you write saves a round trip.
| What you see | Who fixes it | First check |
|---|---|---|
| A button or link that can't be clicked, or elements overlapping on phones | You, in the editor | Something covering it, or a frozen footer |
| A widget from an app another company made, such as reviews or a pop-up | The app's developer | The app's support link in the Wix App Market |
| A Wix feature failing, such as the cart, checkout, Wix Forms or Wix Bookings, or an error page from Wix | Wix Customer Care | Whether it happens on every device |
| Custom code you or a developer added | Whoever wrote the code | Whether it broke after a recent change |
You, in the editor. Wix's help center says an element that can't be clicked on the live site is most likely covered by another element or a page section, sometimes a transparent part of one. Right-click it in the Wix Editor, choose Arrange, then Bring to Front. If it's near the bottom of the page, click the footer, click the Settings icon and check Freeze Footer: turn it off or make the footer shorter. For overlaps that only happen on phones, Wix suggests splitting long text into one text box per paragraph. The guide to rage clicks on Wix has the other usual causes.
The app's developer. Wix Customer Care can only help with apps made by Wix. For any other app, open its listing in the Wix App Market, scroll to the section that says who made it and use the support link there. Your installed apps are listed under Manage Apps in your site's dashboard. Send the developer your written steps, the device and the browser.
Wix Customer Care. For Wix's own features, use the Start a Chat button on Wix's Customer Care help page. Wix suggests having your site's URL ready, along with error messages, screenshots and the steps you've already tried, which is exactly what your report holds.
Find the moments worth watching
Jump to any moment from the Activity list, skip the quiet parts, watch at up to 8x and star the replays worth keeping.

What should a bug report include?
Enough for someone else to find the visit and repeat the problem: where to find the visit, the moment in the replay, the page, the device, the steps before the problem, what should happen, what happened, and whether it happens for you too.
| Detail | Why it matters | Example |
|---|---|---|
| Where to find the visit | Lets anyone with access open the same replay | Starred, October 3, started 2:14 PM |
| Moment in the replay | Skips straight to the problem | 1:42 |
| Page | Shows where it happened | The linen napkins product page |
| Device | Layout bugs can depend on screen size | Phone |
| Steps before the problem | Lets someone repeat it | Chose Large, tapped Add to Cart |
| What should happen | Defines the fix | The cart count goes up |
| What happened | Defines the bug | Nothing changed |
| Your own attempt | Shows whether it repeats | Happens on my phone. Works on my laptop. |
Write the report
Keep each report to one bug, and keep it short. Lead with one sentence that says what broke and where. Then give the steps, what you expected, what happened and where to find the visit.
Urgent. On phones, tapping Add to Cart on the linen napkins page does nothing after choosing a size. To repeat it, open the page on a phone, choose Large and tap Add to Cart. The cart count should go up. Nothing changes. In the replay, at 1:42, the visitor taps three more times, then leaves. I can repeat it on my phone, and it works on my laptop. Replay: starred, the October 3 visit that started at 2:14 PM.
The example leaves out guesses at the cause and anything personal from the visit. Whoever fixes it gets the facts and works out the cause.
Say how urgent it is
A one-word label at the top helps whoever fixes it decide what to do first.
- Urgent. It stops people from buying, booking or contacting you.
- Soon. A feature is broken, but visitors have a way around it.
- Later. Something looks wrong but still works, like a misaligned image or a typo.
Share it with the right people
Replays stay inside your site's dashboard and never get a public link. Share on a replay writes an email with a link to it, or copies the link, and only people with access to your site's dashboard can open it, so a teammate who should watch the visit needs access to your site. You add people under Roles & Permissions in your dashboard, with Invite Collaborators, and choose a role that can use your dashboard and its apps. Once they've accepted, they open Session Recordings, go to the Starred tab in Replays, find the visit by its date and start time and jump to the moment you wrote down.
For people outside your site, like an app's developer or Wix Customer Care, send the written report and, if it helps, a screenshot of the moment with anything personal cropped out. A replay is a record of a real person's visit, so handle it the way the guide to keeping recordings private suggests, and give each bug one owner so it doesn't bounce between people.
Rule out a broken link
Some "bugs" are bad links. If a visit starts on a page that no longer exists, the visitor likely followed an old or mistyped link from an email, a text, an ad or another site. Check the links in your recent campaigns first, and click every link in your next email or text before it goes out. Building campaign links with a UTM builder for email and text links keeps them consistent and easier to trace in your analytics.
Close the loop
Ask whoever fixes it to tell you when the fix is live. Then open a few visits recorded after the fix, including phone visits if the bug showed up on phones, and confirm that visitors who reach that page get through. Write the result on the original report. If the bug comes back, reopen that report and add the date and start time of the new visit, so the whole history stays in one place. Unstar the old replay once the fix holds, so your Starred list stays short.
Frequently asked questions
Is there a simple bug report template?
Yes. Start with one sentence on what broke and where. Then list the steps to repeat it, what should happen, what happened instead, the device, and where to find the visit: its date, its start time and the moment in the replay. Put an urgency label at the top, keep one bug per report, and leave out guesses about the cause and anything personal you saw.
Who do I contact when a Wix app isn't working?
The app's developer, unless Wix made the app: Wix Customer Care can only help with apps made by Wix. For an app made by another company, open its listing in the Wix App Market, scroll to the section that names who developed it and use the support link, which leads to the developer's email, website or phone number. Include the page, the device, the browser and the steps that make it happen.
Why are some bugs hard to reproduce?
Often because they depend on conditions you don't have, such as a certain phone or browser, a browser extension, a weak connection or a particular path through the site. Repeat the visitor's steps in the order the replay shows, on the device they used, and try a cellular connection. If you still can't make it happen, say so in the report and include where to find the visit.
Should a bug report include screenshots?
Yes, when the problem is visual, like overlapping buttons or text running off the screen, and especially for people who can't open your dashboard, such as an app's developer. For anything that happens over several steps, list the steps and note where to find the visit, so a teammate with access can watch what led up to the problem. Crop anything personal out of a screenshot before you share it.
Try it on your site
Session Recordings keeps an Activity list beside every replay, so the clicks and typing behind your report's steps are already listed in order. See how replays work on Wix sites.



