P4 · Listing pages and internal links

Sites: Prajavani (PV, www.prajavani.net, repo tpml) and Deccan Herald (DH, www.deccanherald.com, repo tpml-dh) · Priority: 4 of 6 · Prepared: 18 Nov 2026 by the Product, SEO and Data team · Internal refs: #32, #19, #20, #23, #27

Summary

Listing, section, tag, author, home and horoscope hub pages give Google weak signals on both sites. Pagination links have no href, so deeper stories have no crawlable path through listings. PV has no page-2 URL at all. On PV, the same stories are listed at several URLs (a short URL, a section URL and tag URLs), and many short URLs have no canonical tag. Listing pages carry about 11 <h1> elements on PV and 10 or 11 on DH tag and author pages, while many DH section pages have none. The horoscope hubs, which have the highest click-through rate of any topic, suffer from all of this at once. This package fixes the listing templates and the PV duplicate-URL problem. The redirect rule for PV short URLs must ship together with the redirect cleanup in P2.

Impact

All figures are Search Console unless stated. Nothing here has a measured traffic gain; these are defects and exposure, not forecasts.

Items

Issue: Both sites use react-paginate without hrefBuilder, so page links render as <a role="button"> with no href. PV has no page-N route. ?page=2 is accepted in the address bar but still shows page 1.

Evidence:

Fix:

Impact: gives Google a crawlable path to older stories from listings. Effect on discovery and traffic is unmeasured.

Verify: view-source of a section page shows a page-2 link with an href; that URL returns 200 with different stories than page 1. URL Inspection "View tested page" on the page-2 URL shows its own stories and its own canonical.

2. Self-referencing canonicals and descriptions on paginated pages — Low · PV, DH · Fix proposed

Issue: Paginated listings point their canonical at page 1. Google's guidance is a self-referencing canonical per page.

Evidence:

Fix: after item 1 gives page URLs real links, set each page's canonical to its own URL and give page 2 and later a non-empty description. Change this only together with item 4 (the PV canonical work), so the two do not conflict.

Impact: hygiene. No numbers.

Verify: view-source on page 2 shows a canonical equal to its own URL.

3. Server-render more of the home and section pages; fix empty PV breadcrumbs — Medium · PV, DH · Fix proposed

Issue: Home and section pages render only the first two collections on the server. PV section and sub-section breadcrumbs are empty in server HTML.

Evidence:

Fix:

Impact: more story links in the HTML Google sees on the most-linked pages. Unmeasured.

Verify: view-source of the home page lists headline links for the main rows; PV section view-source contains the breadcrumb trail.

4. Duplicate short listing URLs: one canonical URL per topic — High (PV), Low (DH) · PV, DH · Fix proposed

Issue: The same stories are listed at /<slug>, /<section>/<slug> and tag URLs. Short URLs often have no canonical and carry the site-wide description ("Kannada News - Find Trending Latest News…"), so Google treats each as its own canonical and splits searches. DH has the same short URLs, but with canonicals that point to the wrong place (see "Full URL list" below); low impact.

Evidence:

Full URL list (short-URL inventory, 19 Nov 2026; available as two CSV files, one per site). Every one-segment URL the /:slug route can serve, from the Quintype config (all sections and their backing collections) plus every one-segment URL in Search Console (web + Discover, 20 Jul 2025 – 16 Nov 2026) and the menus. Each row has the kind, the action, the section URL to redirect to, and clicks and impressions.

