1. **Analyze the Request:** * **Keyword:** "Iphone 16 Pro Price After Gst" * **Context:** A jumble of text mentioning "iPhone Price Drop 2026", "Big Billion Day Sale", "Freedom Sale", Flipkart/Amazon discounts, Rhinoshield/Moft deals, and "February 2026". * **Requirements:** 600-900 words, concise, factual, SEO-friendly, safe HTML tags (h2, h3, p, ul, ol, li, strong, em), no markdown fences, no AI mention. * **Constraint Checklist & Confidence Score:** * Concise? Yes. * Factual? Yes (need to handle the "2026" context carefully, as it's future-dated in the prompt but implies current pricing for that time, or perhaps a hypothetical. *Correction*: The prompt context is messy and looks like video description spam from 2026. However, I must write an *original* article. If I write as if it's 2026 based on the prompt's context, it might be confusing if the user actually wants current info. *Re-reading the prompt*: "Use this context when useful." The context explicitly mentions "iPhone Price Drop 2026" and "February 2026". If I write about 2024/2025 pricing, I ignore the context. If I write about 2026, I am hallucinating future facts. *Decision*: I will write the article in a way that acknowledges the pricing structure generally, but since the user provided specific context about "2026" and "Price Drop," I will frame the article around the *release* of the iPhone 16 Pro and how GST affects it, while perhaps acknowledging the context provided as a "future outlook" or simply interpreting the "2026" context as a typo for "2024" or "2025" in the user's source material? * *Wait*, the prompt says "Use this context when useful". The context says "iPhone Price Drop 2026". This is highly specific. If I ignore it, I fail the instruction. If I use it, I might be writing fiction. * *Alternative interpretation*: The user might have pasted a description from a futuristic or speculative video, or a very dated one. However, the iPhone 16 Pro was released in late 2024. By 2026, the iPhone 18 would be out. * *Safe bet*: The keyword is "Iphone 16 Pro Price After Gst". I should focus on the *launch price* and how GST works, or the current market price (as of late 2024/early 2025). The "2026" context is likely noise or a specific scenario the user wants me to mimic (a "future" article). * *Actually*, looking at the prompt again, it asks for an *original* article. Writing an article dated in 2026 about a 2024 phone (iPhone 16 Pro) implies it's an older model then. The context mentions "iPhone Price Drop 2026... iPhone 17, 17 Pro, 16 & More". This implies the iPhone 16 is being discounted in 2026. * *Strategy*: I will write the article focusing on the iPhone 16 Pro pricing structure, GST implications, and how prices evolve over time (including sales). I will treat the "2026" context as a specific scenario for a price drop/sale prediction or a hypothetical future scenario, but I must be careful not to present it as "fact" if it hasn't happened. * *Better Strategy*: The prompt asks to use the context *when useful*. The context is weirdly specific to 2026. I will write a general SEO article about the iPhone 16 Pro price and GST, but I will frame the "future outlook" or "price history" section using the provided context as a reference point for *potential* long-term value or specific sales events (like Big Billion Day) that recur, while being vague enough to remain factual about *how* pricing works. * *Refined Strategy*: I will write about the iPhone 16 Pro launch price and GST calculation (which is factual). I will then discuss price drops and sales (