ads.txt / app-ads.txt Validator
Ek ads.txt ya app-ads.txt file ko line by line apne browser mein validate karein. Jo file aap paste karte hain woh aapke device par rehti hai.
ads.txt / app-ads.txt Validator poori tarah aapke browser mein chalta hai. Jo file aap paste karte hain woh aapke device par parse aur check hoti hai aur kabhi ArrayKit ko upload ya kisi remote URL se fetch nahi ki jaati.
sellers.json Validator kholein
ads.txt Validator ke baare mein
ads.txt / app-ads.txt Validator aapki Authorized Digital Sellers file ko us pal lint karta hai jab aap use paste karte hain. Yeh har line par chalta hai, DATA records ko unke comma-separated fields mein split karta hai, aur confirm karta hai ki har ek mein required 3 ya 4 fields hain: advertising system domain, publisher account id, ek DIRECT ya RESELLER relationship, aur ek optional certification authority id jaise ek TAG-ID. Comments aur blank lines skip ho jaate hain, VARIABLE lines jaise OWNERDOMAIN, CONTACT, SUBDOMAIN, MANAGERDOMAIN aur INVENTORYPARTNERDOMAIN parse hoti hain, aur wrong field counts, bad relationship values, duplicate entries aur stray whitespace ko line number aur ek suggested fix ke saath flag kiya jaata hai. Ek summary DIRECT vs RESELLER records aur unique seller domains ki ginti karti hai. Publishers aur ad-ops teams apni file yahan audit karti hain bina use kisi third-party crawler ko post kiye — har check aapke device par chalta hai.
Features
- Validate karta hai ki har DATA record mein bilkul 3 ya 4 comma-separated fields hain
- Confirm karta hai ki relationship field DIRECT ya RESELLER hai aur casing normalize karta hai
- VARIABLE lines parse karta hai: CONTACT, SUBDOMAIN, OWNERDOMAIN, MANAGERDOMAIN, INVENTORYPARTNERDOMAIN
- Comments (#) aur blank lines ko waise skip karta hai jaise ek ads.txt crawler karta hai
- Duplicate seller records flag karta hai aur pehli line par point karta hai jahan woh appear hue
- Stray whitespace padding aur non-domain-looking advertising system fields par warn karta hai
- DIRECT vs RESELLER counts aur unique seller domains ki sankhya summarise karta hai
- File ko poori tarah aapke browser mein parse karta hai — jo aap paste karte hain woh upload nahi hota
ads.txt Validator kaise use karein
- Apni ads.txt ya app-ads.txt file paste karein, ya format dekhne ke liye sample load karein
- error aur warning counts ke liye verdict banner padhein
- Har flagged line ko suggested correction se fix karne ke liye Findings kholein
- DIRECT, RESELLER, aur unique domains ke summary counts check karein
Example
Input
google.com, pub-0000000000000000, DIRECT, f08c47fec0942fa0
appnexus.com, 3456, RESELLER
badexchange.com, 99, PARTNER
Output
2 records valid
Line 3 — Relationship must be DIRECT or RESELLER (found "PARTNER").
Teesra field DIRECT ya RESELLER hona chahiye; PARTNER reject ho jaata hai.
Common errors aur troubleshooting
- Ek line par "Expected 3 or 4 fields" jo complete lagti hai. — Fields comma-separated hote hain, space- ya tab-separated nahi. domain, account id, aur relationship ke beech ek comma daalein, aur koi extra trailing fields hatayein.
- Ek record flag hota hai bhale hi relationship DIRECT padhta ho. — Ek stray character ya galat keyword check karein — sirf DIRECT aur RESELLER valid hain. Lower-case direct/reseller accept hota hai lekin validator warn karta hai taaki aap use normalize kar sakein.
- Un lines par duplicate warnings jo sirf TAG-ID mein alag hain. — Duplicate detection domain, account id, aur relationship use karta hai. Same seller tuple wali do lines duplicates hain bhale hi certification authority id alag ho — ek rakhein.
- Ek subdomain ke sellers buyers dwara nahi uthaye ja rahe. — Har delegated subdomain ko ek SUBDOMAIN=sub.example.com variable line se declare karein taaki crawlers jaanein ki us subdomain ki apni ads.txt fetch karni hai.
Aksar pooche jaane wale sawaal
- ads.txt Validator har line par kya check karta hai?
- Har DATA record ke liye yeh verify karta hai ki 3 ya 4 comma-separated fields hain — advertising system domain, publisher account id, ek DIRECT ya RESELLER relationship, aur ek optional certification authority id — phir wrong field counts, bad relationship values, duplicates, aur stray whitespace ko line number ke saath flag karta hai.
- ads.txt mein DIRECT aur RESELLER mein kya farak hai?
- DIRECT ka matlab publisher ka us advertising system ke saath ek direct account hai aur woh seller relationship control karta hai. RESELLER ka matlab ek authorized partner apne account ke through inventory resell karta hai. Teesra field bilkul in do keywords mein se ek hona chahiye.
- Kya yeh validator app-ads.txt ke liye bhi kaam karta hai?
- Haan. app-ads.txt ads.txt ke same record grammar use karta hai — same DATA record fields aur VARIABLE declarations — isliye aap koi bhi file paste kar sakte hain aur same checks apply hote hain. app-ads.txt bas aapki app store listing ke developer domain par rehta hai.
- OWNERDOMAIN jaisi VARIABLE lines kaise handle hoti hain?
- KEY=value ke roop mein likhi lines seller records ke bajaye variables ke roop mein parse hoti hain. Validator CONTACT, SUBDOMAIN, OWNERDOMAIN, MANAGERDOMAIN aur INVENTORYPARTNERDOMAIN recognize karta hai, unknown keys par warn karta hai, aur ek variable flag karta hai jiski koi value nahi.
- Ek duplicate ads.txt record kya maana jaata hai?
- Same advertising system domain, publisher account id, aur relationship wale do records — domain par case-insensitively compared — duplicates hain, bhale hi ek certification authority id add karta ho. Validator us pehli line par point karta hai jahan record appear hua taaki aap repeat hata sakein.
- Kya jab main validate karta hoon toh meri ads.txt file upload hoti hai?
- Nahi. Validator file ko aapke device par parse aur check karta hai aur kabhi ek remote ads.txt URL ya ad tag fetch nahi karta. Jo aap paste karte hain woh ArrayKit ya kisi crawler ko nahi bheja jaata.
Related tools
Saare ArrayKit tools