Table of Contents

Article-writing prompt — read this first

This page is the canonical source of truth for every article published on RTI Wiki.
Both Claude and ChatGPT Codex must read it before writing any new content. Update here, not in chat.

Quick answer

When you generate an article for RTI Wiki, you are not writing “an article about X” — you are building the destination citizen-first answer in India for that query. If a smarter article exists elsewhere on the open web, we have failed.

Inputs you may be given

Step 1 — Classify the query in 3 lines

Bucket Trigger Strategy
High opportunity high impressions + low CTR + position 5-20 better title + meta + intro hook
Quick win position 8-15 + already getting clicks add depth — schema, FAQ, internal links
Content gap relevant query but no dedicated page brand-new ultimate-guide article
Topical authority pillar / cluster expansion cross-link siblings, become the hub

State which bucket and why in one sentence.

Step 2 — Mandatory article structure

Every article must follow this skeleton:

  1. Frontmatter — htmlmetatags block (≤165 char description, comma-separated keywords)
  2. Title — H1, ≤70 chars, ends with “— citizen guide 2026”
  3. <WRAP info> quick answer — 40 to 60 words, direct answer to the query
  4. What X is — in 50 words — exact 40 to 60 words for feature snippet
  5. Legal position in India — Act + section, framework, authority structure, RTI relevance, case-law precedent
  6. Step-by-step process — numbered DokuWiki list
  7. Documents required — bullet list
  8. Common mistakes — bullet list, each with a §-citation
  9. Real-life example — <WRAP center round box> with name, district, dates, exact figures, total cost
  10. Sample RTI letter (if applicable) — `
    ` block with §6(1), §10, §6(3), §7(1), §19(1) citations
  - **FAQ** — 6 to 10 questions, each as `==== Q ====` H4
  - **Sources** — bullet list of authoritative URLs
  - **Related on RTI Wiki** — 5-8 internal cross-links

===== Step 3 — Title + meta: 3 variants, pick strongest =====

Generate three. Each must satisfy the **HARD social-readiness rules**:

  * Title ≤ 70 chars
  * Meta description ≤ 165 chars
  * First paragraph ≥ 100 chars and standalone (works as a tweet)

Variant brief:
  - **Curiosity** — opens a loop ("Why does X take 14 months — and how to unstick in 31 days")
  - **Urgency** — frames cost of inaction ("Stuck in mutation? File this RTI before day 90")
  - **Clarity** — most scannable ("Sample RTI for land mutation delays — citizen guide 2026")

Pick the strongest, ship it. List the others below the article for git history.

===== Step 4 — Internal linking =====

Every article links to **at least 3** of these primary anchors:

  * [[https://righttoinformation.wiki/tools/ai-rti-draft-app.html|AI RTI Drafter]]
  * [[https://righttoinformation.wiki/tools/first-appeal-app.html|First Appeal Builder]]
  * [[https://righttoinformation.wiki/tools/awaaz-rti.html|AwaazRTI (voice)]]
  * [[https://righttoinformation.wiki/tools/pio-reply-checker-app.html|PIO Reply Checker]]
  * [[https://righttoinformation.wiki/tools/timeline-calculator-app.html|Timeline Tracker]]
  * [[:act|RTI Act, 2005]]
  * [[:cases|Case-law database]]
  * [[:rules|State RTI rules]]
  * [[:rti-fees-by-state|State-wise RTI fees]]
  * [[:guide:applicant:application:sample:start|Sample RTI letters index]]

**NEVER** use ''[[:tools:slug|...]]'' — those are static HTML, DokuWiki marks them broken. Always full https URL for /tools/ and /intelligence/ files.

===== Step 5 — Trust signals (3 minimum per article) =====

  * **Statute** — Act + section + year (e.g., "RTI Act 2005, §6(1)")
  * **Government body** — official ministry / commission / portal with a hyperlink
  * **Case law** — Supreme Court / High Court / CIC ruling with citation `(YYYY) X SCC Y`

Cite in-line, not as footnotes. Citations make the article quotable.

===== Step 6 — Schema markup (JSON-LD) =====

Every article embeds:

<code>
<html>
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {"@type": "Article", "headline": "…", "datePublished": "…", "dateModified": "…", …},
    {"@type": "FAQPage", "mainEntity": [{"@type": "Question", …}, …]},
    {"@type": "HowTo", "name": "…", "step": [{"@type": "HowToStep", …}, …]}
  ]
}
</script>
</html>

ONLY <script type=“application/ld+json”> is allowed inside <html> blocks. DokuWiki escapes inline <style>, <svg>, and multi-element <div> blocks as raw text.

Step 7 — Visuals

Plan ONE infographic + ONE feature image per article:

Step 8 — Social distribution copy

Generate three variants:

The Buffer automation picks these up via the OG meta tags + AI rewriting.

Step 9 — CTR opening hooks

Every article opens with ONE of:

Avoid generic openers like “In India, the RTI Act allows…”.

Step 10 — Update strategy

  1. Day 0 — IndexNow ping
  2. Day 7 — re-check GSC; if impressions present but CTR <1%, regenerate title + meta
  3. Day 30 — refresh: add new FAQ entries, update real-life example dates, re-verify statutory citations
  4. Quarterly — link audit (we have a recurring job)

Hard rules (these are HARD failures, not warnings)

  1. Title >70 chars → fails social audit
  2. Meta description >165 chars → fails social audit
  3. First paragraph <100 chars OR hidden inside <WRAP> → fails social audit
  4. slug wikilinks → broken (use full https URL)
  5. Inline <HTML> blocks with <style> or multi-element <svg> → DokuWiki escapes them as <pre> text
  6. Image references that 404 → red wikilink2 link
  7. No statute / case-law citations → article reads like opinion
  8. No real-life example → article is forgettable
  9. No internal links to RTI Wiki tools → user dead-ends, no funnel
  10. Smart quotes inside HTML attributes → DokuWiki kills the parsed HTML

Output format (when you produce an article)

Return a single block in this exact order:

  1. Keyword analysis (3 lines max)
  2. Title + meta — 3 variants (with char counts)
  3. Chosen title + meta (with rationale)
  4. Article body — full DokuWiki source, ready to paste
  5. Internal links used (5+ list)
  6. Schema JSON-LD (separate code block)
  7. Social copy (Twitter / FB / long-form)
  8. Image + infographic plan (1-2 sentences each)
  9. Update strategy (specific dates)

Do not produce explainers about what you are doing — just deliver the artefact.

Special instructions for India

Where this file lives

When this page changes, both AI assistants pick up the new rules on next run because they fetch the URL fresh.

Last revised: 4 May 2026. Supersedes the v1 prompt and the earlier 10-step SEO engine.

, , , , , , ,