← Back to blog
PK-SwiftSEOMonetizationDev Log

SEO, AdSense, and Coffee Buttons Without Looking Desperate

The week PK-Swift improved indexing, social previews, and support widgets while trying not to feel like a billboard.

by Jay2 min readPK·SWIFT B.LOG

Series: PK·SWIFT B.LOG

  1. 1. Smart Parse Saved My Sanity, AI Parse Saved My Weekend
  2. 2. Global UX Is 200 Tiny Fixes: The Day I Removed Two Korean Words
  3. 3. SEO, AdSense, and Coffee Buttons Without Looking Desperate ← you are here
  4. 4. Buy Me a Coffee Setup Playbook for Solo Builders

PK-Swift homepage

There is a phase in every solo product where you quietly ask:

"Should this make money now, or should it make sense first?"

In PK-Swift I tried to do both, carefully.

Key commits from that phase:

  • 27bde58 (2026-02-10): sitemap and URL updates
  • 4be5e4f and 08ff6cd (2026-02-10): AdSense rollout
  • 0b42ded (2026-02-16): canonical/hreflang fix + BMC widget optimization

The kind of SEO fixes that are not optional

One representative diff from 0b42ded:

<link rel="canonical" href="https://pk-analyzer.pages.dev/">
<link rel="alternate" hreflang="en" href="https://pk-analyzer.pages.dev/">
<link rel="alternate" hreflang="ko" href="https://pk-analyzer.pages.dev/">

And social metadata was expanded too:

<meta property="og:url" content="https://pk-analyzer.pages.dev/">
<meta property="og:site_name" content="PK-Swift">
<meta name="twitter:url" content="https://pk-analyzer.pages.dev/">

This is not just "SEO stuff." It affects discoverability, share previews, and credibility.

Monetization without breaking user trust

AdSense script integration was straightforward technically, but product sensitivity was the real work.

A science tool cannot feel spammy. So I used a rule:

  • If monetization distracts from analysis, it is too aggressive.

For the full Buy Me a Coffee implementation details (widget config, banner link, copy strategy, and conversion tracking), I split that into a dedicated post:

  • /posts/pk-swift-buy-me-a-coffee-setup-playbook

Practical Tips for Non-Developers

  • Set canonical and hreflang early; retrofitting SEO later is a tax.
  • Validate social preview tags (og:*, twitter:*) on the same day you ship route changes.
  • Keep sitemap and canonical URLs synchronized whenever domains or paths change.
  • Treat monetization as an iterative experiment, not a one-time switch.

What I learned

Shipping product means writing code, yes.

But it also means deciding what your app should feel like when someone opens it for the first time.

I want PK-Swift to feel like a lab partner, not a vending machine.

← All posts