Forge your codebase into a search-ranking machine.

RankForge crawls your live site, finds every technical SEO and performance issue, and opens small, reviewable pull requests that fix them. Connect your repo and let it do the busywork.

Works with the frameworks your team already ships

Next.jsNuxtAstroSvelteKitRemixMDX
fix(seo): add canonical URLs to features pagesOpen
rankforge/seo-canonical-features→ main+21-2
app/features/layout.tsx
  import type { Metadata } from "next";+ export const metadata: Metadata = {+   alternates: { canonical: "https://acme.com/features" },+ };  export default function FeaturesLayout() {
Canonical renders once per page
Query variants resolve to canonical
No change to page content
Generated byRankForgeMerge when ready

From code chaos to SEO clarity

Scroll, and watch a messy repo resolve into clean, indexable structure — every warning turned into a check, every fix backed by a diff.

Before — raw repo

  • <title> missing
  • alt="" on 37 images
  • canonical absent
  • sitemap: 12 / 142 urls
  • h1 × 3 on homepage
  • schema.org: none
54
SEO score

After — RankForge PRs merged

  • <title> unique per page
  • alt text generated
  • canonical valid
  • sitemap: 142 / 142 urls
  • single h1 enforced
  • schema.org: valid

Finding problems was never the hard part.

Crawlers surface hundreds of warnings. RankForge's technical SEO agent connects symptoms, causes, and impact so your team knows what to fix first.

Surface real SEO issues

01

Detect missing metadata, indexation problems, broken internal links, schema gaps, and performance regressions without drowning in raw crawl noise.

<title>canonicalLCPschema

Connect cause and context

02

Group related findings by template, page type, crawl path, and technical pattern instead of treating every URL as an isolated problem.

by templateby page typecrawl path

Prioritize by impact

03

Rank fixes by search impact, implementation effort, affected URLs, and risk, so the next action is obvious.

impacteffortURLsrisk

From install to merged PR, in five steps

01

Install the GitHub App

Read-only by default. You pick the repos RankForge is allowed to see.

02

Add a production URL

Point it at staging or production. It crawls the rendered output, not just your source.

03

Run an audit

Each issue is scored by impact, effort and risk, then sorted so the high-value fixes rise to the top.

04

Review the diffs

Every issue links to the files it touches and a ready patch you can read.

05

Merge the PRs

RankForge opens the pull requests. You stay in control of every merge.

From crawl finding to mergeable diff.

The agent does more than report an issue. It traces the cause, locates the right template or content source, and prepares a reviewable change.

01

Crawl finding

Missing or duplicated metadata detected across product category pages.

duplicate <meta description> ×128
<title> not unique
/category/* templates
02

Source mapping

Finds the template, CMS field, or component responsible for the repeated pattern.

/category/shoes
/category/bags
+126 URLs
CategoryTemplate.tsx
seo/meta.ts
03

Safe diff

Generates a minimal change your team can inspect, edit, and merge.

seo/fix-category-metadata
// CategoryTemplate.tsx
-<title>{page.name}</title>
+<title>{page.name} | {category.name} | Brand</title>
// seo/meta.ts
-description: page.name
+description: categoryDescription(category)

From scattered findings to a clean pull request.

Related SEO issues are grouped into focused changes, validated against risk, and packaged for review instead of dumped into a ticket backlog.

1Collect findings
2Group related issues
3Validate changes
4Assemble PR
5Ready for review

Category metadata

duplicate meta ×128
missing description
title not unique

Canonical rules

canonical drift
redirect chain
trailing slash

Structured data

schema missing
ItemList invalid
Pull requestReady for review
Branch
seo/fix-category-metadata
Files changed
CategoryTemplate.tsxseo/meta.tsschema/product-list.ts
Affected pages
128 category URLs
Checks
Canonical rules preserved
Titles unique per page
Noindex pages excluded
Schema validated

Adds metadata fallbacks for category pages with missing descriptions and normalizes canonical generation.

Group related fixes

Combine repeated issues by template, page type, or source instead of creating one task per URL.

Validate before review

Check indexation rules, canonical behavior, title uniqueness, structured data, and affected URL scope.

Open a focused PR

Produce a small, reviewable pull request with context, changed files, and SEO impact.

Connect GitHub

Free first audit. No credit card.

Technical SEO, without the spreadsheet

Technical SEO automation for the metadata, sitemap and schema work that usually sits untouched at the bottom of a backlog.

GitHub-native fixes

Issues become branch-scoped pull requests, never direct commits to main.

Framework-aware metadata

Knows generateMetadata, useSeoMeta, Astro frontmatter and more.

Sitemap & robots automation

Generates dynamic sitemaps and repairs stale robots directives.

Schema generation

Organization, Article, Product, FAQ, BreadcrumbList and SoftwareApplication.

Internal linking insights

Finds orphan pages, weak anchors and click-depth problems.

Safe PR workflow

Small, reversible diffs with risk scoring and validation steps.

Performance SEO signals

Surfaces render-blocking resources and Core Web Vitals regressions.

Agency-ready dashboard

Manage many repos and sites from one multi-tenant workspace.

It reads your framework's conventions

RankForge knows where metadata lives and how routes are generated in each stack, so its Next.js, Nuxt and Astro SEO fixes look like code you'd have written yourself.

Next.jsDeep support
NuxtSupported
AstroSupported
SvelteKitSupported
RemixSupported
Vite + ReactSupported
MDXContent-aware
StaticSupported
Model Context Protocol

Or bring RankForge into your editor

Connect the RankForge agent to your AI coding assistant. It runs the full technical-SEO audit against your dev server, then fixes the issues in the repository you already have open — measured by RankForge, applied by your assistant.

  • Audits localhost — no deploy, no waiting. See issues as you build.
  • Fixes in place — your assistant edits the real files and you review the diff.
  • Deterministic measurements — the audit is real, not the model guessing.
Set it upWorks with Claude Code · Cursor · VS Code · Windsurf
~/my-app — claude code
$ claude mcp add --transport http rankforge http://localhost:3000/api/mcp
✓ Added MCP server rankforge (5 tools)
› Use rankforge to audit http://localhost:3000 and fix what you can.
audit_site → 12 issues · indexing 76 · perf 96
+ app/robots.ts, + app/sitemap.ts
~ app/layout.tsx (viewport, lang, canonical)
audit_site → re-check: indexing 94 ▲
Fixed 6 issues across 3 files. Opening a pull request for review.

Audits tell you what's wrong. RankForge ships the fix.

CapabilityClassic SEO toolsRankForge
Finds technical issues
Maps each issue to code
Opens pull requests
Framework-aware
Safe review workflow
Compares source vs rendered HTML
Marketing reports & dashboards

Built to be safe with write access

Read-only by default. When you grant write access, RankForge is boxed into its own branches and never touches main or your secrets.

Minimal permissions

Read-only by default. Write access is scoped to RankForge branches only.

Branch-only changes

Never a direct commit or merge to main. Every change arrives as a PR.

Review before shipping

You inspect every diff. Nothing merges without a human.

No access to secrets

RankForge reads your source and rendered HTML. It never reads your environment secrets.

Logs & audit trail

Every action is recorded. Disable the agent at any time.

Enterprise & self-host

Advanced controls and self-hosting available for larger teams.

Plans that scale from solo to agency

Start free. Upgrade when RankForge is opening more pull requests than you can merge.

Starter

For indie hackers and solo devs.

€29/mo
Start free audit
  • 1 repository
  • Rendered-site crawl up to 200 pages
  • All SEO categories
  • Suggest-only & draft PRs
  • Plain-English explanation of every fix
Most popular

Growth

For startups shipping fast.

€99/mo
Start free audit
  • Up to 5 repositories
  • Crawl up to 2,000 pages
  • Auto-create low-risk PRs
  • Priority queue & scoring
  • Slack & email notifications
  • Audit history & trends

Agency

For agencies managing many sites.

€299/mo
Start free audit
  • Up to 25 repositories
  • Multi-tenant client workspaces
  • Monorepo support
  • Per-client reporting
  • Role-based access
  • Bulk scheduling & exports

Enterprise

For teams that need SSO, self-hosting and an audit trail.

Custom
Talk to us
  • Unlimited repositories
  • Self-hosted option
  • SSO / SAML
  • Advanced audit trail
  • Custom SEO rules
  • Custom integrations

Prices are placeholders for this MVP. No credit card required to run your first audit.

Questions you're probably about to ask

Does RankForge replace SEO experts?

No. It removes the manual, mechanical part. Experts still set strategy and review the PRs; RankForge just turns those decisions into code in minutes instead of sprints.

Which frameworks are supported?

Next.js, Nuxt, Astro, SvelteKit, Remix, Vite + React, MDX and static sites. Next.js, Nuxt, Astro and MDX have the deepest framework-aware fixes today.

Can it modify my main branch?

Never directly. RankForge only ever pushes to its own branches and opens pull requests. Nothing reaches main without a human merge.

Does it need write access?

It is read-only by default. Write access is optional and scoped to RankForge's own branches. It can't touch protected branches or your secrets.

Can I review every change?

Yes. Every fix is a small, reviewable diff that comes with an explanation, the expected impact, and steps to validate it. You stay in control of every merge.

What kinds of SEO issues does RankForge fix?

Metadata (titles, descriptions, OpenGraph), indexing (canonicals, sitemaps, robots), page structure, image alt text, structured data and schema, internal linking, performance signals, and framework-specific fixes like generateMetadata usage.

How is RankForge different from Screaming Frog or Ahrefs?

Crawlers and audit suites report issues. RankForge maps each issue to the source file in your repository and opens the pull request that fixes it, so the finding and the fix arrive together.

Does it work with GitLab or Bitbucket?

GitHub only today, via the RankForge GitHub App. Repositories on other hosts can still be crawled and audited, but PR creation requires GitHub.

Will this improve my Google rankings?

No tool can honestly promise rankings, and RankForge doesn't. It fixes the technical layer so your pages can be crawled, rendered, and indexed correctly, which is the part of SEO a repository controls.

Does it support agencies?

The Agency plan adds multi-tenant client workspaces, per-client reporting and role-based access so you can manage many sites from one dashboard.

Does it work with monorepos?

Yes. You can point RankForge at the app within a monorepo, and it scopes its file mapping and PRs to the right package.

What happens if a fix is risky?

Every issue carries a risk score. Low-risk fixes arrive as ready-to-review PRs; higher-risk ones are opened as draft PRs or kept as suggestions. Either way, nothing merges without your approval.

Can I try RankForge without an account?

Yes. The free audit at /audit crawls 3 pages of any public URL and shows every measured issue with evidence, no signup. For unlimited audits (including localhost) use the open-source CLI: npx rankforge-cli audit <url>.

Can I use RankForge from my editor?

Yes. RankForge ships as an MCP server: connect it to Claude Code, Cursor, VS Code or any MCP-capable assistant and your coding agent can run the full deterministic audit against localhost or production, pull fix templates, and patch the repository it already has open. See the guide at /docs/agent.

From broken tags to reviewable diffs

Connect your GitHub repo and let RankForge open the first pull request. Each one is small enough to read in a minute. Merge it when you're ready.