Tools help·4 min read

THINN - how it works

How THINN samples hub pages for thin body, multiple H1s, noindex hubs and weak titles - then splits Do-this into Marketing vs Dev tickets.

Nikko Nanji

Nikko Nanji - technical SEO consultant

Published - Updated - Last reviewed

Under the hood: Inside THINN: what "thin" means in code

What does THINN do?

THINN is a free tool for hub and listing pages that look thin or messy in the live HTML - weak body copy, multiple H1s, noindex hubs, missing titles.

You paste URLs. THINN fetches each page live, scores it, and hands you a Do-this with an owner: Marketing or Dev. No Search Console login. Public HTTP only. If a thin content manual action is the real problem, see Google penalty recovery.

What does THINN check?

  • HTTP status and final URL after redirects.
  • Visible text length (thin band under ~800 characters of stripped body text).
  • H1 count and samples.
  • Title presence.
  • noindex from meta robots or X-Robots-Tag.

How does THINN judge the results?

PASS means OK - live 200, enough body text, one clear H1, usable title, not noindex.

FAIL is labelled with one verdict and an owner:

  • THIN (Marketing, P0) - expand unique value on the template (purpose, proof, FAQs).
  • MULTI_H1 (Dev, P1) - one H1 per template; demote extras to H2.
  • NOINDEX_HUB (Dev, P1) - confirm the hub should be noindex; if it should rank, remove noindex and strengthen content.
  • TITLE_H1_MISS (Marketing, P1) - add a clear title and a single H1 that matches intent.
  • FETCH_ERROR (Dev, P0) - re-run; check the host.

Same page, same rules, same result. The owner column is so Marketing and Dev each get their own ticket list.

How do I run a check?

  1. 01Sign in with your email - one-tap link, no password.
  2. 02Paste up to 30 hub URLs (or press Sample input).
  3. 03Hit Run. Filter by verdict or owner, then export.

How do I turn the results into a ticket?

Split the board by owner so each team gets one job.

  • Filter Marketing fails -> content ticket (thin body, weak title/H1).
  • Filter Dev fails -> template ticket (multi H1, noindex hub, fetch errors).
  • Export CSV or selected URLs with the Do-this column as the ticket body.

Live sample in, two clean tickets out.

Good to know

  • Public HTTP only - no crawl login, no Search Console OAuth.
  • Capped at 30 URLs per run.
  • Email sign-in. Every mode free to use after sign-in.
  • Sibling tools: LOCRA for sitemaps, RAUM for Pages reasons, KNOT for canonicals, GATE before you request indexing, VEXA for robots traps, and GONE to check the pages you decide to remove.

Part of the GSC Companion

THINN isn't a standalone tool - it's one mode inside the GSC Companion at /tools/seo. The same email magic-link opens every mode, so you can move from THINN to another check without signing in again.

If you want the wider picture first, read GSC Companion - how it works.

Sources

Work with me

Stuck on a result? Get in touch.