Mini Banner: Placement, Frequency, and Cascade Rules

A mini banner is a compact, full-column conversion unit inserted between article sections. It turns the value established by the preceding section into one timely next step without taking over the page or interrupting the reader’s current task.

The example names the outcome, connects it to completed work, and predicts the destination. Its position is part of the definition; the same words before the prompts-and-competitors explanation would be premature.

Why this element matters

A long article creates several moments of intent. After a useful explanation or comparison, a reader may be ready to inspect a product, use a tool, download a resource, or subscribe. A mini banner acknowledges that change without making them search the navigation.

The psychological mechanism is earned interruption. The banner spends attention the article has accumulated. After a completed thought, a logical next action feels helpful; at an arbitrary paragraph count, it feels like an advertisement. Repetition teaches readers to treat every distinctive block as an obstacle.

Placement and frequency are therefore content rules. Scroll position supplies a search zone, but the preceding section supplies the reason. The banner should answer “What can I do with what I just learned?”

Machine extractability matters even though the banner does not create special schema. Search systems, AI agents, browser tools, and assistive technology may extract its heading, description, and links without the surrounding visual design. A self-contained statement such as “Open the visibility cockpit to compare your tracked prompts” preserves the action and its purpose. “Ready to get started?” followed by “Learn more” does not identify an object, outcome, or destination.

Typed fields let publishing systems enforce frequency, resolve placement, and suppress a banner when no safe position exists. A styled paragraph cannot participate reliably. Apply the shared element writing rules : purpose takes precedence over appearance, accessibility, safety, and procedural continuity.

When to use it

Use a mini banner when a substantial article has delivered enough value to support a related, optional conversion. Suitable moments include:

• after a framework has helped the reader classify their problem and a product report can apply that framework;
• after a comparison reaches a qualified verdict and a tool can test the reader’s own case;
• after a research section establishes a gap and a downloadable worksheet helps plan the response;
• after a case-study method is explained and a service offers the same kind of implementation;
• after an original analysis, when a newsletter provides future updates of the same kind.

The page must contain at least 1,200 substantive words. Below that threshold, the banner arrives too close to the introduction or closing conversion. The destination must fulfil the copy immediately. Disclose a sales form, email gate, or sign-in requirement before the click.

Near misses need different treatment. A supporting link is navigation; a button in a sentence is an inline action; an end-of-page sales panel is a closing CTA. A newsletter form adds consent, validation, and privacy requirements. An outage, price-change, or legal notice is not a conversion unit.

Do not use a mini banner to fill space, repeat a header action, promote an unrelated campaign, or compensate for weak content. Do not personalize it from sensitive traits. If the surrounding content cannot supply a reason to act, omit it.

Ready to Monitor Your AI Visibility?

Track how AI chatbots mention your brand across ChatGPT, Perplexity, and other platforms.

Get Started Contact

Where to place it

Placement uses two inputs: article progress identifies a reasonable zone, and a semantic boundary confirms that the reader has completed a thought. Article progress is the proportion of substantive body content already passed, measured from the first paragraph after the introduction to the final paragraph before the closing CTA. Navigation, hero copy, table of contents, footnotes, boilerplate, and the banner itself do not count.

For the first banner, define the preferred zone as 35%–55% of article progress and require at least 600 words before it. Place it after a completed H2 section, or after a complete subsection only when the next heading clearly begins a new subject. For a second banner on pages of at least 2,500 words, use the 70%–85% zone. It must be at least 900 words and 30 percentage points after the first.

The placement cascade resolves the exact position in this order:

1. Explicit safe anchor: use the author-supplied section ID when it falls inside the allowed zone and passes every adjacency check.
2. Forward safe boundary: from 40% for the first banner, or 72% for the second, scan forward to the first eligible end of an H2 section, stopping at the zone maximum.
3. Backward safe boundary: if no forward position qualifies, scan backward to the last eligible H2 boundary inside the zone.
4. Suppression: if neither search finds an eligible position, render nothing and record no-safe-anchor for QA. Never fall back to a raw paragraph count.

This order preserves a safe editorial anchor, makes automatic placement deterministic, and treats omission as valid. Calculate progress from rendered or source blocks consistently; never move an explicit banner silently to a different topic.

A mini banner may not sit:

• between required steps, or between an instruction and its expected result;
• between a claim and its citation, a chart and its explanation, or a quotation and its attribution;
• immediately before or after a warning, disclaimer, error, consent request, or safety note;
• inside a list, table, figure, code sample, accordion, tabs panel, blockquote, FAQ answer, or form;
• beside an inline CTA, offer, product card, newsletter form, paywall, purchase control, or another banner;
• directly below a heading, where it would orphan the heading from its first explanatory paragraph;
• at the same boundary as a sticky promotion or an injected advertising slot.

