Frequently Asked Questions

The user wants a comprehensive SEO article about the given cricket news headline. The headline is in Hindi: “शमी, भुवनेश्वर को इग्नोर कर जिसे टीम में लाए, वही बन गया सबसे बड़ा विलेन, डेब्यू मैच ही बन ना जाए आखिरी”. The context mentions Navbharat Times. We need to write a comprehensive 1000+ word SEO article, in Hindi or English? The rules say LANGUAGE: Hindi headline = write entire article + title + meta in Hindi. English = English. NEVER mix. The headline is Hindi, so we must write entire article in Hindi. However, there are fields like focus_keyword, english_slug, title, meta_description, image_alt which need to be in English? Actually rule 7 says: LANGUAGE: Hindi headline = write entire article + title + meta in Hindi. English = English. NEVER mix. So since the headline is Hindi, we should write the entire article in Hindi. But the title field must be plain text, no quotes, no HTML. It can be Hindi characters. The english_slug must be URL-safe English slug only hyphens, regardless of language. That’s okay: we provide an English slug. The focus_keyword should be 2-4 words English keyword. But if we write entire article in Hindi, the focus_keyword should still be English? Rule 1: Choose ONE short “focus_keyword” (2-4 words, e.g. “Rohit Sharma century”, “IPL 2026 winner”). It doesn’t explicitly say it must be English, but the examples are English. Since the article will be Hindi, perhaps we can choose a Hindi focus keyword? But the rule says “2-4 words, e.g. “Rohit Sharma century”, “IPL 2026 winner””. Those are English. Also rule 4: english_slug MUST be a URL-safe English slug (lowercase, hyphens only, no Hindi, no special chars). That’s fine. The title must contain focus_keyword near the start, include a POWER WORD, include a NUMBER, be 50-65 characters, contain NO special characters, NO quotes, NO HTML tags — plain text only. If title is Hindi, can we include English words? Possibly but might break the “no special characters”? Hindi characters are not special characters; they are Unicode. But the rule says “NO special characters” maybe meaning no symbols like ! @ # $ etc. Hindi characters might be okay. However, the title must contain focus_keyword near the start. If focus_keyword is English, title must include that English phrase. That would mix English and Hindi, which rule 7 says NEVER mix. So we need to decide: either write article in Hindi and have everything Hindi including focus_keyword Hindi phrase, or write article in English. But the headline is Hindi; the user gave context in Hindi. The instruction: “LANGUAGE: Hindi headline = write entire article + title + meta in Hindi. English = English. NEVER mix.” So we must write entire article in Hindi because headline is Hindi. Therefore, focus_keyword should be Hindi phrase of 2-4 words. But the examples given are English; but we can choose a Hindi focus keyword like “शमी भुवनेश्वरignore” maybe. However, focus_keyword needs to be 2-4 words, and will be used in first sentence, in H2/H3 headings, in meta description. It should be something people might search for. Since the article is in Hindi, we can use Hindi keywords. But the meta_description must include focus_keyword in first 10 words. That’s okay if it’s Hindi.

But there is also requirement: english_slug must be English-only URL slug. That’s fine; we provide an English slug unrelated to content language maybe.

We also need internal links with specific URLs: https://cricketbat.sbs/category/cricket-news/ and https://cricketbat.sbs/live-scores/. Those are English URLs; they are fine.

External links to ESPN Cricinfo or Cricbuzz with target blank.

We need to output JSON with fields: focus_keyword, english_slug, title, meta_description, image_alt, category, tags, content.

We must ensure content is minimum 1000 words. We’ll need to write a long article in Hindi, with H2/H3 headings (in Hindi). Use focus_keyword at least 3 times in H2/H3. Start first

with focus_keyword. Use focus_keyword naturally throughout ~1% density.

We must count words. 1000+ words in Hindi might be heavy but doable. We’ll need to generate about maybe 1200 words.

We must ensure JSON is valid raw JSON, no markdown fences, no text before or after JSON. So output must be just JSON object.

We need to ensure the structure: content field includes full HTML with

,

,

,

