Skip to content

feat: AdSense verification + advertising privacy disclosure - #167

Merged
fatblaine merged 2 commits into
devfrom
feat/adsense
Aug 6, 2026
Merged

fatblaine merged 2 commits into
devfrom
feat/adsense

Conversation

@fatblaine

Copy link
Copy Markdown
Owner

What

Register SuburbLens with Google AdSense — ownership verification and the required advertising disclosure. Three files:

  • frontend/index.html — add the AdSense loader <script> to <head>. prerender uses the built index.html as its template, so it propagates to all 1494 suburb pages.
  • frontend/public/ads.txt — declare Google as an authorised seller.
  • frontend/src/pages/PrivacyPage.tsx — disclose advertising.

Why

The site is registered in AdSense and needs (1) ownership verification before Request review — the script is the "AdSense code snippet" method and is also the library that serves ads post-approval; (2) ads.txt, or the account shows a persistent "unauthorized sellers" warning; (3) an ads + cookies disclosure, since the old "there is no advertising" wording becomes false once ads run. This privacy page is also the Chrome Web Store policy, so all ad wording is confined to the website and the extension is stated to carry no ads.

Verification/disclosure only — ad units and the AdSlot component come after approval.

How to test

  • cd frontend && npm run build — passes; confirm the AdSense <script> is present in dist/index.html and dist/ads.txt exists.
  • After deploy: curl -s https://www.suburblensapp.com/ads.txt returns the pub line; any suburb page's source contains adsbygoogle.js?client=ca-pub-5982385876517812.
  • Open /privacy — the "In short" advertising bullet, the new "Advertising" subsection, the Google AdSense processor row, and the ads-aware "we do not sell" paragraph all render.

Once AdSense ads run, the "there is no advertising" statements become
false, and reviewers require an ads + cookies disclosure (adsense-plan
§4). This page is also the Chrome Web Store privacy policy, so all ad
wording is confined to the website and the extension is stated to carry
no ads.

- split the "In short" analytics bullet, add a website-only ads bullet
- new Advertising subsection: AdSense funding, third-party cookies,
  opt-out links, and EEA/UK/CH consent
- add a Google AdSense row to "Who processes your data"
- replace the "we do not sell your data" line with an ads-aware version
- bump the last-updated date
Site is registered in AdSense (publisher ca-pub-5982385876517812) and
needs ownership verification plus an authorised-seller declaration before
requesting review (adsense-plan §3.1 / §3.2).

- add the AdSense loader script to index.html's <head>; prerender uses
  the built index.html as its template, so it propagates to every suburb
  page automatically
- add public/ads.txt so the site declares Google as an authorised seller
  and the account stops warning about unauthorized sellers

Ad units come after approval; this is verification only.
@fatblaine
fatblaine requested a lite review from Copilot August 6, 2026 07:25
@fatblaine fatblaine self-assigned this Aug 6, 2026
@fatblaine fatblaine added documentation Improvements or additions to documentation enhancement New feature or request labels Aug 6, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@fatblaine, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: b3f021fc-5fc5-496a-babf-1805f5bced64

📥 Commits

Reviewing files that changed from the base of the PR and between de189c3 and f8069b3.

📒 Files selected for processing (3)
  • frontend/index.html
  • frontend/public/ads.txt
  • frontend/src/pages/PrivacyPage.tsx

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@fatblaine
fatblaine merged commit 8edbcb7 into dev Aug 6, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants