Jatify AdSense rejected my site. Here's what I changed. Blog
← Back

AdSense rejected my site. Here's what I changed.

Google turned jatify.com down for ads on screens without content and for low-value content. What those two lines meant for this site, and the changes that came out of them.

Alexandru Martalogu · 1 November 2026

On 31 October 2026 Google AdSense turned this site down. The email gave two reasons:

  • Google-served ads on screens without publisher content
  • Low-value content

Neither comes with a list of pages or a score. So I went through the site the way a reviewer would, page by page, and asked of each one: what is a reader here for, and is there an ad on it? This post is what I found and what I changed. I haven’t asked for a new review yet, so I can’t tell you it worked. I can tell you what changed and why.

Why a portfolio site has ads at all

Fair question. This site isn’t here to make money, and a few ads on its posts won’t. The ads are an experiment: I wanted to understand how AdSense actually works from the publisher’s side, and how search can turn a small site’s content into ad revenue. That means classic SEO, getting pages found and ranked by Google, and the newer GEO (generative engine optimization): getting a site’s content picked up and cited by AI assistants and Google’s AI answers.

Reading about it only gets you so far. Running it on a real site with real pages, real Search Console data and a real rejection email teaches a lot more, and this post is the first thing it taught me.

What the site looked like

Jatify started as a homepage for my projects. The homepage is a carousel of cards, one per project, and most of the text lives inside those cards. The Valheim mods had their own pages, built from each mod’s README on GitHub. A few cards were placeholders for things that weren’t out yet.

For ads, a cookie banner on every page asked for consent, and once you accepted, the AdSense script loaded on whatever page you were on: the homepage, the list of mods, the privacy policy, all of it.

Read with the two rejection reasons in mind, the problems are easy to see.

Ads on screens without content

The homepage is a menu. The list of mods is a menu. The privacy policy is a legal page. None of them is something a person comes to read, and all of them could show an ad. That is exactly the first reason.

The fix was to decide where ads belong and enforce it. Ads now load only on pages people come to read: each mod’s own page, the changelog, and the posts, this one included. Those are pages people stay on for a while, because they’re looking for what a mod does, what changed in the last version, or how something was built. The homepage, the lists, the About page, the project pages and the legal pages have no ads.

“Only on these pages” is easy to say and easy to break later, so it’s a check in the build: after the site is built, a script reads every page and fails the deploy if the AdSense script appears anywhere it shouldn’t, or is missing from a page that should have it.

Low-value content

This one is less mechanical. A placeholder card that says something is coming is low value by definition, so those went first. The rest of the work was adding pages with real substance:

  • A changelog. Every mod already had a CHANGELOG.md in its repository. A sync script now pulls them in, so the changelog page is always the one the release was built from.
  • Notes on how the mods were made. What Jatify UI changes in the game, what went into the 0.3.0 release and how it’s tested, and what the smaller mods do and why they exist.
  • Project pages and write-ups. Brimdock, Argus and Claude Usage Tracker each got a page from their README and a note on how they were built.
  • An About page with my actual work history, and a /projects/ page that lists everything in plain HTML.

Every note is written from the repositories: commit history, tests, release scripts. If I couldn’t point at where a claim came from, it didn’t go in. That rule threw out a few nice-sounding numbers, and the notes are better for it.

Making the site readable for a crawler

The carousel is a JavaScript component. A person sees every project; a crawler that doesn’t run the script sees much less. So the homepage now has a plain menu bar of links to every page with content, and the /projects/ page lists the same things without any JavaScript at all.

Search Console found a few more things once I looked:

  • Pages with redirects. Internal links pointed at /privacy while the page lives at /privacy/, so every click went through a redirect, and Search Console listed those addresses as “Page with redirect”. Every internal link now uses the final address, and the build checks it.
  • A duplicate site. www.jatify.com served the same pages as jatify.com. It now redirects permanently to the bare domain, so Google sees one site, not two copies.
  • A sitemap that matches. The sitemap is written by hand, and the build fails if it lists a page that doesn’t exist or misses one that does.
  • Structured data. Each mod and project page describes itself as a piece of software, and each note as an article, in the schema.org format search engines read. The build checks that it parses.
  • An old side project. A test app on a subdomain had been indexed and was showing up in results for the domain. I took it offline.

Smaller things came along with these: alt text on every image, and a phone layout that opens each project card on its text instead of its pictures.

My own cookie banner worked, but it isn’t what Google wants to see. AdSense has a consent message of its own, from a consent platform Google certifies, and for visitors in Europe, the UK and Switzerland that’s the one that should ask. It now does, with a “Do not consent” button next to “Consent”. For US states with their own privacy laws there’s a second message with a “Do not sell or share my personal information” link. The custom banner is gone, and the privacy policy describes what actually happens.

What I’d tell someone else

  • Ask what each page is for. If the honest answer is “to get somewhere else”, it shouldn’t carry an ad.
  • Put the rules in the build. Ads only on content pages, links without redirects, a sitemap that matches: each is a rule I’d break by accident sooner or later, and a check catches it before Google does.
  • Placeholders are worse than nothing. A card that says “coming soon” adds a page with nothing on it.
  • Write from sources. A note built from commits and test scripts is slower to write than a summary, but every line in it is true.

The next step is to wait until Google has indexed the new pages, then ask for another review. I’ll update this post with the answer.