Site Kind Action URLs Known to Google Clicks (16 months)
PV A (section's collection) 301 to section URL 238 93 48,437,192 (48,352,845 are /cartoons + /churumuri-op-ed)
PV B (bare section slug) 301 to section URL 212 154 214,421
PV C (hand-made collection) keep; own canonical and description 50 50 943,536
DH A canonical to section URL (or 301) 140 41 31,760
DH B canonical to section URL (or 301) 100 8 6,280
DH C keep (already self-canonical) 102 102 1,562,840

Fix:

  1. CMS, no deploy: fill in canonical URL and summary on each duplicate collection (for example horoscope → https://www.prajavani.net/horoscope, hasana → /district/hasana).
  2. Code default: when a collection has no canonical, use the page's own URL (customSeo.canonicalUrl in the section loader, or a TPML SEO generator). Preferred route: port DH's generator (item 5).
  3. Redirect rule on /:slug, in this order: (1) a collection with that slug exists and its template is section: 301 to its section URL (kind A); (2) a collection exists with any other template: leave it (kind C); (3) no collection, but a section has that slug: 301 to the section URL (kind B). Reuse the redirectCollectionHandler logic. Keep the query string (/cartoons?page=9 → /news/cartoons?page=9), compare slugs in lower case, and put the rule behind an on/off switch.
  4. Tag pages that duplicate a hub (/tags/cartoons, /tags/horoscope, /tags/chinakurali): canonical to the hub or noindex, follow. Decide per tag.

Staged rollout (agreed 11 Nov 2026, recommended over a single release):

Step What Undo
0. Baseline Record clicks, impressions and position for every URL that will change and its section URL, plus the searches "prajavani cartoon", "chinakurali", "churumuri". —
1. Build The rule above, with /cartoons and /churumuri-op-ed on an exclusion list. Ship the redirect cleanup (P2) in the same release so no hand-written redirect chains through the rule. Switch off
2. Test Every kind A and B URL reaches its section URL in one 301. Kind C URLs and top-level sections are untouched. No loops. —
3. Wave 1 All kind A and B URLs except /cartoons and /churumuri-op-ed: 448 URLs, 245 known to Google (full list above). Straight 301. Switch off
4. Watch 3–4 weeks. Compare section-URL clicks with old-URL clicks combined. A dip of 1–3 weeks is normal. —
5. Wave 2, canonical trial Set the canonical of /cartoons to /news/cartoons and of /churumuri-op-ed to /op-ed/churumuri (CMS or code), not a redirect. Watch 2–3 weeks until Google shows the section URLs for the brand searches. Remove the canonical
6. Wave 2, 301 Remove the exclusion so the rule 301s them. Restore the exclusion

Wave 1 moves about 299K clicks over 16 months (about 10K in a typical 28 days); wave 2 moves 48.4M over 16 months (2.26M in 28 days). The canonical trial exists because Google currently prefers /cartoons (2.19M clicks vs 459k for /news/cartoons). A lower-risk alternative for wave 2: leave both pages as they are and give each a canonical pointing to itself. That ends the "no canonical" state but keeps the duplicate.

Kind C pages (/horoscope, /news-landing, /daily-horoscope, /district-landing, /trending, /abhimata; 47,523 clicks) are a separate editorial decision: choose one URL per topic, fill in canonical and summary, and point old redirect entries at the chosen URL. Horoscope is covered in item 8.

Risks: a 1–4 week re-processing dip; the consolidated URL ranking lower than the old one (main risk, for /cartoons); a different title or description on the section URL changing click-through; implementation bugs (wrong pages redirected, dropped query strings, loops), which are the most likely way to lose traffic; reports by URL showing the old URL dropping.

Impact: ends split rankings for the topics in the Impact section. Whether the section URLs rank as well as the short ones is not proven; hence the staging.

Verify: view-source shows one canonical on every short URL; URL Inspection shows Google's canonical as the chosen hub; split searches in Search Console converge on one URL.

5. DH canonical generator as the model for PV — Reference · DH (no defect), PV (port)

Issue: DH has the same /:collectionSlug catch-all and an older @quintype/seo (1.42.2) that always skips the collection canonical. DH avoids the problem with its own SEO generator.

Evidence:

Fix: port this generator and its section-page branch in customizedTags to PV instead of patching each collection. Tidy its condition (sectionURL !== null || sectionURL !== ""), which is always true.

Impact: covered by item 4.

Verify: as item 4.

6. One H1 per listing page — Medium (PV and DH) · PV, DH · Fix proposed

Issue: PV listing pages have about 11 <h1> elements (one per story card plus the collection name). DH section pages often have none, while its tag and author pages have 11.

Evidence:

Fix: card headlines default to H2 or H3 on both sites. One H1 per listing page: the section, tag, author or collection name. Remove the headerLevel={1} overrides in the listed widgets. Keep CSS classes so the look does not change.

Impact: clearer page topic for Google. Ranking effect unmeasured.

Verify: view-source of a section, tag and author page on each site shows exactly one <h1>.

7. PV hub head tags — Medium · PV · Fix proposed

Issue: Listing hubs have weak titles and the site-wide description. Live check, 12 Nov 2026: /horoscope title is just "ದಿನ ಭವಿಷ್ಯ"; /weekly-horoscope is "Weekly Horoscope" and /monthly-horoscope is "Monthly Horoscope" (English on a Kannada site); all three use the site-wide description.

Fix: own Kannada titles and descriptions per hub, for example "ಇಂದಿನ ದಿನ ಭವಿಷ್ಯ (12 ನವೆಂಬರ್ 2026): 12 ರಾಶಿಗಳ ರಾಶಿ ಭವಿಷ್ಯ | ಪ್ರಜಾವಾಣಿ", "ವಾರ ಭವಿಷ್ಯ", "ಮಾಸ ಭವಿಷ್ಯ". The CMS summary fixes the description. A dated title needs code (customTags or the item 5 generator). Wider title and meta-tag rules are in P5.

Impact: snippet quality on the highest-click-through topic. Unmeasured.

Verify: view-source of each hub shows the new title and its own description.

8. Horoscope hubs and pages: listing-specific fixes — High · PV, DH · Fix proposed

Overlaps are not repeated here. One topic with several URLs is item 4 (kind C). Heading counts on listings are item 6. DH server-rendered horoscope text belongs to P1. The DH articleBody JSON-LD value and other head tags belong to P5. The DH /amp/horoscope canonical belongs to P5. All evidence below is from live checks on 12 Nov 2026 (raw HTML with a Googlebot user agent, plus headless Chrome).

PV fixes:

DH fixes:

Impact: horoscope is the highest click-through topic (figures in Impact). Do not add this benefit to items 4 or 6; it overlaps them.

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 and 12 sign H2s. Track "dina bhavishya", "rashi bhavishya kannada" and DH "horoscope today" weekly; "prajavani dina bhavishya" should rank with one URL.

Release checklist