📘 Checklist: what to fix now, what can wait →

Network environment checklist for cross-border sellers and social media teams

What you must fix now, and what can wait

Updated 2026-11-21

First, the boundary: this guide is about keeping a legitimate business from being misjudged by automated systems, not about evading platform penalties. Every platform has clear multi-account rules, and continuing in a new environment after a penalty is itself a violation.

1. Know the platform rules first

Bottom line: compliant multi-account operations are possible, but each account must be genuine, independent and stable over time. Your network setup is what makes “independent” and “stable” hold up technically.

2. The five problems teams actually run into

1. Verification on every sign-in, or even a locked account

Google states that signing in from somewhere other than your usual location triggers an extra verification step, and that it estimates location from your IP address. An IP that is in the US today and Singapore tomorrow, or a shared proxy exit that keeps changing, triggers verification again and again. Root cause: an unstable exit.

2. Several stores or accounts penalised together (“linked”)

Logging into several clients’ accounts from the same computer, the same browser profile and the same IP looks to a platform like one person managing them all. When one account has a problem, the others are pulled in. Root cause: no isolation.

3. A new ad account is disabled immediately — and so is the next one

Apart from violating ad content, a common cause is a new ad account sharing a payment method, device or network with one that was already suspended. Under Google’s rules, related accounts are suspended together and new accounts are suspended automatically. Find the original reason before opening another account.

4. The IP you bought is already “dirty”

If anyone else on a shared IP has sent spam or attacks, that IP can be blocklisted and you inherit the problem. For the Spamhaus SBL, removal can only be requested by the network provider, not by you. Root cause: a shared IP of unknown origin.

5. An environment that contradicts itself

A US IP with the browser on Beijing time; a proxy that covers only the browser while WebRTC exposes the real IP; an antidetect profile that claims Windows but still reports an Apple GPU. These contradictions are easier to detect than the proxy itself.

3. Fix now vs. can wait

IssueLevelWhy
Accounts of different clients or entities share one IP or one browser profileFix nowPlatforms list shared devices and management as linkage signals; one problem spreads to all
WebRTC leaks your real IPFix nowWeb pages see your real exit, undoing your isolation
The IP is a public proxy, a Tor exit, has abuse reports or is blocklistedFix nowHigh-risk labels, and you cannot remove a blocklisting yourself
Sign-in IP changes often or jumps between countriesFix nowRepeated unusual-location checks, and in bad cases a lock
Payment method, phone or email shared between entities’ accountsFix nowWritten linkage criteria in platform policy; a new IP will not fix it
Contradictions: time zone vs. IP, OS vs. GPU vs. fontsFix soonMay not cause trouble at once, but adds to the risk score
Logging into stores or ad accounts from a datacenter IPFix soonReal users rarely browse from servers, so datacenter IPs are usually treated as higher risk
Browser language differs from the IP’s countryCan waitMany people abroad use their native language; on its own this rarely matters
City-level location is inaccurateCan waitIP location is only reliable at country level, and platforms know it
Broadcast IP (registered and used in different countries)DependsSome platforms compare them; switch to a native IP if your business is strongly local
Average speed or higher latencyCan waitStability matters for account safety, not raw speed — except for live streaming and video
No IPv6Can waitDoes not affect account safety

4. How to choose an IP

  1. One entity, one device, one fixed IP. Never share an exit between clients or entities, and keep each account on the same IP over time.
  2. Prefer residential-grade static IPs; avoid datacenter IPs and rotating proxies. Rotating proxies suit data collection, not account logins.
  3. Match the IP’s location to where you do business. Selling in the US means a US IP, with time zone and clock set to match.
  4. Dedicated, with a known origin. Run a quality check before you buy: no abuse reports, not a proxy or VPN exit.
  5. Send the whole device or router through one exit instead of a browser-only proxy, so WebRTC and other apps cannot leak.

Every item in this checklist can be checked with the free tools below. The scoring rules are public and the same for every IP.

Check yourself with free tools

References