Competitor gap
Competitors cover bonus terms; bonus pending, register timing and agent-code proof remain weak.
Improved answer
Separate register timing, invite code, bonus not received and agent program FAQ clusters.
Action order
- Confirm the user symptom and device context before choosing the matching fix path.
- Keep download, update, register and payment-check routes on the same crawlable page.
- State evidence requirements and support timing without outcome guarantees.
- Route readers to the FAQ and support path at the end of the page.
FAQ
What should be checked first?
Separate register timing, invite code, bonus not received and agent program FAQ clusters.
Why does this need a separate intent page?
A dedicated page keeps one visible intent clear, reduces keyword dilution and makes the support path easier for users and crawlers to understand.