← Issues index

20. Multiple H1s on listing pages; no H1 on horoscope articles — Medium (PV)

Added 11 Nov 2026. Every listing page has about 11 <h1> elements (one per story card plus the collection name). Ordinary articles have one H1; horoscope articles have none.

Cause:

🛠️ Fix: card headlines default to H2/H3; one H1 per page (the collection or section name); horoscope headline in an <h1> (keep the class for styling). Each of the 12 signs as <h2 id="<sign>"> in the horoscope template.

DH: the same card defaults exist (listing-story-card line 192, story-card1, story-card7, story-card9 default to 1; story-card18/21/23, slider-with-multiple-big-cards, video-slider, budget and election widgets pass headerLevel={1}). Live result is the opposite problem on section pages: of 228 DH listing URLs, 59 have no H1 (including /india, /india/karnataka, /world, /latest-news, /top-bengaluru-news, /horoscope) and 27 have 11 (tag and author pages: /tags/bengaluru 11, /author/dh-web-desk 10). Fix: one H1 per listing page (section or collection name), cards as H2/H3.

Validated 19 Nov 2026: code and live (Chrome DevTools, headless).

Code (PV tpml upstream/master 0b3f7227, 16 Nov 2026; DH tpml-dh upstream/main ab4a2e58, 18 Nov 2026; read with git grep / git show):

Live (evidence/listing_h1_devtools_2026-11-19.json; rendered DOM after JavaScript vs the same URL's server HTML):

Page H1 after JavaScript H1 in server HTML Story <h2>s: rendered / server Story links in server HTML
DH /india (section) 1 ("India") 0 24 / 0 12
DH /tags/bengaluru (tag) 11 11 0 / 0 22
PV /horoscope (hub) 11 (hub name + 10 stories) 11 0 / 0 22
PV /news/karnataka-news (section) 11 ("ರಾಜ್ಯ" + 10 stories) 11 0 / 0 22

Reading: PV listings and DH tag pages: confirmed, 11 H1s in both server HTML and rendered page. DH section pages: readers see one correct H1, but Google's first copy has no H1 and no story list (24 story headings appear only after JavaScript). That second part is an internal-linking problem (#32, DH) as much as a heading one. Fix for DH section pages: render the title and the first page of stories on the server (initialise from the server-loaded stories instead of waiting for useEffect), then apply the H2/H3 card change.