Here is the English translation of the provided text:
Create a comprehensive, expert-level journal-style article (minimum 2800 words) demonstrating Expertise, Experience, Authoritativeness, and Trustworthiness (EEAT) principles while being optimized for both Google Discover and Bing search engine algorithms. Focus on the title topic using a natural, journalistic writing style with proper HTML structure throughout, written from the perspective of a domain-specific expert with verifiable credentials for an informed audience seeking authoritative information.
Key Requirements:
- Language and EEAT Foundation: Match the language of the keyword/topic. Maintain a professional tone with appropriate technical accuracy while incorporating domain-specific terminology, evidence-based statements with precise data points, contextual references to relevant professional qualifications, nuanced perspectives showing deep understanding of topic interdependencies, and natural variations in sentence structure, vocabulary, and paragraph length.
- Advanced SEO Optimization: Integrate primary, secondary, and tertiary keywords with natural semantic variations. Implement proper keyword density (2-3% maximum) with strategic placement in H2/H3 headers. Include conceptually related terms and entities without keyword stuffing. Utilize natural LSI (Latent Semantic Indexing) keyword integration based on topic clusters. Incorporate topic-appropriate schema markup suggestions where relevant. Create a user-intent focused meta description suggestion (140-155 characters). Structure content with an information hierarchy reflecting search intent stages.
- Expertise Demonstration: Analyze complex concepts with clarity and precision using domain-appropriate terminology. Present balanced viewpoints showcasing multifaceted understanding of the subject. Incorporate subtle historical context and evolutionary developments relevant to the topic. Reference methodological approaches and industry-standard practices without excessive jargon. Demonstrate critical thinking through measured evaluative statements with supporting evidence.
- Content Architecture: Develop a logical progression of ideas with seamless transitions between sections. Balance theoretical frameworks with practical applications and real-world examples. Include data-driven insights with appropriate contextual interpretation. Address potential objections or limitations with nuanced perspective. Provide actionable insights derived from demonstrated expertise.
Important: Create authentic, specific content with natural human variations. Avoid AI-detection patterns, including repetitive sentence structures or paragraph lengths, overuse of transition phrases or specific adjectives, perfectly consistent formatting or unnaturally uniform section lengths, excessive use of qualifiers or hedging language, and perfectly balanced pro/con arguments with predictable patterns.
HTML Structure:
- Present specific, relevant contextual foundation with natural narrative flow in opening paragraphs. Establish topical authority through demonstrated knowledge rather than explicit claims.
- Use
<h2>for main sections with conceptual keyword integration. - Use
<h3>for subsections with semantic relevance to main topics. - Use
<strong>for key emphasis (varied usage, 2-4 per section). - Use
<em>for technical terms or conceptual highlights (judicious use). - Use
<table>for data presentation with contextual interpretation. - Use
<ul>or<ol>for specific lists with meaningful organization.
Article Key Points:
- Include a visually distinct key points section after the introduction using either a
<div class="key-points-box">or a<table class="key-points-table">. - Provide 4-6 essential takeaways with specific, actionable information.
Required Elements:
- HTML Structure Implementation: Use
<p>for all paragraphs with natural variation in length and structure. - Content Architecture: Develop a logical progression of ideas with seamless transitions between sections.
- Authority Elements: Include industry-relevant data with proper contextual interpretation, technical accuracy with accessible explanation, illustrative examples demonstrating practical application, balanced comparative analysis based on established criteria, and professional perspectives grounded in domain expertise.
- FAQ Section (HTML Only): Include a FAQ section after the main content using semantically natural question formulations. Develop 3-6 questions addressing different informational needs related to the topic.
Critical Requirements:
- Never use abstract placeholders or templated language.
- Always provide contextually specific information with natural variation.
- Incorporate subtle linguistic irregularities that reflect human writing.
- Vary sentence structures, transition phrases, and paragraph lengths.
- Balance technical precision with accessible explanation.
- Structure content according to conceptual logic rather than rigid formulas.
- Integrate domain-specific terminology naturally within explanatory context.
Writing Pattern Requirements:
- Incorporate varied paragraph lengths (3-8 sentences) with natural transitions.
- Utilize occasional sentence fragments for emphasis where contextually appropriate.
- Include natural rhetorical questions in selective locations.
- Vary transition phrases beyond predictable patterns.
- Incorporate measured subjective assessments based on established criteria.
- Use imperfect synonyms and natural word choice variations.
- Demonstrate natural thought progression rather than algorithmic patterns.
Avoid:
- Opening title (start directly with the first paragraph).
<pre>or<code>tags in content structure.- Markdown formatting within HTML framework.
- Excessive or formulaic HTML formatting patterns.
- Marketing language or promotional tone.
- Conclusion heading (integrate closing naturally).
- External links or explicit references to sources.
- Mixing languages within the content.
- Placeholder language or templated structures.
- Square brackets with variables [like this].
- Perfectly balanced section lengths.
- Predictable paragraph structures.
- Repetitive transition phrases.
- Excessive use of qualifiers or hedging language.
- Unnaturally consistent formatting patterns.
