Natural-language agent
Tell it "why is this site slow?" or "did the last deploy break the canonicals?" The AI agent plans the checks and calls the right commands itself.
SSH Workspace
AI-assisted SSH access to your websites.
Connect to a client's server from inside AlmaSEO, ask what's wrong in plain language, run approved commands with intelligent analysis, and save every finding to the site's permanent history.
PowerShell gives you a terminal. Claude Code gives you an intelligent terminal assistant. The AlmaSEO SSH Workspace gives you an intelligent workspace that knows the website, organizes the session, and connects the result to your SEO and client data.
Connects over: SSH to WordPress and static sites — credentials encrypted at rest.
Connect once
Save a connection, open the workspace.
Point AlmaSEO at a site's server — hostname, port, username, password or key — and pick the environment. Credentials are encrypted at rest, so you test the connection once and open the workspace whenever the site needs work.
- Password or key-based authentication on a saved, restricted account
- Environment-aware from the start — WordPress on Linux, static hosts, and more
- Test the connection before you open the session — no surprises
- Edit a saved connection's details whenever the server changes
What the workspace does
Everything you'd expect from an AI-assisted SSH session — and the context a terminal never has.
One workspace to investigate, fix, and document website work over SSH, with the client's SEO data and history behind every session.
Run a real session
Ask in plain language. It runs the commands.
You describe what you're chasing. The agent decides what to inspect, runs approved commands, and explains what it finds — with the raw terminal one click away.
Runs on Claude, with your key
The agent is powered by Claude — the AI assistant you already know — using your own API key, validated before the session starts.
Quick-start templates
Open a session straight into a common job — Why is my site slow? · Check error logs · Post-deployment SEO check — from six clickable cards, no typing required.
Clean session activity
Readable steps like "reviewing PHP errors" or "checking active plugins," each with the exact command, raw output, and timestamp expandable underneath.
Command safety & approval
The workspace always shows whether it is reading, proposing, or changing. Anything that alters the site waits for your approval first.
Multi-command investigation plans
For bigger jobs it proposes a batch of commands as one investigation plan. You approve the plan, and it runs them in sequence — no command-by-command babysitting.
It already knows the site
Not a blank terminal — a workspace with context.
The session opens inside the client and carries what AlmaSEO already knows about the site, so the agent reasons with real context instead of starting from zero.
AlmaSEO context injection
Search Console top queries, recent articles, and site infrastructure data are fed into the agent, so it knows the site's real SEO shape — not just its file system.
Opens inside the client
You enter the workspace from a client's site record, so their priorities, hours, and history are already in the room.
WordPress environment detection
It detects the WordPress install, checks the WP-CLI version and install path, and adjusts how it works to match the environment.
Reads across your stack
The same connected data behind your audits, content, and reporting is available to the session — one source of truth, not a second silo.
Nothing gets lost
Every session becomes memory the site keeps.
The work doesn't evaporate when you close the window. Findings, decisions, and outcomes stay attached to the right website and flow straight into your records.
Structured session summary
When you end a session, the agent writes a clean recap — what was checked, what it found, what changed, what remains, and the recommended next steps.
Findings panel
Every finding from the session collects in one place — problem, evidence, affected pages, and recommended action — separated from the raw command stream.
Turn a finding into a task
Convert any finding into a tracked task in one click, so the fix doesn't get lost between spotting it and getting it done.
Add your own notes
Annotate a session with your own notes, so the context you know but the terminal doesn't stays attached to the site.
Saved to the client's history
The whole session — conversation, commands, findings, and decisions — is attached to the site, auto-named from your first message, ready to reopen later.
Straight into Activity Logs
Export a session into the activity and reporting system it already feeds, so the work counts toward the client record without re-entering anything.
Session to client report
Turn a finished session into a formatted, client-ready report of what was done and why it mattered.
Hand off the work
Generate a ready-to-send handoff from the session — developer instructions and an implementation checklist, a Claude Code prompt to run the fix, or a plain-English explanation for the client.
Resume where you left off
Reconnect to a dropped session and pick up the thread — the history comes back with it.
Safe on a client's server
Built to be trusted with a live site.
Fast doesn't mean careless. The workspace reduces scope before it skips a control, and nothing meaningful happens without you.
Credentials encrypted at rest
Connection details are stored encrypted. You save a connection once and open the workspace from it — no re-entering credentials every session.
Restricted, non-root accounts
Built around limited, key- or password-based accounts on supported environments rather than open root shells.
Session isolation
Credentials, context, and output stay inside the client they belong to. Nothing leaks between the sites you manage.
Full transparency
Exact commands, output, and timestamps are stored for review, so a technical user can inspect everything instead of trusting a black box.
What people open it for
The jobs you reach for a terminal to do.
WordPress slowdown
Find what's dragging the site down.
Disk use, debug logs, PHP errors, database size, cache state, active plugins, and recent changes.
Critical WordPress error
Read the log, name the cause.
Identify the failing component, explain the likely cause, and prepare a safe next step.
Indexing or canonical problem
Compare live HTML to what should ship.
Sitemap status, robots directives, canonicals, connected search data, and recent changes side by side.
Redirect or migration issue
Untangle chains, loops, and dead ends.
Redirect behavior and broken destinations, with the affected high-value pages flagged.
Suspicious or injected code
Surface the evidence, honestly.
Indicators, unexpected recent changes, obfuscated code, or altered core files — shown, never waved off.
Post-deployment SEO check
Catch what the deploy changed.
Changes against search-critical templates, metadata, canonicals, schema, and indexability.
Open a workspace
Connect a website and start a session.
Point AlmaSEO at a WordPress or static site, ask it what's wrong in plain language, and keep every command, finding, and decision attached to the client.
Already using Claude Code, PowerShell, or a terminal over SSH? This is that — cleaner, persistent, and built for SEO and multi-site client work.