Coding AgentEngineering

Turn SEO fixes and articles into pull requests you review.

Your own Claude prepares a small change to your website code, Kanso checks it and shows you the exact diff, and a pull request is opened only when you confirm. It never merges and never deploys.

Free to start · No credit card required. Pull requests need GitHub connected. See how it works

Works with
  • Your website
  • GitHub logoGitHub
Review proposed change
Ready to review
Repository
acme-inc/website
Base branch
main
Branch to create
kanso/seo-geo/3f9a1c0b7d42-g1-9be41c07-5d2e8a
File
about.html (modified)
Diff
--- a/about.html
+++ b/about.html
@@ -1,6 +1,8 @@
 <!doctype html>
 <html lang="en">
 <head>
+  <link rel="canonical" href="https://acme.example/about">
+  <meta name="description" content="Acme Inc. builds inventory software for small retail shops. Meet the team behind it and how we work.">
   <meta charset="utf-8">
   <title>About Acme</title>
   <link rel="stylesheet" href="/site.css">
Checks KANSO ran
  • Passed: One file only
  • Passed: Matches the recommendation's findings
  • Passed: Modifies an existing file (no create or delete)
  • Passed: Path is safe
  • Passed: A static HTML document

And 9 more, including that the change is small and that no secret is added.

This creates a pull request for human review. It does not merge or deploy the change. Nothing is created until you confirm.

Illustrative example. The company, repository, page and pull request shown are invented, not real data.

The problem

Between an audit and a fix, work gets stuck.

Kanso prepares the change so your team only has to review it.

Findings that sit

Audits list issues, but turning them into code changes takes time.

Finding the right file

Someone has to work out which file produces each page.

Review overhead

Even a small fix needs a ticket, a branch and a pull request.

The Coding Agent does not replace your developers. It prepares small, reviewable changes so their time goes on reviewing them.

The difference

Without Kanso, and with it

Without Kanso
  • An audit lists the issue
  • Someone files a ticket
  • A developer finds the file and edits it
  • Everything is tracked by hand
With Kanso
  • A finding with its evidence
  • A small change prepared by your own Claude, checked by Kanso
  • Your confirmation before a pull request
  • The fix marked done once you merge

How it works

From a finding to a reviewed change.

Prepare the fix
The fix
https://acme.example/about
Meta description missingCanonical link missing
Prepared by your own Claude
about.html
Your Claude read the file in your repository and prepared the change. Kanso checked it and kept it for you to read. Nothing has been sent to GitHub.
Before it can be sent
  • Read the exact change
  • Owner confirms
  • Pull request opens on a new branch
Illustrative example. The company, repository, page and pull request shown are invented, not real data.

Capabilities

What the Coding Agent covers

GitHub App connection

The workspace owner installs the Kanso GitHub App with access to Contents and Pull requests, using GitHub's own sign-in, and picks the single repository the project uses.

Prepared by your own Claude

Your own Claude reads your repository's file list and up to five files at a time, finds where the page really lives, and prepares the change as whole files.

A Web Engineering strategy

One short Web Engineering strategy, written once by Kanso and then kept up to date by your own Claude. You can read it, and rewrite it once a day.

Checked by Kanso

Kanso checks every change: the repository is the one you connected, protected files are refused, the change must match the file as it is now, and its size is bounded.

A diff preview

See the exact lines before you decide. Nothing reaches GitHub until you do.

Owner approval

Only the workspace owner can create a pull request, on a new branch of Kanso's own, with a note that it is a proposal for human review. Kanso then stops.

Articles as pages

An approved article becomes a page in your site's own design: your Claude reads how your site lays out its articles, and the pull request carries the page.

Nothing merged for you

Kanso opens the pull request and stops. Your developer reviews and merges it on GitHub.

Part of Kanso, not a separate tool

The Coding Agent works alongside Kanso's other specialists, using shared business information. See the pricing page for which plans include it.

See pricing →

Questions

Coding Agent questions

Plans and what each one includes are on the pricing page.

  • It turns a fix found by your SEO or GEO lead, or an article you approved, into a pull request your developer can review. Your own Claude reads your repository and prepares the change, Kanso checks it and shows you the exact diff, and a pull request is opened only after you confirm. It is not a general-purpose coding assistant.

Start

Turn the next finding into a reviewable change.

Kanso prepares the change and opens the pull request when you approve it. Your team keeps the review, the merge and the release.

Free to start. See pricing

Explore use cases →