P1 · Article server HTML

Sites: Prajavani (PV, www.prajavani.net, repo tpml) and Deccan Herald (DH, www.deccanherald.com, repo tpml-dh) · Priority: 1 of 6 · Prepared: 18 Nov 2026 by the Product, SEO and Data team · Internal refs: #1, #2, #7 (hero image part), #9, #11, #12, #31 (measurement), #32 (fix 1), #41

Summary

Both sites send article paragraphs as empty containers in the first HTML response. The text exists only in a JSON data script and appears after JavaScript runs. Google indexes from the first HTML and renders JavaScript later, if at all. On PV this has left an estimated 76% of print and web-desk articles indexed without body text. Ship the paragraph fix (item 1) on both sites first. It is built for PV and verified on the DH training host. In the same release, ship the other article-template changes that make the first HTML complete: the "more from this section" link block (item 2), the "Also read" link fix (item 3), the hero image (item 4) and the premium-story body (item 5). Items 2 to 5 touch the same templates, so one release saves repeat QA. Items 6 and 7 are already fixed in the same branch and only need checking at release. Then measure (item 8).

Impact

What changes for Google: the article body, the contextual links to other stories and the hero image are in the first HTML. Google no longer depends on a JavaScript render to see them.

What changes for readers: nothing visible is intended. Ad positions must stay the same (see item 1, Verify). Ad volume rises for in-site navigation (item 6).

Numbers (each with its source):

Not proven:

Items

1. Article paragraphs missing from server HTML — Critical · PV and DH · Status: DH fix live 19 Nov 2026; PV fix built, not pushed

Issue: the server sends every plain-text paragraph as an empty container. The text sits only in the JSON data <script> and appears after JavaScript runs.

<div id="text-element-with-ad"><div></div></div>

Evidence:

Cause: story-templates/story-elements/index.js, component CustomStoryElement. To insert ads between paragraphs, the text is split with the browser-only DOMParser, and <p> tags are counted inside a useEffect. Neither runs on the server.

Fix:

Impact: removes the dependence on Google's render step for article text. For PV this targets the 76% indexed-without-body share above. For DH it protects a currently better position and puts the "Also read" card into server HTML (see item 3). Traffic effect is not proven.

Verify:

2. No related-story links in the server HTML of articles — High (PV), Medium (DH) · PV and DH · Status: fix proposed

Issue: the automatic "latest", "most read" and "more from section" blocks are not in the server HTML. Google's saved article HTML has few contextual links to other stories.

Evidence:

Fix: server-render a "more from this section" block of 5 to 10 links from the story's section collection, fetched in the article page loader, on every article, both sites. Use real <a href> links with the story headline. Keep the scroll-gated widgets for users.

Impact: gives each article a crawlable path to other stories. The effect on discovery speed and traffic is not measured. Low crawl per new URL (see P3) and never-shown articles (item 8) are context, not proof of cause.

Verify: view-source of an article shows at least 5 same-section story links. URL Inspection "View tested page" shows the block. The links are in the HTML before JavaScript and not only inside hide-mobile groups.

Issue: the desktop "Also read" (ಇದನ್ನೂ ಓದಿ) card links to /https://www.prajavani.net/<story path>. That path returns 200 with the full article and a canonical to the real URL, so Google crawls and indexes a second copy.

Evidence:

Cause: PV tpml app/isomorphic/components/story-templates/story-elements/also-read/index.js:51 (master 0b3f7227; line from ea2d8e98, 16 Oct 2023): <Link href={/${linkedStorySlug}}>. linkedStorySlug comes from getLinkedStory() (app/api/utils.js:65) and holds the full url, not a slug. The mobile card (same file, line 14) and the AMP card (app/server/amp/override/components/rows/story-elements/also-read/index.js:36) use the value as is and are correct. The desktop card is hide-mobile, but it is still in the HTML Googlebot reads. DH: tpml-dh ee69e96a, also-read/index.js:50.

Fix:

Impact: stops new doubled URLs on PV. For DH it removes a redirect hop on each link. The effect on rankings is not measured.