Require one substantive block between the banner and any non-safety callout, media, or interaction. On responsive layouts, test adjacency against stacked source order.

Frequency is page-wide. Use zero mini banners below 1,200 words, no more than one from 1,200 to 2,499 words, and no more than two from 2,500 words upward. Count all promotional units in the body—mini banners, inline conversion buttons, newsletter captures, offer boxes, and product promotions—toward a ceiling of one under 1,500 words, two from 1,500 to 2,499, and three from 2,500 words upward. When the limits conflict, the lower number wins. A limit is permission to use fewer, never a target to fill.

Anatomy

1. Placement anchor: a stable section ID and calculated progress value that explain why the banner occupies this boundary.
2. Container: a visually bounded, full-column region that remains part of normal document flow.
3. Heading: names a concrete outcome or next step without relying on the previous heading.
4. Description: connects the completed section to the action and discloses meaningful commitment such as sign-in, email capture, payment, or a sales conversation.
5. Primary action: one descriptive link or form submit control that fulfils the stated promise.
6. Secondary action: an optional, quieter route for readers who are not ready for the primary commitment; it is not a second campaign.
7. Clear space: separates the banner from prose and prevents nearby controls from appearing to belong to it.
8. Placement ID: a stable analytics label describing the semantic anchor, not a mutable paragraph number.

The renderer owns presentation. The author owns the promise, qualification, destination, preferred anchor, and variant.

Stay Updated on AI Visibility Trends

Get the latest insights on AI mentions, brand monitoring, and optimization strategies.

Email address

Subscribe

Design examples

All variants share one placement and frequency contract. A different visual treatment does not create another promotional allowance.

Single-action CTA

Use one primary action when the preceding content points to a clear next step. This is the default.

Primary and secondary actions

Use two actions only when they represent the same journey at different commitment levels, such as “Start the assessment” and “View the methodology.” Make the hierarchy unmistakable and keep both destinations relevant to the preceding section.

Resource or download

Use this variant for a directly available template, checklist, dataset, or guide. State the format and disclose gating before the action. If the click downloads immediately, name the file type and approximate size when known.

Newsletter capture

Use the newsletter variant only after demonstrating what future messages contain. It needs an email label, consent, privacy destination, validation, success, and error states.

Responsive stacked

On narrow screens, text comes first and actions follow in the same source order. Buttons may become full width, but the banner must not become sticky, cover content, or push the next heading below an artificial interstitial.

Parameters

The canonical contract separates authored meaning from placement calculation. “Source” says where an adapter obtains the value; it does not mean the banner may infer marketing copy from unrelated page metadata.

The body’s first heading maps to title; its first paragraph maps to description. Newsletter consent remains later. secondaryText and secondaryUrl are an all-or-nothing pair. Campaign identifiers must never contain personal data.

Progress limits are defaults controlled by this specification, not knobs for authors to move a promotion upward. A renderer may expose stricter limits but may not accept values outside the stated zones. If preferredAfter fails the safety checks, the adapter runs the cascade and records both the requested and resolved anchors.

Syntax and code examples

The portable directive is canonical authored content. Platform adapters preserve its fields, safe-placement result, source order, and accessible names.

Portable Markdown directive

:::mini-banner{variant=cta primaryText="Open the visibility cockpit" primaryUrl="https://app.amicited.com/reports/cockpit" preferredAfter="benchmark-your-prompts" placementId="after-prompt-benchmark" campaignId="visibility-cockpit-contextual"}
## See where your brand appears in AI answers

Open your visibility cockpit after you have identified the prompts and competitors that matter.
:::

The first heading and paragraph supply the display copy. The publishing adapter validates the preferred anchor and suppresses the component when no safe boundary exists.

Hugo shortcode

The current Hugo mini-banner-cta shortcode renders the CTA fields. Placement metadata belongs to the page assembly or placement adapter until the shortcode accepts it directly:

{{< mini-banner-cta
  heading="See where your brand appears in AI answers"
  description="Open your visibility cockpit after you have identified the prompts and competitors that matter."
  primaryText="Open the visibility cockpit"
  primaryUrl="https://app.amicited.com/reports/cockpit"
>}}

Use named parameters only. The source example is escaped so it documents the shortcode without rendering a second banner. A production placement layer must associate it with after-prompt-benchmark and apply the frequency cascade before Hugo emits the component.

WordPress block

<!-- wp:amicited/mini-banner {"variant":"cta","primaryText":"Open the visibility cockpit","primaryUrl":"https://app.amicited.com/reports/cockpit","preferredAfter":"benchmark-your-prompts","placementId":"after-prompt-benchmark","campaignId":"visibility-cockpit-contextual"} -->
<h2>See where your brand appears in AI answers</h2>
<p>Open your visibility cockpit after you have identified the prompts and competitors that matter.</p>
<!-- /wp:amicited/mini-banner -->

