SEO + GEO audit engine — free in your terminal
Orino audits the signals that decide whether Google ranks you and whether AI engines cite you — then writes the fix and opens the pull request. Rules, not a language model: the same site gets the same score, every run.
$npx orino-cli auditSEO SCORE
DRAG IT · CLICK TO RE-SCORE
Search happens in two places now. Google ranks your pages and AI engines quote them. Orino audits both surfaces with one deterministic command.
Rule-based checks that read your source and your live HTML. No crawl quotas, no black-box scores — and the free CLI never asks you to log in.
Orino reads your codebase and your live URL, runs every check in parallel and hands back a weighted score, with the file, the finding and the fix for anything that fails.
$ npx orino-cli audit
Detected Next.js (App Router) · 54 checks queued
The CLI runs locally. The only network request is to the URL you choose to audit.
Rules, not a language model. Scores never drift between runs, so they belong in CI.
Point it at the repo — Orino works out the framework and applies the checks that fit.
robots · sitemaps · canonicals
Can engines reach every page you care about? Robots rules, XML sitemaps, canonical tags, redirect chains and status codes.
Can engines reach every page you care about? Robots rules, XML sitemaps, canonical tags, redirect chains and status codes.
Titles and descriptions on every route, Open Graph and Twitter cards, with length and uniqueness rules applied per page.
JSON-LD presence and validity — Organization, Article, FAQ and breadcrumbs, matched against what each page type needs.
LCP, CLS and INP, render-blocking assets and image weight — the speed signals that gate rankings.
Heading order, alt text, internal linking and content depth — including the H1 a crawler actually receives.
GPTBot, ClaudeBot and PerplexityBot access, llms.txt, and whether your content survives without JavaScript.
Framework config, route structure and client-only rendering traps that hide finished pages from every crawler.
Connect your GitHub repo. Orino writes the fix, opens a pull request, and you review it like any other teammate’s contribution.
Step 01 / 04
Point it at a codebase, a live URL, or both. Orino resolves your framework and reads routes, metadata exports and build output the way a crawler never could.
reading source…
Step 02 / 04
See exactly what's broken and why. Every finding links to the fix guide. Select what you want fixed.
Step 03 / 04
Orino writes the actual code. Not a suggestion, the real diff, following the correct pattern for your framework.
export const metadata = {
- title: "Home",
+ title: "Meridian — Architecture studio in Oslo",
+ description: "Practice, projects and contact.",
}
Step 04 / 04
A pull request opens on a new branch. Nothing touches main until you approve it.
Orino SEO fixes (3 issues) #42
3 commits · orino-fixes bot · orino/seo-fixes → main
Free to start · no credit card
Orino rescans on a schedule you choose and emails you the moment something breaks.
Daily, weekly, or monthly. Orino checks your site automatically so you don't have to remember to.
If your score drops below a threshold you set, you get an email before it becomes a problem.
Generate a public link to any scan. Send it to a client, drop it in a PR, no login required to view.
The CLI is free forever. The dashboard adds fixes, monitoring, and reporting on top.
Free
Try it out
Pro
For solo developers and freelancers
Agency
For teams managing client sites
All plans include the free CLI · billing is monthly · cancel anytime
No AI guesswork. Just the SEO and GEO issues that decide whether you rank — and whether AI engines quote you.
$npx orino-cli auditQuestions about Orino, partnership ideas, or just want to say hello? Drop us a line. No ticket queue, no chatbot.
support@bynaree.dev