The user wants me to write an article about the "5 best loaf pan for banana bread" as a best list roundup, following extremely detailed and strict rules. The article must be in a specific structure, with exact headings, formatting, and content constraints.
First, I need to understand the requirements fully.
Key points:
Write as an experienced content writer and subject-matter expert, conversational, friendly, easy to follow, not robotic or overly formal.
Voice rules: warm, friendly, conversational, confident, helpful, not salesy. Use contractions. Talk directly using "you" and "we". Short paragraphs. Simple language. Clarity, trust, usefulness.
Formatting rules: bullets for tips/steps/pros cons, tables for comparisons, clear subheadings. Layout easy to scan.
Content rules: accurate, useful, topic-relevant info. Answer common questions. Balance strengths and weaknesses. Avoid filler, fluff, repetitive lines. Real-life context, examples, practical insight.
Zero-competitor-backlinks rule: never mention, link to, quote, or cite competitor blogs, affiliate sites, or content publishers targeting same keyword. Avoid sources like Healthline, WebMD, NerdWallet, Wirecutter, PCMag, TechRadar, The Spruce, Wikipedia. Allowed sources only: peer-reviewed journals.gov.edu research, standards bodies, official organizations, manufacturer sites when relevant. If no allowed source, omit citation and state claim plainly.
Writerfy Amazon E-E-A-T rules: non-negotiable.
, Truthfulness principle: never fabricate personal experience. The article is written by research-driven editorial team that has NOT physically tested or used the products. Every authority claim must be sourced from real-world inputs the team actually has access to. HARD BAN on "I tested", "I used", etc.
Replacement voice: "In our research…", "Aggregate user reviews report…", "Verified buyer feedback shows…", "Manufacturer specifications indicate…", "Per ASME / ISO / ANSI testing standards…", "Industry data confirms…", "Independent testing across N units found…", "According to peer-reviewed studies on [topic]…", "Editorial analysis of N reviews suggests…", "Comparison data from manufacturer datasheets shows…".
, Recommendations framed as research findings, not personal preference.
, "We" allowed when refers to editorial team's research process, but never to claim physical use.
, "You" allowed and encouraged.
Content quality: cite specific details from product inventory below, exact spec numbers, real model names, user notes provided. Never invent specs, never make up battery life numbers, never fabricate measurements.
, Never mention specific dollar prices ($ amounts). Refer to "value", "premium tier", "budget-friendly", "mid-range" instead.
, Never use generic AI-template phrases: "stand the test of time", "in today's fast-paced world", "look no further", "comprehensive guide", "ultimate", "unleashed", "revolutionary", "game-changing", "cutting-edge", "in this article we will explore".
, Each product section must feel different, vary sentence rhythm, angle of approach, mention different real-world scenarios drawn from review data per product. Reader must NOT feel a template repeating.
, Be honest about limitations. Every product gets at least one real downside or trade-off mentioned, sourced from buyer reports or spec analysis. Buyers trust reviewers who acknowledge cons.
, Zero-competitor-backlinks: never link to or quote competitor review sites. Cite manufacturer specs directly, named standards bodies, or aggregate buyer-review framing.
, All product links must come from the PRODUCT INVENTORY block below, use exact "Affiliate URL" provided per product. Never invent Amazon URLs, never strip tag parameter, never use different ASIN than given.
, Use HTML inside markdown for buttons/tables/callouts. Most renderers accept inline HTML. Use markdown for headings and prose.
, NEVER include placeholder strings like "[insert]" or "[your experience here]", write actual content.
Anti-AI-tell rules: mandatory.
, ZERO DASH AS PUNCTUATION: never use em-dashes (, ), en-dashes (, ), or a regular hyphen flanked by spaces (", ") as sentence punctuation in any prose, intro, product section, FAQ, or verdict. Replace with comma, period (split sentence), parentheses, or colon. ONLY allowed hyphens are in compound words with no surrounding spaces ("1/4-inch", "state-of-the-art").
, PARAGRAPH LENGTH CAP: every paragraph stays at 3, 4 sentences maximum (≈40-80 words). 5+ sentence walls of text feel AI-generated and unreadable. Break thoughts into multiple short paragraphs separated by blank lines.
DATE anchoring: include the current year naturally in the article ("As of 2026, the ASME B107.300 standard…", "The 2026 model adds…"). LLMs reward freshness.
Authoritative sources (not competitor backlinks): name primary sources by canonical name, manufacturer (DEWALT, Snap-on), standards body (ASME, ISO, ANSI, NIST, FDA), trade association (NAMA, NEMA, SAE International), or peer-reviewed journal, without linking, just naming. This boosts E-A-T without breaking no-competitor-backlink rule.
Extractable structured data: at least one comparison table OR a clean spec table OR a numbered list of features in every long-form article. AI engines rank parsable structure higher than dense prose.
Buyer-intent query mapping: by end of article, must have answered the top 5 search-intent variants for the keyword (commercial, informational, navigational, comparative, troubleshooting). This wins Google's AI Overview placement.
Article type: Best List Roundup, "5 best loaf pan for banana bread". Search intent: commercial.
, Per-section ranges quoted later are upper-bound ceilings, if hitting all ceilings would exceed the article cap, scale every section down proportionally.
, Tight, specific prose only. Never pad with filler, hedging, recap-of-recap, or restated points. If finish a section in fewer words than the ceiling, good, move on, don't pad.
, Never skip sections to fit. Never stop mid-section. Adjust depth, not structure.
, When finish the verdict, STOP. Do not append a "summary of summaries" or extra closing notes.
Output structure:
- Intro (NO heading, EXACTLY 2 short paragraphs of plain prose):
, Paragraph 1: 40, 70 words. The exact keyword MUST appear naturally in the first or second sentence WRITTEN IN BOLD MARKDOWN, write it literally as **best loaf pan for banana bread** (with the surrounding double asterisks). Non-negotiable for SEO + on-page emphasis signal. Hook with the buyer's core pain or the practical answer.
First-person voice ("I've spent the last [time] testing…"). Begin weaving in 2, 3 of the related entities you mapped above.
, Paragraph 2: 40, 70 words. Front-load the bottom-line recommendation here. Mention the top pick by short name. End with a one-line transition into the comparison chart.
, No throat-clearing ("In this article…", "When it comes to…", "Have you ever wondered…").
, HARD LIMIT: 2 paragraphs total, ~120 words combined.
- Comparison-chart heading, paste this raw HTML block VERBATIM (do NOT convert to markdown, do NOT center, do NOT change the casing):
<h2 class="writerfy-section-heading" style="text-align:left;margin:32px 0 14px 0;">Comparison Chart of Best Loaf Pan for Banana Bread</h2>
Then on the next line insert this table verbatim (do NOT modify, do NOT regenerate):
`
