[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:google-proxy-ip-guide":3,"blog-article:\u002Fblog\u002Fgoogle-proxy-ip-guide":77,"blog-related:\u002Fblog\u002Fgoogle-proxy-ip-guide":1138,"blog-translations:\u002Fblog\u002Fgoogle-proxy-ip-guide":1139},{"available":4,"article":5,"relatedArticles":316,"translations":972},true,{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":18,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":23,"bodyHtml":116},"strapi",649,"ewjtaatviga7g93p03thpo7a","zh","google-proxy-ip-guide","\u002Fblog\u002Fgoogle-proxy-ip-guide","Google代理IP怎么选：账号登录、Chrome配置与风控避坑","说明 Google 账号登录、Chrome 配置、长期使用场景下该选哪类代理 IP。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_SEO_cddbcf97ca.webp","2026-06-18T10:26:20.354Z","2026-06-18T10:26:20.321Z","Global Proxies Team",[],false,0,14,"blocks",[24,30,34,40,44,49,53,57,61,65,117,121,125,129,133,137,141,146,150,154,158,162,166,170,174,178,182,186,229,233,237,241,245,249,253,257,261,265,269,273,277,281,285,289,293,297,301,305,309,313],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"搜 `google代理ip` 的人，通常不是只想让 Google 能打开，而是想解决 Gmail 反复验证、Google Ads 登录提醒变多、Chrome 挂了代理但地区还是不对，或者账号长期使用后越来越不稳定这类实际问题。Google 代理 IP 真正要看的，不是“能不能访问”这么简单，而是出口地区、IP 类型、账号稳定性和浏览器配置能不能彼此对上。","text",{"type":25,"children":31},[32],{"text":33,"type":29},"如果你的任务是长期登录 Gmail、YouTube 后台或 Google Ads，通常应该优先看静态住宅或独享住宅 IP，因为这类场景更依赖固定出口和连续会话；如果只是做短期查询、SEO 检查或批量测试，动态住宅往往更合适，重点会落在地区覆盖和切换节奏上。场景没分开时，后面的验证码、地区跳变和异常提醒就很容易越试越多。",{"type":35,"level":36,"children":37},"heading",2,[38],{"text":39,"type":29},"Google代理IP适合哪些场景",{"type":25,"children":41},[42],{"text":43,"type":29},"Google 相关任务差别很大，不能只按“都是 Google”来配同一套代理。搜索观察、广告预览、Gmail 长期登录和 YouTube 后台维护，对出口稳定性、地区一致性和成本结构的要求并不在同一层。",{"type":45,"children":46},"code",[47],{"text":48,"type":29},"| 场景 | 推荐方向 | 稳定与风控重点 | 成本与并发提醒 |\n| --- | --- | --- | --- |\n| Google 搜索、SEO 查询、一次性地区结果观察 | 动态住宅代理IP | 地区命中、切换节奏、验证码频率 | 更适合短会话，先看流量成本 |\n| Gmail、YouTube 后台、Google Ads 长期登录 | 静态住宅代理IP | 会话稳定、地区一致、少跳变 | 单价通常更高，但排查成本更低 |\n| 多账号隔离、固定单账号单出口 | 独享住宅IP | 独享性、账号环境隔离、长期稳定 | 更适合低并发长期任务 |\n| 批量测试、速度优先、住宅属性要求一般 | 机房代理IP | 登录风控更敏感时要谨慎 | 并发和成本更好控，但别拿来硬顶长期账号 |",{"type":25,"children":50},[51],{"text":52,"type":29},"真正需要账号隔离和固定出口的，通常是三类业务：长期登录 Gmail、Google Ads、YouTube 后台这类账号型业务；团队分工运营、需要多人分别维护不同账号的协作型业务；以及一号一线、希望把每个账号和固定环境长期绑定起来的多账号业务。这几类任务共同怕的都不是“偶尔打不开”，而是出口国家、网络属性和登录环境反复变化。",{"type":25,"children":54},[55],{"text":56,"type":29},"原因也很直接。只要同一账号今天走美国、明天走英国，或者几个成员轮流共用一条出口，平台看到的就是一组不断变化的访问身份，验证码、二次验证和异常提醒自然更容易增加。固定出口的价值，不只是让代理能连通，而是让账号的地区轨迹、会话节奏和使用环境尽量稳定下来。",{"type":25,"children":58},[59],{"text":60,"type":29},"相反，公开采集、临时地区查看、广告预览和一次性测试这类短会话任务，未必需要把账号隔离和长期固定出口放在第一位。它们更看重地区覆盖、切换节奏和整体成本，不是所有 Google 相关业务都要按长期登录方案来配。",{"type":25,"children":62},[63],{"text":64,"type":29},"如果你还没先分清类型，可以先对照 [静态住宅代理](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fstatic-residential-proxy-ip-guide) 和 [独享住宅IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fdedicated-residential-ip-guide) 的边界，再决定是不是要继续用高频切换资源。",{"type":66,"image":67,"children":114},"image",{"id":68,"ext":69,"url":70,"hash":71,"mime":72,"name":73,"size":74,"width":75,"height":76,"caption":77,"formats":78,"provider":111,"createdAt":112,"updatedAt":112,"documentId":113,"focalPoint":77,"previewUrl":77,"publishedAt":112,"alternativeText":77,"provider_metadata":77},601,".webp","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_google_proxy_ip_guide_seomaster_draft_clean_1_93e9d274ee.webp","google_proxy_ip_guide_seomaster_draft_clean_1_93e9d274ee","image\u002Fwebp","google-proxy-ip-guide-seomaster-draft-clean-1.webp",169.89,2732,1534,null,{"large":79,"small":87,"medium":95,"thumbnail":103},{"ext":69,"url":80,"hash":81,"mime":72,"name":82,"path":77,"size":83,"width":84,"height":85,"sizeInBytes":86},"\u002Fuploads\u002Flarge_google_proxy_ip_guide_seomaster_draft_clean_1_93e9d274ee.webp","large_google_proxy_ip_guide_seomaster_draft_clean_1_93e9d274ee","large_google-proxy-ip-guide-seomaster-draft-clean-1.webp",40.85,1000,561,40852,{"ext":69,"url":88,"hash":89,"mime":72,"name":90,"path":77,"size":91,"width":92,"height":93,"sizeInBytes":94},"\u002Fuploads\u002Fsmall_google_proxy_ip_guide_seomaster_draft_clean_1_93e9d274ee.webp","small_google_proxy_ip_guide_seomaster_draft_clean_1_93e9d274ee","small_google-proxy-ip-guide-seomaster-draft-clean-1.webp",14.95,500,281,14948,{"ext":69,"url":96,"hash":97,"mime":72,"name":98,"path":77,"size":99,"width":100,"height":101,"sizeInBytes":102},"\u002Fuploads\u002Fmedium_google_proxy_ip_guide_seomaster_draft_clean_1_93e9d274ee.webp","medium_google_proxy_ip_guide_seomaster_draft_clean_1_93e9d274ee","medium_google-proxy-ip-guide-seomaster-draft-clean-1.webp",27.33,750,421,27332,{"ext":69,"url":104,"hash":105,"mime":72,"name":106,"path":77,"size":107,"width":108,"height":109,"sizeInBytes":110},"\u002Fuploads\u002Fthumbnail_google_proxy_ip_guide_seomaster_draft_clean_1_93e9d274ee.webp","thumbnail_google_proxy_ip_guide_seomaster_draft_clean_1_93e9d274ee","thumbnail_google-proxy-ip-guide-seomaster-draft-clean-1.webp",5.14,245,138,5138,"local","2026-06-17T12:34:11.590Z","enmrzgozcaqq0huueotfs7f4",[115],{"text":116,"type":29},"",{"type":35,"level":36,"children":118},[119],{"text":120,"type":29},"Google账号登录为什么更看重稳定出口",{"type":25,"children":122},[123],{"text":124,"type":29},"Google 账号场景里，真正麻烦的通常不是一次访问失败，而是同一账号的地区、网络属性和使用轨迹不断变化。昨天还在美国登录 Gmail，今天切到日本，过几天又换成共享机房出口，这类连续变化往往比单次报错更容易把风控推高。",{"type":25,"children":126},[127],{"text":128,"type":29},"长期登录和一次性查询要分开判断。一次性查询、临时广告预览、地区结果核对，可以接受短会话和适度轮换；长期登录 Gmail、Google Ads、YouTube Studio，就更应该优先稳定出口，让同一账号尽量固定在同一国家、同一类 IP、同一浏览器环境里。",{"type":25,"children":130},[131],{"text":132,"type":29},"账号历史地区也不能忽略。一个账号如果长期在香港或美国使用，突然换到完全不同的国家，再叠加新的设备环境，验证码和二次验证通常会明显增加。这里的问题不是 Chrome 配没配好，而是地区一致性没有守住。",{"type":35,"level":36,"children":134},[135],{"text":136,"type":29},"Chrome里怎么配置代理IP",{"type":25,"children":138},[139],{"text":140,"type":29},"Chrome 本身通常跟随系统代理，所以配置前先准备好四个字段：`host`、`port`、`username`、`password`。如果你连认证信息都没核对清楚，后面看到的“连不上”或“部分页面异常”，很可能只是接入参数不完整。需要对照系统层代理或扩展接管方式时，可以直接参考 [ChromeOS 代理设置文档](https:\u002F\u002Fsupport.google.com\u002Fchrome\u002Fa\u002Fanswer\u002F14113552?hl=en) 和 [Chrome 扩展 `chrome.proxy` API](https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Fextensions\u002Freference\u002Fapi\u002Fproxy)。",{"type":35,"level":142,"children":143},3,[144],{"text":145,"type":29},"Chrome里最小可用配置顺序",{"type":25,"children":147},[148],{"text":149,"type":29},"如果你只是想先把 Google 相关流量跑通，可以先按这个顺序操作：",{"type":25,"children":151},[152],{"text":153,"type":29},"1. 先确认这次任务是长期登录，还是一次性查询、广告预览或批量测试。\n2. 长期固定出口优先走系统代理；只想让 Google 相关站点走代理，再考虑扩展分流。\n3. 填好 `host`、`port`、`username`、`password` 后，先重开 Chrome，再检查地区、时区和登录状态。\n4. 别只测搜索页，至少再测一次 Gmail、Ads、YouTube 后台或你的目标站点入口。",{"type":25,"children":155},[156],{"text":157,"type":29},"固定使用一个代理出口时，走系统代理最省事。你在 Windows 或 macOS 的网络设置里填好地址、端口和认证信息，再重启 Chrome，通常就能让浏览器流量统一走代理。这个方式更适合长期登录、固定地区访问和低频切换场景。",{"type":25,"children":159},[160],{"text":161,"type":29},"频繁切换不同国家或只想让 Google 相关网站走代理时，用扩展方式更灵活。扩展更适合规则分流，但前提是你要确认权限、分流范围和认证方式，避免把其他站点也一起带走。配置完成后，别只看 Google 搜索能不能打开，至少再核对地区、时区和登录表现是不是一起对上了。",{"type":25,"children":163},[164],{"text":165,"type":29},"如果你要在浏览器之外接客户端工具，或者不只是纯网页流量，再补看 [SOCKS5住宅代理](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fsocks5-residential-proxy-guide) 会更合适。",{"type":35,"level":36,"children":167},[168],{"text":169,"type":29},"HTTP、SOCKS5、静态住宅和动态住宅怎么选",{"type":25,"children":171},[172],{"text":173,"type":29},"先别把这四类放在一层比较。HTTP \u002F HTTPS 和 SOCKS5，先回答的是“流量怎么走”；静态住宅和动态住宅，回答的才是“出口稳不稳、要不要频繁切换”。",{"type":25,"children":175},[176],{"text":177,"type":29},"纯浏览器访问 Google 搜索、Gmail、网页端 YouTube 或 Ads 后台，通常先用 HTTP 或 HTTPS，配置更直接，也更适合 Chrome 这类浏览器场景；如果任务还涉及客户端、自动化工具、指纹浏览器或不只是网页流量，再考虑 SOCKS5。",{"type":25,"children":179},[180],{"text":181,"type":29},"再看住宅类型。动态住宅更适合 SEO 巡检、地区结果观察、广告预览和一次性查询，重点是地区覆盖和轮换能力；静态住宅更适合 Gmail、YouTube 后台、Google Ads 这类长期登录，重点是固定出口和连续会话。要是一号一线、账号隔离要求更高，可以继续看独享住宅；只要任务回到长期登录，机房代理IP通常就不是优先项，因为风控压力往往更高。",{"type":25,"children":183},[184],{"text":185,"type":29},"一句话判断：浏览器流量先看 HTTP \u002F HTTPS，工具流量再看 SOCKS5；短会话先看动态住宅，长期登录先看静态住宅。",{"type":66,"image":187,"children":227},{"id":188,"ext":69,"url":189,"hash":190,"mime":72,"name":191,"size":192,"width":193,"height":194,"caption":77,"formats":195,"provider":111,"createdAt":224,"updatedAt":224,"documentId":225,"focalPoint":77,"previewUrl":77,"publishedAt":226,"alternativeText":77,"provider_metadata":77},602,"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_google_proxy_ip_guide_seomaster_draft_clean_2_7199cbec7e.webp","google_proxy_ip_guide_seomaster_draft_clean_2_7199cbec7e","google-proxy-ip-guide-seomaster-draft-clean-2.webp",173.48,2658,1427,{"large":196,"small":203,"medium":210,"thumbnail":217},{"ext":69,"url":197,"hash":198,"mime":72,"name":199,"path":77,"size":200,"width":84,"height":201,"sizeInBytes":202},"\u002Fuploads\u002Flarge_google_proxy_ip_guide_seomaster_draft_clean_2_7199cbec7e.webp","large_google_proxy_ip_guide_seomaster_draft_clean_2_7199cbec7e","large_google-proxy-ip-guide-seomaster-draft-clean-2.webp",44.42,537,44418,{"ext":69,"url":204,"hash":205,"mime":72,"name":206,"path":77,"size":207,"width":92,"height":208,"sizeInBytes":209},"\u002Fuploads\u002Fsmall_google_proxy_ip_guide_seomaster_draft_clean_2_7199cbec7e.webp","small_google_proxy_ip_guide_seomaster_draft_clean_2_7199cbec7e","small_google-proxy-ip-guide-seomaster-draft-clean-2.webp",15.91,268,15910,{"ext":69,"url":211,"hash":212,"mime":72,"name":213,"path":77,"size":214,"width":100,"height":215,"sizeInBytes":216},"\u002Fuploads\u002Fmedium_google_proxy_ip_guide_seomaster_draft_clean_2_7199cbec7e.webp","medium_google_proxy_ip_guide_seomaster_draft_clean_2_7199cbec7e","medium_google-proxy-ip-guide-seomaster-draft-clean-2.webp",29.29,403,29290,{"ext":69,"url":218,"hash":219,"mime":72,"name":220,"path":77,"size":221,"width":108,"height":222,"sizeInBytes":223},"\u002Fuploads\u002Fthumbnail_google_proxy_ip_guide_seomaster_draft_clean_2_7199cbec7e.webp","thumbnail_google_proxy_ip_guide_seomaster_draft_clean_2_7199cbec7e","thumbnail_google-proxy-ip-guide-seomaster-draft-clean-2.webp",5.41,132,5414,"2026-06-17T12:34:12.664Z","hilixbc87gp1cou50hkuuoc9","2026-06-17T12:34:12.665Z",[228],{"text":116,"type":29},{"type":35,"level":36,"children":230},[231],{"text":232,"type":29},"Google代理IP常见风控和连接问题",{"type":25,"children":234},[235],{"text":236,"type":29},"Google 代理IP最常见的误判，是把所有问题都归到“IP不干净”。实际上，频繁验证通常至少有四个来源：地区跳变、账号历史地区不一致、多人共用同一出口、浏览器环境和登录行为不连续。",{"type":25,"children":238},[239],{"text":240,"type":29},"如果你刚配完代理就频繁验证，先别立刻换更多 IP。先查当前出口国家是不是和账号平时活动地区差太远，再查是不是多个账号共用同一出口，接着看 Chrome 的语言、时区、Cookie 和登录节奏有没有一起变化。只有把这些项对上，代理IP的稳定价值才会真正体现出来。",{"type":25,"children":242},[243],{"text":244,"type":29},"还有一种情况是共享出口本身太杂。多人共用、历史记录复杂、短时间内被不同业务反复切换的代理，即便能访问 Google，也不适合长期登录。真正要降低风控，通常得回到更稳定的住宅或独享出口上来。",{"type":35,"level":36,"children":246},[247],{"text":248,"type":29},"推荐配置：长期登录、SEO查询、批量测试分别怎么选",{"type":25,"children":250},[251],{"text":252,"type":29},"这三类任务别共用一套代理。长期登录看稳定，SEO 查询看地区和切换节奏，批量测试看成本、并发和是否真的需要住宅属性。",{"type":25,"children":254},[255],{"text":256,"type":29},"长期登录：如果你的目标是长期登录 Gmail、YouTube 后台或 Google Ads，默认先看静态住宅；要是一号一线、账号隔离要求更高，再看独享住宅。这里优先级是固定出口、地区一致和连续会话，不是切换速度。",{"type":25,"children":258},[259],{"text":260,"type":29},"SEO 查询：如果你的目标是地区 SERP 观察、广告预览或一次性市场调研，动态住宅通常更省成本，也更适合短会话。重点是地区命中和切换节奏，不要因为“能换”就频繁跳地区。",{"type":25,"children":262},[263],{"text":264,"type":29},"批量测试：如果你的目标是工具请求、接口调试或浏览器外流量，先确认是不是必须住宅属性。不是所有任务都需要最贵方案。能用机房解决的测试任务，不必硬上长期静态资源；但一旦任务转成长期登录，就该及时换回更稳的出口。",{"type":25,"children":266},[267],{"text":268,"type":29},"一句话推荐：长期登录优先静态住宅或独享住宅，SEO 查询优先动态住宅，批量测试先看机房代理，再按是否涉及长期登录决定要不要升级。",{"type":35,"level":36,"children":270},[271],{"text":272,"type":29},"常见问题",{"type":35,"level":142,"children":274},[275],{"text":276,"type":29},"Google代理IP和Chrome代理IP是不是一回事？",{"type":25,"children":278},[279],{"text":280,"type":29},"不是一回事。先按 Google 任务定国家和代理类型，再决定 Chrome 用系统代理还是扩展，并填 `host`、`port`、`username`、`password`。",{"type":35,"level":142,"children":282},[283],{"text":284,"type":29},"为什么Google账号长期登录更适合静态住宅或独享住宅IP？",{"type":25,"children":286},[287],{"text":288,"type":29},"因为长期登录最怕地区跳变和共享出口。先看静态住宅；如果要一号一线、减少互相影响，再升到独享住宅，临时查询则不用默认上这类方案。",{"type":35,"level":142,"children":290},[291],{"text":292,"type":29},"配好代理后还频繁验证，先查什么？",{"type":25,"children":294},[295],{"text":296,"type":29},"先别急着继续换 IP。先看账号历史地区和当前出口国家，再查是否共用同一出口，接着核对 Chrome 时区和语言；前两项没对齐时，先修环境别先换池子。",{"type":35,"level":142,"children":298},[299],{"text":300,"type":29},"什么时候该把HTTP换成SOCKS5？",{"type":25,"children":302},[303],{"text":304,"type":29},"当流量不再是纯 Chrome 网页访问时，就该看 SOCKS5。纯网页先留在 HTTP\u002FHTTPS；浏览器外工具请求明显增多，或网页登录和工具请求并存时，再小范围试跑 SOCKS5。",{"type":25,"children":306},[307],{"text":308,"type":29},"---",{"type":25,"children":310},[311],{"text":312,"type":29},"如果你的任务已经明确是 Google 账号长期登录、固定国家访问或多账号隔离，别再继续用共享低质量出口硬试。长期登录这类场景，优先看的是稳定出口、固定地区和连续会话；不管你是在承接 Gmail、YouTube 后台、Google Ads 这类长期账号任务，还是更在意一号一线、账号隔离和稳定出口，统一先看 [全球静态住宅方案](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fstatic-residential-native)，重点确认目标国家、固定出口、会话时长和账号隔离方式。如果你还没开始配置和试跑，先到 [注册\u002F咨询页](https:\u002F\u002Fwww.quanqiudaili.com\u002Fsignup) 完成注册、咨询或申请测试，再按长期登录、稳定出口和账号隔离这几项做小范围验证。",{"type":25,"children":314},[315],{"text":116,"type":29},[317,532,802],{"source":6,"id":318,"documentId":319,"translationKey":319,"locale":9,"slug":320,"path":321,"_path":321,"title":322,"description":323,"excerpt":323,"image":324,"publishedAt":325,"updatedAt":326,"author":17,"tags":327,"featured":19,"sortOrder":20,"readingTime":328,"bodyType":22,"bodyBlocks":329,"bodyHtml":116},1450,"ju75n5vv4hql1x4q86c41glb","crawler-403-429-captcha-proxy-ip-troubleshooting","\u002Fblog\u002Fcrawler-403-429-captcha-proxy-ip-troubleshooting","爬虫一直 403、429 或验证码，代理 IP 要怎么排查？","这篇文章是 403、429、验证码主题下的爬虫场景子页，重点解决网页采集中的排查 SOP：先分清状态码和失败类型，再记录并发、重试、单 IP 请求量、UA、headers、Cookie、浏览器是否可复现和代理 IP 类型。只有在低频、完整请求环境下仍然集中失败时，才建议调整动态住宅、静态住宅或数据中心代理 IP 方案。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_SEO_6_2602763c1c.webp","2026-07-28T09:54:31.556Z","2026-07-28T09:54:31.535Z",[],6,[330,334,338,342,346,350,354,358,362,366,370,374,378,382,386,390,394,398,402,406,410,414,418,422,426,430,434,438,442,446,450,454,458,462,466,470,474,478,481,485,489,493,497,501,505,509,513,517,521,525,529],{"type":25,"children":331},[332],{"text":333,"type":29},"爬虫一直出现 403、429 或验证码时，不要先急着扩大代理 IP 池。采集场景要先按状态码、请求频率、浏览器渲染、UA、headers、Cookie、会话一致性和代理 IP 类型逐项排查。若你需要先看所有代理使用场景的总判断顺序，可回到父页：[代理出现 403、429、验证码时先查什么](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-403-429-captcha-troubleshooting)。本文只处理爬虫和网页采集里的专项 SOP。",{"type":35,"level":36,"children":335},[336],{"text":337,"type":29},"爬虫遇到 403、429 或验证码，先按这 6 步排查",{"type":25,"children":339},[340],{"text":341,"type":29},"遇到 403、429 或验证码时，不要只判断“代理 IP 好不好”。更稳的排查顺序是：",{"type":45,"children":343},[344],{"text":345,"type":29},"| 步骤 | 要确认的问题 | 记录什么 | 下一步判断 |\n| --- | --- | --- | --- |\n| 1. 分清错误类型 | 是 403、429、验证码、空页面、重定向还是超时 | 状态码、返回片段、出现页面 | 决定先查权限、频率还是环境 |\n| 2. 降低请求频率 | 是否并发过高、重试太密 | 并发数、重试次数、单 IP 请求量 | 低频恢复则优先改采集节奏 |\n| 3. 对比浏览器和程序 | 同一代理 IP 下浏览器是否正常 | 浏览器结果、程序结果、Cookie 状态 | 程序失败则查请求环境 |\n| 4. 补齐请求特征 | UA、headers、Referer、Cookie 是否合理 | 请求头、访问顺序、是否需要渲染 | 缺环境先补环境，不先换 IP |\n| 5. 检查会话一致性 | 是否频繁换 IP、换 UA、丢 Cookie | 会话、出口地区、账号或任务 ID | 会话混乱会提高验证码概率 |\n| 6. 再测代理类型 | 动态住宅、静态住宅、数据中心代理 IP 是否匹配 | 成功率、验证码位置、地区命中 | 低频仍失败再调整代理类型 |",{"type":25,"children":347},[348],{"text":349,"type":29},"低频请求恢复正常，优先调整并发、重试和退避策略；浏览器正常但程序失败，优先补齐 UA、headers、Cookie 和访问顺序；低频、完整请求环境下仍集中失败，再判断代理 IP 类型是否不匹配。403、429 和验证码在爬虫里分别指向哪些问题",{"type":25,"children":351},[352],{"text":353,"type":29},"爬虫排查要先看“失败类型”，再看“代理 IP 类型”。403、429 和验证码都可能和代理 IP 有关，但它们不是同一种问题。",{"type":35,"level":142,"children":355},[356],{"text":357,"type":29},"爬虫 403 不一定是代理 IP 被封",{"type":25,"children":359},[360],{"text":361,"type":29},"403 更常见于访问被拒绝，可能是权限、地区、UA、headers、Cookie、Referer、登录态、目标路径或目标站策略问题。它不一定说明代理 IP 被封，也可能是程序请求不像正常浏览器访问。",{"type":25,"children":363},[364],{"text":365,"type":29},"如果浏览器能打开，程序请求却 403，先对比程序是否带了必要请求头、Cookie、Referer 和访问顺序；如果目标页需要 JavaScript 渲染，普通 HTTP 请求可能拿不到正确内容。只有在请求环境已经接近浏览器、但某类出口仍集中 403 时，才进入代理 IP 类型对照。",{"type":35,"level":142,"children":367},[368],{"text":369,"type":29},"爬虫 429 先查频率、并发和失败重试",{"type":25,"children":371},[372],{"text":373,"type":29},"429 通常表示请求频率过高或触发限流。它更常和并发、重试、单 IP 请求量、短时间访问密度有关。继续堆代理 IP 不一定能解决，如果重试策略不改，更多 IP 也会被快速打满。",{"type":25,"children":375},[376],{"text":377,"type":29},"先把并发压低，拉开请求间隔，减少失败后立即重试，记录同一 IP 在单位时间内请求了多少次。如果 429 随低频测试明显下降，优先说明采集节奏是主因。",{"type":35,"level":142,"children":379},[380],{"text":381,"type":29},"验证码变多要同时看 IP 和程序行为",{"type":25,"children":383},[384],{"text":385,"type":29},"验证码说明目标站要求额外验证，常常是代理 IP 类型、访问频率、浏览器指纹、Cookie、行为轨迹共同触发。验证码突然变多时，不要只看“换不换动态住宅代理 IP”，还要看 UA 是否频繁变化、Cookie 是否丢失、访问顺序是否机械、同一会话是否频繁换出口。",{"type":35,"level":36,"children":387},[388],{"text":389,"type":29},"排查前先把失败样本记录清楚",{"type":25,"children":391},[392],{"text":393,"type":29},"排查时不要只写“失败”。建议把 403、429、验证码、空页面、字段缺失、重定向和超时分开记录。不同失败类型对应的处理方式不同，混在一起会让团队误以为只要换代理 IP 池就能解决。",{"type":25,"children":395},[396],{"text":397,"type":29},"建议记录这些字段：",{"type":45,"children":399},[400],{"text":401,"type":29},"| 字段 | 为什么要记录 |\n| --- | --- |\n| 目标站、URL、接口或页面类型 | 判断是公开页、登录页、搜索页还是接口限制 |\n| 状态码和返回片段 | 区分 403、429、验证码、重定向、空页面 |\n| 代理 IP 类型和出口地区 | 判断地区命中和出口类型是否影响结果 |\n| 并发数、重试次数、请求间隔 | 判断是否是频率或退避策略问题 |\n| UA、headers、Cookie、Referer | 判断程序请求是否缺少正常访问特征 |\n| 是否浏览器可复现 | 区分浏览器环境问题和程序请求问题 |\n| 会话或任务 ID | 判断是否多任务共用出口、会话是否混乱 |",{"type":25,"children":403},[404],{"text":405,"type":29},"如果 429 集中出现在高并发时段，优先查频率和退避策略；如果 403 只在程序请求里出现，优先查 headers、Cookie 和访问顺序；如果验证码随单 IP 请求量上升而增加，再进入代理 IP 类型和轮换策略测试。",{"type":35,"level":36,"children":407},[408],{"text":409,"type":29},"429 频繁出现时，先改并发、重试和单 IP 请求量",{"type":25,"children":411},[412],{"text":413,"type":29},"排查 429 时，先看请求频率、并发、重试和单 IP 请求量。很多 429 不是代理 IP 差，而是节奏太密。目标站如果对自动化访问敏感，应先降低频率、增加退避、减少无效重试、拆分任务和控制单会话请求量。否则换成住宅代理 IP，也可能只是把验证码延后出现。",{"type":25,"children":415},[416],{"text":417,"type":29},"建议做一个小样本对照：同一目标站、同一请求条件下，分别测试低频和高频、浏览器和程序、数据中心代理 IP 和住宅代理 IP。先确认是哪一类变量影响最大，再决定是否扩大代理 IP 采购。",{"type":35,"level":142,"children":419},[420],{"text":421,"type":29},"没确定触发原因前，先做小样本对照",{"type":25,"children":423},[424],{"text":425,"type":29},"在没有确定触发原因前，直接扩大代理 IP 池很容易把问题放大。更稳的做法是保持目标站、接口、UA、Cookie、请求间隔和并发不变，每次只改变一个变量，比如代理 IP 类型或单 IP 请求量。",{"type":25,"children":427},[428],{"text":429,"type":29},"一轮小样本至少要记录成功率、状态码分布、验证码出现位置、平均响应时间和结果完整度。只看“能不能打开”不够，因为很多采集问题是在连续翻页、批量查询或重复访问后才出现。",{"type":35,"level":36,"children":431},[432],{"text":433,"type":29},"浏览器能打开但程序 403，先查请求环境",{"type":25,"children":435},[436],{"text":437,"type":29},"浏览器能打开，不代表程序请求能通过。目标站可能检查 JavaScript 渲染、UA、headers、Accept-Language、Cookie、Referer、TLS 指纹、登录态和页面访问顺序。程序请求缺少这些信号时，代理 IP 正常也可能出现 403、空页面或验证码。",{"type":25,"children":439},[440],{"text":441,"type":29},"如果浏览器访问正常、程序访问 403，先补齐请求环境，而不是直接升级代理 IP。比如确认 UA 是否合理，headers 是否缺失，Cookie 是否过期，是否需要先访问首页再访问列表页，是否需要浏览器渲染。更细的程序端验证问题，可继续看[浏览器能打开但程序一直验证码怎么办](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fbrowser-works-program-captcha-proxy)。",{"type":25,"children":443},[444],{"text":445,"type":29},"如果程序和浏览器都在同一代理 IP 下出现验证码，再看代理 IP 类型、地区命中、单 IP 使用强度和会话稳定性。采集 SOP 要把这些记录下来，而不是只记录“代理 IP 可用\u002F不可用”。",{"type":35,"level":36,"children":447},[448],{"text":449,"type":29},"低频访问仍然验证码很多，再判断代理 IP 类型是否匹配",{"type":25,"children":451},[452],{"text":453,"type":29},"如果低频访问仍然频繁出现验证码，且浏览器环境、headers、Cookie 和访问顺序都已经排查过，再重点看代理 IP 类型是否匹配。",{"type":45,"children":455},[456],{"text":457,"type":29},"| 采集条件 | 可先测试的代理 IP 类型 | 判断依据 |\n| --- | --- | --- |\n| 低风控公开页面、基础连通性测试 | 数据中心代理 IP | 看成本、速度和基础成功率 |\n| 多地区公开采集、价格监测、搜索结果采样 | 动态住宅代理 IP | 看地区命中、分散访问和验证码频率 |\n| 登录态、同一账号、长会话采集 | 静态住宅代理 IP | 看地区一致、会话连续和账号验证变化 |\n| 某类出口集中失败 | 换类型做对照 | 同地区、同请求条件下比较状态码分布 |",{"type":25,"children":459},[460],{"text":461,"type":29},"判断代理 IP 类型是否合适时，不要只看单次能不能打开页面。更有价值的是连续请求后的状态码分布、验证码出现位置、地区命中情况和单 IP 使用强度。如果同一套程序在低频、完整请求环境下仍然只对某类出口频繁失败，才说明需要调整代理 IP 类型。",{"type":35,"level":36,"children":463},[464],{"text":465,"type":29},"排查后什么时候该换动态住宅代理 IP",{"type":25,"children":467},[468],{"text":469,"type":29},"[动态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdynamic-residential)适合多地区公开采集、价格监测、搜索结果采样和短会话轮换。它能分散访问来源，减少单一出口被用重的问题。",{"type":25,"children":471},[472],{"text":473,"type":29},"低风控公开站点或基础连通性测试，可以先用[数据中心代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdatacenter-proxy)验证成本。如果目标站对机房出口敏感、地区真实性要求高，或多轮后验证码明显增加，再测试动态住宅代理 IP。",{"type":25,"children":475},[476],{"text":477,"type":29},"涉及登录态、同一账号、长会话和稳定地区复查时，不要只靠频繁换 IP，应评估[静态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fstatic-residential-standard)。住宅和数据中心的取舍可继续看[数据采集用住宅代理 IP 还是数据中心代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fscraping-residential-vs-datacenter-proxy)。如果想先看通用排障，可参考[代理出现 403、429、验证码时先查什么](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-403-429-captcha-troubleshooting)；如果问题已经进入批量代理 IP 管理和可用率监控，则应单独参考[大规模代理 IP 池](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Flarge-scale-proxy-ip-pool)的维护思路。",{"type":35,"level":36,"children":479},[480],{"text":272,"type":29},{"type":35,"level":142,"children":482},[483],{"text":484,"type":29},"爬虫 429 是代理 IP 被封了吗？",{"type":25,"children":486},[487],{"text":488,"type":29},"不一定。429 更常见于频率、并发、重试和目标站限流策略。先看请求节奏，再判断代理 IP 类型。如果低频、低并发下仍持续 429，再做不同代理 IP 类型和不同出口地区的对照。",{"type":35,"level":142,"children":490},[491],{"text":492,"type":29},"为什么浏览器能打开，爬虫请求却 403？",{"type":25,"children":494},[495],{"text":496,"type":29},"常见原因是程序请求环境不完整，例如缺少 Cookie、Referer、Accept-Language、访问顺序或必要渲染。先把程序请求和浏览器请求对齐，再判断是否需要调整代理 IP 类型。",{"type":35,"level":142,"children":498},[499],{"text":500,"type":29},"验证码突然变多，是不是该换动态住宅代理 IP？",{"type":25,"children":502},[503],{"text":504,"type":29},"不一定。先检查浏览器环境、UA、headers、Cookie、访问顺序、会话连续性和单 IP 请求量。动态住宅代理 IP 对短会话、多地区公开采集可能有帮助，但不能替代请求节奏和目标站规则排查。",{"type":35,"level":142,"children":506},[507],{"text":508,"type":29},"代理 IP 池越大，429 就越少吗？",{"type":25,"children":510},[511],{"text":512,"type":29},"不一定。如果失败后立即重试、并发峰值过高，或多个任务共用出口，扩大 IP 池只是把同样的问题复制到更多出口。先改频率和退避，再根据低频测试结果判断是否需要扩池。",{"type":35,"level":142,"children":514},[515],{"text":516,"type":29},"采集排查和普通代理 IP 连不上有什么不同？",{"type":25,"children":518},[519],{"text":520,"type":29},"采集 SOP 更关注状态码曲线、频率、headers、Cookie、会话和目标站策略；通用排障更关注协议、认证、连通性和代理 IP 配置。需要总排查路径时，可回到[代理出现 403、429、验证码时先查什么](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-403-429-captcha-troubleshooting)。",{"type":35,"level":142,"children":522},[523],{"text":524,"type":29},"做公开数据采集时，HTTP、HTTPS、SOCKS5 该怎么选？",{"type":25,"children":526},[527],{"text":528,"type":29},"按目标站和程序支持选择。先保证协议、认证和 DNS 行为正确，再比较代理 IP 类型和地区命中。协议选错会导致程序部分请求没走代理 IP，容易把接入问题误判成资源问题。",{"type":25,"children":530},[531],{"text":116,"type":29},{"source":6,"id":533,"documentId":534,"translationKey":534,"locale":9,"slug":535,"path":536,"_path":536,"title":537,"description":538,"excerpt":538,"image":539,"publishedAt":540,"updatedAt":541,"author":17,"tags":542,"featured":19,"sortOrder":20,"readingTime":328,"bodyType":22,"bodyBlocks":543,"bodyHtml":116},1449,"i39t4afhr6uktwvdjmm258fz","proxy-403-429-captcha-troubleshooting","\u002Fblog\u002Fproxy-403-429-captcha-troubleshooting","代理出现 403、429、验证码时先查什么？","这篇文章作为 403、429 和验证码总排查父页，重点讲代理 IP 使用中出现访问失败时的判断顺序：先区分权限、地区限制、请求频率、并发重试、账号状态和浏览器\u002F程序环境差异，再判断问题是否真的来自代理出口或代理 IP 类型。公开采集、程序验证码、Cloudflare\u002FTurnstile、长期账号登录等细分问题，应通过对应子页继续排查。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_proxy_403_429_captcha_troubleshooting_cover_afc3715177.webp","2026-07-28T09:54:09.337Z","2026-07-28T09:54:09.314Z",[],[544,548,552,556,560,564,568,572,576,580,584,588,592,633,637,641,645,649,653,657,661,665,669,673,677,681,685,689,693,697,701,705,709,713,717,721,725,729,733,737,741,745,749,753,757,760,764,768,772,776,780,784,788,792,795,799],{"type":25,"children":545},[546],{"text":547,"type":29},"代理出现 403、429 或验证码时，先不要只换代理 IP。更有效的顺序是：先区分 403、429、验证码分别代表什么，再看目标站规则、请求频率、浏览器与程序差异、账号状态和代理 IP 类型是否匹配。若问题发生在爬虫或网页采集任务里，可以继续看[爬虫一直 403、429 或验证码，代理 IP 要怎么排查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fweb-scraping-403-429-captcha-proxy)；本文先作为通用父页，解决所有代理使用场景里的总排查顺序。",{"type":35,"level":36,"children":549},[550],{"text":551,"type":29},"代理出现 403、429、验证码分别可能代表什么",{"type":25,"children":553},[554],{"text":555,"type":29},"先把 403、429、验证码拆开看：403 多查权限、地区限制、请求特征和账号状态；429 多查频率、并发、失败重试和多人共用出口；验证码变多则要同时看浏览器环境、会话连续性、地区跳变、账号状态和代理 IP 类型。把三类现象混成一句“代理不能用”，后续排查会很难归因。",{"type":45,"children":557},[558],{"text":559,"type":29},"| 现象 | 更常见的原因 | 第一轮先查什么 | 适合继续看的页面 |\n| --- | --- | --- | --- |\n| 403 | 权限、地区、请求特征或账号状态被拒 | 登录状态、目标路径、请求头、Cookie、出口地区 | 程序请求差异、Cloudflare\u002FTurnstile 专项 |\n| 429 | 请求频率、并发、重试或共享出口过高 | 单 IP 请求量、并发峰值、失败后重试、任务是否共用出口 | 爬虫 403\u002F429\u002F验证码专项 |\n| 验证码变多 | 环境可信度下降或验证层级升高 | 账号、设备、浏览器指纹、地区跳变、会话中断 | 程序验证码、账号登录稳定性文章 |\n| 只有某类代理 IP 异常 | 目标站对出口类型更敏感 | 同国家不同类型出口对照、地区命中、IP 使用强度 | 动态住宅、静态住宅、数据中心代理 IP 选型 |",{"type":35,"level":142,"children":561},[562],{"text":563,"type":29},"403 不一定是代理 IP 被封",{"type":25,"children":565},[566],{"text":567,"type":29},"同一代理 IP 在浏览器正常、程序却 403，先查请求头、Cookie、TLS 指纹、目标路径权限和登录状态。这类情况更像请求特征不完整，不一定是 IP 被封。若只在某些国家或数据中心代理 IP 上反复出现，再看地区限制、IP 信誉和目标站对出口类型的风控力度。遇到 Cloudflare、Turnstile 或循环验证，可转到 [Cloudflare Turnstile 验证失败怎么选代理 IP 更稳](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fcloudflare-turnstile-verification-failure-proxy-ip-selection) 继续排查。",{"type":35,"level":142,"children":569},[570],{"text":571,"type":29},"429 先看频率和出口共用",{"type":25,"children":573},[574],{"text":575,"type":29},"429 更常见的是频率、并发和重试失控。先核对单位时间请求数、失败后是否立即重试、多个任务是否共用同一出口；这些问题不改，换更多代理 IP 只会把限流扩散成更高成本。若是公开页面采集、批量查询或爬虫任务，应进入[爬虫一直 403、429 或验证码，代理 IP 要怎么排查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fweb-scraping-403-429-captcha-proxy)做更细的 SOP。",{"type":35,"level":142,"children":577},[578],{"text":579,"type":29},"验证码变多说明验证层级在上升",{"type":25,"children":581},[582],{"text":583,"type":29},"首次就出验证码，多半是访问行为、浏览器环境或出口类型让目标站觉得可疑；操作几轮后明显变多，常见于地区跳变、会话中断、账号状态异常、多人共用出口，或把动态住宅代理 IP 用在长期登录场景。先记录验证码出现页面、时间、账号、代理 IP 类型和请求方式，再决定是补环境、降频，还是调整代理 IP 方案。",{"type":35,"level":36,"children":585},[586],{"text":587,"type":29},"先判断这是哪一种任务，不要直接扩大代理 IP 池",{"type":25,"children":589},[590],{"text":591,"type":29},"同样是 403、429 或验证码，公开页采集、登录后台、API 请求、多地区检查的根因并不一样。排障第一步不是采购更多代理 IP，而是把任务场景、错误类型和触发时间记录清楚，再做小样本对照。",{"type":66,"image":593,"children":631},{"id":594,"ext":69,"url":595,"hash":596,"mime":72,"name":597,"size":598,"width":75,"height":599,"caption":77,"formats":600,"provider":111,"createdAt":629,"updatedAt":629,"documentId":630,"focalPoint":77,"previewUrl":77,"publishedAt":629,"alternativeText":77,"provider_metadata":77},1155,"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5.webp","proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5","proxy-403-429-captcha-troubleshooting-1-02a7228f9cea.webp",64.66,882,{"large":601,"small":608,"medium":615,"thumbnail":622},{"ext":69,"url":602,"hash":603,"mime":72,"name":604,"path":77,"size":605,"width":84,"height":606,"sizeInBytes":607},"\u002Fuploads\u002Flarge_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5.webp","large_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5","large_proxy-403-429-captcha-troubleshooting-1-02a7228f9cea.webp",19.66,323,19658,{"ext":69,"url":609,"hash":610,"mime":72,"name":611,"path":77,"size":612,"width":92,"height":613,"sizeInBytes":614},"\u002Fuploads\u002Fsmall_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5.webp","small_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5","small_proxy-403-429-captcha-troubleshooting-1-02a7228f9cea.webp",7.4,161,7404,{"ext":69,"url":616,"hash":617,"mime":72,"name":618,"path":77,"size":619,"width":100,"height":620,"sizeInBytes":621},"\u002Fuploads\u002Fmedium_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5.webp","medium_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5","medium_proxy-403-429-captcha-troubleshooting-1-02a7228f9cea.webp",13.37,242,13374,{"ext":69,"url":623,"hash":624,"mime":72,"name":625,"path":77,"size":626,"width":108,"height":627,"sizeInBytes":628},"\u002Fuploads\u002Fthumbnail_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5.webp","thumbnail_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5","thumbnail_proxy-403-429-captcha-troubleshooting-1-02a7228f9cea.webp",2.14,79,2136,"2026-07-28T08:26:28.559Z","snwy3vvzk2l0ykdyjx8pi82s",[632],{"text":116,"type":29},{"type":45,"children":634},[635],{"text":636,"type":29},"| 任务类型 | 容易出现的限制 | 先做的动作 | 建议承接 |\n| --- | --- | --- | --- |\n| 公开页面采集 | 429、验证码、字段缺失 | 降低并发、拉开重试、记录单 IP 请求量 | 爬虫专项排查页 |\n| 浏览器能打开但程序失败 | 403、空页面、程序端验证码 | 对比 headers、Cookie、渲染、代理接入方式 | 程序验证码排查页 |\n| 登录后台或账号任务 | 验证码、二次验证、权限收紧 | 查账号状态、地区一致性、设备和 Cookie | 静态住宅代理 IP 选型 |\n| API 或程序请求 | 429、403、token 限制 | 区分账号\u002Ftoken\u002Fendpoint 限流和出口共用 | 留样后再判断代理类型 |",{"type":35,"level":142,"children":638},[639],{"text":640,"type":29},"公开页面采集先降频，再进入爬虫子页",{"type":25,"children":642},[643],{"text":644,"type":29},"公开页面采集遇到 403、429 或验证码，先把并发、重试和同一 IP 的单位时间请求量压低，观察 429 与验证码是否明显下降。若降频后恢复，说明目标站限流更关键；这时盲目扩大 IP 池，只会把成本放大。采集场景里的 headers、Cookie、渲染、会话和动态住宅代理 IP 使用边界，建议继续看[爬虫一直 403、429 或验证码，代理 IP 要怎么排查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fweb-scraping-403-429-captcha-proxy)。",{"type":35,"level":142,"children":646},[647],{"text":648,"type":29},"登录后台先查账号状态，不要只查代理 IP",{"type":25,"children":650},[651],{"text":652,"type":29},"店铺后台、广告后台、社媒账号和长期登录任务，更常见的是账号近期频繁换地区、改密码、切 Cookie、换设备或登录方式变化，随后验证层级上升。此时即使用更高成本的住宅代理 IP，也可能继续异常。代理 IP 能改善网络出口和地区一致性，不能替代账号合规运营、设备稳定和平台规则。",{"type":35,"level":142,"children":654},[655],{"text":656,"type":29},"API 或程序请求要区分目标站限流和出口共用",{"type":25,"children":658},[659],{"text":660,"type":29},"如果限制落在账号、token、接口路径或时间窗口，换代理 IP 只能部分缓解，改不了接口规则。另一类问题是多个任务共用同一出口，聚合后频率过高，429 会集中出现。排查时至少保留账号或 token 类型、目标 URL、代理 IP 类型、出口国家、请求方式、状态码、返回片段、并发和时间窗口。",{"type":35,"level":36,"children":662},[663],{"text":664,"type":29},"浏览器能打开但程序失败，采购代理 IP 前先查哪些差异",{"type":25,"children":666},[667],{"text":668,"type":29},"人工点开页面，不等于程序也具备同样访问条件。浏览器会自动处理 Cookie、重定向、JS 执行、缓存、语言、时区和部分安全挑战；程序如果只发基础请求，常见结果就是 403、空白页，或浏览器能打开但程序验证码更密。这个问题应优先按请求环境排查，不要直接算成代理 IP 不稳。",{"type":35,"level":142,"children":670},[671],{"text":672,"type":29},"同一个代理 IP 在浏览器和程序里表现不同，先查接入方式",{"type":25,"children":674},[675],{"text":676,"type":29},"确认程序是否真的完整走了代理 IP。HTTP、HTTPS、SOCKS5 的适配差异、认证方式、DNS 解析和超时设置，只要有一处和浏览器不同，就可能出现页面能开、接口失败，或静态资源绕过代理后暴露本地网络特征。更细的程序端排查，可继续看[浏览器能打开但程序一直验证码怎么办](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fbrowser-works-program-captcha-proxy)。",{"type":35,"level":142,"children":678},[679],{"text":680,"type":29},"程序端验证码更密时，先看行为信号",{"type":25,"children":682},[683],{"text":684,"type":29},"瞬时并发高、失败后立即重试、固定节奏过于机械，或多个账号共用同一会话，都会让验证层级上升：先偶发验证码，再变成高频验证，最后可能直接拦截。此时盲目加动态住宅代理 IP，成本会上去，结果未必改善。更稳妥的判断，是先降频、拆分会话、补齐请求环境，再决定是否调整代理 IP 类型。",{"type":35,"level":36,"children":686},[687],{"text":688,"type":29},"动态住宅、数据中心、静态住宅代理 IP 怎么选",{"type":25,"children":690},[691],{"text":692,"type":29},"代理触发验证码后怎么选 IP 类型，别从“哪种更高级”开始，而要先看任务是不是短会话、是否频繁换地区、是否需要长期保持同一身份。类型选反了，常见结果不是慢一点，而是验证码先变多，再变成权限收紧。",{"type":45,"children":694},[695],{"text":696,"type":29},"| 任务条件 | 优先考虑 | 原因 | 不适合的情况 |\n| --- | --- | --- | --- |\n| 多地区公开采集、SEO 监控、市场调研 | 动态住宅代理 IP | 更适合短会话、多地区、分散访问 | 长期登录、同一账号持续会话 |\n| 公开页面、低风控、重速度或成本 | 数据中心代理 IP | 成本和速度更容易控制 | 目标站明显排斥机房出口 |\n| 店铺后台、广告后台、社媒账号、长期登录 | 静态住宅代理 IP | 更利于地区一致和会话连续 | 账号行为异常时不能单独解决验证 |\n| 高敏感账号、地区一致性要求更高 | 原生静态住宅代理 IP | 更适合对网络身份要求更高的长期任务 | 短时采样或频繁轮换任务 |",{"type":35,"level":142,"children":698},[699],{"text":700,"type":29},"哪些任务更适合动态住宅代理 IP",{"type":25,"children":702},[703],{"text":704,"type":29},"做多地区落地页检查、公开采集、SEO 监控或市场调研时，可以优先评估[动态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdynamic-residential)。这类任务需要分散访问，动态住宅代理 IP 更容易把出口打散，减少多人共用同一出口后的聚合风险。短板也要看清：如果拿它去跑长期账号、店铺后台或持续登录，出口频繁变化会让平台不断识别为新环境，验证码可能从偶发变成高频。",{"type":35,"level":142,"children":706},[707],{"text":708,"type":29},"什么时候值得先测数据中心代理 IP",{"type":25,"children":710},[711],{"text":712,"type":29},"访问公开页面、目标站风控力度较轻、计费模式又卡得紧时，可以先小量测试[数据中心代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdatacenter-proxy)。它更适合速度和成本优先的任务，但不适合对住宅属性敏感的平台。若 403 和验证码集中出现，继续堆同类 IP 资源通常只会放大失败样本，这时应先换动态住宅代理 IP 做对照。",{"type":35,"level":142,"children":714},[715],{"text":716,"type":29},"长期账号和稳定地区为什么更该看静态住宅代理 IP",{"type":25,"children":718},[719],{"text":720,"type":29},"登录后台、社媒运营、电商店铺这类持续会话，更看重地区一致、出口稳定和身份连续，[静态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fstatic-residential-standard)更合适。原因不在“更贵”，而在它能减少地区跳变和重复校验。限制也要看清：账号近期改密、频繁切 Cookie 或操作节奏异常时，即使用静态住宅代理 IP，验证码和限制也不会自动消失。",{"type":35,"level":36,"children":722},[723],{"text":724,"type":29},"快速判断：403、429 和验证码出现后，该不该马上换代理 IP",{"type":35,"level":142,"children":726},[727],{"text":728,"type":29},"403 出现后就换代理 IP 吗",{"type":25,"children":730},[731],{"text":732,"type":29},"不一定。先排查账号权限、地区限制、请求特征和登录状态；若这些没问题，再对比更换代理 IP。只换出口不改访问方式，403 往往会继续出现。",{"type":35,"level":142,"children":734},[735],{"text":736,"type":29},"429 出现后要不要继续加 IP 资源",{"type":25,"children":738},[739],{"text":740,"type":29},"多数时候先别加。先降频、拉开重试间隔、拆分并发，再看是否仍集中触发；否则只会把限流从单一出口扩散到更多 IP 资源。",{"type":35,"level":142,"children":742},[743],{"text":744,"type":29},"浏览器正常，为什么程序里验证码更多",{"type":25,"children":746},[747],{"text":748,"type":29},"更常见是程序请求环境、接入方式或会话保持不一致。先校验请求头、Cookie、代理接入和访问节奏，再判断是否要换代理 IP；否则容易误把行为问题当成 IP 问题。",{"type":35,"level":142,"children":750},[751],{"text":752,"type":29},"动态住宅、数据中心、静态住宅代理 IP 怎么挑",{"type":25,"children":754},[755],{"text":756,"type":29},"短会话分散访问优先动态住宅代理 IP；公开页面、低风控且重成本，可先测数据中心代理 IP；长期登录、稳定地区和持续会话，更适合静态住宅代理 IP。",{"type":35,"level":36,"children":758},[759],{"text":272,"type":29},{"type":35,"level":142,"children":761},[762],{"text":763,"type":29},"怎么判断问题来自账号、目标站规则，还是代理出口？",{"type":25,"children":765},[766],{"text":767,"type":29},"做一次小量对照：同一账号、同一路径、同一请求方式下，只更换一个变量。如果换账号恢复，优先查账号状态；如果同账号在不同出口都失败，优先查目标站权限、token 或路径规则；如果只在某类代理 IP 上集中失败，再考虑出口信誉、地区限制或代理类型不匹配。",{"type":35,"level":142,"children":769},[770],{"text":771,"type":29},"排查 403、429、验证码时，应该留哪些样本给售后？",{"type":25,"children":773},[774],{"text":775,"type":29},"至少保留时间、目标 URL、账号或 token 类型、代理 IP 类型、出口国家、请求方式、状态码、返回片段、是否浏览器可复现、并发和重试策略。只说“不能用”很难判断根因；有这些样本，服务商才更容易区分是接入配置、目标站规则、频率过高，还是代理出口异常。",{"type":35,"level":142,"children":777},[778],{"text":779,"type":29},"为什么同一个代理 IP 上午正常，下午就开始异常？",{"type":25,"children":781},[782],{"text":783,"type":29},"先看是否有频率累积、多人共用出口、账号操作变化或目标站风控窗口变化。短时间内请求量升高、失败后连续重试、频繁切换地区，都会让同一出口的风险评分变化；这类问题不能只按“IP 突然坏了”处理。",{"type":35,"level":142,"children":785},[786],{"text":787,"type":29},"测试代理 IP 时，怎样避免把接入问题误判成资源问题？",{"type":25,"children":789},[790],{"text":791,"type":29},"先用一个明确目标站、一个稳定国家、少量并发和短时间窗口测试，确认协议、认证、DNS、超时和程序代理配置都一致。测试还没跑通前，不要同时换国家、换代理类型、改程序参数和提高并发，否则结果很难归因。",{"type":25,"children":793},[794],{"text":308,"type":29},{"type":25,"children":796},[797],{"text":798,"type":29},"排查 403、429 和验证码时，先区分目标站限制、请求频率过高、账号状态异常，还是浏览器与程序访问环境不一致。只有根因接近代理出口、地区一致性或 IP 类型错配时，换动态住宅代理 IP、静态住宅代理 IP 或数据中心代理 IP 才更有意义。",{"type":25,"children":800},[801],{"text":116,"type":29},{"source":6,"id":803,"documentId":804,"translationKey":804,"locale":9,"slug":805,"path":806,"_path":806,"title":807,"description":808,"excerpt":808,"image":809,"publishedAt":810,"updatedAt":811,"author":17,"tags":812,"featured":19,"sortOrder":20,"readingTime":813,"bodyType":22,"bodyBlocks":814,"bodyHtml":116},1447,"yjl0wy95ir38uvf7jl59e3xh","proxy-reseller-commission-vs-resale","\u002Fblog\u002Fproxy-reseller-commission-vs-resale","代理 IP 分佣模式和转售模式有什么区别？","分佣和转售是两种代理合作模式。分佣通常侧重推荐成交和收益分配，转售通常侧重报价空间、套餐组合和客户协作方式，但售前、售后和技术支持责任并不固定，也不是由客户规模单独决定，应按工具支持、使用习惯和具体合作约定确认。判断清楚合作方向后，可以通过[代理商入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)提交合作意向，再进一步确认申请方式、合作模式和服务分工。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_ip_cover_32c9b152ca.webp","2026-07-28T09:51:53.949Z","2026-07-28T09:51:53.930Z",[],4,[815,819,823,827,831,835,839,843,847,851,855,859,863,867,871,875,879,883,887,891,895,899,903,907,911,915,940,944,948,952,956,960,964,968],{"type":25,"children":816},[817],{"text":818,"type":29},"很多代理商在谈合作时会把代理 IP 分佣模式和转售模式混在一起：都能带来收益，也都和客户成交有关，但真正影响后续合作体验的是客户归属、定价权、结算方式和售前售后协作。简单判断，分佣模式通常更侧重推荐成交后的收益分配，转售模式通常更侧重代理商是否拥有自主报价、套餐组合或客户经营空间。至于售前咨询、技术排障和复杂售后由谁承担，并不是模式天然决定的，也不是由客户规模单独决定的，要以工具支持方式、平台规则、代理商使用习惯和双方合作约定为准。如果你已经在评估代理 IP 合作，可以先通过[代理商入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)了解申请方式、适合人群和合作流程，再结合本文判断更适合分佣还是转售。",{"type":35,"level":36,"children":820},[821],{"text":822,"type":29},"两种合作方式怎么快速区分",{"type":25,"children":824},[825],{"text":826,"type":29},"分佣模式看推荐是否有效、成交如何归因、收益如何结算；转售模式看是否有转售价格空间、套餐组合方式、客户归属和后续协作规则。两者都可以约定不同的售前售后分工，不宜只用“谁承担服务”来判断模式。",{"type":45,"children":828},[829],{"text":830,"type":29},"| 判断项 | 分佣模式重点 | 转售模式重点 |\n| --- | --- | --- |\n| 客户来源 | 谁推荐、如何记录、归属有效期多久 | 是否由代理商持续经营客户、是否允许二次分销 |\n| 收益口径 | 分佣比例、有效订单、结算周期 | 进货成本、转售定价权、续费归属 |\n| 客户关系 | 可偏线索推荐和成交归因，也可约定后续跟进 | 可偏客户经营、复购和套餐组合，也可由平台继续参与服务 |\n| 售前售后 | 可由平台承接更多成交和技术支持，也可约定代理商协助解释 | 可由代理商承接，也可由平台和代理商分工协作，取决于工具支持和合作约定 |\n| 风险边界 | 不把推荐成交写成长期收益保证 | 不把客户业务结果包装成平台承诺 |\n| 下一步动作 | 适合先申请代理商合作，确认分佣归因、结算周期和客户跟进方式 | 适合申请代理商合作后，与商务确认转售价格空间、客户管理和售后分工 |",{"type":35,"level":36,"children":832},[833],{"text":834,"type":29},"代理 IP 分佣模式适合什么样的代理商",{"type":25,"children":836},[837],{"text":838,"type":29},"分佣型适合有推荐能力，希望先从线索推荐和成交归因开始合作的人。常见情况包括有行业内容渠道、社群资源、客户线索、咨询入口，或者能把有代理 IP 需求的客户推荐给平台承接。",{"type":25,"children":840},[841],{"text":842,"type":29},"比如你运营着一个跨境电商社群，群里经常有人问去哪买住宅代理IP，但你暂时只想先做推荐和线索转化，不想马上设计套餐、报价和客户管理流程，这种情况更适合先走分佣。",{"type":25,"children":844},[845],{"text":846,"type":29},"这种模式的重点不是自己定价，而是先验证客户需求和线索质量。具体结算细节见下文“结算和退款影响怎么确认”。如果你目前主要有社群、内容、客户线索或咨询入口，但还不想自己搭建报价和售后流程，可以先从[代理商合作入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)提交合作意向，再确认分佣归因、结算周期和客户跟进方式。",{"type":35,"level":36,"children":848},[849],{"text":850,"type":29},"转售模式适合什么样的团队",{"type":25,"children":852},[853],{"text":854,"type":29},"转售型更适合希望自主报价、组合套餐，或把代理 IP 和自身服务方案一起交付的团队。它不是简单“拿货再卖”，核心在于是否需要更灵活地组织价格、产品包、客户入口和交付流程。报价解释、产品边界说明、客户预期管理、续费提醒和问题升级路径可以由代理商承担，也可以由平台和代理商按约定分工。",{"type":25,"children":856},[857],{"text":858,"type":29},"客户数量不是唯一标准，也不是转售的前置门槛。即使客户规模不大，只要你的工具、业务流程或客户使用习惯更适合自己报价、组合套餐、统一收款或统一交付，也可以评估转售；如果已经有一批长期采购客户，并且能回答“登录异常先查什么”“测试失败怎么反馈”这类基础问题，只是会让转售推进更顺。",{"type":25,"children":860},[861],{"text":862,"type":29},"转售的收益空间通常更依赖报价组织、套餐设计和协作管理能力。团队可以围绕客户需求组织报价和服务，但不代表所有售前售后都必须自己承担。更关键的是提前形成清晰口径：客户为什么选择某类代理 IP、测试资源如何使用、续费价格是否变化、遇到连接或业务问题时先由谁排查、哪些问题升级给平台。",{"type":25,"children":864},[865],{"text":866,"type":29},"如果这些问题没有提前确认，后续容易把“客户是谁的”“谁来解释产品”“退款是否影响结算”混在一起。代理 IP 本身只解决出口环境，不能替代理商承担客户业务结果。如果你已经有客户管理、套餐组合或统一交付需求，建议通过[代理商入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)进入合作沟通，重点确认转售价格空间、续费归属、售后升级路径和客户边界。",{"type":35,"level":36,"children":868},[869],{"text":870,"type":29},"售前售后责任不是固定模板",{"type":25,"children":872},[873],{"text":874,"type":29},"分佣和转售只是合作模式，不等于售前售后责任已经天然确定。实际合作中，可以约定由平台负责产品介绍、技术排障和资源问题，也可以由代理商负责客户沟通、基础解释、续费提醒，再由平台处理复杂问题。反过来，分佣方也可能参与客户跟进，转售方也可以把部分售前售后交给平台协作，关键看工具能支持什么、双方怎么约定，以及代理商习惯用什么方式管理客户。",{"type":25,"children":876},[877],{"text":878,"type":29},"判断时不要只问“分佣还是转售”，还要问清楚：谁负责售前咨询，谁解释套餐边界，谁处理连接失败，谁收集客户报错，谁负责续费提醒，哪些问题需要升级给平台。",{"type":35,"level":36,"children":880},[881],{"text":882,"type":29},"定价、售后和结算分别怎么确认",{"type":35,"level":142,"children":884},[885],{"text":886,"type":29},"定价权看什么",{"type":25,"children":888},[889],{"text":890,"type":29},"定价权不只是能不能自己报价，还包括折扣空间、续费价格、测试资源和退款影响。分佣模式通常按平台或商务规则执行；转售模式则要提前确认是否能自行报价、是否需要遵守最低价格，以及价格变化时由谁通知客户。",{"type":35,"level":142,"children":892},[893],{"text":894,"type":29},"售后责任怎么分",{"type":25,"children":896},[897],{"text":898,"type":29},"售后责任要看合作约定，而不是只看模式名称。分佣方可以只做线索解释，也可以协助基础沟通；转售方可以承担客户经营和续费提醒，也可以把资源、后台、认证和复杂技术问题升级给平台处理。涉及服务边界时，可以再对照[代理商售后责任分工](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-reseller-after-sales-responsibility)。",{"type":35,"level":142,"children":900},[901],{"text":902,"type":29},"结算和退款影响怎么确认",{"type":25,"children":904},[905],{"text":906,"type":29},"结算前要确认有效订单、结算周期、客户归属有效期、退款是否扣减分佣，以及续费是否继续计算收益。退款或业务失败不能直接等同于平台责任，必须回到订单、资源状态、配置问题和客户业务结果边界来判断。",{"type":35,"level":36,"children":908},[909],{"text":910,"type":29},"合作前要准备哪些信息",{"type":25,"children":912},[913],{"text":914,"type":29},"进入合作沟通前，建议先把客户来源、推广记录、预计用量、工具支持方式、使用习惯和结算诉求整理清楚。准备越具体，越容易判断适合分佣还是转售。",{"type":916,"format":917,"children":918},"list","unordered",[919,924,928,932,936],{"type":920,"children":921},"list-item",[922],{"text":923,"type":29},"客户来源、推广链接或首次沟通记录是否可追溯。",{"type":920,"children":925},[926],{"text":927,"type":29},"分佣比例、结算周期、有效订单和退款影响是否明确。",{"type":920,"children":929},[930],{"text":931,"type":29},"转售方是否拥有报价权、套餐组合权、续费沟通权，以及售前售后如何分工。",{"type":920,"children":933},[934],{"text":935,"type":29},"售前解释、基础排障和平台升级支持分别由谁承接。",{"type":920,"children":937},[938],{"text":939,"type":29},"是否已写清不能承诺解封、过审、KYC 或采集成功。",{"type":25,"children":941},[942],{"text":943,"type":29},"准备好这些信息后，下一步不是继续纠结名称，而是进入[代理商入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)提交合作意向。平台侧会根据客户来源、合作方式、预期用量和服务分工，进一步确认更适合分佣、转售，还是先从轻量推荐合作开始。涉及归因规则时，再单独确认[客户归属管理](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-reseller-customer-attribution)；如果需要完整合作前清单，可以再查看[代理商合作指南](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-reseller-program-guide)。",{"type":35,"level":36,"children":945},[946],{"text":947,"type":29},"FAQ",{"type":35,"level":142,"children":949},[950],{"text":951,"type":29},"转售一定可以自己定价吗？",{"type":25,"children":953},[954],{"text":955,"type":29},"转售方是否可以自己定价，取决于合作协议、产品成本、品牌展示方式和售后责任划分。",{"type":35,"level":142,"children":957},[958],{"text":959,"type":29},"客户归属争议怎么处理？",{"type":25,"children":961},[962],{"text":963,"type":29},"客户归属争议优先回到推广链接、后台记录、首次有效沟通和商务确认规则。",{"type":35,"level":142,"children":965},[966],{"text":967,"type":29},"不确定选分佣还是转售，可以先申请代理商吗？",{"type":25,"children":969},[970],{"text":971,"type":29},"可以。合作前不一定要先把模式完全确定好，建议先通过[代理商入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)提交合作意向，再根据客户来源、报价需求、售后能力和结算诉求确认合作方式。",[973],{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":974,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":975,"bodyHtml":116},[],[976,979,982,985,988,991,994,997,1000,1003,1012,1015,1018,1021,1024,1027,1030,1033,1036,1039,1042,1045,1048,1051,1054,1057,1060,1063,1072,1075,1078,1081,1084,1087,1090,1093,1096,1099,1102,1105,1108,1111,1114,1117,1120,1123,1126,1129,1132,1135],{"type":25,"children":977},[978],{"text":28,"type":29},{"type":25,"children":980},[981],{"text":33,"type":29},{"type":35,"level":36,"children":983},[984],{"text":39,"type":29},{"type":25,"children":986},[987],{"text":43,"type":29},{"type":45,"children":989},[990],{"text":48,"type":29},{"type":25,"children":992},[993],{"text":52,"type":29},{"type":25,"children":995},[996],{"text":56,"type":29},{"type":25,"children":998},[999],{"text":60,"type":29},{"type":25,"children":1001},[1002],{"text":64,"type":29},{"type":66,"image":1004,"children":1010},{"id":68,"ext":69,"url":70,"hash":71,"mime":72,"name":73,"size":74,"width":75,"height":76,"caption":77,"formats":1005,"provider":111,"createdAt":112,"updatedAt":112,"documentId":113,"focalPoint":77,"previewUrl":77,"publishedAt":112,"alternativeText":77,"provider_metadata":77},{"large":1006,"small":1007,"medium":1008,"thumbnail":1009},{"ext":69,"url":80,"hash":81,"mime":72,"name":82,"path":77,"size":83,"width":84,"height":85,"sizeInBytes":86},{"ext":69,"url":88,"hash":89,"mime":72,"name":90,"path":77,"size":91,"width":92,"height":93,"sizeInBytes":94},{"ext":69,"url":96,"hash":97,"mime":72,"name":98,"path":77,"size":99,"width":100,"height":101,"sizeInBytes":102},{"ext":69,"url":104,"hash":105,"mime":72,"name":106,"path":77,"size":107,"width":108,"height":109,"sizeInBytes":110},[1011],{"text":116,"type":29},{"type":35,"level":36,"children":1013},[1014],{"text":120,"type":29},{"type":25,"children":1016},[1017],{"text":124,"type":29},{"type":25,"children":1019},[1020],{"text":128,"type":29},{"type":25,"children":1022},[1023],{"text":132,"type":29},{"type":35,"level":36,"children":1025},[1026],{"text":136,"type":29},{"type":25,"children":1028},[1029],{"text":140,"type":29},{"type":35,"level":142,"children":1031},[1032],{"text":145,"type":29},{"type":25,"children":1034},[1035],{"text":149,"type":29},{"type":25,"children":1037},[1038],{"text":153,"type":29},{"type":25,"children":1040},[1041],{"text":157,"type":29},{"type":25,"children":1043},[1044],{"text":161,"type":29},{"type":25,"children":1046},[1047],{"text":165,"type":29},{"type":35,"level":36,"children":1049},[1050],{"text":169,"type":29},{"type":25,"children":1052},[1053],{"text":173,"type":29},{"type":25,"children":1055},[1056],{"text":177,"type":29},{"type":25,"children":1058},[1059],{"text":181,"type":29},{"type":25,"children":1061},[1062],{"text":185,"type":29},{"type":66,"image":1064,"children":1070},{"id":188,"ext":69,"url":189,"hash":190,"mime":72,"name":191,"size":192,"width":193,"height":194,"caption":77,"formats":1065,"provider":111,"createdAt":224,"updatedAt":224,"documentId":225,"focalPoint":77,"previewUrl":77,"publishedAt":226,"alternativeText":77,"provider_metadata":77},{"large":1066,"small":1067,"medium":1068,"thumbnail":1069},{"ext":69,"url":197,"hash":198,"mime":72,"name":199,"path":77,"size":200,"width":84,"height":201,"sizeInBytes":202},{"ext":69,"url":204,"hash":205,"mime":72,"name":206,"path":77,"size":207,"width":92,"height":208,"sizeInBytes":209},{"ext":69,"url":211,"hash":212,"mime":72,"name":213,"path":77,"size":214,"width":100,"height":215,"sizeInBytes":216},{"ext":69,"url":218,"hash":219,"mime":72,"name":220,"path":77,"size":221,"width":108,"height":222,"sizeInBytes":223},[1071],{"text":116,"type":29},{"type":35,"level":36,"children":1073},[1074],{"text":232,"type":29},{"type":25,"children":1076},[1077],{"text":236,"type":29},{"type":25,"children":1079},[1080],{"text":240,"type":29},{"type":25,"children":1082},[1083],{"text":244,"type":29},{"type":35,"level":36,"children":1085},[1086],{"text":248,"type":29},{"type":25,"children":1088},[1089],{"text":252,"type":29},{"type":25,"children":1091},[1092],{"text":256,"type":29},{"type":25,"children":1094},[1095],{"text":260,"type":29},{"type":25,"children":1097},[1098],{"text":264,"type":29},{"type":25,"children":1100},[1101],{"text":268,"type":29},{"type":35,"level":36,"children":1103},[1104],{"text":272,"type":29},{"type":35,"level":142,"children":1106},[1107],{"text":276,"type":29},{"type":25,"children":1109},[1110],{"text":280,"type":29},{"type":35,"level":142,"children":1112},[1113],{"text":284,"type":29},{"type":25,"children":1115},[1116],{"text":288,"type":29},{"type":35,"level":142,"children":1118},[1119],{"text":292,"type":29},{"type":25,"children":1121},[1122],{"text":296,"type":29},{"type":35,"level":142,"children":1124},[1125],{"text":300,"type":29},{"type":25,"children":1127},[1128],{"text":304,"type":29},{"type":25,"children":1130},[1131],{"text":308,"type":29},{"type":25,"children":1133},[1134],{"text":312,"type":29},{"type":25,"children":1136},[1137],{"text":116,"type":29},[],[]]