Skip to content
Zevian

SEO · GEO · AEO, fixed in your code

Your SEO,merged.

Zevian audits your site, opens pull requests, and proves the ranking lift. Every change arrives as a pull request you review.

Start free$ how it works
  • Next.js first
  • You review every PR
  • Search Console + Bing
  • Gemini visibility checks
Merged

fix(seo): descriptive title for / #142

app/layout.tsx
 export const metadata: Metadata = {-   title: "Home",+   title: "Acme — Trail running shoes",+   description: "Light, grippy trail shoes. Free returns.",
build passed reviewed by youexample
app.zevian.tech/example.com

Crawl · 14 checks

Scanning
  • <title> is the word “Home”
  • No canonical URL
  • Organization JSON-LD missing
  • GPTBot allowed in robots.txt
  • 3 images without alt text

Proof, not promises

Every fix is a pull request you can read.

No pixel, no injected script, no dashboard you have to take on faith. The work lands in your git history, where your team already reviews code, and it is graded with accounts you already own.

  • GitHubpull requests, both ways
  • Search Consoleclicks · impressions · CTR
  • Bing Webmasterclicks · impressions
  • Geminibrand mentions, 3 repeats

Later:XReddit

$ git log --graph --onelineexample feed
  1. 4f2a9c1fix(seo): descriptive <title> on /app/layout.tsx+2 −1open
  2. b81e03dfix(seo): canonical for /pricingapp/pricing/page.tsx+1 −0merged
  3. 0c7d5e2fix(geo): let GPTBot and ClaudeBot crawlpublic/robots.txt+3 −2merged
  4. e93b7a4feat(aeo): FAQPage JSON-LD on /faqapp/faq/page.tsx+24 −0merged
  5. 71c0f8bfix(seo): meta description for /blogapp/blog/page.tsx+1 −0merged
  6. d45a2e9fix(a11y): alt text on 3 imagescomponents/hero.tsx+3 −3merged

The kind of pull requests Zevian opens. Illustration, not customer data.

The problem

Search fixes that never land in the codebase.

  1. 01

    Overlays that never enter git

    A pixel or an edge script can change what a crawler sees without changing the repository. The people who review code never see the fix. When the subscription ends, the overlay leaves and the site snaps back.

  2. 02

    Volume dressed up as SEO

    Another category publishes pages, posts, and links faster than anyone can read them. Scaled content and automated links are how sites get into trouble with search policies. Zevian does not generate that kind of output.

  3. 03

    Charts with no diff beside them

    A tracker can say an assistant mentioned a brand. A single sample is a weak measurement, and a chart alone does not repair a title, a canonical, or a missing schema block. The useful loop puts a reviewable change next to first-party data.

Zevian keeps the fix in git, next to the data that grades it.

How it works

Connect, audit, open a pull request, then measure.

Four steps. The repository stays the source of truth, and the proof comes from accounts you already own.

  1. Step 01

    Connect

    Add a domain, the GitHub repository behind it, Google Search Console, and Bing Webmaster Tools. Zevian reads the site and the repo. It does not inject a script.

    Your repo

    Solid marks ship in v1. Dashed marks are later. v1 does not post to X or Reddit.

  2. Step 02

    Audit

    A crawler runs deterministic checks: titles, meta, duplicates, Open Graph, canonicals, headings, alt text, broken links, sitemap, robots.txt, JSON-LD, AI crawler access, llms.txt, and structured content. Next.js projects also get metadata checks for the App Router and the Pages Router. Search Console adds a second pass: high impressions with a weak click-through rate, queries sitting in positions 8–20, and URLs that are not indexed.

    • titles & meta fix
    • canonicals fix
    • Open Graph pass
    • JSON-LD fix
    • sitemap.xml pass
    • robots.txt · AI crawlers pass
    • llms.txt pass
    • GSC · positions 8–20 fix

  3. Step 03

    Pull request

    A Gemini-powered coding agent prepares a fix, runs a build, and opens a pull request. The diff carries a rationale and the Search Console evidence next to it. You review it like any other change. Nothing merges unless you merge it.

    seo: describe the homepage#142
    - title: "Home"+ title: "Field notes — technical SEO"+ canonical: "https://example.com"
    1. Agent prepares the change
    2. Build runs
    3. Pull request opens
    4. You review and merge

  4. Step 04

    Measure

    After a merge, Zevian reads clicks, impressions, CTR, and position from Google Search Console and Bing and lines them up with the earlier baseline. Separately, prompts you choose are asked of Gemini each week, three times each, and the mention rate is reported with the method in view.

    ClicksImpressionsCTRPosition

    Example shape. If the numbers do not move, the chart says so.

Features

Fixes in the diff. Proof in Search Console.

Code-level fixes

Pull requests, not a snippet

Titles, meta, JSON-LD, sitemap, robots.txt, llms.txt, canonicals, Open Graph, alt text, and internal links. Each pull request includes the rationale and the Search Console context.

seo: describe the homepage

+4−1Waiting for review
app/layout.tsx
  export const metadata = {
-   title: "Home",
+   title: "Field notes — technical SEO",
+   description: "Search fixes, reviewed in git.",
+   alternates: { canonical: "https://example.com" },
  }
components/organization-schema.tsx
+ { "@type": "Organization", "name": "Field notes" }

The title was the word Home. The page had no description and no canonical. This card uses example.com on purpose. It is not a customer result.

AI visibility

Gemini

Three repeats, method shown

You pick the prompts. Zevian asks Gemini weekly, three times each, and reports the mention rate. It is directional. ChatGPT and Perplexity are later.

  1. Run 1sample
  2. Run 2sample
  3. Run 3sample

Illustration of the method. Not a measured rate.

AI readiness

Crawlers, llms.txt, structure

The audit checks whether AI crawlers are allowed, whether llms.txt is present, and whether FAQ and schema content is in the page. Readiness is not a ranking promise.

Google has said you do not need a special AI text file to appear in AI features.

Impact tracking

Google Search Console and Bing

Clicks, impressions, CTR, and position, compared with the baseline from before the merge. Bing Webmaster sits beside Search Console so the loop is not tied to a single panel.

Before and after a merge

Search Console · illustration
Example Search Console chartAn illustrative chart. Two lines move unevenly, then rise after a marker labeled Merged. The shape is not customer data. Low and high are the only axis words.highlowMergedbeforeafter
Clicks, example Impressions, example

Your charts use your Search Console and Bing data. This drawing has no percentages because none are claimed.

What a PR can touch

Nine kinds of fix

Code-level changes only. No generated pages, no link schemes.

  • Titles and meta
  • JSON-LD
  • Sitemap
  • robots.txt
  • llms.txt
  • Canonicals
  • Open Graph
  • Alt text
  • Internal links

Framework

Next.js first

Metadata checks for the App Router and the Pages Router. Other frameworks are outside the v1 target.

app/layout.tsx
pages/_app.tsx

Why Zevian

Depth and a review, against three kinds of tools.

Categories, not vendors. The last column is the only one that keeps the change in your git history and grades it with data you already own.

Swipe sideways to compare columns.

How Zevian compares with content-spam tools, pixel injectors, and trackers. No vendors are named.
ConcernContent-spam toolsPixel injectorsTrackers onlyZevian
Where the change livesOn pages they generate and publishIn a script, pixel, or edge overlayNowhere. The site is not editedIn a pull request on your repository
After you cancelPublishing stops, or filler pages remainThe overlay turns off and the fixes leaveNothing was in your codebaseMerged commits stay. Revert with git
Who reviews itVolume is the point, so review is rareThere is no pull request to readNot applicableYou do, before anything merges
How impact is shownSeparate from your Search ConsoleA dashboard attached to the overlayMention charts, with no fix to gradeYour Search Console and Bing data, before and after
AI visibilitySometimes added, method often unpublishedSometimes bundled with the overlayThe chart is the productGemini, three weekly repeats, method disclosed
Link schemes and auto-postingPart of the categoryNot the modelNot the modelNot offered

Developers

You still own the merge button.

Built for a business that has developers. The owner watches the Search Console movement. The developer approves the pull request.

  • Review every change

    The GitHub App opens a pull request. You read the diff, the rationale, and the Search Console note, then merge or close. v1 does not auto-merge.

  • Your repository

    The repo is the source of truth. Fixes are ordinary commits in the project you already ship. There is no second copy of the site living on someone else’s edge.

  • No lock-in

    Cancel whenever you want. Merged code stays. There is no runtime snippet to uninstall. git revert removes a fix you no longer want.

MCP soonCLI soon

An MCP server and a CLI are planned so the same checks can run from an editor. They are not in v1.

Open

#142 · seo: describe the homepage

Illustration

zevian opened this pull request

Checks

Running…
  • build· runs before the pull request opens
  • diff· title, canonical, JSON-LD
  • evidence· Search Console context on the URL

Waiting for review. Nothing merges automatically.

Merge is yours
terminalCLI · soon

$ zevian audit example.com

# planned: the same checks from your editor or CI

$

Permissions & data

What Zevian can touch, and what it keeps.

Written to match the code. The Privacy Policy has the legal detail, the list of processors and your rights.

What the GitHub App asks for

You choose which repositories to grant when you install it. Zevian cannot see the others.

Contents
Read and write
Read your files to audit the site and prepare a fix, and write the branch that holds it.
Pull requests
Read and write
Open the pull request. Zevian never merges it.
Metadata
Read
Required by GitHub for every app.
Email addresses (account, optional)
Read
Only to show your email when you sign in with GitHub.

How access tokens work

  • Each token is created for one job, for the one repository it works on, and expires after an hour. Zevian never stores it.
  • A read-only token clones your repository into the sandbox. It goes to a single git process and is not left in the clone URL, the git config, or the environment your build runs in.
  • A separate write token is created only after your build passes, is used once to create the branch, and never enters the sandbox.
  • Zevian checks what GitHub issued. A token that is broader than the one asked for is refused, not used.

Where your code goes

  • Fixes are prepared in an isolated E2B sandbox, a separate virtual machine, not on Zevian's servers. It is destroyed when the run ends and expires on its own after 25 minutes.
  • Your install and build scripts run there. They can reach the internet, because installing your dependencies needs it, but the sandbox holds none of Zevian's secrets and no write access to your repository.
  • Zevian records every edit its agent makes and commits only those edits. If a script in your repository changes any other tracked file, the run fails and no pull request opens.
  • The commit is made by the GitHub App's bot account. Nothing merges unless you merge it.
  • To write a fix, the parts of your files that the agent reads (up to 20,000 characters at a time) and the audit's findings for the page go to Google's Gemini API. Gemini also answers the AI-visibility prompts you choose.

What Zevian stores

  • Your account: name, email and picture from GitHub or Google sign-in. No passwords.
  • Your projects: domain, brand, repository name and branch, and the Search Console and Bing properties you connect.
  • Search Console and Bing numbers for those properties: queries, pages, clicks, impressions, click-through rate and position.
  • Audit results: scores, issues, and for each page the crawler read, its title, meta description, canonical URL, H1 and a text excerpt of up to 400 characters.
  • Pull request records: title, description, evidence, branch, link, and the last 20,000 characters of the build output, which can include file paths and error text from your repository.
  • Connection secrets (Search Console, Bing, Cloudflare, and a Gemini key if you bring your own) are encrypted at rest with AES-256-GCM.
  • API keys, for the Zevian API and the MCP server, are stored only as a SHA-256 hash, with their first few characters so you can tell your keys apart. A key is shown once, when you create it, and cannot be read back.

Not stored: your repository's contents after a run (beyond what the pull request and build output contain), GitHub access tokens, and card numbers, which Dodo Payments handles.

Keeping and deleting it

  • Audit and measurement history stay while the project exists.
  • An owner can delete a domain in the app. Everything stored for it goes, including its connection secrets.
  • Disconnecting Cloudflare deletes its token and removes Zevian's rule. Uninstalling the GitHub App removes the installation record.
  • To delete your account and workspace, write to support. We act within 30 days of a verified request.

Questions, or a deletion request: support@zevian.tech. Full detail in the Privacy Policy; how the crawler behaves is on the ZevianBot page.

Pricing

Free to try the loop. Paid to keep it weekly.

USD and INR are list prices for the same plans. India prices are the rupee amounts, not a converted sticker. Pull requests per month: 1 on Free, 20 on Pro, 80 on Team.

Free

See the audit. Ship one fix.

$0No charge
  • One domain, audited daily
  • 1 pull request per month
  • Technical SEO findings
  • AI-readiness findings
Open the app

Pro

Weekly loop

The weekly fix-and-measure loop.

$39per month
  • Everything in Free
  • Up to 3 domains
  • 20 pull requests per month
  • Optional autopilot opens pull requests for you. You still review and merge each one
  • Weekly Google Search Console and Bing measurement
  • Before and after for each merged fix
  • Gemini mention checks, three repeats per prompt
Open the app

Team

A shared workspace across projects.

$99per month
  • Everything in Pro
  • Up to 10 domains in one workspace
  • 80 pull requests per month
  • Shared review for the people who approve pull requests
  • Email when an audit finishes, a pull request opens, and once a week
Open the app

Quotas are per calendar month (UTC). A pull request counts when Zevian opens it, whether or not it is later merged. Autopilot only opens pull requests on its own schedule, on paid plans. Zevian never merges: every pull request, autopilot or not, waits for you to review and merge it.

Billed monthly through Dodo Payments. Cancel any time. Billing details · Refund policy

FAQ

Straight answers.

Including the parts that are easy to oversell: rankings, llms.txt, and AI mention rates.

Zevian is SEO, GEO, and AEO CI for developers and the businesses they ship for. Connect a domain and its GitHub repository, plus Google Search Console and Bing Webmaster Tools. Zevian audits the site, opens pull requests that fix issues in the codebase, and shows before-and-after impact from your own Search Console and Bing data.

Product updates

Start in the app, or get product updates.

The product is live at app.zevian.tech. If you would rather hear about new features and changes first, leave an email. We use the address only to send Zevian product updates. It is not sold.

Open the app