Giving Zelrin access to fix your website
Only needed if you asked us to implement the fixes. Scanning, diagnosing and proving results need no access at all — we read your site the way your customers and Google do. Forward this page to whoever runs your website.
What we change — and what we don't
- Content and presentation: titles, descriptions, page copy, colours and font sizes, button size and placement, price visibility, form length, trust blocks, heading order, alt text, broken links, schema, sitemap, tracking tags via your GTM
- Never: redesigns, new pages, plugin or theme installs, hosting, DNS, databases, checkout logic, or your orders and customer data
- Never anything you didn't approve on a finding card — approval is the only trigger
Fixes that genuinely need a developer (server speed, framework rendering, plugin conflicts) come to you as a paste-ready fix pack instead — and the next scan still verifies the result. Full scope →
The rules we hold ourselves to
- We ask for the lowest role that can edit content — never an owner or admin account
- We change only what you approved on a finding card — nothing else, ever
- Every change is logged, and the next scan shows before / after proof
- You remove our access from your own dashboard in one click, any time
- We never ask for your hosting, domain, bank or email passwords
- We never ask you to paste a script that "lets us edit the page" — that would hide the fix from Google, so it isn't a fix
WordPressEditor role
- In your WordPress admin, go to Users → Add New
- Email: fixes@zelrin.com
- Role: Editor (not Administrator — Editor is enough for pages, text, titles and images)
- Tick "Send the new user an email" and add
Editor cannot install plugins, change themes or touch settings. WordPress keeps a revision of every edit, so any change we make can be rolled back by you from the page's own revision history.
ShopifyStaff / collaborator
- Settings → Users and permissions → Add staff (or "Collaborators" if we're working through an agency account)
- Email: fixes@zelrin.com
- Permissions: tick Products, Online Store → Themes and Pages/Blog posts. Leave Orders, Customers and Finances unticked — we never need them
Customer and order data stay invisible to us by design.
WixWebsite Manager
- Wix dashboard → Settings → Roles & Permissions → Invite
- Email: fixes@zelrin.com
- Role: Website Manager (edits the site; cannot transfer or delete it, no billing access)
SquarespaceWebsite Editor
- Settings → Permissions → Invite Contributor
- Email: fixes@zelrin.com
- Permission: Website Editor (content only — no billing, no domain settings)
WebflowEditor / Content access
- Project Settings → Members → Invite
- Email: fixes@zelrin.com
- Access: Editor for content and SEO fields. If a fix needs Designer access, we'll say so on the card and you can grant it for that job only
Google Tag ManagerPublish rights — for tracking fixes
- GTM → Admin → User Management → +
- Email: fixes@zelrin.com
- Container permissions: Publish
This is the one case where a code snippet is involved — but it's your GTM container snippet on your site, which you own and control. We publish tags inside it; you can pause or eject us instantly, and every GTM version is revertible.
Custom-coded site / your own developerNo access needed
- Don't give us anything. Open the finding card and use Copy fix pack
- It contains the page URL, the exact defect, the corrected text or CSS, and what to expect after
- Send it to your developer. Next week's scan checks the page again and marks it fixed — or tells you it isn't
This route works on every platform, including ones not listed here. It's slower, but you keep every key.