← Issues index

27. Horoscope pages: all technical issues, ranked by impact — High (PV, DH)

Added 12 Nov 2026. One place for every horoscope defect on both sites. Some are cases of wider issues (#1, #19, #20, #22, #24); those rows point there and are fixed there. Live check 12 Nov 2026: raw HTML with a Googlebot User-Agent plus headless Chrome for the rendered page; outputs in evidence/horoscope_2026-11-12/. Traffic: Search Console 12 Oct – 8 Nov 2026 (../Content Engine/programmatic-content-research.md §4.2 and §4.5, and #19).

Why it matters: horoscope has the highest click-through rate of any topic on both sites (8–18%). PV /horoscope had 267,134 impressions and 26,000 clicks at position 5.7; the generic searches sit at positions 4–8 ("dina bhavishya" 42,822 impressions at p6.1). DH "horoscope today" is at p11 (30,410 impressions, 4,401 clicks). Moving the generic searches into the top 3 is worth several times the current clicks.

Where horoscope traffic comes from now (19 Nov 2026)

Search Console web + Discover, 20 Oct – 16 Nov 2026 (28 days, before #1 reached Google), every URL matching horoscope / astrology paths: checks/horoscope/horoscope_traffic_{pv,dh}_2026-10-20_2026-11-16.md (re-run: checks/horoscope/horoscope_check.py traffic). Live server HTML of 2 daily articles per site as Googlebot, 19 Nov 2026: checks/horoscope/horoscope_live_{pv,dh}_2026-11-19.md.

Prajavani: 51,952 web clicks (1.5% of the site's 3.36M) and 55,358 Discover clicks on horoscope pages, excluding panchanga (another 3,735 web / 27,401 Discover).

Page kind Web clicks Impressions Avg position Discover clicks
Hub /horoscope 33,043 361,087 6.1 –
Other hubs (/weekly-horoscope 3,879, /daily-horoscope 2,118, /astro-vastu/horoscope 508, /astro-vastu/astrology 499, /monthly-horoscope 369 …) 7,485 204,140 – –
Daily articles 7,164 116,778 – 43,399
Weekly articles 1,799 26,130 3.7 6,478
Other astrology articles 1,726 54,977 – 5,481
Tag pages (/tags/horoscope*) 509 50,021 – –

Deccan Herald: 34,906 web clicks (2.7% of the site's 1.30M) and 13,082 Discover clicks on horoscope pages.

Page kind Web clicks Impressions Avg position Discover clicks
Hub /horoscope 21,765 193,665 9.3 –
Daily articles (/astrology/todays-horoscope-<date>…) 5,241 60,547 8.6 9,954
Tag pages (21: /tags/horoscope-weekly 1,399, /tags/horoscope 622, /tags/weekly-horoscope 430, sign tags 2–219 each) 3,249 104,938 2.8 –
Weekly articles 2,965 51,427 5.4 3,128
Other hubs (/astrology 868, /astrology/weekly-horoscope 37 …) 940 23,692 6.2 –
AMP (/amp/horoscope etc.) 251 16,514 2.0 –

Priority: P1 = touches the pages/searches that carry the traffic, fix first · P2 = clear ranking or snippet effect, next frontend release · P3 = hygiene.

Prajavani

P Issue Evidence (12 Nov 2026) Fix Owner / where
P1 One topic, four URLs. /horoscope and /daily-horoscope have no canonical; /astro-vastu/horoscope is self-canonical; all three list the same 10 stories. Google treats each as its own canonical, and "prajavani dina bhavishya" ranks with 4 URLs. Same for weekly (/weekly-horoscope vs /tags/horoscope-weekly, /tags/weekly-horoscope). Part of #19 (kind C). pv_listings.txt Choose /horoscope as the hub. Stopgap with no deploy: set canonical + summary on the horoscope, daily-horoscope and weekly-horoscope collections in the CMS. Then 301 /daily-horoscope → /horoscope; /astro-vastu/horoscope canonical (or 301) → /horoscope; /tags/horoscope* canonical to the hub or noindex, follow. Point the old redirect-urls.js entries (/dailyhoroscope.html → /daily-horoscope) straight at /horoscope (#25). CMS now; tpml with #19
P1 Hub head tags. /horoscope title is just "ದಿನ ಭವಿಷ್ಯ"; /weekly-horoscope "Weekly Horoscope", /monthly-horoscope "Monthly Horoscope" (English on a Kannada site); all three use the site-wide description ("Kannada News - Find Trending Latest News…"). pv_listings.txt Dated Kannada titles and own descriptions, e.g. "ಇಂದಿನ ದಿನ ಭವಿಷ್ಯ (12 ನವೆಂಬರ್ 2026): 12 ರಾಶಿಗಳ ರಾಶಿ ಭವಿಷ್ಯ | ಪ್ರಜಾವಾಣಿ"; "ವಾರ ಭವಿಷ್ಯ", "ಮಾಸ ಭವಿಷ್ಯ". The CMS summary fixes the description; a dated title needs code (customTags / the #19 generator). CMS + tpml
P2 No H1 on horoscope articles; signs aren't headings. Even after JavaScript the headline is a <div> and the 12 signs are plain text cards, each stamped "7 hours ago". Google can't link to or show a single sign. Part of #20. pv_articles.txt; headless Chrome Headline in <h1> (story-templates/horoscope/index.js:394); each sign as <h2 id="mesha">ಮೇಷ ರಾಶಿ</h2> (ids: mesha, vrushabha, mithuna, kataka, simha, kanya, tula, vrischika, dhanu, makara, kumbha, meena); a jump list of the 12 signs at the top. tpml
P2 11 H1s on every horoscope listing (page name + 10 story cards). Part of #20. pv_listings.txt One H1 (hub name); cards as H2/H3. tpml
P2 Article SEO titles inconsistent. 12 Nov: "Daily Horoscope: ದಿನ ಭವಿಷ್ಯ: ಗುರುವಾರ, 12 ನವೆಂಬರ್ 2026" (dated, good, but English prefix). 11 Nov: no date and a doubled vowel sign, "…ಸ್ಪರ್ಶಿಸಲಿದ್ದೀರಿಿ", still in <title> although the headline and og:title were corrected. Slugs: 11 Nov has the date (…-11-nov-2026-4387580), 12 Nov doesn't (daily-horoscope-thursday-november-4388744). pv_articles.txt One pattern for every daily article: "ದಿನ ಭವಿಷ್ಯ <ದಿನ> <ತಿಂಗಳು> <ವರ್ಷ>: <tagline>", the date in the slug, English prefix dropped or moved to the end. Correct the 11 Nov SEO title. Editorial (desk checklist)
P3 Articles filed outside the horoscope section. The weekly listing skips 1–7 Nov; the monthly listing jumps Nov → Sep → Jun → Feb 2026. Confirmed 19 Nov 2026 and wider: daily articles are mis-filed too — /astro-vastu/vaastu/ articles earned 2,495 horoscope web clicks in 28 days (daily 1,528, weekly 833; e.g. …/vaastu/daily-horoscope-job-prediction-4359300, …/vaastu/weekly-horoscope-astrology-prediction-4366400). pv_listings.txt; checks/horoscope/horoscope_traffic_pv_2026-10-20_2026-11-16.md Re-file under /astro-vastu/horoscope/ (or add the collection), so every week and month appears on its hub. Editorial / CMS
P3 Stale related link and no link to the hub. Every horoscope article links to /horoscope/ugadi-2025-new-year-horoscope-3226114; none links to /horoscope. pv_articles.txt Link to the hub (and later the sign pages) from the template; drop the Ugadi 2025 link. tpml / CMS

Deccan Herald

P Issue Evidence (12 Nov 2026) Fix Owner / where
P1 Daily horoscope text not in the server HTML. The 12 Nov article's raw HTML has none of the 12 sign texts (1,827 characters of visible text, navigation only); they appear only after JavaScript. PV's horoscope articles do have the text in the HTML. Same cause class as #1. dh_pages.txt; headless Chrome Ship the #1 port for DH and confirm it covers the horoscope template (it renders sign cards with images, not plain paragraphs). Check the crawled page in URL Inspection for one daily article before and after. tpml-dh with #1 · ✅ fixed 19 Nov 2026 (#1 release, 250ef126: horoscope template now imported statically instead of loadable): 12 of 12 sign texts in the server HTML of …4223276 and …4221979, fresh and cached (checks/ssr_compare/dh_horoscope_2026-11-19.json). Still no <h1>/<h2> in that HTML (see the headings row). PV, 19 Nov 2026, training host with the PV #1 fix vs live (…-4404474, …-4401995; checks/ssr_compare/pv_horoscope_training_vs_live_2026-11-19.json, HTML in evidence/pv_ssr_2026-11-19/): 12 of 12 sign texts (from story.metadata) in server HTML on both hosts, with identical markup. So there's no regression, and none was needed: PV already rendered them. On both hosts the sign names are <div>s and there are 0 <h1>/<h2> (the only headings are unrelated <h3> story cards).
P1 articleBody in the article's JSON-LD is junk: <p>https://www.deccanherald.com/</p> instead of the horoscope text. Still the same on 19 Nov 2026, after the #1 release (16 Nov article …4219494 too; on 28 Oct …4197583 it is the meta description). PV: articleBody is ~700 characters of HTML-escaped markup (&lt;p&gt;…), too short for the 12 readings (19 Nov 2026) — same fix on PV. Cause: the sign texts live in story.metadata (horoscope/index.js:341), so the default articleBody takes the story's only text element, which holds the site URL. dh_pages.txt; evidence/dh_ssr_2026-11-19/4223276_horoscope_fresh.html In app/server/helpers/seo-hard-gate.js (where articleBody is already overridden for premium, line 171), for story-template === "horoscope" build articleBody as plain text from the 12 story.metadata sign texts ("Aries: …"). Check whether other DH story templates have the same value. tpml-dh
P1 Generic, changing SEO titles on daily articles. 12 Nov <title>: "Daily Horoscope: Today's astrological predictions and sun sign insights" (no date; near-identical to 10 Nov "…and sun signs"); 11 Nov: "Today's Horoscope - November 11, 2026: …"; 5 Nov: "Daily Horoscope: Aries, Taurus, Gemini & Cancer predictions for November". The visible headline is dated every day; the SEO title field is overriding it. Duplicate titles across days compete with each other for "horoscope today" (p11). Still mixed on 19 Nov 2026 (16 Nov dated, 28 Oct undated), and the 16 Nov article has no meta description. dh_pages.txt; titles of 4213912, 4213170, 4207851; checks/horoscope/horoscope_live_dh_2026-11-19.md One dated pattern in the SEO title, e.g. "Horoscope Today, November 12, 2026: Predictions for all 12 sun signs", or leave the SEO title empty so the dated headline is used. Editorial (desk checklist)
P1 (raised from P2, 19 Nov 2026) Hubs are empty without JavaScript, and lose the generic searches to daily articles. "horoscope today" (28,772 impressions, 20 Oct – 16 Nov 2026): /horoscope p18.3 while dated daily articles rank p2.0–4.5; same for "today's horoscope" (p12.4), "horoscope" (p13.8), "daily horoscope" (p33.9). /astrology and /horoscope raw HTML: about 1,800 characters of text, no links to horoscope articles, no sign names, no H1 (#20). The DH tag pages, by contrast, do render story links in the HTML. dh_pages.txt Render the story list (real <a href> links) and one H1 in the server HTML; ideally today's 12 signs on the hub. tpml-dh
P2 Two hubs plus an AMP hub. /astrology and /horoscope list the same stories, each self-canonical; /amp/horoscope is indexed with a self canonical (#24). Search Console: "horoscope today" split between /horoscope p17.3 and /astrology p60.6 (#19). dh_pages.txt Choose /horoscope as the hub (it has the impressions); /astrology canonical or 301 to it; /amp/horoscope canonical to /horoscope. tpml-dh / CMS
P2 No H1 on daily articles; signs aren't headings. After JavaScript the only headings are H2s of unrelated "related stories"; the headline isn't an H1 and each sign is plain text. Still true in server HTML on 19 Nov 2026, after the #1 release: 0 <h1>, 0 <h2> (…4223276). headless Chrome; evidence/dh_ssr_2026-11-19/4223276_horoscope_fresh.html tpml-dh origin/main ab4a2e58, story-templates/horoscope/index.js: headline <div styleName="title">{story.headline}</div> (line 604) → <h1>, keeping the class. Sign name <div styleName="horoscope-name">{item.name}</div> (line 380) → <h2 id="aries"> (lower-case sign name as id), keeping the class. tpml-dh
P3 Sign tag pages are the de facto sign pages but weak. /tags/aries-horoscope (and the other 11) is 200, self-canonical, title "Aries Horoscope", description "Read stories listed under on Aries Horoscope" (#24's broken default), 11 H1s, and lists the all-signs articles, not Aries text. Tagging is patchy: the Aries tag skips 9, 10 and 12 Nov. dh_pages.txt Short term: tag meta title/description in the CMS ("Aries Horoscope Today: daily, weekly predictions | Deccan Herald"), tag every daily article with all 12 signs. Longer term: real sign pages (content plan item 10). CMS / editorial
P3 Sign images: no alt, URL ends in ?w=undefined (width bug), served from a dh-sandbox/ path. Still true in server HTML on 19 Nov 2026: 12 of 12 sign images have no alt and src="…/aries?w=undefined" (the srcset has w=100). headless Chrome; evidence/dh_ssr_2026-11-19/4223276_horoscope_fresh.html horoscope/index.js:38-42, ZodiacIcon: pass alt={name} and a default width to ResponsiveImage (widths={[100]} sets only the srcset), e.g. <ResponsiveImage … widths={[100]} defaultWidth={100} alt={${name} horoscope} />. Move the images from dh-sandbox/ to the production path. tpml-dh / CMS
P3 December 22 has no sign. The template date ranges say Sagittarius "November 22 - December 21" and Capricorn "December 23 - January 20". Seen in server HTML, 19 Nov 2026. horoscope/index.js:217, :223 Change Capricorn to "December 22 - January 20" (the usual range). Virgo "August 22 - September 23" and Libra "September 23 - October 22" overlap on 23 Sep; use "August 23 - September 22" for Virgo if that is the source used for the readings. tpml-dh
P3 /horoscope description says "predictions for 2025". dh_pages.txt Remove the year or update it each January. CMS

Not technical (tracked in the content plan, ../Content Engine/build-plan.md items 2 and 10): today's 12 signs on the hub itself, and 12 permanent sign pages per site. These target the sign searches that earn almost nothing now (PV "kanya rashi today in kannada" 1,991 impressions, 5 clicks, p9.5).

Verify: URL Inspection shows /horoscope as Google's canonical for PV's three listing URLs and for DH's /astrology; view-source of one daily article per site shows one H1, 12 sign H2s and (DH) the sign text; the weekly scorecard (build-plan.md item 0) shows "dina bhavishya", "ಭವಿಷ್ಯ", "rashi bhavishya kannada" and DH "horoscope today" moving up, and "prajavani dina bhavishya" ranking with one URL.