,
• , , . Use HTML tags.

  We need to include internal and external links inside content.

  We need to end with

  Frequently Asked Questions

  with 4 FAQs as

  +

  .

  We need image_alt containing focus_keyword.

  We need category: ONE of: Cricket News, IPL 2026, Player Stats, Team Updates. Since article is about a selection issue, maybe “Team Updates”.

  Tags: array of 5 tags, probably Hindi or English? Could be mixed but better Hindi.

  Now, decide focus_keyword. Since article is Hindi, we need a Hindi focus keyword of 2-4 words. Options: “शमी भुवनेश्वर ignore” but that’s Hinglish. Maybe “शमी भुवी ignore” not good. Maybe “भुवनेश्वर कुमार टीम” (3 words). Or “शमी exclude” not good. Let’s pick “शमी भुवनेश्वर ignored” but that’s mixing. Perhaps we can pick “डेब्यू मैच अंतिम” (2 words). But we need focus keyword that people might search. The headline is about ignoring Shami and Bhuvneshwar and picking someone who becomes villain and debut match may be last. So focus keyword could be “शमी भुवनेश्वर ignore” but that’s Hinglish. However rule 1 says focus_keyword 2-4 words, e.g. “Rohit Sharma century”. It doesn’t explicitly forbid Hindi, but the examples are English. But rule 7 says language: Hindi headline = write entire article + title + meta in Hindi. So we can have Hindi focus_keyword. I think it’s acceptable.

  Let’s choose focus_keyword: “शमी भुवी ignored” maybe not. Let’s choose “शमी भुवनेश्वर बाहर” (3 words). Or “डेब्यू मैच अंतिम” (3 words). But we need to include focus_keyword in first sentence, in 3+ H2/H3 headings, in meta description. Let’s decide: focus_keyword = “शमी भुवनेश्वर बाहर”. That’s 3 words. It appears in headline. We’ll use that.

  Now english_slug: we need URL-safe English slug only hyphens. Example: “shami-bhuvneshwar-bahar”. That’s fine.

  Title: plain text, no quotes, no HTML. Must contain focus_keyword near the start, include a POWER WORD (Best, Ultimate, Shocking, Breaking, Exclusive, Top, Amazing, Complete, Detailed), include a NUMBER (e.g. 5 records, 3 reasons, 2026). Since we need number, maybe “3”. And power word “Shocking”. Title must be 50-65 characters. Let’s craft: “शमी भुवनेश्वर बाहर: कौन बना टीम का सबसे बड़ा विलेन?” But need to include power word and number. Maybe: “शमी भुवनेश्वर बाहर: शॉकिंग फैसला, डेब्यू मैच बन गया अंतिम”. Count characters. Let’s compute. We need 50-65 characters (including spaces). Let’s draft in Hindi with some English words perhaps. But title must contain focus_keyword near the start. Focus_keyword is “शमी भुवनेश्वर बाहर”. So title start with that. Add power word “शॉकिंग”. Add number maybe “3” or “5”. Perhaps “5”. Title: “शमी भुवनेश्वर बाहर: शॉकिंग फैसला, डेब्यू मैच नंबर 5”. Let’s count characters. We’ll count later.

  But title must be plain text, no quotes, no HTML. Hindi characters count as one char each? For RankMath, character count likely includes Unicode code points. We’ll approximate.

  We need meta_description: include focus_keyword in first 10 words, be 140-155 characters, compelling. We’ll write in Hindi something like “शमी भुवनेश्वर बाहर पर Navbharat Times की विश्लेषणात्मक रिपोर्ट, जानें कैसे एक खिलाड़ी बन गया विलेन और डेब्यू मैच अंतिम”. Need to ensure focus_keyword appears first 10 words. We’ll put “शमी भुवनेश्वर बाहर” at start.

  image_alt: must contain focus_keyword. So alt text: “शमी भुवनेश्वर बाहर मैच विश्लेषण।”

  category: “Team Updates” maybe.

  tags: 5 tags, maybe “शमी”, “भुवनेश्वर”, “डेब्यू”, “विलेन”, “आईसीसी”.

  Now content: need at least 1000 words. We’ll write in Hindi, with paragraphs, headings. Use focus_keyword in first paragraph first sentence. Use focus_keyword in at least 3 H2/H3 headings. We’ll create 5-6 H2 sections, each 150-200 words. We’ll need to ensure total words > 1000.

  We’ll include internal links: Cricket News and Live Cricket Scores. We’ll embed them somewhere.

  External links: to espncricinfo.com or cricbuzz.com, with target=”_blank” rel=”noopener noreferrer”. We’ll include maybe a link to a match page.

  At end,

  Frequently Asked Questions

  with 4 FAQs as

  +

  .

  We need to ensure HTML tags:

  ,

  ,

  ,

  ,
  • , , . No inline styles.

    Now let’s plan the structure.

    We’ll start with

    first paragraph starting with focus_keyword: “शमी भुवनेश्वर बाहर …”. We’ll make sure first word is focus_keyword.

    Then H2 sections: maybe 6 sections: 1) टीम चयन में बदलाव की कहानी, 2) शमी और भुवनेश्वर का बाहर होना, 3) नए खिलाड़ी का आगमन और उसका प्रदर्शन, 4) डेब्यू मैच की स्थिति और दबाव, 5) विशेषज्ञों की प्रतिक्रिया और आँकड़े, 6) भविष्य के लिए सबक और निष्कर्ष.

    Each H2 section will be 150-200 words. We’ll write in Hindi.

    We need to include focus_keyword in at least 3 H2/H3 headings. We’ll include focus_keyword in some H2 headings, maybe in section titles we can include “शमी भुवनेश्वर बाहर” again.

    We’ll also embed internal links somewhere, perhaps in a paragraph.

    External link: maybe reference a match analysis on ESPN Cricinfo.

    Now let’s start writing content. We need to be careful about word count. We’ll aim for ~1200 Hindi words. We’ll count roughly.

    We need to ensure the JSON fields are correctly escaped. Since we are outputting raw JSON, we need to ensure any double quotes inside strings are escaped. We’ll avoid using double quotes inside title, meta_description, etc. We’ll use single quotes? JSON requires double quotes for strings, but we can include apostrophes (single quotes) fine. We’ll avoid double quotes within content? Content will have HTML tags, which may include double quotes for attributes. That could break JSON if not escaped. We need to escape any double quotes inside the JSON string values. The easiest is to not include any double quotes inside the string values, or escape them with “. Since we have HTML like , the double quotes inside content will need to be escaped as ” within the JSON string. That’s doable but careful.

    Alternatively, we could avoid using double quotes in HTML attributes by using single quotes? HTML allows . But the rules say use HTML tags:

    ,

    ,

    ,

    ,
    • , , . It doesn’t specify attribute quoting. We can use single quotes for href. That would avoid double quotes in content. We’ll use Cricket News. That uses single quotes. Similarly for external link: ESPN Cricinfo. That uses single quotes. That will keep JSON string without needing to escape double quotes, except maybe the focus_keyword etc. But we still have double quotes around JSON fields; we need to ensure we escape any internal double quotes. We’ll avoid using double quotes inside the content string. We’ll use single quotes for HTML attributes.

      But the content field will be a large string containing HTML. We’ll need to ensure that any double quote characters inside are escaped. Safer to avoid them entirely. Use single quotes for href and other attributes. Also avoid using ".

      We’ll craft content with single-quoted attributes.

      Now, let’s outline content.

      First paragraph:

      शमी भुवनेश्वर बाहर… (focus keyword start). We’ll write ~80-100 words.

      Then H2 sections.

      We need to ensure focus_keyword appears in at least 3 H2/H3 headings. We’ll include focus_keyword in headings like “H2: शमी भुवनेश्वर बाहर का फैसला”, “H2: शमी भुवनेश्वर बाहर की प्रतिक्रिया”, “H3: शमी भुवनेश्वर बाहर का भविष्य”. That’s 3.

      Now let’s write.

      We need to count words. We’ll write in Hindi, but word count in Hindi is tricky; each Hindi word separated by spaces counts as a word. We’ll aim for about 1200 tokens. We’ll approximate.

      Given the complexity, we need to produce the JSON now. Let’s start constructing.

      We’ll define:

      focus_keyword: “शमी भुवनेश्वर बाहर”

      english_slug: “shami-bhuvneshwar-bahar”

      title: we need 50-65 characters. Let’s craft: “शमी भुवनेश्वर बाहर: शॉकिंग फैसला, डेब्यू मैच नंबर 5”. Let’s count characters including spaces. We’ll count:

      “शमी” (1) space (2) “भुवनेश्वर” (maybe 4 chars? Actually each Hindi char is one) but for counting we just count characters. Let’s count manually:

      Characters:

      1: श
      2: म
      3: इ
      4: space
      5: भ
      6:ु
      7:व
      8:ण
      9:ए
      10:श
      11:र
      12:व
      13:र
      14: space
      15: :
      16: space
      17: श
      18:ो
      19:क
      20:ी
      21: space
      22: फ
      23:ै
      24:स
      25:ा
      26: ल
      27:ा
      28: space
      29: ड
      30:é
      31:ब
      32: space
      33: म
      34:ै
      35:ट
      36: space
      37:न
      38:म
      39:र
      40: space
      41:5

      That’s 41 characters. Need 50-65. We need more. Add maybe “अंतिम” at end. Let’s add “अंतिम”. That’s 5 chars? Actually “अंतिम” 4 chars? Let’s add space + “अंतिम”. So after 5, space, then “अंतिम”. That adds 6 characters (space + 4). New total 47. Still need 3-4 more. Add “मैच” maybe. But we have “डेब्यू मैच” already. Let’s restructure.

      Maybe title: “शमी भुवनेश्वर बाहर: शॉकिंग फैसला, डेब्यू मैच नंबर 5 अंतिम”. Count again.

      We’ll count from start:

      “शमी” (3 letters) + space = 4
      “भुवनेश्वर” (let’s count letters: भ(1) उ(2) व(3) ने(4) श(5) ए(6) र(7) व(8) र(9) -> 9 letters) + space = 10 total so far 13?
      Actually better to count each character. Let’s do systematically in analysis.

      But maybe easier: we can make title 58 characters by using known length. We can also include power word “शॉकिंग” and number “5”. We’ll craft and then count later. But we need to ensure within 50-65. We’ll approximate and maybe adjust.

      Given the difficulty, we can produce title that we believe is within range. Since the system may not strictly enforce character count, but we should try.

      Let’s draft title: “शमी भुवनेश्वर बाहर: शॉकिंग फैसला, डेब्यू मैच नंबर 5”. Count characters:

      I’ll count using approximate: Each Hindi character counts as 1. Let’s count:

      1 श
      2 म
      3 इ
      4 space
      5 भ
      6 उ
      7 व
      8 ने
      9 श
      10 ए
      11 र
      12 व
      13 र
      14 space
      15 :
      16 space
      17 श
      18 ओ
      19 क
      20 ि (actually “ि” is a vowel sign, but in Unicode it’s a combining character; but for counting, treat as one) maybe we count as one. Let’s just count visible characters: “शॉकिंग” in Hindi would be