Skip to content

AdSense site review and resubmission runbook

Status: Active review procedure. Dashboard state and provider policy must be checked at the time of each review or resubmission.

Audience: Product, privacy, and operations owners responsible for AdSense review.

Last reconciled: 2026-09-13

Related documents:

Revalidate these official requirements when live integration begins because provider behavior and policy can change:

This runbook records the operational AdSense review process. Passing a site review and serving ads are separate milestones. Nothing in this document authorizes enabling advertising, publishing a CMP message, changing production feature flags, or deploying a branch without the usual review.

Current state

As of 2026-09-13:

  • The active publisher identifier is ca-pub-3785916341303123.
  • The root layout publishes that identifier through the google-adsense-account metadata field.
  • https://verbolus.com/ads.txt publishes exactly:
google.com, pub-3785916341303123, DIRECT, f08c47fec0942fa0
  • AdSense site ownership has been verified.
  • The first site review did not approve the site. The dashboard returned the site to Requires review and separately displayed ads.txt as Not found. Google supplied no specific policy or content reason, and the Policy Center displayed no current issues.
  • A human browser could retrieve the correct public ads.txt record. That fact does not establish when Google's AdSense crawler last fetched it or why the dashboard reported Not found.
  • Do not record speculative explanations—SPA routing, response headers, container cold start, or content depth—as the rejection reason unless crawler logs or Google provide evidence.
  • The account-level AdSense JavaScript is prepared on the submitted homepage entry point and pages with implemented placements: both launched game routes, both How-to-Play guides, and substantial Update articles. It is present for site review only; no ad unit markup, slot ID, or adsbygoogle.push request exists.
  • Auto Ads must remain disabled in the AdSense dashboard until that product decision is made.
  • Google's certified CMP has not been configured or published. The existing Verbolus analytics consent control is not a replacement for the AdSense TCF/CMP flow.
  • Privacy discloses the active account-level review script and distinguishes it from ad-unit requests and displayed advertising. It must be reviewed again against the actual CMP and live serving behavior before live requests begin.
  • The inert desktop gameplay rehearsal now uses one shared 1,600px-and-wider layout for both games, with a 150px game-to-rail gutter and a neutral, non-interactive 300×600 preview. This is not a live placement approval.
  • The follow-up content/indexing work is deployed. A pre-script production audit confirmed the root seller record, robots file, and sitemap return 200 without setting a player cookie. All 17 sitemap URLs return 200 with a distinct title, self-canonical URL, and publisher meta tag. After the account-script change is deployed, repeat the route-scope checks below before requesting review.

Implemented review foundation

The following work supports review without enabling advertising:

Area Implemented behavior
Ownership Global publisher metadata and the root Google seller record are present. The account script is centralized and rendered by the homepage review entry point and implemented placement boundaries.
Static crawler endpoints Explicit /robots.txt and /sitemap.xml are published. /ads.txt is excluded from the application identity proxy so a crawler fetch does not create a Verbolus player cookie.
Public discovery The homepage contains a concise product description and separate, crawlable Play and How-to-Play links for each launched game. Letter Golf appears first; playable Reverse Cross is not mislabeled as a preview.
Original content Letter Golf and Reverse Cross have public instructional guides; About, Contact, Privacy, Updates, and Terms are public and linked through site navigation where appropriate.
Legal/trust content Privacy describes the current data model and choices, discloses the account-level AdSense review script, and distinguishes it from future ad-unit requests. It covers cookies, web beacons, IP addresses, identifiers, purposes, partners, and the still-deferred certified CMP. Terms covers guest/account play, game records, acceptable use, user content, payments/subscriptions, third parties, availability, and contact paths. Both are product baselines, not substitutes for jurisdiction-specific legal review.
Metadata Public pages have distinct titles, useful descriptions, and self-canonical URLs. Personal, transactional, prototype, Settings, Groups, Account, Support, and Thank-you surfaces are marked non-indexable. Published update articles have their own metadata.
Dynamic game routes Initial loading HTML keeps the game identifiable with one useful rules sentence and a visible How-to-Play link. Game-shaped skeletons avoid a blank or generic loading screen.
Failure recovery Both games provide useful failure copy, How-to-Play access, and a Retry action that performs a full document reload rather than relying on a cached Next.js segment reset.
Regression coverage Tests cover publisher metadata, ads.txt, robots, sitemap membership/exclusions, proxy exclusion, metadata/canonicals, game-card link structure, route loading content, skeleton semantics, full-reload recovery, legal-page discovery, and key Terms clauses.

