How do I install the XeoRank CLI?

Run npm install -g @xyleapp/cli, then xyle login, which opens your browser to sign in with Google, grants XeoRank access to that account's Search Console properties and saves your credentials locally. A personal key from your settings in the AGENT_API_KEY environment variable works for URL checks such as crawl, analyze and rewrite, but sites and the search-console commands need xyle login.

Why is the command called xyle and not xeorank?

XeoRank was called Xyle before the rebrand. The npm package @xyleapp/cli and the command xyle kept the old name. It is the same product, the same API and the same account.

Can the CLI edit my website?

No. The CLI reads data and returns suggestions, such as a rewritten title, but it does not change your site. Editing WordPress, Elementor, Framer or code sites goes through the XeoRank MCP server, and WordPress writes are off for each site until you enable them.

Does the CLI work with Claude Code, Cursor and other coding agents?

Yes. xyle seed writes XeoRank instructions into the file your coding tool reads, for example CLAUDE.md for Claude Code, .cursorrules for Cursor or AGENTS.md for Codex. The agent can then call the CLI itself, and most commands return JSON with --json.

Is the CLI included in my plan?

Yes. The CLI uses the XeoRank API, which comes with every plan, starting with Starter at $19 a month for one site with a 14-day free trial and no card to start.

SEO CLI for Search Console, Crawls and Page Checks

XeoRank's SEO CLI is the npm package @xyleapp/cli, and it lets you pull Search Console queries, run site crawls, check content gaps and get title or meta rewrites from your terminal. The command is xyle, a name kept from XeoRank's previous brand, and it talks to the same account and API as the dashboard.

It suits two kinds of user: people who prefer a terminal to a dashboard, and coding agents such as Claude Code, Cursor or Codex that can run commands while they edit your site's code.

Who it is for

Developers who build and ship their own site and want SEO data next to the code.
Teams using a coding agent that should check a page's title, headings or content gaps while it works.
Anyone scripting SEO checks in a shell script or a CI job.

Install and first command

The docs walk through this exact sequence:

npm install -g @xyleapp/cli
xyle login
xyle queries --site your-domain.com --limit 5

xyle login opens your browser to sign in with Google, grants XeoRank access to that account's Search Console properties and stores your credentials locally. xyle login is required for sites and the search-console commands; a personal API key from your XeoRank settings in AGENT_API_KEY works on its own for URL checks such as crawl, analyze and rewrite. Search Console needs to be connected for the site before queries returns data. Add --json to most commands to get machine-readable output for scripts and agents.

Commands

These are the commands in the current CLI. Run xyle <command> --help for every option.

Account

Command	What it does
`xyle login`	Signs in with Google and saves credentials locally
`xyle logout`	Removes stored credentials
`xyle whoami`	Shows the signed-in email, API key prefix and API URL
`xyle status`	Checks that the API is reachable
`xyle sites`	Lists the sites connected to your account

Search Console

Command	What it does
`xyle queries --site <domain>`	Top search queries with impressions, clicks, CTR and position
`xyle sync --site <url>`	Pulls fresh Search Console data for a site
`xyle search-console overview --site <domain>`	Performance totals, top queries and pages, coverage, sitemaps and indexing issues
`xyle search-console sync --site <domain>`	Syncs queries, pages, coverage and sitemaps
`xyle search-console sitemaps --site <domain>`	Submitted sitemaps with status and indexed counts
`xyle search-console issues --site <domain>`	URLs with indexing issues, filterable by verdict

Pages and competitors

Command	What it does
`xyle crawl --url <url>`	Crawls one URL: title, meta description, word count, headings, AEO and GEO signals
`xyle geo --url <url>`	GEO signals and score for a URL
`xyle competitors --query "<query>"`	Competitor pages ranking for a query
`xyle gaps --page <url>`	Content gaps for a page: missing topics, CTR issues, position buckets
`xyle analyze --url <url> --text "<page text>"`	Scores page text against competitors, with missing topics and AEO recommendations
`xyle rewrite --url <url> --type title`	Suggests a rewrite for a title, meta description, heading or section

Site crawls

Command	What it does
`xyle site-crawl start <url>`	Starts a full-site crawl, with optional JavaScript rendering
`xyle site-crawl status`, `pages`, `issues`, `list`	Checks a crawl, lists crawled pages or issues, or lists recent crawls

History and guidance

Command	What it does
`xyle history`	Snapshot history for a URL or a site
`xyle trends`	Score trends over time for a URL or a site
`xyle diff --before <id> --after <id>`	Compares two snapshots
`xyle ask --question "<text>"`	Asks XeoRank's SEO, AEO and GEO knowledge base, with sources

Agent setup

Command	What it does
`xyle seed --tool <name>`	Writes XeoRank instructions into your coding tool's config file

xyle seed supports Claude Code (CLAUDE.md), Cursor (.cursorrules), GitHub Copilot (.github/copilot-instructions.md), Windsurf, Cline, Codex (AGENTS.md), Aider and Augment. The file it writes lists the core commands with their syntax and a few ready-made workflows, such as a full SEO, AEO and GEO audit and a page optimization pass. If the file already exists, XeoRank adds its block or updates the block it added before, and leaves the rest of the file alone.

A coding-agent workflow

Once seeded, you can ask your coding agent something like:

"Use the xyle CLI to find the top queries for our /pricing page, check its content gaps, then suggest a new title and meta description. Edit the page component with the version I approve."

The agent runs xyle queries, xyle gaps and xyle rewrite, shows you the suggestions, and edits the file in your repository once you pick one. The CLI supplies the data; the agent edits the code you own. The seeded file sits in your project folder, so if you commit it, teammates who use the same coding tool get the same instructions.

CLI, MCP server or API?

All three reach the same account. The MCP server is the better fit when you work in Claude, ChatGPT or Cursor chat, since it exposes more than 200 tools and needs no install. The REST API suits your own code. The CLI sits between them: scriptable, JSON-friendly, and easy for a coding agent to call.

What the CLI does not do

It does not edit your website. Rewrites are suggestions; changing a WordPress, Elementor, Framer or code site goes through the MCP server, and WordPress writes are off for each site until you enable them.
It does not cover the whole platform. AI visibility checks, keyword research and clustering, rank tracking, content briefs and backlinks are not CLI commands; use the MCP server or the dashboard.
It does not add sites to your account. xyle login grants XeoRank access to the Search Console properties of the Google account you sign in with, but the site itself must already be in your XeoRank account.
It does not run on its own. Each command runs when you, a script or your coding agent calls it.

Pricing

The CLI uses the XeoRank API, which comes with every plan. Starter is $19 a month for one site, with a 14-day free trial and no card to start. Pro is $49 a month and Growth is $109 a month. See pricing for details.

SEO CLI: Search Console data, crawls and page checks from your terminal