Client settings reference
Configure a Rankability client's profile, brand voice, sources, integrations, portal, reports, alerts, and monitoring.
Client settings define the identity, defaults, evidence, connections, and delivery rules Rankability uses for one client. Confirm the client name at the top of the workspace before changing a setting; these controls can affect generated content, tracking, Serena's context, scheduled reports, alerts, and outside access.
Open a client and select Settings. On a smaller screen, use the settings-section menu in place of the left navigation.
Profile
General
Basic information contains the client name, website domain, and completion-email preference. The client name is required. A valid domain improves setup and is needed for many website-based workflows, but it can be added later.
Project defaults prefill new work and can still be overridden inside an individual project:
Industry, default language, and target location guide new Copywriter projects.
Default brand aliases prefill new Tracker projects for brand-mention detection; they are not backlink-domain aliases.
A LinkedIn company or profile URL lets Tracker recognize the client's own LinkedIn content as an owned result without connecting a LinkedIn account.
Brand & voice
Define the brand name, tagline, audience, differentiators, competitors, tone, writing guidance, restricted words, excluded topics, and branded GSC terms. Rankability uses supported fields as grounding for content and analysis, so review specific facts rather than treating an AI suggestion as authoritative.
Auto-fill from website analyzes the client's site and can fill all fields or only empty fields. Extract voice from samples accepts representative URLs or pasted text. Each button displays its credit cost before the run; the current shared rates are also listed in the credit costs reference. Review AI-suggested values, edit anything inaccurate, and select Save changes.
When creating a new client, only the General and Brand & voice sections are available. Save the client before configuring the client-only sections below.
Content
Assets stores approved photos and reusable visual material for supported content workflows. In the Copywriter editor, Insert an approved image lets you choose a saved asset or add one. Saved alt text is used when available; otherwise the filename is a fallback that you should review. Autopilot does not silently select a featured image.
Sources manages client-specific material that Serena and supported workflows can use as context. Keep sources current and remove material that should no longer influence execution.
Assets and sources use their own controls inside their panels; do not assume the page-level Save changes button submits a pending upload or source action.
Connections
Integrations groups data, publishing, task-management, and notification connections. A connected badge confirms saved authorization, not necessarily current data freshness or permission to every property. Project-management authorization is created once under Settings → Organization → Integrations; the client panel maps that client to a destination. For the current Asana workflow, see Connecting Rankability to Asana.
Client portal manages a no-login report link, report visibility, and individually invited portal users. The portal is read-only and scoped to the selected client.
For the Google authorization and property-selection workflow, see Connecting client Google services. For external access, see Setting up the client portal.
Performance
Reports controls scheduled report delivery for this client. Review the recipients, cadence, report configuration, and connected-data coverage before enabling delivery. Scheduling a report does not create missing GSC, GA4, or Tracker history.
Monitoring
Alerts configures which eligible detector signals can create client alerts and which supported channels receive them.
Monitoring capabilities controls the capabilities that feed Serena and the weekly brief. Integration-dependent capabilities can enable automatically after the required service is connected.
Monitoring capability and alert settings serve different purposes: enabling a capability makes its evidence available to supported analysis, while an alert rule determines whether an eligible finding should notify someone.
Saving and troubleshooting
General and Brand & voice edits use the sticky Save changes button. If you switch those tabs with unsaved edits, Rankability asks whether to save, discard, or remain on the current section. Field limits can block saving; review highlighted brand fields when the button is unavailable.
If a setting appears missing, confirm that the client has already been created, that you have access to it, and that you are not editing a demo client. If connected data is absent elsewhere, verify the selected account and property in Integrations rather than entering a zero value manually.
Related articles
Last updated
Was this helpful?