The creator is testing short summaries at the top of blog pages so visitors get the main information before scrolling.
- Test 2-3 sentence summaries and a clear CTA near the top of informational pages, then measure engagement and conversion impact.
Source record

This is how most websites do their blogs. You arrive to your page from Google and it's this big screen before you can get your information...
This is how most websites do their blogs. You arrive to your page from Google and it's this big screen before you can get your information. To get your information you have to scroll and scroll and scroll.
It's often not provided. At the top. You gotta scroll down.
You gotta search through the page to find it. This is what I'm trying. Right there at the top of the page, before you even start scrolling, there is the information you want.
I don't make people scroll and scroll to find their info. They land on my page, they get the information at the top. This strategy works really well with bottom of funnel SEO landing pages.
At the top you have a short bit of info and then a call to action button. But nobody tries doing it with a blog. This is on Reddit.
How adding TL DR boosted my conversions by thirty 3%. For articles, I added a short 2 to 3 sentence summary at the top giving the main points right away. Here's another, and I have the TLDR right here.
At the top. Everyone does this with their blog. I'm trying this follow to see the data Google Analytics gives me for it.
The creator is testing short summaries at the top of blog pages so visitors get the main information before scrolling.
Test 2-3 sentence summaries and a clear CTA near the top of informational pages, then measure engagement and conversion impact.
This is how most websites do their blogs. You arrive to your page from Google and it's this big screen before you can get your information. To get your information you have to scroll and scroll and scroll. It's often not provided. At the top. You gotta scroll down. You gotta search through the page to find it. This is what I'm trying...
Base2026 attributes this public source record to @build_in_public, published 2025-06-09, with the original platform link and correction/removal path kept on the page.