Restore Adsterra placement code and add AdSense verification - #89
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The existing BorderPulse native banner placement was inactive and its current dashboard code uses a different script host. Reactivated the same placement with adult ads disabled and updated the loader to match its current code.
Also adds the account-provided AdSense ownership meta tag and Google ads.txt entry. Google ad serving remains off pending account activation and site review.
Validation: Vite production build and prerender passed; generated homepage and crossing HTML include the publisher tag and dist/ads.txt matches the account entry. Release checks run in CI. Adsterra showed zero impressions and zero revenue for August 29–September 27 before reactivation; no revenue projection is asserted.