Tamil is not just English with a different font. Tamil script rendering, per-edition URLs, Google News Tamil eligibility, paywall in ₹, Tanglish-aware search, and correct handling of Tamil ligatures (ஸ்ரீ, க்ஷ, த்ரி) all need first-class support — not plugin bolt-ons. Here's what actually matters when you pick a CMS for a Tamil news site, plus what dpublish ships for Tamil publishers baseline.
/ta/)
hreflang between English + Tamil
Google News Tamil ready
Most CMSes technically "support" Tamil in the sense that Unicode text renders in a Tamil font if you install one. That is not the same as being a good Tamil news CMS. Tamil publishing has structural requirements that generic platforms treat as edge cases: per-edition URLs, hreflang between translation-group siblings, per-language sitemaps, Tamil font weight (200-350 KB before subsetting), correct html lang="ta" + og:locale="ta_IN" + schema.org inLanguage: "ta" on every public page, paywall in ₹, and Google News Tamil eligibility (separate publisher-center registration from English).
What to look for: a CMS that ships opinionated defaults for all of the above, not a CMS that says "yes it's possible" and hands you 8 configuration surfaces. For most Indian Tamil publishers in 2026 the honest choice is between: dpublish (Tamil baseline on every plan, per-edition URL on Growth+, ₹19,999/mo start), WordPress + WPML + Tamil font plugins (works but you assemble it), or a bespoke build (only if you have engineers).
Six technical requirements that separate "supports Tamil" from "built for Tamil publishing". Ask any prospective CMS these — the answers reveal whether the platform is opinionated for Tamil or just tolerant of it.
A full Noto Sans Tamil file is ~220 KB (WOFF2) — smaller than Devanagari but still enough to hurt mobile LCP if you ship it on every page. A good Tamil CMS ships automatic subsetting per tenant (only the glyphs your site actually uses) and lazy-loads Tamil fonts only on pages that render Tamil text — not on your English homepage. Bad Tamil CMSes ship the full font on every page or make you configure a plugin like Autoptimize to do it. Also watch for Grantha script support (used in older Tamil literary content and Sanskrit-loanwords) if your archive has classical or religious content — not every Tamil font ships Grantha glyphs.
/ta/, ta.example.com, or example.tamil?Three URL strategies for Tamil content, three tradeoffs. Subdirectory /ta/ (recommended by Google for most cases) is easiest for consolidating link equity and simpler for hosting. Subdomain ta.example.com gives operational independence per edition. ccTLD is rarely useful. Most WordPress multilingual plugins default to language cookies + URL parameters, which is the worst option because it breaks caching and hurts SEO. A Tamil CMS should default to /ta/ subdirectory with proper canonical + hreflang — no configuration needed.
html langSetting <html lang="ta"> on Tamil pages is table-stakes. The real signal Google needs is <link rel="alternate" hreflang="ta" href="..."> on the English version of the same story and vice-versa, plus hreflang="x-default" pointing to the language-picker page. This tells Google "the Tamil version at /ta/chennai-metro is the Tamil translation of /en/chennai-metro" so Tamil readers land on the Tamil version from search. Most WordPress multilingual plugins get this partly right; most Indian custom CMSes skip it entirely, and that failure costs Tamil publishers most of their Tamil-search traffic.
Google News requires a separate publisher-center listing per language. Your English site being approved for Google News doesn't automatically qualify your Tamil edition. The Tamil site needs its own Google News sitemap (/sitemap-news-ta.xml), correct og:locale="ta_IN", correct NewsArticle schema with inLanguage: "ta", and a distinct publisher-center submission with Tamil-labelled ownership documents. A Tamil CMS should generate the sitemap and metadata automatically; you handle the publisher-center submission.
Tamil news subscribers pay in ₹, expect UPI as a payment option, and often prefer Razorpay-familiar checkout over Stripe. A Tamil-first CMS should ship paywall with Razorpay + UPI + one of PayU/Cashfree as first-class options, not Stripe-only. Also worth verifying: does the paywall UI itself render in Tamil (button labels, error messages, receipt emails)? Most SaaS paywall products are English-only in the UI even when they support INR in the currency dropdown — a small friction that consistently costs conversion with Tamil-first readers.
Tamil readers search for Tamil content using a mix of scripts — more so than in any other Indic language, because Tanglish (Roman-script Tamil) is heavily used in messaging apps and social media. "chennai metro" (Roman), "சென்னை மெட்ரோ" (Tamil script), and "chennai மெட்ரோ" (Tanglish mixed) should all return the same Tamil article. This requires transliteration handling in the search index, not just Unicode normalization. Ask your prospective CMS: does search treat chennai and சென்னை as the same token? If it doesn't, most of your Tamil-first readers won't find the content they're looking for — they'll bounce to Google and land on a competitor.
Fonts, per-post metadata, hreflang, and per-language sitemaps ship baseline on every plan — for all ten scripts, not just Tamil. If you plan to add regional editions (Telugu, Malayalam, Kannada) later, the infrastructure is already in place.
How the main options for a Tamil news site actually compare on the six Tamil-specific requirements above. Sourced from each platform's public documentation and standard Indian-publisher implementations.
| Capability | dpublish | WordPress + WPML | ThePubLive | Custom build |
|---|---|---|---|---|
| Tamil font subsetting per tenant | Automatic | Plugin (Autoptimize + WPML) | Manual | You build it |
Per-edition URL /ta/ | Growth+ default | WPML config; often URL-param default | Not offered | You build it |
| hreflang between EN/TA translation-group siblings | Automatic | WPML supports; often misconfigured | Manual per-post | You build it |
Per-language sitemap /sitemap-ta.xml | Automatic | Yoast Multilingual (extra) | Not offered | You build it |
Correct html lang="ta" + og:locale="ta_IN" | Automatic | WPML sets this | Manual | If you remember |
Google News Tamil sitemap (sitemap-news-ta.xml) | Baseline | Yoast News Add-on | Yes | You build it |
| Paywall in ₹ with UPI + Razorpay | Native on Starter | MemberPress + Razorpay add-on (~₹36k/yr) | Advanced+ tier only | You build it |
| Tanglish + transliteration search (Roman ↔ Tamil) | Growth+ | Not standard | Not standard | You build it |
| Paywall UI localised to Tamil (buttons, receipts) | Yes | English-only | English-only | You build it |
| Wire ingest (PTI/ANI/IANS/Reuters) + AI translate to Tamil | Growth+ (native) | Manual copy-paste | Manual copy-paste | You build it |
| PWA + push notifications for Tamil readers | Every plan | PWA plugin | Separate app build | You build it |
| Time to launch a Tamil site | 24-48 hours | 2-4 weeks (plugin config) | 1-2 weeks | 2-6 months |
| Starting monthly cost | ₹19,999/mo, ₹0 setup | ₹8-15k/mo + WPML + MemberPress | ₹20,503/mo + ₹98,808 setup | ₹4L+ upfront |
Four patterns Tamil publishers should build around from day one — not retrofit after the site goes live.
Tamil readers search Google in a mix of Tamil script, Roman-transliterated Tamil (Tanglish), and mixed script — Tanglish share is materially higher than in Hindi or Bengali because Tanglish is the default on messaging apps for a large fraction of Tamil-speaking youth. "சென்னை மெட்ரோ", "chennai metro", and "chennai மெட்ரோ" all show different SERPs. A Tamil-first CMS should optimize titles + slugs so Google's Tamil indexing surfaces your content on all three query variants — usually by keeping the Tamil title as H1 while including a transliterated Tanglish slug and English meta description.
Google Discover has significantly higher click-through rates on regional-language content in India than on English content, because Discover surfaces content in the user's device language and most Android devices in Tamil Nadu are configured in Tamil. This means Tamil publishers should over-index on Discover-optimization work: 1200x600px hero images, avoid clickbait titles (Discover penalizes them harder than search does), correct NewsArticle schema with inLanguage: "ta", and use IndexNow for freshness. Tamil Discover CTR is competitive with Hindi and materially above English.
Tamil news traffic skews heavily to lower-bandwidth 3G/4G connections and mid-range Android devices — particularly in Tier-2 and Tier-3 Tamil Nadu towns. AMP pages load 2-3x faster on this hardware than non-AMP mobile pages, which measurably improves Google News + Discover CTR. Global AMP relevance has declined, but for Tamil news publishers with meaningful district-level readership it's still worth shipping AMP versions.
Google's AI Overviews rolled out in Tamil in late 2025 and Perplexity added Tamil in early 2026. Both retrieval systems index Tamil content but the corpus is still small relative to English — which means Tamil content that's well-structured for LLM extraction (proper NewsArticle schema, self-contained answer paragraphs, clear author + published-date metadata) has a disproportionate opportunity to be cited. This window closes as more Tamil publishers ship LLM-optimized markup. dpublish ships AEO / LLMO defaults on every page — you don't have to think about it.
Whether you're launching a fresh Tamil edition or migrating an existing Tamil WordPress site, the sequence is the same.
Decide whether your Tamil edition lives at /ta/, ta.yourdomain.in, or a distinct .in ccTLD. For most Tamil publishers we recommend /ta/ subdirectory: consolidates link equity, easier CDN configuration, no separate SSL cert. If you already have an established English domain, we set up /ta/ as an edition prefix on Growth+ tenants. If you plan to add Telugu, Malayalam, or Kannada later, the same edition-URL pattern extends cleanly.
If you have existing Tamil content on WordPress or another CMS, we migrate it with Tamil encoding preserved (UTF-8 throughout, no character-set drift, Grantha script glyphs retained where present). Fresh Tamil sites get 3 sample Tamil posts, a Tamil category tree, and Noto Sans Tamil font subsetting configured automatically for your tenant. Category names, tag slugs, and navigation labels get localized.
hreflang between Tamil and English translation-group siblings gets auto-generated on every post. Tamil Google News sitemap (/sitemap-news-ta.xml) is available immediately. We help you file the Google News publisher-center registration for the Tamil edition — typically 48-72 hour turnaround from Google. IndexNow ping-on-publish is enabled by default so Bing + Perplexity notice new Tamil content within seconds of publish.
Paywall configured with Razorpay + UPI + one of PayU/Cashfree, with Tamil UI on the checkout flow and Tamil-localized receipt emails. Newsletter templates get Tamil variants with Tamil subject-line and preview-text handling. Comment moderation rules include Tamil profanity + spam pattern seeds (including Tanglish variants).
Your team starts publishing. We monitor GSC for Tamil indexation, verify all hreflang tags render correctly, check Core Web Vitals field data on mobile (where most Tamil traffic lands), and confirm Google News Tamil ingest is working. Any issues get fixed by our team — you focus on the content.
Tamil-specific questions that come up on every publisher call.
Noto Sans Tamil (from Google Fonts) is the safest default — comprehensive Tamil coverage including ligatures (ஸ்ரீ, க்ஷ, த்ரி), weights 400 + 700 available, matches system fonts on most Android devices in Tamil Nadu. Mukta Malar is a good alternative if you want slightly more editorial character; Catamaran and Hind Madurai also work well for headlines. Avoid using English fonts (Inter, Roboto) with a Tamil fallback — the fallback substitution creates visual inconsistency and hurts readability. dpublish ships Noto Sans Tamil lazy-loaded per tenant by default; you can swap to any Google Fonts Tamil face on Growth+.
.in domain for a Tamil news site?No. Google's own guidance (Search Central docs) recommends using subdirectories (example.com/ta/) or subdomains for multi-language sites. ccTLDs like .in are useful only when you're targeting a specific country's audience distinct from a global one — not when the language itself already implies the geography. For a Tamil news site targeting Indian readers, a /ta/ subdirectory on an existing .in or .com domain works well and consolidates link equity. If you have a Sri Lanka Tamil audience too, that's a case for a separate hreflang ta-LK variant, not a separate domain.
Google runs Tamil content through Google's Indic-language processing (tokenization, morphological analysis specific to Tamil, ligature normalization) before indexing. Practical implications: you need correct html lang="ta" or Google may run English-language processing on your Tamil text, which produces garbage results; schema.org inLanguage: "ta" on NewsArticle helps Google confirm the language; transliterated titles (Tamil title in native script, transliterated Tanglish slug) give the same content two search-surface presences and materially expand your query-match coverage.
Yes. This is the default multi-edition setup. Your English content lives at yourdomain.in/, Tamil at yourdomain.in/ta/. Each edition has its own homepage, its own category tree, its own newsletter, and its own Google News registration. Content translated between editions gets linked via hreflang automatically. Shared: your admin login, subscriber accounts (a paying subscriber gets access to both editions), and your paywall plans. Available on Growth+. Same pattern extends if you later add Telugu, Malayalam, or Kannada editions.
Yes — this is a first-class use case. Paywall UI is fully localized to Tamil (button labels, plan descriptions, error messages, checkout screens, receipt emails). Payment gateway options include Razorpay + UPI + PayU + Cashfree, all with INR as the native currency. Subscribers can also pay in EMI installments via Razorpay's EMI option on subscription plans, which materially improves conversion for premium annual plans (₹499-₹999 range). UPI conversion for Tamil subscribers is particularly strong — Tamil Nadu has among the highest UPI transaction volumes in India.
Tamil content typically monetizes at 45-65% of English CPMs on programmatic ad networks (AdSense, Google Ad Manager, direct buys), reflecting Indian ad market economics. But: Tamil audiences are large and Tamil Nadu has strong urban consumer spending power, engagement rates are typically higher (longer session duration, more pages per visit), and paywall conversion is competitive with English for the right content categories (business, politics, entertainment, cinema). Cinema and celebrity content in Tamil monetizes particularly well through direct advertisers. Net result: Tamil editions often out-earn English editions in absolute terms despite the lower per-impression rate.
Strongly recommended — more so than for any other Indic language. Tanglish (Roman-script Tamil) is the default input method for a large fraction of Tamil readers, especially in messaging apps and social media, which spills over into search behaviour. A significant fraction of your readers will search for Tamil content using Roman transliteration (typing "chennai metro" instead of "சென்னை மெட்ரோ"). Without transliteration handling in your search index, these queries return zero results and readers bounce. dpublish's search on Growth+ handles this — the same query returns the same results regardless of script. WordPress-based sites need a specific plugin like SearchWP Indic to get comparable behavior.
dpublish tenants include several Tamil-language regional newsrooms (small-to-mid-sized publishers focused on state, city, and district news across Tamil Nadu and Puducherry). We don't publish tenant names publicly because most publishers on the platform prefer their tech stack not be a marketing point — we can share references privately on a sales call under NDA. The pattern that repeats: Tamil regional publishers migrating from custom PHP builds or WordPress + WPML, choosing dpublish for the per-edition URL + paywall-on-Starter + Tamil-font-subsetting + Tanglish-search combination.
No difference in platform cost. Pricing is by page-view tier (Starter up to 100K PV/mo, Growth up to 1M, Scale up to 10M), not by language. Tamil content and English content count the same in the page-view meter. Per-edition URL structure and Indic scripts are baseline / Growth+ features — you don't pay a per-language surcharge. If you run a bilingual Tamil + English site, the whole site counts against one page-view tier.
Yes. Standard Tamil WordPress migration (with or without WPML) is a supported free migration on Starter and Growth for archives under 15,000 posts. Tamil encoding is preserved end-to-end (we verify no character-set drift during import, and Grantha glyphs in older literary content are retained). If your WordPress site uses WPML, translation-group relationships between English and Tamil posts get preserved as dpublish translation groups. Timeline: 5-7 business days for a standard Tamil migration, 2-3 more days if it's a full English+Tamil bilingual site.
Send us your publication name, target city/region, and (if migrating) your current platform. Within 24 hours we come back with a launch or migration plan, timeline, and — for standard sites — confirmation the migration is free. No sales call needed unless you want one.
Email [email protected]Google indexing guidance sourced from Google Search Central: Managing multi-regional and multilingual sites. WPML + MemberPress pricing sourced from their public pricing pages. Verified 2026-08-09. Have a correction? Email [email protected].