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.
Is this for you?
If you already work on client sites over SSH, yes.
You reach for a terminal, PowerShell, or Claude Code to dig into a client's site — on WordPress or a static host, over SSH. The AlmaSEO SSH Workspace is that exact workflow, with the client's context and history already attached.
- SSH
- Terminal
- Command window
- PowerShell
- Claude Code
- WordPress
- Static sites
- Server access
Why not just keep doing it by hand?
The same work — without rebuilding the situation every time.
You can already do most of this across a stack of separate tools. AlmaSEO's difference is that it keeps all of it in one place, attached to the right site.
Doing it by handInside AlmaSEO
PowerShell, a terminal, or a command windowA calm, readable workspace with a persistent client record
Claude Code or another coding agentThe same kind of agent, plus the site's business, search, and agency context
SSH credentials and hosting toolsSaved connections, controlled access, and team continuity
Search Console, Analytics, Bing, and crawlersA direct bridge from a search signal to the technical investigation
Slack, email, tickets, and private notesOne durable history of decisions, commands, changes, and outcomes
Rebuilding the client report each monthReport-ready evidence of what was actually investigated and done
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.
Updates SEO metadata on approval
With your approval, the agent can rewrite title tags and meta descriptions on live pages — turning a diagnosis into a shipped on-page fix without leaving the session.
Drafts content from a gap
Spot a missing or thin page and have the agent draft a new article to fill it, using the same content engine as the rest of AlmaSEO.
Publishes to static sites, not just WordPress
Finished an AlmaSEO article for a Hugo, Jekyll, Next.js, or plain-HTML site? Send it to the workspace and the agent reads the site's structure, drops the file in the right place, updates the sitemap, commits, and deploys — no export-and-manual-upload.
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.
Queries your search data live
Mid-session, the agent can pull current Search Console, Analytics, content, and link-profile data itself — so its reasoning stays grounded in the site's real numbers, not just its files.
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.
In the agent's own words
"With my client's SEO data, what can you actually do?"
A real answer from a live session — every capability tied to the client's own Search Console and Analytics data, and every one something the workspace can do in the same conversation.
With full access to my client's SEO data in AlmaSEO, what can you do to help them — and what tools let you do it?
Here's the complete answer — what I can do, and what powers it:
📊 1. Analyze their current performance
Tools: GA4 + Google Search Console
- Pull real traffic — sessions, users, engagement, bounce rate
- See which pages get traffic and which are invisible
- Identify the keywords they already rank for, and exactly where they sit
- Spot traffic drops and tie them to a specific date and cause
🔎 2. Find exactly what's missing
Tools: GSC + content gaps + WordPress file access
- Keywords they get impressions for but have no page targeting
- Every service + location combination that should have a page but doesn't
- Thin content, missing metadata, and duplicate titles
✍️ 3. Create the missing pages — right now
Tool: AlmaSEO Content Engine
- Write and queue service pages, location pages, FAQs, and posts
- Targeted to specific keywords pulled from real GSC/GA4 data — not generic
- Examples for a property-management client:
- "Property Management Detroit MI"
- "Single Family Property Management Ferndale"
- "Multifamily Property Management Oakland County"
- "How Much Does Property Management Cost in Michigan?"
🏷️ 4. Optimize metadata on live pages — instantly
Tool: WP-CLI via SSH + AIOSEO
- Rewrite title tags and meta descriptions on the live site
- Target the exact keywords GSC shows people searching for
- Fix duplicate titles causing keyword cannibalization
- No logging into WordPress — I do it from right here
📈 5. Push "almost ranking" keywords to page 1
Tools: GSC + WP-CLI + Content Engine
- Find every keyword sitting at positions 8–20 — the low-hanging fruit
- Diagnose what's holding each one back, and fix the metadata on the spot
- Add supporting content to boost authority — the highest-ROI work in SEO
…and more in the same session: technical WordPress fixes, malware and security scans, and a full local-SEO build-out.
💡 The bottom line: I don't just tell you what's wrong — I fix it, build it, and optimize it in the same conversation. Every action is driven by your client's real data, not guesswork.
Every capability above is live in the workspace today.
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.
Questions
Frequently asked questions
What is the AlmaSEO SSH Workspace?
It's AI-assisted SSH access to your website's server, built into AlmaSEO. You connect to a client's site, ask what's wrong in plain language, and the agent runs approved commands, explains what it finds, and saves the whole session to the site's history — with the client's SEO data and context already in the room.
Do I need to know the command line to use it?
No. You describe what you're chasing in plain language and the agent decides which commands to run. The exact commands and raw output are always one click away if you want them, but you never have to type a command yourself.
What can it connect to?
WordPress and static sites over SSH, using a saved connection with the hostname, port, username, and password or key. It detects the environment — WordPress on Linux, static hosts, and more — and adjusts how it works to match.
Which AI powers the workspace?
Claude — the AI assistant many people already know — running on your own API key, which is validated before the session starts. You bring the key; AlmaSEO brings the workspace, the context, and the memory.
Why can't I just use Claude Code and PowerShell?
You can — and if you already do, you understand the value. AlmaSEO keeps the client context, search data, commands, decisions, session history, and proof together instead of making you reassemble them from six tools every time. The workflow is the same; the setup and the memory are what change.
Isn't this just a browser terminal?
No. The terminal is only the access layer. AlmaSEO organizes the agent's work into readable activity, findings, approvals, history, and client-specific records — while keeping the exact commands and raw output available for when you want them.
Is it safe to connect my server to AlmaSEO?
Yes — safe access is the foundation this feature is built on, not an afterthought. Because AlmaSEO connects directly to your server to diagnose issues from the inside, we designed it so that nothing can change or damage your site without your explicit approval.
Here's how it works. AlmaSEO reads and investigates freely, but the moment it wants to run anything that could modify a file, alter your database, or send data off your server, it stops and asks you first. You see exactly what it wants to run and why, and it doesn't proceed until you click approve. You're always the final decision-maker — the AI can recommend, but it can't act on anything sensitive on its own.
We also assume the internet is a hostile place, and we built accordingly. Your login credentials are encrypted, and your server's identity is verified on every connection, so AlmaSEO won't be fooled into connecting to an impostor. If we ever read something sensitive like your site's configuration file, the AI can use it to help you, but it's automatically hidden from our activity logs rather than stored in plain text. And because AI assistants can be manipulated by malicious content, AlmaSEO is specifically instructed to treat anything it finds on a server as untrusted — it will never follow hidden instructions buried in a file or a log.
Finally, every one of these protections was independently stress-tested by separate review passes whose only job was to try to break them, and each command AlmaSEO runs is permanently logged so you have a complete, reviewable record of everything that happened.
Does it change my site on its own?
No. The workspace always shows whether it's reading, proposing, or changing, and anything that alters the site waits for your approval first. Bigger jobs come back as a multi-command investigation plan you approve before it runs.
What happens to a session after I close it?
It's saved to the client's site history — the conversation, commands, findings, and decisions — with a structured summary. You can reopen it, turn findings into tasks, export it to your Activity Log, or generate a developer, client, or Claude Code handoff from it.
Can I use it across multiple client sites?
Yes. Each site has its own saved connections, sessions, and memory, and credentials and context never leak between clients — so a portfolio of sites stays organized and isolated.
Will this replace my developer?
No. It speeds up investigation, produces clearer evidence, prepares the work, and handles supported actions — but human technical judgment still matters. It makes your best technical work faster to do and easier to hand off, not a person you remove from the process.
Does this only do SEO?
It's SEO-focused, not SEO-restricted. You can investigate recognizable website and server problems — slow sites, errors, redirects, suspicious files — while AlmaSEO contributes the search and client context a blank terminal doesn't have.
I only manage one site — is it worth it?
For occasional, one-off work, a local session may be all you need. AlmaSEO earns its place when continuity, connected SEO data, repeated investigations, or client reporting matter — and the value compounds the more sites and history you build up.
What's new
The workspace ships forward.
New capabilities land as focused releases — each one a new job you can do from the same workspace.
-
Release 2 · July 2026
Prepare the work
Turn a finished session into a ready-to-send handoff — developer instructions and an implementation checklist, a Claude Code prompt to run the fix, or a plain-English explanation for the client. Plus your own session notes and one-click finding-to-task.
-
Release 1 · July 2026
Connect, investigate, remember
The core workspace: AI-assisted SSH sessions on Claude with command-safety approvals, connected AlmaSEO context, six quick-start templates, structured findings, session summaries, saved site history, WordPress detection, and export to Activity Logs.
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.