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
- PV Google News: about 450 clicks/day before 12 Nov 2026 and about 45/day since. If the cause is a setting, fixing it brings back about 400 clicks/day. That is small next to web search, but it is the one loss that is not explained.
- Risky pages: DH piracy-name tag pages had 17M impressions in 28 days (Search Console, 28 days to early Nov 2026). PV cartoon traffic includes satta-matka searches worth several thousand clicks a day. Google can stop showing these pages at any time, so they must not count as stable traffic.
- Not proven: none of these items has a measured traffic gain.
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:
- Search Console, search type Google News, daily clicks, PV: 2–11 Nov 2026 between 322 and 468 a day; 12 Nov 70; 13 Nov 48; 14 Nov 38; 15 Nov 44; 16 Nov 47.
- PV web search over the same days dropped from 6 Nov and recovered on 15–16 Nov (134,399 clicks on 16 Nov). Google News moved on a different date and has not recovered, so the festival did not cause it.
- PV's news sitemap was compliant when checked on 16 Nov 2026: 1,000 URLs, publication name "prajavani", language
kn, IST dates, listed in robots.txt.
Fix (investigation steps):
- Quintype: did anything change on 11–12 Nov 2026 in the news sitemap, the RSS feeds or the Google News feed settings?
- 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?
- 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:
- DH piracy-name tags:
/tags/movierulz9.36M impressions and 47.6K clicks,/tags/moviezwap5.36M and 40.0K,/tags/bolly4u1.23M and 30.0K, and/tags/tamilrockersand/tags/filmy4webon top. Together they had 17M impressions in 28 days (Search Console, 28 days to early Nov 2026). - They are already volatile. Between 3–5 Nov and 12–16 Nov 2026,
/tags/tamilrockersfell from 2,859 to 215 clicks/day, and the query "tamilrockers" dropped from position 7.2 to 16.8. All DH tag pages together fell from 11,047 to 7,192 clicks/day (Search Console). - PV satta-matka cartoon queries, per day, before and during the Deepavali week of 6–14 Nov 2026: "kalyan cartoon" 2,251 → 718 clicks, "matka cartoon" 2,269 → 1,047 (Search Console).
- No manual actions or security issues on either site (Search Console, checked 16 Nov 2026).
Fix:
- 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.
- 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.
- 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:
- Search Console reports pages whose body Google doesn't have as "indexed", with no warning. Re-run the body-text
site:test on the same 663-story sample monthly and after P1 ships (first run 16 Nov 2026: about 76% of PV stories had no body in Google's copy). - GA4 "Organic Search / google" includes Google Discover and Google News, so it can exceed Search Console web clicks. Use Search Console for search-only numbers.
- Exact-phrase searches over-count "not indexed" when wire copy appears on other sites. Always confirm with a
site:search.
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
- [ ] Quintype and PV editorial report what changed on 11–12 Nov 2026 (item 1).
- [ ] Publisher Center checked for PV (items 1–2).
- [ ] Weekly scorecard has a separate "risky traffic" line (item 3).
- [ ] Monthly body-text re-test scheduled (item 4).
- [ ] AI-crawler decision recorded (item 5).
Dependencies and related packages
- P1: the body-text re-test (item 4) is P1's main measure.
- P2 item 10: sponsored-content indexing, separate from item 3.
- P4: PV cartoon listing canonicals (#19) affect the same cartoon pages as item 3.