Moving the block to an unsafe location must surface a validation warning.

Examples

Good

An ultimate guide explains how to group brand prompts by audience and intent, then ends the section with a worked benchmark. At 43% article progress, after 1,080 words, it shows this banner:

Compare your tracked prompts in one cockpit
See which competitors appear for each prompt and where your brand is missing.
Open the visibility cockpit

This works because the section produces a specific need, the destination performs the stated task, the label remains meaningful alone, and the position passes the first-banner zone and adjacency rules.

Bad

After the second paragraph of the introduction, a 3,000-word guide shows:

Ready to transform your business?
Unlock the power of AI today.
Learn more   Get started

It fails before copy quality is considered: the reader has not completed a useful section, the placement is outside the allowed zone, and two generic actions create no intelligible hierarchy. The heading makes an unsupported promise, the description has no concrete object, and neither link predicts a destination. Moving the same banner downward would not fix its vague contract.

Schema markup and accessibility

A mini banner feeds no dedicated Schema.org type. Its text remains content within the enclosing Article, TechArticle, WebPage, or other justified page type. Do not mark it as an Advertisement, Offer, or HowToStep merely because it contains a commercial action. Other structured data is valid only when the visible page and its schema specification support every fact.

Use a labelled region only when that landmark aids navigation; otherwise use an aside or grouped container. Keep the title in the page’s heading hierarchy. Links navigate with <a>; <button> submits a form or performs an on-page action. Accessible names must match the visible purpose.

Keyboard focus follows source order. Focus indicators must remain visible, targets need adequate size and spacing, and zoom must not clip copy. Responsive layouts must not reorder controls. Color, icons, and button fill cannot be the only state or priority signal.

For newsletters, associate the label with the input, expose errors programmatically, retain the address after recoverable errors, and announce success without moving focus. Consent cannot be preselected. Never animate the banner into view or steal focus at the placement threshold.

Writing rules

Write the value proposition as a continuation of the preceding section, not as a universal slogan.

• Use a 4–10 word heading, preferably under 70 characters. Name the outcome, object, or resource.
• Use one description of 12–28 words and no more than 160 characters. Connect context to action and disclose material commitment.
• Use one primary label of 2–6 words and no more than 40 characters. Start with an accurate verb such as “Open,” “Compare,” “Download,” “Calculate,” or “Subscribe.”
• Allow one secondary action at most. It must concern the same topic and require less or equal commitment.
• Keep the total CTA variant under 55 visible words, excluding necessary consent and privacy text.
• Address the reader directly when useful, but avoid manufactured excitement, fear, countdown language, and claims the destination cannot prove.
• Repeat the key noun across the heading, description, or action so extracted fragments retain their subject.
• Disclose sign-in, payment, email capture, file format, or sales contact before the click when it would change the reader’s decision.

Never put a paragraph of product features, testimonial, price table, coupon terms, navigation list, multi-step form, legal disclaimer, star rating, countdown, autoplaying media, or more than two actions inside a mini banner. Never use “Click here,” “Learn more,” “Go,” “Submit,” “Get started,” or “Unlock the power” without a concrete object and destination context.

Post types that use it

The postTypes[] frontmatter is the source of this matrix. Inclusion means the element is permitted when the placement and intent tests pass; it never makes the banner mandatory.

QA checklist

• The page is at least 1,200 substantive words before any mini banner is considered.
• The preceding section creates a specific reason for the banner’s action.
• The first banner falls between 35% and 55% progress and follows at least 600 words.
• A second banner appears only on a page of 2,500 words or more, between 70% and 85% progress.
• Two banners are separated by at least 900 words and 30 percentage points.
• All in-body conversion units were counted and the lower applicable frequency ceiling was used.
• The explicit anchor or cascade result is a complete H2 boundary, not a paragraph-count insertion.
• The banner is absent when the cascade finds no safe anchor.
• No step, warning, evidence-and-source pair, table, figure, form, or interactive component is interrupted.
• No competing conversion, purchase control, consent request, or injected ad sits beside the banner.
• Heading, description, labels, commitments, and destinations meet the writing limits and agree with one another.
• The primary and optional secondary actions have a clear hierarchy and concern the same journey.
• Links, buttons, form labels, focus order, focus states, errors, and responsive stacking work with keyboard and assistive technology.
• The banner remains understandable when extracted without color, icons, surrounding prose, or visual layout.
• No unsupported schema type or property was added.
• placementId, campaignId, requested anchor, resolved anchor, and suppression reason are available for QA without containing personal data.
• Mobile rendering keeps the banner in normal flow and does not cover or push aside article content.

FAQ

The frequently asked questions below define the preferred scroll zone, frequency ceilings, safe-placement cascade, two-action rule, schema limits, and non-sticky behavior.