Blog
Publisher tools, thoughtfully built

Sellers.json, Schain & GAM Tag Checkers

Investigate seller declarations and ad-tag setup with separate checks for sellers.json, OpenRTB SupplyChain JSON and Google Publisher Tag code. Keep structural findings distinct from identity and delivery verification.

Explore all toolsNo signup required
20 purpose-built toolsLocal-first privacyIndependent diagnostics

Understand the seller declarations behind an ad request

ADXLens brings seller-ID lookup, SupplyChain structure validation and static Google Publisher Tag inspection together. Use the findings to investigate declarations and setup issues, then verify identities and commercial relationships separately.

Sellers.json checker · SupplyChain validator · GAM tag inspector

Follow the evidence through the advertising supply chain

  1. Look up a seller declaration

    Inspect an exact seller ID in a supported live sellers.json source or pasted JSON. Treat confidential fields as unknown.

  2. Validate a SupplyChain object

    Review the structure and declared node fields in the JSON you provide. Verify identities and payment relationships separately.

  3. Inspect GPT setup without running code

    Read recognizable ad-unit paths, sizes and calls. Use actual browser and platform diagnostics for delivery questions.

Questions about ADXLens

Do ads.txt, sellers.json and schain show the same thing?

No. They describe different parts of the advertising supply chain. Compare the relevant identifiers and scope rather than treating one valid file as proof of the whole path.

Can these checks prove that an ad request will fill?

No. Seller declarations and static tag structure do not establish demand, targeting eligibility or an auction outcome.

Operated by Vivek Kushwah. Independent publisher utilities with transparent inputs and limitations. Read the method and official reference on each tool page.

Everything you need. Nothing you don’t.

Search, calculate, validate. Choose a tool to get started.

20 of 20 tools

Useful evidence. Clear limits.

Choose a tool, enter your own numbers or public website information, and review the result. Every report separates what was observed from what still needs a human review. No invented approval scores.

Your inputs stay yours.

Calculations and pasted-text checks run in your browser. Live scans send only your supplied public domain to the configured backend. We never ask for Google passwords, account access or API keys.

Publisher tools: methods & instructions

AdX Readiness Checker

Checks HTTPS, homepage text, recognizable policy links, ads.txt and indexing directives. A fetched link is evidence of a link, not a review of its contents.

Open AdX Readiness Checker →

AdSense Website Readiness

This advisory review cannot inspect your AdSense account, verify content rights or determine approval. Review Google policies manually.

Open AdSense Website Readiness →

Ads.txt Live Checker

Retrieves the root /ads.txt over HTTPS. Syntax does not prove seller authorization. Network failures and missing files are reported separately.

Open Ads.txt Live Checker →

Ads.txt Syntax Validator

Paste plain text to check three required seller fields, the optional certification ID and supported ads.txt 1.1 directives. Runs locally.

Open Ads.txt Syntax Validator →

Ads.txt Generator

Use the advertising-system domain and seller account ID supplied by your monetization provider. We never generate or verify real seller IDs.

Open Ads.txt Generator →

App-ads.txt Checker

Fetches /app-ads.txt from the supplied developer domain. App-store developer website links, ownership and package identity need separate verification.

Open App-ads.txt Checker →

Sellers.json Checker

Checks a domain’s root /sellers.json, or pasted JSON. Confidential entries may legitimately omit name and domain; confidentiality alone is not evidence of fraud. Files over 2 MB are explicitly refused by live scans.

Open Sellers.json Checker →

SupplyChain Validator

Supports SupplyChain 1.0 objects and common bid-request wrappers. Validates ver, complete, nodes, asi, sid and hp. Structure alone cannot prove supply-chain authenticity.

Open SupplyChain Validator →

GAM Tag Inspector

Static heuristic inspection of pasted Google Publisher Tag code. The code is never executed. Dynamic paths, comments and variable-based sizes may need manual review.

Open GAM Tag Inspector →

CPM Calculator

CPM = advertising cost ÷ impressions × 1,000. Choose a currency shared by all money inputs. Reverse calculations solve cost or impressions.

Open CPM Calculator →

eCPM Calculator

eCPM = revenue ÷ impressions × 1,000. Uses realized revenue rather than a guaranteed auction price. Reverse calculations are supported.

Open eCPM Calculator →

Page RPM Calculator

Page RPM = estimated earnings ÷ page views × 1,000. Page views and ad impressions are different denominators; this tool calculates Page RPM only.

