What Serena can do
Use Serena to interpret client evidence, plan work, and run supported Rankability workflows while preserving permissions, costs, and human approval.
Use Serena to interpret client evidence, plan work, and run supported Rankability workflows while preserving permissions, costs, and human approval.
Serena is Rankability’s AI assistant. Serena works within the selected client and can use the client context, approved sources, connected data, and supported Rankability tools available to your account.
Before you start
Select the correct client. Add reliable source material and connect any service required for the task. Then state a concrete objective, relevant page or keyword, audience, location, and date range.
What Serena can help with
Explain and analyze — Answer questions about a client, interpret available performance data, review screenshots, and work from approved sources.
Plan and prioritize — Turn supported signals into suggested work and explain why it matters.
Prepare work — Help draft or organize supported research, content, audit, promotion, and tracking work.
Start supported actions — Use Rankability tools when the required access, confirmation, and credits are available.
Prepare reviewable website changes — Inspect a connected repository, propose a bounded change, and create a pull request when the client connection and selected execution mode permit it.
Track the workflow — Use Activity to separate suggested, in-progress, waiting, and completed work.
Costs and confirmation
Chat itself is free. A metered Rankability action shows its credit cost before it begins. The exact controls depend on the action, your role, and the selected client.
Work with connected apps
Depending on your organization’s configuration, Serena can use connected Google data, Google Drive sources, YouTube sources, and Slack. Each connection has its own permissions and data boundary.
Repository execution
When a client has a connected GitHub repository, Serena can inspect relevant text files and prepare a bounded pull request for supported website changes. Choose the execution mode beside the chat composer before requesting the work:
Ask first requires your approval before Serena creates the proposed pull request.
Auto-create PRs allows a supported, bounded proposal to become a reviewable pull request without another card click.
Full access permits the broader repository workflow shown by Rankability and should be reserved for repositories where the organization accepts that level of automation.
Serena does not write directly to the default branch. Repository changes are bounded, protected paths and secret-like content are rejected, and the resulting pull request remains the reviewable record. Connecting GitHub does not deploy the customer's website. After the customer deploys an approved change, ask Serena to verify supported live Site Auditor findings when that verification is available.
Execution boundaries
Serena cannot use a client, source, connection, or external account that your access does not permit.
Serena cannot supply authoritative client facts that are absent or incorrect in the available sources.
A recommendation, audit finding, or draft is not proof that an external website or account changed.
A created or merged pull request is not proof that the customer website deployed; confirm the deployment before treating a live issue as fixed.
Review publishing decisions and other consequential actions before they occur.
Verify legal, medical, financial, reputational, and brand-sensitive claims with an accountable human and authoritative evidence.
Get a better result
Choose the correct client and describe the outcome you need.
Name the relevant keyword, page, project, audience, market, and time period.
Tell Serena which client sources or connected evidence should control the answer.
Review the cited or displayed evidence, assumptions, cost, and proposed next action.
Correct inaccurate information at its source so later work uses better context.
If Serena lacks context
Check the selected client, source status, connected account, property, permissions, and date range. If a supported action repeatedly fails, contact support with the client, task or conversation context, time, and visible error.
Related articles
Last updated
Was this helpful?