Verify: a story with one "Also read" element has no /https: in its server HTML and no <a> inside <a>. About 4 to 6 weeks after release (with P2's 301), Search Console pages filtered by contains /https: trend to 0 and the doubled URLs in Page indexing move to "Page with redirect" or drop out.

4. Hero image not in server HTML — Medium (PV) · PV · Status: fix proposed

Issue: the article hero image is client-only, so Google's first HTML has no hero <picture>.

Evidence:

Fix: render the hero <img> directly on article pages, with no WithLazy above the fold. Add fetchpriority="high" and explicit width and height. The header layout shift (useDevice returns null until mount; min-height 456 to 184 px) belongs to P6 Page speed, ads and analytics.

Impact: gives Google the hero image in the first HTML and is the main LCP fix on mobile. The size of the LCP gain is not measured.

Verify: view-source shows the hero <img> with fetchpriority="high" and width/height. On training or staging, the mobile LCP element is the hero image, not an ad.

5. Premium stories: spinner instead of body — Low (PV), DH noted · PV and DH · Status: investigated, optional fix

Issue: for access === "subscription" (non ad-free), story-elements/index.js (about lines 887 to 894) shows <SpinnerLoader /> instead of the body until a 500 ms timer and client-side premium-card computation finish.

Evidence:

Fix: after item 1 ships, confirm the server HTML of premium stories holds the truncated body (the preview) and not the spinner. Optional: restore hasPart paywall markup (deleted in seo-hard-gate.js:274,291; see P5 Structured data and head tags).

Impact: low, because premium is a small share. Not a priority within this package.

Verify: fetch a premium story with a Googlebot UA: preview text and subscribe prompt present, no spinner-only body.

6. Mid-article ad counters never reset — Low · PV and DH · Status: fixed in the PV #1 branch; check at release

Issue: countPara and hasRenderedMidAd1/2 were module-level and never reset, so mid-article ads showed only on the first story viewed in a browsing session.

Fix: done in fix/ssr-story-paragraphs (per-story plan; ads on the first story of each page). DH has the same module-level variables (lines 236 to 238 on 0bc245a1); the port in item 1 covers them.

Verify: navigate through 3 stories in one session. Mid-article ads show on each. Ad volume will rise for in-site navigation, so tell ad operations before release.

7. isWebView / ?app=true check inverted — Low · PV · Status: fixed in the PV #1 branch; check at release

Issue: isWebView was set to true when the URL did not contain app=true, and the second mid-article ad was hidden when true. It worked only because of a stale value.

Fix: removed in the #1 branch with behaviour unchanged: the app still shows the second mid ad. Product to decide the intended app behaviour.

Verify: open an article with and without ?app=true. Both show the second mid-article ad, as before.

8. Before and after measurement plan — Analysis

Issue: PV print copies (published by the Varta Setu print-to-web system, syndicated-print template, live from late Mar 2026) are 79% of PV output and 96% of the articles Google never shows. The body is missing in Google's copy at about the same rate whether stories are shown or not (item 1). The likely causes of low traction are the missing body plus low demand for hyperlocal items.

Evidence:

Plan:

  1. Ship items 1 to 5. Then compare the print-copy "any impression" share and clicks per story for the 4 weeks before and after release. Collect data with a window that starts after the release.
  2. About 4 weeks after release, re-run the body-phrase search test on the same sampled stories (about 200 paid search queries are budgeted). Compare with 76% body not indexed.
  3. Optional separating test: about 50 stories from early Mar 2026 against about 50 from mid-Apr 2026 (same age, before and after print-to-web), about 100 queries.

Hold until the comparison is done: no other change to print copies in the same window (removal, noindex, length rules, round-ups, news-sitemap rules, or spreading the 06:00–09:00 publishing burst), so the effect of the fix can be measured on its own.

Not recommended now: noindex or removal of print copies. They are unique content and the fix has not shipped. If print copies stay low after the fix, the next step is an editorial decision (minimum length, district round-ups), outside this package.

Release checklist

  1. PV: push and review branch fix/ssr-story-paragraphs (bcd5d909). Add the changes for items 2 to 5 (same templates).
  2. DH: port items 1 and 3, add item 2. Re-run the training-host check (29 of 29 on the 3 reference stories was the pass on 18 Nov 2026).
  3. QA on training or staging, Googlebot UA, JavaScript off: no empty text-element-with-ad containers; at least 5 same-section links; no /https: links; hero <img> present; premium stories show the preview and not the spinner.
  4. QA with JavaScript on: same ad and Taboola positions as before; no hydration warnings; mid-article ads show on each story in a session; second mid ad shows with ?app=true.
  5. Check page weight: DH training HTML was 1.30 MB against 1.29 MB live. Flag any large rise.
  6. Release PV and DH.
  7. Same day: re-run the 3-story server-HTML check on the live hosts; URL Inspection "View crawled page" on 3 stories per site; request indexing for priority URLs.
  8. After 4 weeks: body-phrase re-test and before/after traffic comparison (item 8).