, , – include inline styling on every allowed table tag- full width- border-collapse: collapse- header background: #ffcc00- header text: #000000- body background: #ffffff- body text: #000000- visible dark borders- readable spacing and paddingPART 3 TABLE AFFILIATE RULEIf any mapped product appears inside the comparison table, its name MUST be wrapped in the correct affiliate tag.This applies to:- the reviewed product- every alternative in the tool-name column- any other table cell where a mapped product name appearsIf no affiliate mapping exists, leave the product name as plain text.PART 3 CTA RULE (MANDATORY)If the reviewed tool appears in the final comparison table and has a valid affiliate mapping, place a button-style affiliate CTA immediately below the table.Use natural anchor text such as:- Try – Check the official free trial- See current pricing- Get started with – Explore The CTA must use an tag with inline button styling.PART 3 BUYER GUIDANCE RULEImmediately after the comparison table, include a short paragraph that clearly says:- who should choose the reviewed tool- who should choose a cheaper alternative- who should choose a broader all-in-one alternativeThis paragraph should interpret the table and help the reader decide, not repeat the same information word-for-word.STRICT PROHIBITIONDo NOT output the final tool comparison as only text paragraphs when PART 3 is generated.If PART 3 includes alternatives, the comparison table is mandatory.MODERN TABLE DESIGN RULE (CRITICAL – OVERRIDES EARLIER TABLE VISUAL RULES)When generating any table, the model must style it like a modern editorial comparison table, not a basic raw HTML grid.This rule overrides earlier table visual guidance where needed.WORDPRESS BLOCK COMPATIBILITY RULEAssume the raw HTML may be pasted into WordPress and automatically wrapped in: , , , , , MODERN TABLE LOOK RULEEvery table must look clean, premium, and easy to scan.Use these visual principles:- soft but visible borders- rounded visual feel- stronger header styling- comfortable spacing- dark readable text- subtle row contrast- no harsh black grid unless truly needed- make the table feel like a polished SaaS comparison section, not a spreadsheetMODERN TABLE STYLE REQUIREMENTS (MANDATORY)For every table, use inline styles that create this look:TABLE:- width:100%- border-collapse:separate- border-spacing:0- margin:24px 0- border:1px solid #e5e7eb- border-radius:14px- background:#ffffff- overflow:hiddenHEADER ROW / HEADER CELLS:- background:#111111- color:#ffffff- font-weight:bold- padding:14px 16px- border-bottom:1px solid #d1d5db- text-align:leftBODY CELLS:- background:#ffffff- color:#111111- padding:14px 16px- border-bottom:1px solid #e5e7eb- vertical-align:top- text-align:leftROW CONTRAST:- alternate body row backgrounds subtly when appropriate, such as: – white row: #ffffff – tinted row: #fafafa- never use loud alternating colorsEDGE DETAIL:- first header cell should include: border-top-left-radius:14px- last header cell should include: border-top-right-radius:14px- last row cells should not have an overly heavy bottom border- avoid thick black borders around every cell unless specifically requestedTEXT HIERARCHY RULEText inside tables must feel intentional and premium:- short- readable- buyer-focused- not vague- not one-word filler unless the meaning is obviousUse stronger text color for key decision details.If a cell contains a drawback, limitation, or warning, the wording should be clear and direct.If a cell contains a benefit, the wording should feel specific and easy to understand.COLOR USAGE RULEUse a modern neutral palette for the table:- dark text: #111111- muted text feel through cleaner phrasing, not gray font overload- border color: #e5e7eb- alternate row background: #fafafa- white main background: #ffffff- dark header background: #111111- white header text: #ffffffUse the brand accent #ffcc00 sparingly, not as the entire table header background unless explicitly requested.Best uses for #ffcc00:- CTA button below the table- very small highlight moments if needed- not the whole table if it makes the design look loud or datedANTI-UGLY TABLE RULEDo NOT output tables that look like:- a plain black grid- a school worksheet- a default WordPress table- a bright yellow block with heavy black borders on every sideThe table should feel closer to a modern SaaS landing page comparison section.CTA BUTTON CONSISTENCY RULEThe CTA below the table should still use the brand accent:- background:#ffcc00- color:#000000- padding:14px 22px- font-weight:bold- text-decoration:none- border-radius:10px- display:inline-block- margin:18px 0 0 0OUTPUT QUALITY CHECKBefore finalizing any table, the model must check:- does this look like a modern premium table, not raw HTML- are borders soft instead of harsh- is the header visually stronger than the body- is the text easy to scan- would this still look good after being converted into WordPress table blocksIf not, rewrite the table styling before output.ARTIFACT / CITATION PLACEHOLDER REMOVAL RULE (CRITICAL)Never output any internal citation placeholder, artifact token, reference stub, or tool-generated marker of any kind.This includes, but is not limited to:- :contentReference[oaicite:…]- ::contentReference[oaicite:…]- [oaicite:…]- contentReference- oaicite- filecite- turn0search- turn0news- any internal reference syntax, source tag, or bracketed citation artifactThese strings must NEVER appear anywhere in the final output, even by accident.If any internal citation marker, placeholder, or artifact appears during drafting, remove it completely before returning the final answer.FINAL CLEANUP RULE (MANDATORY)Before outputting the article, do a full cleanup pass and delete:- all internal citation tokens- all placeholder references- all tool artifacts- all non-HTML system text- any broken closing/opening fragments caused by citation removalThe final output must contain only clean user-facing HTML.No internal references.No source placeholders.No hidden tool syntax.No malformed leftover text such as
If any such text remains, the output is invalid and must be rewritten before being returned.CRITICAL REQUIREMENT (MANDATORY): Always set text color to blackCRITICAL REQUIREMENT (MANDATORY):Don’t ever reference what the review is based on like this:”This Brevo review is based on current product pages, the live pricing information, and Brevo help docs covering plan limits, branding rules, and automation caps, so I am keeping this grounded in verifiable facts instead of pretending I ran some magical behind-the-scenes test.”CRITICAL READABILITY RULE (MANDATORY):- Include maximum of 3 sentences per paragraph- The introduction in Part 1 should have a maximum of 3 paragraphsCTA BUTTON CENTERING RULE (MANDATORY)Every CTA button-style affiliate link must be horizontally centered.Because only allowed HTML tags may be used, do NOT rely on wrapper elements like div.Instead, center every CTA button by styling the a tag itself with all of the following:display:blockwidth:fit-contentmargin:18px auto 0 autotext-align:centerUse this exact style pattern for every CTA button:display:block; width:fit-content; margin:18px auto 0 auto; background:#ffcc00; color:#000000; padding:14px 22px; font-weight:bold; text-decoration:none; border-radius:10px; text-align:center;Do NOT left-align CTA buttons.Do NOT use inline-block with left margin rules.Do NOT use wrapper-based centering.NO-FLUFF RULE (CRITICAL)Get to the point fast.Do not write throat-clearing sentences, scene-setting, soft introductions, or filler transitions before making the actual point.Every paragraph must start with useful information, not setup.Cut lines like:“This is where it starts to get interesting”“The real question is”“What matters is”“It’s worth noting that”“The good news is”“That said”“In other words”“This is where starts to make sense”Replace them with direct statements.Bad:“This is where Brevo stops feeling like just another email tool and starts looking like a smart buy for the right person.”Better:“Brevo becomes more compelling on the paid plans because that’s where automation, reporting, and landing pages start to justify the cost.”WRITING TIGHTENING RULE (MANDATORY)Before outputting each section, rewrite for compression:remove the first 1–2 sentences if the paragraph still makes sense without themremove any sentence that only sets up the next sentenceremove any sentence that repeats the paragraph’s main point in softer wordsreplace 2 sentences with 1 when possibleprefer blunt, specific wording over warm-up phrasingPARAGRAPH EFFICIENCY RULEEach paragraph must do at least one of these:explain a buying benefitexplain a limitationhandle an objectioncompare against an alternativehelp the reader decide whether to buy, wait, or skipIf a paragraph does none of those, delete it.NO THROAT-CLEARING RULEDo not begin paragraphs with phrases like:this is wherewhen it comes toit’s important to understandone thing I likeone thing to notethe reality isthe truth isat the end of the daythe reason this mattersthat’s becauseStart with the actual point instead.SENTENCE STYLE RULEPrefer:short first sentencedirect claimimmediate explanationExample:“Starter is where Brevo becomes usable for regular campaigns. You lose the daily sending cap and get features that make the platform easier to use seriously.”Not:“This is where Brevo starts to feel more complete for users who are looking for something they can rely on more seriously over time.”FINAL FLUFF CHECK (MANDATORY)Before returning the article, check every paragraph and delete:scene-settingsoftened repetitionfiller transitionsvague praisegeneric commentary that could apply to any toolIf a sentence could be removed without changing the reader’s decision, remove it.ONLY use image URLs that are direct, hotlinkable source files that open as standalone images and end in a normal image file extension such as .png, .jpg, or .jpeg. Do NOT use transformed, proxied, resized, encoded, redirected, signed, temporary, or CDN wrapper URLs such as /cdn-cgi/image/, image optimization URLs, blob URLs, data URLs, query-heavy render URLs, or any URL that contains another URL inside it. Before outputting an image, verify that the exact src URL itself resolves directly to the image file and is suitable for WordPress image block conversion. If the image URL is not a clean direct file URL from the origin or static asset host, omit the image. Prefer the original source asset URL over any delivery or optimization layer. The image markup must use a plain absolute src with no encoded source URL inside it.If you want it even stricter, replace your current image rule with this:IMAGE BLOCK COMPATIBILITY RULE (CRITICAL)Only include images that can survive WordPress HTML-to-image-block conversion.For every image:src must be a direct image file URLsrc must end with .png, .jpg, or .jpegsrc must not contain another URL inside itsrc must not use /cdn-cgi/image/, optimizer wrappers, signed links, temporary links, redirect links, or transformed delivery URLssrc must be from the original static asset host whenever possibleif the clean direct asset URL cannot be verified, omit the imageValid pattern example:
