New link cannot be saved because slug/path is invalid.
Where to Check in PassiveWP
WordPress Admin -> PassiveWP -> Branded Links -> My Links
Step-by-Step Fix Walkthrough
Fix Step 1: Use lowercase letters, numbers, and hyphens only.
Where to click WordPress Admin→PassiveWP→Branded Links→My Links
What to do In WordPress Admin→PassiveWP→Branded Links→My Links, do this in order: open the relevant panel, find the control related to "Use lowercase letters, numbers, and hyphens only.", apply one change, click Save/Run, then reload once to confirm it stuck.
How to verify Private-window click tests should route correctly and keep required attribution params.
Fix Step 2: Avoid paths similar to wp-admin, wp-json, login, and other system routes.
Where to click WordPress Admin→PassiveWP→Branded Links→My Links
What to do In WordPress Admin→PassiveWP→Branded Links→My Links, do this in order: open the relevant panel, find the control related to "Avoid paths similar to wp-admin, wp-json, login, and other system routes.", apply one change, click Save/Run, then reload once to confirm it stuck.
How to verify Private-window click tests should route correctly and keep required attribution params.
Fix Step 3: Choose a unique campaign-specific slug and retry.
Where to click WordPress Admin→PassiveWP→Branded Links→My Links
What to do In Basics, set "Branded URL" with a unique lowercase slug (no query/hash), then continue when validation passes.
How to verify Private-window click tests should route correctly and keep required attribution params.
Fix Step 4: Adopt a consistent naming convention to avoid collisions.
Where to click WordPress Admin→PassiveWP→Branded Links→My Links
What to do In WordPress Admin→PassiveWP→Branded Links→My Links, do this in order: open the relevant panel, find the control related to "Adopt a consistent naming convention to avoid collisions.", apply one change, click Save/Run, then reload once to confirm it stuck.
How to verify Private-window click tests should route correctly and keep required attribution params.
Most Common Causes
- Slug conflicts with reserved WordPress paths.
- Slug contains unsupported characters or query/hash fragments.
- Slug already exists in another link.
How to Prevent It Next Time
- Keep a campaign slug registry.
- Use structured naming per channel/date/topic.
- Reserve short premium slugs for evergreen campaigns.
When to Contact Support
- You completed every fix step and still get the same error.
- The issue impacts revenue-critical pages or high-volume campaigns.
- You can share timestamps, affected link/product IDs, and screenshots of the exact error state.
