GTMRun

Readable structure & media

Last updated: 2026-11-16

Readable structure (sections with headings) #

Google recommendation

What it is and why it matters #

Clear sections with descriptive headings help people find the answer they came for, and help Google understand what each part of the page is about. Google's guidance on helpful content and on AI features is the same: write for people. It explicitly says you don't need to "chunk" or rewrite pages for AI.

How we check it #

We count <h2> headings in your homepage's initial HTML and pass this check at two or more. On JavaScript-rendered pages we can't see headings, so the check shows not measured.

How to fix #

  • Give each major section its own <h2> that says what's in it, like "How it works", "Pricing" or "Who it's for", instead of "Section 2".
  • Keep one <h1> for the page's main topic, and nest <h3> under <h2>.
  • Lead with the answer. The first lines under a heading should state the point, then support it.

Supporting images or video #

Google recommendation

What it is and why it matters #

Real product screenshots, diagrams or a short demo show what text alone can't, and they build trust. Google recommends supporting content where it genuinely helps the reader. Decorative stock photos don't count.

How we check it #

We look for <img>, <video> or an embedded YouTube player in your homepage's initial HTML. On JavaScript-rendered pages this shows not measured.

How to fix #

  • Add one or two real screenshots of the product doing the job your headline promises.
  • Write descriptive alt text: what the image shows, for someone who can't see it.
  • Compress images (WebP or AVIF) and lazy-load anything below the fold.

Exactly one H1 on the homepage #

Google recommendation

What it is and why it matters #

The <h1> is the page's one main heading. Google says heading structure is for people first, and one clear <h1> is the simplest way to tell a reader (and a screen reader) what the page is about. Several <h1>s on one page usually mean a template reused the tag for styling.

How we check it #

This row is measured by serp's page audit, which renders the page in a browser and counts the <h1> elements it ends up with — so it works on JavaScript-rendered sites too. It passes at exactly one. If serp does not answer, the row shows not measured. Informational, 0 points.

How to fix #

Keep one <h1> with the page's promise; turn the others into <h2> (or a styled <p> when they are not headings at all).

Every image has alt text #

Google recommendation

What it is and why it matters #

alt text describes an image for people who cannot see it and for Google Images. Google's image SEO guidance asks for descriptive alt text on meaningful images; decorative images get an empty alt="" so screen readers skip them.

How we check it #

Measured by serp's page audit on the rendered page: the number of <img> elements without an alt attribute. It passes at zero (a page with no images passes — there is nothing to fix). If serp does not answer, the row shows not measured. Informational, 0 points.

How to fix #

Write what the image shows, for someone who cannot see it: alt="Dashboard showing three approved drafts for this week", not alt="image1". Decorative images: alt="".

Verify it yourself #

curl -s https://yourdomain.com/ | grep -o '<h2' | wc -l
curl -s https://yourdomain.com/ | grep -c '<img'
curl -s https://yourdomain.com/ | grep -o '<h1' | wc -l

Runs GTMRun's own checks only — seconds, no third-party calls.

Tips #

  • First-hand beats generic. Google's helpful-content guidance favors original information: your own data, screenshots and results. That's hard to fake and it compounds.
  • Don't pad. There's no word-count target. Say what's useful and stop.

Sources #