How the platform fits together

Agencies and clients

An agency is the top-level container: branding, team, billing, API keys and templates live there. A client is one business you do work for, with its own website, locations, integrations, content and reports. Clients are linked to an agency, and team members are assigned to the clients they are allowed to see.

This two-level structure is deliberate. Everything that should be shared across a book of business, your logo, your report template, your API keys, lives on the agency. Everything that is specific to one business, its keywords, its audit findings, its published articles, lives on the client. You never have to worry about one client's data leaking into another's report, because the data model does not allow it.

The client workspace

Almost all day-to-day work happens inside a client workspace, grouped into four areas:

Data, then action

Most features follow the same shape. Something collects data (a crawl, a rank check, a grid search, a backlink pull), the platform turns it into a prioritised recommendation or a draft, you approve it, and then it gets deployed or reported. Anything that can run on a schedule usually does, audits, rank refreshes, grid searches, answer-engine checks, Search Console syncs and daily summaries all have recurring jobs behind them.

That "collect → recommend → approve → deploy" loop is worth memorising because it explains most of the interface. If a page feels unfamiliar, ask which of the four stages it belongs to and the layout usually makes sense: a data table, a queue of suggestions, an approve/reject control, and a deploy or publish action.

Where AI is used

• Writing: blog articles, geo articles, press releases, Business Profile posts, outreach emails, page copy.
• Rewriting: task-level fixes for titles, meta descriptions, headings and body content.
• Analysis: audit insights, backlink summaries, content-gap and SERP-opportunity analysis, call scoring.
• Research: topical maps, keyword clusters, visibility prompts, competitor discovery.

How the pieces connect in practice

Consider a single keyword moving through the platform: it starts as a suggestion inside a Keywords.ai topical map, gets sent into Rankings for tracking, informs a blog brief once its cluster is chosen for content, and finally shows up as a line in the client report once the article is live and the position has moved. No single feature does all of that, the workspace structure is what lets them share one client's context end to end.