Fixes you can tap: what Rabbot puts back and never touches

What a tap can put back

A finding can carry a fix when the thing that changed is one Rabbot watched change, and one it can put back exactly. There are five: an SEO title, an SEO description, a search visibility (noindex) setting, a product’s web address when the old one shows Page not found, and a redirect that grew a hop or sends visitors in a circle.

The first three are field restores: the card says “The SEO title changed on 6 October. Rabbot can put back the value it had before.” The last two are redirect fixes, and Check my redirects walks through each card. Everything below applies to both kinds.

One-tap fixes are available on the Starter plan and above. On Free the finding still opens and still names the earlier value, and the card says which plan the tap needs.

The two taps

The first tap opens a confirmation. It shows the field, the date it changed, the value the product has now and the value Rabbot will write. The sentence above the buttons is the same every time: “Put this value back? It replaces what the product has now.”

The second tap, “Yes, put it back”, writes it. “Leave it” closes the confirmation and writes nothing. Nothing is written on the first tap, and nothing is written without the second.

If the field changed more than once between two Rabbot checks, the card lists each earlier value with the date it stopped being true, and you choose the one you want back.

Rabbot does not know who changed a field

Shopify records no event for a field edit, so Rabbot cannot tell whether a person, an app or a theme made the change. No card says who did, and no card guesses. You say which value is yours.

If the same field changes again after Rabbot put it back, the card says so: “Something keeps changing this field: check your apps and theme.” Rabbot offers no second tap on that finding for 30 days, so a fix and an app do not take turns overwriting each other.

Undo for 30 days, with one exception

After a fix, the card reads “Rabbot put the value back on 6 October. You can undo this until 5 November.” The Undo button on that card reverses the write. After 30 days the undo closes and the stored values are cleared, so Rabbot has nothing left to restore.

The exception is a redirect chain pointed straight at its end. Shopify does not let a redirect point at an address that is itself redirected, so the old step cannot be put back. The card says so before you tap, and shoppers go straight to the page the chain already ended on.

Write access is asked when you tap

Installing Rabbot grants three read permissions and nothing else. The first time you tap a fix, Shopify shows its own permission prompt for the write access that fix needs. You can decline it. The finding then stays open, with nothing else changed, and the card says: “This finding stays open until you give Rabbot permission.”

Rabbot never writes on its own. Every write is one you confirmed on a finding, and every one of them is on the card with its date.

What Rabbot never writes

• Price, inventory or availability.
• Your theme, its files or its settings.
• A product’s web address, except to put the old one back as part of a redirect fix.
• A redirect you made. Rabbot never removes or reverses one. The taps fix a redirect’s consequences: a dead address, a chain, a loop.
• Anything from an agent. Over the MCP server, an agent can preview a fix and undo one Rabbot made. It can never apply one: that takes your two taps in the Rabbot app.

The install grant and the write-on-tap fact are both on the trust page, where you can check them against the Shopify install screen.