How to Check Which Posts Generate AdSense Revenue (URL Channel Registration)

When you visit your AdSense site, you can immediately see how much revenue was generated each day. However, you cannot tell which posts generated revenue or how much they earned. To resolve this issue, you must register URL channels. Now, let’s discuss how to check which posts are generating AdSense revenue.

AdSense revenue

If you run a Tistory or WordPress blog and have even received AdSense approval, you’ll likely check the AdSense site frequently to monitor your earnings.

“Wow, I earned this much today.” Even if you manage multiple blogs, you can set the date in the site-specific performance section of the report to see how much each blog earned that day.

However, you couldn’t see which specific post on that site generated the revenue or how much it earned until you registered the URL channel. This is precisely why we need to register our blog posts to URL channels.

How to Check Which Posts Generate AdSense Revenue

To check which posts generate AdSense revenue, you need to register URL channels. Think of URL channels as the addresses of your blog posts.

URL Channel Registration Order

1) Access URL Channel Management in AdSense Reports

After logging into your AdSense site, click Reports in the left menu. Once you’re in Reports, you’ll see a gear icon (Settings) in the top right corner. Click it and select URL Channel Management.

2) Add URL Channel

Click the blue Add Channel button shown above.

3) Enter the URL of the blog post you wish to register

Enter the URL address of the blog post you wish to register in the URL field. For Tistory, even if you create a separate posting URL address, a numerical URL that links to the same page is automatically generated by default.

For example, let’s say you’ve posted 100 articles.

Tistory automatically generates URL addresses such as apple.tistory.com/1 through apple.tistory.com/100. Instead of registering these generated addresses one by one, simply type apple.tistory.com/1 into Excel, scroll down to create addresses up to 100, and copy-paste them.

Alternatively, you can copy and paste URLs you’ve created yourself instead of using numbers. However, if you use a Korean URL, characters may appear garbled after registration, and you’ll have to input each address individually. If you’re unsure

what this means, try typing your Tistory blog URL (e.g., yourblog.tistory.com/1) into your browser’s address bar and press Enter. You’ll see which page it connects to.

After registering your desired blog post, you can view the registered (active) pages on the URL channel management page.

Check posts generating AdSense revenue

To check which posts generate AdSense revenue, go to the reports section and navigate to the URL channel item. You can also specify the date like I did. If you entered

the Korean address directly into URL Channel Management, the address will appear in a foreign language, like the title of my top blog post. If you registered

numbers, they will appear as numbers, like the second and third entries. In my case, you can see that the URLs with addresses 215 and 301 generated revenue on that day.

Why URL addresses are good in English

For WordPress blogs, I write URLs in English. This is because it’s convenient when checking which posts generate AdSense revenue. When

posts appear in Korean, the URLs get garbled. By copying the URL and pasting it into the address bar, I can immediately identify what the post is about. The same applies to numeric URLs.

However, English URLs don’t break like Korean ones do. Just by looking at the URL address, I can immediately recognize what the post is about, allowing me to quickly identify which posts are generating AdSense revenue.

Conclusion

Today, we discussed how to check which posts generate AdSense revenue. You can register up to 500 URL channels. If you wish to register more, simply delete URLs from existing blog posts that generate little to no revenue. If deletion is difficult due to circumstances

, deactivating them allows you to register additional URLs equal to the number deactivated. Please try this method.