For developers and agencies

How a fix is written

SiteRemora edits Liquid the way you would, one file at a time:

1. It reads the current file from the theme you're viewing.
2. It finds the snippet the fix replaces. If the snippet is missing, or appears more than once, it stops.
3. It checks the change keeps the Liquid tags balanced. Then it writes the file back with only that snippet changed.
4. It records the fix: the file, the theme, and the code before and after.

A revert runs the same steps in reverse, against the same theme. Creating, duplicating and deleting themes stays with you.

Find the source of an issue

Every issue is traced to where it comes from. Open one and expand Advanced to see:

• the theme file and line, with the section and template when known,
• the element's selector and a sample of its rendered HTML,
• up to 12 pages it appears on.

Markup injected by another app shows up with the page it's on. Fix it in that app's settings, or with its developer.

Try fixes on a draft first

Duplicate the live theme, scan the copy, and apply fixes there before you publish. Each theme keeps its own results and fixes. See Scan and fix a draft theme.

Hand your client a record

• The Fixes page lists every change with its before and after.
• The change report sums up a month of work: dates, files, and who applied each fix. It prints, or saves as a PDF.
• Export Record downloads every scan and fix as a spreadsheet.

See Change report and record export.

Several client stores

Install SiteRemora on each store. Each has its own plan, results and history. On Shopify development stores, paid plans are billed as test charges.

Agencies can give clients a partner code that lowers the plan price. Write to hello@siteremora.com about the partner program.