Skip to content
Help centre
Scans and audits

Let zrdio fix your code on GitHub

Connect your site's repository and turn audit findings into a ready-to-review pull request, in one click.

Updated 4 hours ago

If the site you audit lives in a GitHub repository, zrdio can go one step further than telling you what is wrong: it can fix it in your code and hand you the result as a pull request. You review the diff on GitHub and click merge. Nothing touches your live site until you do.

What it will and will not fix

zrdio only applies fixes that are deterministic — changes where a wrong result is impossible. Today that covers:

  • Missing page language, so screen readers pronounce your content correctly
  • Missing or zoom-blocking viewport tags
  • Missing meta descriptions and canonical links
  • Incomplete social sharing (Open Graph) tags
  • target="_blank" links without rel="noopener"
  • Images below the fold without lazy loading
  • Insecure http:// links on secure pages

Findings that need human judgment — alt text for images, thin content, vague page titles — are never guessed. The pull request lists them under "Still needs a human" so you know exactly what is left.

Setting it up

  1. On GitHub, open Settings → Developer settings → Fine-grained personal access tokens and create a token scoped to *just your site's repository*, with Contents and Pull requests both set to read and write.
  2. In zrdio, open your project's Settings tab and find the GitHub repository card. Paste the repository name (or its URL) and the token.
  3. zrdio checks the token against the repository before storing anything, so a typo fails immediately with a clear message. The token is stored encrypted and never shown again; you can revoke it on GitHub at any time.

Using it

Run a scan, then open the Action plan. When findings are auto-fixable and a repository is connected, a card tells you how many can be fixed right now. One click:

  1. zrdio reads your repository's HTML files.
  2. It applies every safe fix, as a single commit on a new branch named zrdio/fixes-<date>.
  3. It opens a pull request against your default branch, describing every change file by file.

It never pushes to the branch that deploys your site. Merging is always your call.

Good to know

  • Works best on static HTML sites. If your site is built by a framework, the change usually belongs in a template, so those files are left alone.
  • The fixes are idempotent: running it twice does not duplicate anything.
  • After you merge, re-run the scan to watch the score move.

Related