← Issues index

41. PV "Also read" card links to /https://www.prajavani.net/…, a second indexable copy of the article — Medium (PV)

Added 18 Nov 2026. Found in the Search Console Page indexing exports (indexing/2026-11-18/, data to 13 Nov 2026; summary checks/index_coverage/summary_pv_2026-11-18.md).

What: inside article bodies, the desktop "Also read" (ಇದನ್ನೂ ಓದಿ) card links to the linked story with the host repeated in the path, e.g. href="/https://www.prajavani.net/entertainment/cinema/yash-ramayana-ravana-cinema-history-4165600" (seen in the Googlebot HTML of …/nitesh-tiwari-ramayana-odyssey-similarities-explanation-4383444, 18 Nov 2026). That path returns 200 with the full article and a canonical to the real URL (any prefix returns 200, #21/#35), so Google crawls and sometimes indexes it.

Evidence

Cause: 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 is the linked story's full url, not its 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 it as is and are correct. The desktop card is hide-mobile, but it is still in the HTML Googlebot reads. DH has the same line (tpml-dh ee69e96a, also-read/index.js:50; same getLinkedStory returning the full url) but no such URLs in Search Console. Checked 18 Nov 2026: 55 of DH's 60 latest stories have an "Also read" element, yet the card is not in DH's server HTML (the body is JavaScript-only, #1; the link exists only in the embedded story JSON), and the doubled path 301s to the real story (/https://www.deccanherald.com/india/karnataka/bengaluru/…-4156084 → /india/karnataka/bengaluru/…-4156084). Confirmed in the browser the same day (user's DOM copy from …/the-room-where-nobody-has-to-buy-anything-4222355): after JavaScript runs, the DH desktop card is <a href="/https://www.deccanherald.com/…-4156084"> with the same nested headline <a>. Google renders JavaScript, so it can find these links; they 301, which is why none show up as pages in Search Console. So on DH it costs at most one redirect hop per link. Fix it in the same release as DH's #1, which will put the card into the server HTML.

🛠️ Fix: href={linkedStorySlug} on line 51 (and rename the variable to linkedStoryUrl); same one-line change on DH for consistency. #21's fix (301 for any non-canonical story path) removes the 200 copies that already exist.

Verify: a story with a single "Also read" element has no /https: in its server HTML; in ~4–6 weeks the doubled URLs in Page indexing → "Page with redirect" (after #21) or drop out; Search Console pages contains /https: → 0.

Confirmed in the browser (18 Nov 2026, user's DOM copy from …-4383444): the desktop card (hide-mobile) is <a href="/https://www.prajavani.net/…-4229527"> wrapping the @quintype/arrow Headline, which renders its own <a href="https://www.prajavani.net/…-4229527"> (correct). The mobile card (hide-desktop) links correctly. Two smaller defects in the same card: