NTE QUICK TOOLS ADSENSE REVIEW EVIDENCE PACKET
Last reviewed: 2026-05-29
Production site: https://ntequicktools.pages.dev
Publisher client: ca-pub-9685799956452365
ads.txt URL: https://ntequicktools.pages.dev/ads.txt
Expected ads.txt line: google.com, pub-9685799956452365, DIRECT, f08c47fec0942fa0
Sitemap: https://ntequicktools.pages.dev/sitemap.xml
Robots: https://ntequicktools.pages.dev/robots.txt
Media kit: https://ntequicktools.pages.dev/media-kit.json
Revenue setup console: https://ntequicktools.pages.dev/advertising/setup/

Purpose
- Give the owner one no-secret packet for the AdSense site-review and ads.txt recrawl gap.
- Separate public site evidence from Google account UI state.
- Avoid repeatedly changing working ads.txt or publisher values while waiting for Google to recrawl.
- Make account-level blockers explicit so the site-side evidence is not mistaken for AdSense approval.

Public evidence the site can prove
- Production HTTPS site is live: https://ntequicktools.pages.dev
- ads.txt is expected at: https://ntequicktools.pages.dev/ads.txt
- Current expected seller line: google.com, pub-9685799956452365, DIRECT, f08c47fec0942fa0
- Site-level AdSense script is configured for: ca-pub-9685799956452365
- Privacy, Terms, Contact, Disclaimer, Advertising, Sources, sitemap, robots, feed, and ads.txt are public.
- Ads are clearly labeled Advertisement and are kept away from tool controls.
- The site states it is fan-made and not affiliated with Hotta Studio or Perfect World Games.
- The site does not use official NTE logos, official screenshots, official key art, copied game UI, or copied guide text.
- 2026-05-29 CST site-side fix: the AdSense script is emitted as a raw static HTML head script for crawler verification, not only a Next.js client-side runtime script.

When AdSense still says ads.txt Not found
- First verify the public URL in a normal browser and with curl.
- Confirm the publisher ID in ads.txt matches the AdSense publisher client without the ca- prefix.
- Do not swap publisher IDs or keep redeploying unless the public file is wrong.
- Google account UI can lag behind the public file. Wait for recrawl or use the AdSense UI action if it offers one.
- Keep a timestamped note of the public ads.txt HTTP 200 check.

Owner-side AdSense review checklist
1. Open AdSense > Sites.
2. Confirm the site URL is exactly the production URL being submitted.
3. Use the AdSense code verification action after the raw head script deployment is live.
4. Confirm site review is requested or still pending, not accidentally left unsubmitted.
5. Confirm ads.txt status again after public ads.txt has returned HTTP 200 for a while.
6. Confirm Auto ads are enabled if the site is relying on the site-level script before manual slots exist.
7. If the account shows a temporary disabled notice or ad serving disabled notice, resolve the visible account action before treating the AdSense path as usable.
8. If the Payments page asks for identity, address, tax, country, or bank details, the owner completes those directly.
9. Do not upload private payment screenshots to the public site or repository.

Latest account UI observation
- 2026-05-29 CST read-only check: AdSense Home and Payments show an account-level temporary disabled notice and say ad serving is disabled.
- 2026-05-29 CST read-only check: Policy Center says there are currently no site policy issues.
- 2026-05-29 CST AdSense Sites detail check: clicking Verify after the previous deployment returned 'Unable to verify your site'. The likely site-side cause was that the public HTML head only contained a preload while the real script was injected after interaction.
- 2026-05-29 CST after deploying the raw static head script: AdSense code verification passed and site review was requested.
- 2026-05-29 CST a Google CMP consent message was created with Agree / Disagree / Manage options for EEA, UK, and Switzerland users.
- This means the public site can still be technically ready, but AdSense cannot generate the first dollar until the account-level blocker is cleared.

Local / public verification commands
curl -I https://ntequicktools.pages.dev/ads.txt
curl -s https://ntequicktools.pages.dev/ads.txt
NEXT_PUBLIC_SITE_URL=https://ntequicktools.pages.dev npm run ad:readiness
NEXT_PUBLIC_SITE_URL=https://ntequicktools.pages.dev npm run adsense:review-evidence
NEXT_PUBLIC_SITE_URL=https://ntequicktools.pages.dev npm run revenue:readiness
NEXT_PUBLIC_SITE_URL=https://ntequicktools.pages.dev npm run live:check

What this packet does not prove
- It does not prove AdSense site approval.
- It does not prove Google has recrawled ads.txt.
- It does not prove Auto ads are enabled in the Google account.
- It does not prove the AdSense account is active or able to serve ads.
- It does not prove ad impressions, clicks, RPM, traffic, payable balance, or first-dollar revenue.
- It does not replace owner-only payment, identity, address, tax, or payout verification.

First-dollar gate after approval
- AdSense site approval must be visible in the account.
- Auto ads or approved manual ad units must be enabled.
- The public site must load the real AdSense script and keep ads clearly labeled.
- AdSense reports must show non-zero estimated earnings for the site before claiming first-dollar ad revenue.