Open Page RPM Calculator →

CTR Calculator

CTR = clicks ÷ impressions × 100. Use matching reporting periods and scope. This calculator requires clicks not to exceed impressions.

Open CTR Calculator →

Fill Rate Calculator

Default definition: filled ad requests ÷ total ad requests × 100. Platforms may define fill differently; use matching request metrics, not impressions as a substitute.

Open Fill Rate Calculator →

Ad Revenue Calculator

Daily opportunities × assumed fill rate × CPM ÷ 1,000. If impressions are already served, set fill to 100% to avoid counting fill twice. Monthly projection uses 30 days.

Open Ad Revenue Calculator →

Revenue Share Calculator

Revenue × each party’s percentage. Shares must total 100%. The optional 88/12 split is an editable example, not a claimed industry or Google contract.

Open Revenue Share Calculator →

Viewability Calculator

Viewability = viewable ÷ measurable impressions × 100. Measurable impressions are those where viewability could be measured; they are not the same as all served impressions.

Open Viewability Calculator →

CPC Calculator

CPC = total advertising cost ÷ clicks. Choose a calculation mode to solve for CPC, total cost or clicks using a consistent currency.

Open CPC Calculator →

Ad Size Preview

Visual placeholders only: 300×250, 336×280, 320×50, 320×100, 728×90, 970×250, 160×600 and 300×600. Large previews scale down to fit; actual dimensions stay visible. No ads are requested.

Open Ad Size Preview →

Monetization Health Report

Rules-based suggestions use matching live scan results from this browser session and metrics you supply. No fabricated score, AI claim or official eligibility decision. Thresholds are diagnostic heuristics, not Google requirements.

Open Monetization Health Report →

Independent readiness assessment — not an official Google approval decision. Technical findings cannot establish content compliance, traffic quality or monetization eligibility.

Good questions. Straight answers.

Can ADXLens approve my website for AdX or AdSense?

No. Google or the applicable authorized process decides approval. ADXLens offers independent technical checks and manual-review guidance.

Why do live checks need a backend?

Browsers restrict many cross-origin website requests. A configured scanning backend retrieves permitted public files safely. Without it, live tools show “Live Scan Not Configured”; local tools remain usable.

Does a valid ads.txt file prove seller authorization?

No. Valid formatting only establishes that a file follows supported syntax. Confirm the account ID and commercial relationship with the advertising provider.

Are revenue projections guaranteed?

No. They are calculations from your assumptions. Actual demand, geography, viewability, consent, invalid traffic deductions and reporting definitions affect outcomes.

Can these tools rank in Google or appear in AI answers?

Useful original content and sound technical SEO support discovery, but rankings, indexing and AI recommendations are never guaranteed. Separate tool pages can be developed later with their own unique explanations and functionality.

Schain Validation: Fix JSON Structure Before Investigating Seller Identity

When SupplyChain JSON fails validation, first decide whether the problem is readable JSON, the supported object structure or an unresolved identity question. Those require different actions. Editing a seller ID to silence an error can hide the original evidence.

Keep the original request evidence

Save the original privately where appropriate, then isolate the SupplyChain object you are authorized to inspect. Remove unrelated credentials or sensitive request data before using a public tool. Our schain validator does not execute supplied code.

Three layers to check

  1. JSON syntax: compare brackets, quotes and commas. A copied fragment may not be a complete JSON value.
  2. Supported structure: the checker supports version string 1.0, integer completeness values and a nonempty nodes array. Read each field-level result.
  3. Identity: compare declared seller information separately with relevant evidence and the provider’s explanation.

Consult the IAB SupplyChain object specification for the field meanings. A completeness flag is the supplied declaration, not the checker independently certifying every participant.

A controlled correction example

Suppose a copied object uses the text "1" for a completeness value. This tool expects the supported integer form. First compare the original source and determine why the type changed. Do not rewrite an actual transaction’s evidence and then describe the edited object as the original request.

For reproducible testing, keep the original, a clearly labelled corrected test copy and the specific result from each. A successful test explains the parser difference; it does not prove a commercial relationship.

What happens after structural errors are fixed?

Use the seller-ID checker to investigate relevant public declarations where appropriate. Record confidential or missing data as unresolved rather than inventing a seller name. Request-level validation cannot establish visitor quality or guarantee an auction outcome.

Official references

References checked: 26 October 2026. Examples identified as fictional are teaching inputs, not performance benchmarks.

← Back to all articles

Publisher tool