Using Serena chat
Open Chat for a client to ask Serena questions, use client context, attach supported material, and move useful work into Rankability.
Open Chat for a client to ask Serena questions, use client context, attach supported material, and move useful work into Rankability.
Serena is most useful when the correct client is selected and its sources and integrations are current. Use client Chat for client-specific execution; do not use a generic support surface when the answer requires live rankings, GSC, GA4, projects, or client memory.
Open Serena
Select a client.
Open Chat in the client sidebar.
Ask a question or describe the result you want.
Serena uses the selected client’s sources, settings, connected data, memory, and available Rankability tools. Starting a new chat does not change the selected client.
Begin with the outcome, scope, and constraints: for example, name the page, keyword, country, date range, or report you want Serena to inspect. Serena can read available client context and propose or perform supported Rankability actions, but it should not invent facts that are absent from the workspace.
Attach screenshots
You can attach up to four screenshots to one message. Use screenshots when the visible page, chart, layout, or error message is important to your question.
Actions and charges
Chat itself is free. Some actions Serena can start—such as audits, research, tracking, or content generation—use credits. Serena and the product show the action and its cost before a metered run begins. Actions that change external systems require approval where the product presents an approval step.
Read the structured action details before approval. They are the source for scope, inputs, and estimated credits. A chat response promising a later result is not evidence that background work exists; use the visible progress and terminal result in the conversation or the relevant project/task status.
Complete a Serena workflow
Select the client and open Chat.
State one concrete objective and include the relevant page, keyword, market, or evidence.
Answer a necessary clarifying question or attach up to four relevant screenshots.
Review any proposed action, cost, and destination before approving it.
Keep the chat open or return later and use the persisted progress/result rather than starting a duplicate.
Open the created project, report, list, or task to verify the output and continue the work.
Limits and recovery
Serena can be wrong. Verify high-impact recommendations against captured data and authoritative client sources.
A screenshot shows only the visible state; include the URL, date, filters, and error text when they matter.
Connected services can be stale or unauthorized. Check Serena sources and connections before treating missing data as zero.
A tool can fail after approval. Preserve the error and action details, then retry only when the original run is no longer active.
External publication, messaging, or destructive changes may require explicit approval and cannot be inferred from a general request.
Get a better answer
Name the page, keyword, market, or date range you mean.
Connect the relevant data service in client settings.
Add authoritative client sources instead of asking Serena to infer private facts.
Open a separate chat when you switch to a different goal.
Related articles
Last updated
Was this helpful?