Above-fold content weight
Content placement affects both what people read and how the page is assessed. A page whose substance starts 900px down is judged on whatever sits above it. This skill measures what is actually visible first and rebalances.
Use when a page has strong content that begins only after a large hero, carousel or announcement bar.
The skill file
What you need first
- The page at 375px and at a common laptop height
- Its heading and body structure
Method
- 01 Load the page at 1366x768 and 375x812 and record the vertical position of the H1, the first body paragraph and the primary call to action.
- 02 Measure how much of the first screen is spent before the first substantive sentence. Anything over half is a problem.
- 03 Identify what occupies that space. Announcement bars, oversized heroes and decorative blocks are the usual causes.
- 04 Check whether promotional elements outrank the value proposition - a feature announcement written for existing users sitting above the explanation of what the product is.
- 05 Rebalance by moving promotional and secondary elements below the primary message rather than by shrinking the hero, which usually damages the design.
- 06 Re-measure at both sizes and confirm the primary call to action is fully above the fold on a 768px-tall screen.
What this produces
Measured positions before and after, with the specific elements moved and the reason each was demoted.
Where this goes wrong
- Measuring only on a large desktop monitor where everything fits
- Shrinking type to fit more in, which trades one problem for another
- Assuming a tall hero is always wrong - it is only wrong when it delays the message
Use this skill in your own AI
The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.
Questions about this skill
When is measuring the fold the right method rather than shrinking the hero?
When a page has good content that only starts after a hero, carousel or announcement bar. The reflex is to shrink the hero or the type, which damages the design and trades one problem for another. Measuring where the H1, first paragraph and primary call to action actually land at two real viewport sizes tells you what to move instead.
What do I need in hand before starting?
The page loaded at 1366x768 and 375x812, and its heading and body structure. Measuring on a large desktop monitor only is how this gets signed off wrongly, because everything fits on a tall screen and nothing fits on a laptop. You also need to know which elements are promotional, since that is the judgment about what gets demoted.
What do I end up with, and which part gets used?
Recorded vertical positions before and after at both sizes, with the elements moved and why each was demoted. The before and after numbers are the part that gets used, because this argument is usually with a designer and a measured 900px delay is harder to wave away than an opinion that the hero feels too tall.
What most often ruins this?
Treating a tall hero as automatically wrong. It is only wrong when it delays the message, and a large image that carries the message is doing its job. The expensive version of this mistake is stripping a hero a team spent weeks on, seeing no change, and losing the credibility to ask for the next layout change.
More in On-page SEO
Title rewrite diagnosis
Use when Search Console shows impressions for a page but the title in results is not the title y...
Keyword cannibalisation resolution
Use when two or more of your pages trade places for the same query, or when a page that used to...
Internal link equity audit
Use when important pages are buried deep in the site, or when new content takes weeks to be inde...
Intent mismatch repair
Use when a page ranks on page one but gets almost no clicks, or gets clicks and immediate bounce...