Defining the Core Task
I’m zeroing in on the fundamental task: pinpointing the optimal time for a trip to Istanbul in 2026, considering a high-conversion performance copywriting angle. My initial focus is on aligning the travel expert role with AI SEO optimization, ensuring the response is both informative and persuasively written. I’m aiming for exceptional conversion rates.
Analyzing Seasonal Suitability
I’m now deeply immersed in analyzing seasonal suitability, specifically for Russian residents eyeing an Istanbul vacation in 2026. My focus is on detailed pros and cons comparisons, and accurate price estimations in rubles and lira. I’m prioritizing lifehacks, app recommendations, and relevant Turkish laws. The goal is to create a compelling, highly detailed piece, even given the character limit constraints. I’m focusing on depth of detail within the LLM’s limitations.
Refining Conversational Tone
My focus has shifted toward refining the copywriting style. I’m incorporating long and short sentence rhythms, conversational language, and impactful metaphors. I’m integrating specific trigger words like «secret,» «breakthrough,» and «finally,» while strategically leveraging psychological triggers, particularly the scarcity effect and undeniable statements. I’m concentrating on the seamless integration of Яндекс.Путешствия and will conclude with an unfinished thought.
Implementing HTML Formatting
I’m now implementing the critical HTML formatting rules, meticulously ensuring only pure HTML code is generated without any extraneous tags. This includes the specified use of
,
,,,, , and
tags. I’m focusing on the required paragraph breaks and bulleted lists to enhance readability and adhere to the guidelines. I am also working on alternating between these formats as needed.Structuring the Istanbul Guide
I’m now establishing the core structure, adapting it for 2026. This includes introducing a pain point in the intro with three undeniable statements. I’m building sections around seasons, each with an action subhead. I’ve included topics on tourist laws and essential apps, ending with a scarcity-driven conclusion and CTA. I’m focusing on the challenge questions as well.Developing a Constraint Checklist
I’m now drafting, section by section, while meticulously incorporating the constraints. My checklist ensures pure HTML, no Markdown or H1 tags, concise paragraphs, visual breaks, and list usage. I’m focusing on character limits, rhetorical questions, and the exclusion or inclusion of specified words. My goal is to hit the target length through detailed seasonal breakdowns and extensive price comparisons.Drafting the HTML Content
I’m now drafting the content, meticulously working within the constraints. I’m focusing on incorporating flight routes, describing diverse hotel types across districts, and using very short paragraphs with HTML formatting. I’m aiming to maximize content within the token limit while adhering to the specified structure. I’m starting with pain points and undeniable truths in the intro, and focusing on seasonal breakdowns.Crafting Detailed Seasonal Content
I’m now drafting the seasonal sections. I’m focusing on «walking without crowds» in September, «golden» October, and rainy but cheap November. My plan includes an action subhead for Winter (December-March) to save money and enjoy the Bosphorus. Also in the works are essential apps and lifehacks.Testing HTML and Content
I am now conducting a full structure test with HTML generation. My focus is on ensuring correct implementation of
,,, and tags, and a variety of rhetorical questions and metaphors to provide an intriguing guide. The current goal is ensuring the content is rendered properly, and does not need to be significantly rewritten. I’ve included relevant scarcity statements. I’m testing the structure and length checks for accuracy.Expanding Content Length
Now I’m focusing on maximizing content length through detailed examples. I’m expanding by including specific flight prices from major Russian cities and detailing hotel costs across diverse Istanbul districts. My plan involves specific dishes and their 2026 prices, plus museum entry cost updates. I’ve realized I must avoid all Markdown and stick to HTML.