Relevant implementation history:

  • 550aa5d — publish crawl metadata and exclude ads.txt from the identity proxy.
  • 3193865 — add scalable homepage game-discovery content.
  • 9c8bfdc — present playable Reverse Cross as launched.
  • 1fb5f6d — add public Terms of Service.
  • 9005768 — define metadata and indexing boundaries.
  • 848a54a — add game-shaped loading states.
  • b517aaa — explain and recover from puzzle loads.
  • a4809e9 — protect public game recovery and legal flows with focused tests.
  • 337bd2c — disclose planned Google advertising without claiming it is active.
  • 0ed0451 — rehearse one neutral desktop rail with a 150px game separation.

Pre-resubmission checklist

Do not request another review from a local branch. Complete these steps against the deployed production revision.

  1. Merge and deploy the reviewed AdSense account-script change.
  2. Record the deployed commit or image tag and deployment time.
  3. Check the root seller record without cookies or authentication:
curl -i https://verbolus.com/ads.txt

Require 200, a plain-text content type, the exact single seller line above, no redirect loop, and no Set-Cookie response header. 4. Check crawler discovery:

curl -i https://verbolus.com/robots.txt
curl -i https://verbolus.com/sitemap.xml

Require 200; robots must allow the site and reference the production sitemap; the sitemap must list the homepage, launched games, both guides, About, Contact, Privacy, Terms, Updates, and published update articles while excluding personal and prototype surfaces. 5. Fetch or view source for the homepage, both game routes, both guides, About, Contact, Privacy, Terms, and Updates. Confirm useful visible content, working navigation, distinct titles, descriptions, and canonical URLs. 6. Confirm the global publisher ID still matches the current AdSense account exactly. 7. View source for the homepage, both launched game routes, both How-to-Play guides, and every substantial Update article. Confirm the document head contains exactly one async account script with client=ca-pub-3785916341303123 and crossorigin="anonymous". Confirm the script is absent from short Update articles, the Updates index, About, Privacy, Settings, account, and Groups routes. 8. Confirm there is no <ins class="adsbygoogle">, manual slot ID, or adsbygoogle.push call on any route, and confirm Auto Ads remains disabled in the AdSense dashboard. 9. Confirm the AdSense Policy Center has no listed issue. An empty Policy Center is useful evidence but does not itself mean the site is approved. 10. Allow for dashboard/crawler lag after deployment. Record AdSense's ads.txt status and its displayed last-updated time instead of repeatedly changing a correct file. 11. Request review once the deployed checks pass, then record the request date and dashboard state.

During review

  • Keep the production seller record, metadata, route-scoped account script, robots, sitemap, and public routes stable and available.
  • Monitor frontend availability and unusual crawler failures if the hosting logs expose them.
  • Treat scale-to-zero or cold-start latency as a hypothesis only if request logs show a crawler timeout or failed response. Do not change hosting cost or scaling policy solely from an unsupported guess.
  • Avoid repeated resubmissions or speculative content churn while a review is active.
  • Preserve screenshots of dashboard status, ads.txt status, Policy Center state, and relevant dates. Dashboard labels can lag the public endpoint.
  • Google Search Console can help validate general Google crawlability, but it does not replace the AdSense site-review or ads.txt crawler.

If another review is unsuccessful

  1. Record the exact dashboard status, status details, notification email, and timestamps.
  2. Check Policy Center and every available site-status detail before changing code.
  3. Re-run the production checklist above from a clean session and, where useful, more than one network.
  4. Inspect production request logs for Google crawler responses if available. Record evidence such as status, duration, redirect, or timeout; do not record guessed user agents or causes as fact.
  5. Compare the deployed site with the current AdSense Program Policies and site-readiness guidance.
  6. Make a material, evidence-based correction before resubmitting. Do not simply press Review again against an unchanged revision.

Post-approval live-ad launch

An AdSense Ready status completes external site review only. It does not authorize an ad request. Perform this sequence in order; keep AdsEnabled false until the final production step.

1. Prepare the AdSense and CMP configuration

  1. Record the approved site status, publisher ID, date, and dashboard screenshots.
  2. Create one manual content-page ad unit for the first experiment. Record its public slot ID in configuration; do not add gameplay or post-completion units yet.
  3. Keep Auto Ads disabled.
  4. In AdSense Privacy & messaging, create a Google-certified European regulations message targeting the EEA, UK, and Switzerland. Use the Verbolus name/branding, the production Privacy URL, required languages, and three first-page choices: Consent, Do not consent, and Manage options.
  5. Keep message optimization and optional custom ad-technology vendors disabled unless a later reviewed experiment requires them. Review every generated screen and vendor/purpose link.
  6. Save the CMP message as a draft. Do not publish it before the application can coordinate it with the existing Verbolus consent experience.

