[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],[],[[["While not mandatory, implementing an ads.txt file is recommended as many advertisers prioritize ads.txt verified ad requests."],["Platforms with numerous child accounts can manage ads.txt by registering their domains on the Public Suffix List or getting whitelisted by AdSense for `data-ad-host` verification."],["Registering on the Public Suffix List requires placing ads.txt files on each subdomain, typically containing the child publisher ID unless AdSense whitelisting is also utilized."],["AdSense whitelisting enables ad request verification based on either `data-ad-client` or `data-ad-host`, allowing platforms to use a single ads.txt entry with the host publisher ID."],["This scalable solution using `data-ad-host` applies only to platform domains, while custom domains still require the child publisher ID in their ads.txt files."]]],["Ads.txt files list publisher IDs authorized to request ads on a domain. Platforms can manage this with two options: registering on the Public Suffix List or using special ads.txt treatment. Public Suffix List registration requires ads.txt files on each subdomain with child publisher IDs. Special treatment allows whitelisted domains to verify requests using `data-ad-host` or `data-ad-client`, needing only one entry with the host ID. This solution works only for platform domains. Google manually maintains the platform domain list.\n"]]