Detect → Plan → Implement → Validate

An agent that ships SEO fixes to your site while you sleep.

It crawls your site, detects what kind of business it is, plans the highest-impact improvements, opens pull requests against your repo, and only flags what passes Lighthouse. You watch it work in real time.

See how it works Recent runs

✓ No code changes by you✓ Every change is a reviewable PR✓ First run free, no credit card

syntra.dev/runs/run_a7f3c2e1

Suggestions

7 proposed · 2 in flight · 1 implemented

Add FAQ structured data to the top 6 landing pagesstructured_data

HIGH

Impact HIGHRisk LOW

Add JSON-LD Organization schema to layoutstructured_data

DISPATCHING

job_cc_8f2a · editing src/app/[city]/page.tsx

Generate sitemap.xml covering all routessitemap_robots

PR OPEN

PR #284 · +87 −3

Built on tools you already trust

Next.jsVercelGitHubClaude CodeLighthouseMCP

What it does

Five agents. One pull request at a time.

Each run takes about five minutes. You point it at your site and your repo; it does the rest. Nothing ships until Lighthouse on the preview deployment confirms a real improvement.

Crawl

Indexes every page on your live site and captures a baseline Lighthouse score to beat.

→

Research

Analyzes search visibility — the keywords, topics, and (for local businesses) the areas and intents that matter in your market.

→

Plan

Generates ranked suggestions with impact, risk, and the exact files each change would touch.

→

Modify

You approve. Claude Code edits your repo and opens one PR per accepted suggestion.

→

Validate

Waits for Vercel preview, re-runs Lighthouse, and only flags wins that actually improved scores.

Why teams run it

Get found by the people searching for you — without hiring an SEO team.

Adapts to any industry

Syntra detects what kind of business your site is — SaaS, healthcare, e-commerce, local services — and tailors the audit, schema, and content to it. Location-based? It layers in local search intelligence too.

∞industries, one engine

Every change is reviewable

Nothing touches your site without a pull request. You approve in GitHub. Roll back any time. No mystery edits, no scary "AI did something".

100%of changes are PRs

Proven by Lighthouse

Suggestions don't ship on hype. Every accepted change is re-measured on a Vercel preview deploy and only flagged a win if the numbers actually move.

A/Bbefore vs. after on every PR

How a run looks

From "needs work" to "good in every category" — in one run.

An illustrative run: a site audited and improved across four Lighthouse categories in a few minutes of agent time, every change a reviewable pull request. Each run shows the real before/after from your own preview deploy.

Before score

Baseline Lighthouse on your live site

→

Syntra analysis

Crawl, detect the business, plan the highest-impact fixes

→

Optimization PR

Claude Code opens one reviewable pull request

→

Validation

Re-run Lighthouse on the Vercel preview deploy

→

Improved score

Merge only what measurably moved

For developers

Your repo is the source of truth. Always.

Every agent runs against a real workspace, talks to your codebase over MCP, and produces git diffs you can read. No magic, no lock-in, no proprietary representation of your site.

▸
One PR per change Reviewable diffs, never bulk commits.
⊙
MCP everywhere Filesystem, shell, Vercel, GitHub, Lighthouse.
↗
Self-hosted MCP Bring your own server. We talk to it, not the other way.
●
Live SSE traces Every span, every tool call, every LLM token.
⧗
OpenTelemetry-ready Pipe spans to your own observability stack.
⌥
Webhook triggers Run on push, on Vercel deploy, or on schedule.

~ syntra/run.config.ts

// One operator, one site, deeply observable.
import { defineRun } from "@syntra/agent";

export default defineRun({
  site:    "https://your-site.com",
  repo:    "your-org/your-site",
  industry: "auto-detect",
  trigger: { kind: "github_webhook" },

  mcp: {
    url:     "https://mcp.your-org.dev",
    plugins: ["repo", "fs", "shell",
               "lighthouse", "vercel", "github"],
  },

  policy: {
    maxPRsPerRun: 5,
    requirePassingLighthouse: true,
    autoMerge: false,
  },
});

A run, end to end

Five minutes. Four agents. One you-approved PR.

— 01

Point it at your site

Paste your URL, your repo, and a GitHub token. The wizard pre-checks GitHub access, MCP reachability, and your Vercel project. You hit start and walk away.

00:00site: your-site.com

00:00repo: your-org/your-site

00:00industry: auto-detected

00:01✓ pre-flight passed

— 02

Watch agents work, live

SSE-driven flight deck. Every crawl, every tool call, every token. Suggestions appear as they're generated, ranked by impact and risk.

00:13[crawl] 47 pages indexed

00:30[geo] 23 landmarks · 14 intents

00:59[planner] 7 suggestions

04:49[edit] page.tsx

— 03

Approve only what you want

One click accepts a suggestion. Claude Code drafts the PR. Vercel deploys a preview. Lighthouse re-runs. Wins are flagged green; you decide what merges.

01:48PR opened on a feature branch

03:02preview ready

03:21✓ SEO improved on preview

03:21✓ perf improved on preview

FAQ

Questions you'd be smart to ask.

Will it push code to my repo without me approving?+

No. Every change is a pull request on a feature branch. Auto-merge is off by default; you turn it on per repo if and when you want to. Until then, the agent stops at "PR opened" and waits.

What stack does my site need to be on?+

Syntra reads your repo and adapts to whatever framework it finds. It's best-supported on Next.js (App Router or Pages) deployed on Vercel with GitHub as the remote — that's where preview deploys and Lighthouse validation are fully wired end to end. Other stacks work for the audit and pull requests; the validation step depends on your preview setup.

How does it handle local / location-based SEO?+

Only when it matters. Syntra detects whether your business is location-based; if it is, the research agent maps the areas you serve, nearby landmarks, and local search intents into keyword clusters and local landing-page suggestions. Online or global businesses skip this step entirely — no invented geography.

What happens if a suggestion regresses Lighthouse?+

The validation agent re-runs Lighthouse on the Vercel preview deploy and compares it to baseline. Regressions are flagged in red on the run page. The PR stays open but isn't marked "validated" — you can close it without merging.

Is my data going through your servers?+

The orchestrator is hosted; the MCP server (which actually touches your files) can be self-hosted on your own infra. The only thing crossing our boundary is the planning prompt and the agent traces — never your source code.

Who is this not for?+

Sites with no code repository to open pull requests against — some closed website builders and hosted platforms. The audit and plan still run, but the auto-implement step needs a repo it can push a branch to. If you can give Syntra a GitHub repo, it can ship.

Run it on your site. See what changes.

First run is free. No card required. About five minutes from "paste URL" to a Lighthouse-validated pull request waiting in GitHub.

Analyze my site →How it works