P7 · Monitoring, risky pages and open investigations

Sites: Prajavani (PV, www.prajavani.net) and Deccan Herald (DH, www.deccanherald.com) · Priority: runs alongside P1–P6 · Prepared: 19 Nov 2026 by the Product, SEO and Data team · Internal refs: #42, #36, #24, #19, #17, #18

Summary

These items are not code fixes in the website templates. Each one needs an owner who investigates, decides or watches. One item is still under investigation: PV's Google News traffic fell to near zero from 12 Nov 2026. The others are the pages that bring traffic but carry risk, gaps in how we monitor, and one policy decision.

Impact

Items

1. PV Google News near zero since 12 Nov 2026 — High (PV) · Status: under investigation · Owner: Quintype + PV editorial (Publisher Center), SEO team (tracking)

Issue: PV's Google News clicks fell from about 450/day to 70 on 12 Nov 2026 and stayed at 38–48/day on 13–16 Nov. PV's web search traffic recovered after Deepavali on 15–16 Nov; Google News did not. DH Google News held steady (13–22K clicks/day) over the same days.

Evidence:

Fix (investigation steps):

  1. Quintype: did anything change on 11–12 Nov 2026 in the news sitemap, the RSS feeds or the Google News feed settings?
  2. PV editorial or whoever holds the account: check Google Publisher Center. Is the publication still verified? Is the language set to Kannada? Are the sections mapped? Are there any notices?
  3. SEO team: look up a few PV stories from 12–16 Nov in the Google News app and on news.google.com. Re-pull daily Google News clicks each week.

Impact: recovers about 400 clicks/day if a setting caused it. Also tells us whether the PV feed needs work before it can grow (item 2).

Verify: PV daily Google News clicks back above about 400/day in Search Console.

2. PV gets very little Google News traffic overall — Note (PV) · Status: check Publisher Center · Owner: PV editorial + Quintype

Issue: even before 12 Nov, PV got about 14K Google News clicks a month while DH got about 400K.

Evidence: Search Console, search type Google News, Oct 2026: PV 13,559 clicks, DH 406,785. The news sitemap is compliant (see item 1).

Fix: together with item 1, set up the Publisher Center publication fully: language Kannada, sections, logo. If Google News simply carries few Kannada sources, record that and stop here.

Impact: Unknown. DH shows the size of the channel for an English site. The same is not proven for Kannada.

Verify: monthly Google News clicks in Search Console.

3. Risky traffic pages: piracy-name tags and gambling-linked pages — Note · PV and DH · Status: kept by choice, monitored · Owner: DH editorial, PV editorial, SEO team (monitoring)

Issue: some pages bring large traffic from searches for piracy sites or for gambling. On DH these are tag pages such as /tags/movierulz and /tags/tamilrockers. On PV they are the cartoon pages, which rank for satta-matka searches. We keep these pages: they add traffic. But Google can stop showing them at any time, through a core update, a spam-policy update or a manual action. They also tie the brand to these searches.

Evidence:

Fix:

  1. Report this traffic as a separate line, "risky traffic", in every weekly scorecard, so that growth elsewhere is not hidden by swings in these pages.
  2. Editorial: decide each page's content consciously. Write about the topic (for example, "why piracy sites are blocked"). Never link to piracy or betting sites.
  3. SEO team: watch these pages' positions weekly. Check Search Console Manual actions after every Google core or spam update.

Impact: traffic is kept. The risk is seen and measured instead of hidden in the totals.

Verify: the scorecard shows risky traffic separately. Manual actions stay at "No issues detected".

4. Monitoring gaps — Note · PV and DH · Status: process · Owner: SEO team

Issue: some problems don't show up in the standard reports.

Evidence and fix:

Verify: the monthly re-test is on the calendar and its results are in the scorecard.

5. AI crawlers blocked in robots.txt — Note · PV and DH · Status: decision · Owner: Leadership (editorial + product)

Issue: robots.txt on both sites blocks GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, PerplexityBot, CCBot, Google-Extended, Bytespider, Amazonbot and others.

Evidence: robots.txt on both sites, checked Nov 2026.

Fix: confirm that this is a deliberate policy. If visibility in AI search answers (ChatGPT search, Perplexity) becomes a goal, allow the search bots (OAI-SearchBot, PerplexityBot) and keep the training bots blocked. Blocking Google-Extended does not affect Google Search or AI Overviews.

Impact: none on Google Search. A possible referral channel if the search bots are allowed.

Verify: a written decision. robots.txt changes only if the decision is to allow some bots.

Release checklist