2. Implement while every live-ad flag remains off

  1. Establish denied Google consent defaults before Analytics, CMP, or advertising code can run. Use Basic Consent Mode initially; do not add cookieless advertising pings as an incidental consequence of this launch.
  2. Add one consent coordinator that owns the states checking, google-cmp, verbolus, consented, denied, and unavailable. Use the provider-supported CMP/TCF integration to determine which surface governs the user; do not build a separate GeoIP classifier.
  3. Suppress the Verbolus banner when Google's message is authoritative. Outside that region, retain the existing Verbolus choice. An unresolved, timed-out, blocked, or failed CMP state must fail closed without breaking gameplay.
  4. Make Settings reopen the authoritative consent surface for the current user. Do not show or persist two conflicting consent choices.
  5. Update the Privacy Policy's site-review wording with an accurate description of the configured, active Google advertising behavior. Verify state-law sale/sharing and opt-out language against the chosen ad mode.
  6. Add one idempotent, centrally managed live-ad coordinator. Reuse the centralized account script; keep public publisher and manual slot IDs in one configuration boundary rather than pasting code into individual pages.
  7. Require production environment, AdsEnabled, placement flag, ad-free entitlement, eligible route/surface/viewport, and resolved consent before requesting each unit. The account-level review script remains independent of these live-serving gates.
  8. Add one declarative manual unit to an approved substantial How-to-Play or Updates page. Keep gameplay rail and post-completion flags disabled for this first live experiment.
  9. Narrowly update Content Security Policy for the currently documented Google endpoints. Do not pass Verbolus identity, group, puzzle, score, or game-state data to the provider.

3. Test the disabled production candidate

Deploy the complete integration with AdsEnabled: false, then verify:

  • no ad unit request occurs while any eligibility gate is false;
  • the route-scoped account script remains de-duplicated and no manual request occurs until all gates pass in controlled test/provider-preview modes;
  • EEA/UK/Switzerland consent, refusal, manage-options, revocation, timeout, blocked-provider, and unavailable cases never produce competing dialogs or fail open;
  • Settings reopens the correct consent surface;
  • client navigation, back/forward navigation, and repeated Practice puzzles do not duplicate the account script or a unit request;
  • prohibited, private, transactional, account, Settings, Groups, Privacy, Support, Thank-you, active-gameplay, and post-completion surfaces remain ad-free;
  • no-fill and blockers collapse or reserve space according to the placement contract without causing application errors;
  • accessibility, light/dark themes, supported phones, 200% zoom, performance, and CSP behavior pass review;
  • turning AdsEnabled off prevents every new unit request on both a fresh load and an already-running session.

Never click a live ad, ask another person to click one, or automate live impressions/clicks during validation.

4. Publish and enable in controlled order

  1. Publish the reviewed CMP message while AdsEnabled remains false.
  2. Verify the production Privacy copy and Settings reopening flow, including a controlled EEA/UK/Switzerland scenario, and confirm that only one consent surface appears.
  3. Exercise the master kill switch once in production.
  4. Enable only AdsContentPages and the single manual unit for a small, stable eligible cohort. Keep Auto Ads, desktop gameplay rail, and post-completion disabled.
  5. Monitor consent outcomes by category, loader failures, request/no-fill behavior, layout shift, page performance, complaints, and policy/dashboard status without logging consent strings or unnecessary personal data.
  6. Widen the cohort only after the observation window is healthy. Treat the desktop rail and post-completion placement as separate later experiments with independent review and flags.

What approval does not do

Before the first real request, the separate plan in advertising-strategy.md still requires:

  • a reviewed and published Google-certified CMP flow for applicable regions;
  • one consent coordinator so Google's message and the Verbolus banner never compete;
  • an idempotent, centrally managed live-ad coordinator and manual-unit request path;
  • manual ad units rather than Auto Ads;
  • AdsEnabled, placement, viewport/surface, ad-free-entitlement, and consent gates;
  • CSP, privacy, Settings/revocation, no-fill, blocker, performance, and accessibility validation;
  • a tested master kill switch that prevents every ad unit request.

Until those pieces ship together, keep AdsEnabled off and continue using inert house-ad previews only for the explicitly targeted internal cohort.