Credential redaction is the replacement or removal of sensitive values — API keys, passwords, tokens, connection strings — before logs, diagnostics, or on-screen state are displayed, copied, or exported.
| Term | Credential Redaction |
|---|---|
| Category | APIs, Reliability and Publishing |
| Also known as | Secret Redaction |
| Where it appears | Diagnostics and credential handling |
What it means in RankGear
RankGear connects to third-party providers and to your own publishing targets, which means it holds secrets: search-data API keys, model credentials, CMS or FTP logins. Credential redaction is the safeguard that keeps those secrets from leaking into places they were never meant to travel. When RankGear writes a diagnostic log, prints a connection test result, or lets you copy the details of a failed request, the sensitive portions are masked — shown as placeholders rather than the raw value. The goal is that a log file or a screenshot you share while troubleshooting can be handed to support or pasted into a ticket without also handing over a working key.
How to interpret it
Treat a redacted value as a deliberate blank, not a bug. Seeing sk-•••••••• or [redacted] in a diagnostic line means RankGear recognized that field as a secret and hid it on purpose; the underlying credential is still intact and in use. When you are diagnosing a connection problem, lean on the surrounding signals — the visible status, the HTTP response, the credential test result — to tell a transient failure apart from an invalid configuration, rather than expecting the secret itself to be printed. If a value you consider sensitive is not redacted, that is the finding worth escalating, because it means the log is unsafe to share as-is.
Example
A publishing job to your WordPress site fails and you open the diagnostics panel to see why. The log shows the request URL, the response code (401 Unauthorized), and the header set — but the application-password field reads Authorization: Basic •••••• instead of the encoded credential. The 401 tells you the login was rejected, so you re-enter the password and retry; at no point did the panel expose the secret you would otherwise have leaked by pasting that log into a support thread.
Important considerations
- Credentials and remote publishing targets deserve extra care: where a provider offers it, run connection tests as read-only checks so a misconfigured credential cannot trigger a destructive or billable action.
- Redaction protects displayed and copied output — logs, diagnostics, UI state, exports — but the stored credential still exists on your machine; protect the machine and the RankGear configuration the way you would any password store.
- Redaction is best-effort pattern matching on known secret shapes. If you paste a secret into a free-text field or a filename, it may fall outside what the masking recognizes, so avoid putting live keys anywhere they are not explicitly requested.
- A redacted log confirms nothing about whether a credential is correct — only that it was hidden. Use the credential test and the response status to judge validity.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.