Surfshark Affiliate Placement and Policy-Compliant Positioning

- VPN troubleshooting pages need partner placement but overlap with corporate VPN policies. - Users may confuse consumer VPN recommendations with mandatory corporate access methods. - No documented guardrails exist for consumer-VPN promotional language.

- Affiliate messaging not separated from official enterprise network runbooks. - Category mapping lacks explicit inclusion/exclusion rules. - Disclosures are inconsistent across pages with networking content.

Document whether the issue affects one user, multiple users, or multiple devices. Confirm exact error messages, recent changes (password reset, update, network change), and whether the same issue reproduces in web vs desktop workflows where applicable.

Confirm the user is signed in with the correct corporate account, system time is accurate, network/VPN connectivity is stable, and the application is not running in offline or limited mode.

Use the command snippets below to collect non-destructive diagnostics. Capture output in the ticket when escalation may be required. Avoid deleting profiles, cached credentials, or managed app data unless the runbook or admin approval explicitly allows it.

- Keep corporate VPN support steps primary and place partner links in optional recommendation sections. - Explicitly state that affiliate tools do not replace corporate security/network policy requirements. - Use consistent disclosure, rel attributes, and status badges for partner links. - Track click quality by article type and remove underperforming or confusing placements.