Where to Put the Preferred Sources Button
The Google Preferred Sources button is a 20-second add to your site. Placement is the variable that decides whether 0.05% or 2% of readers actually click it. The order-of-magnitude gap between bad placement and good placement is real, observable, and easier to fix than most publishers realize.
Brass-SEO's recommendation, based on testing across multiple publisher templates and a review of the placements working sites use in May 2026: three placements convert reliably, two common placements underperform, and the copy on the button affects conversion almost as much as the placement does. This post covers all three with specific examples and an A/B testing methodology.
This is a tactical follow-up to Google Preferred Sources: How to Add the Button. Read that first if you're not yet familiar with the underlying feature.
Quick Navigation
- Why Placement Matters More Than Design
- Placement 1: End of Every Article
- Placement 2: Sticky Sidebar or Hello Bar
- Placement 3: Newsletter Confirmation Page
- The Two Underperforming Placements
- The Copy Question
- A/B Testing Methodology
- Frequently Asked Questions
Why Placement Matters More Than Design
Brass-SEO's review of publisher implementations across May 2026 shows a consistent pattern: the same button design converts at different rates depending solely on where it sits on the page. The official Google badge in a post footer outconverts the same badge in a site footer by a wide margin. A simple text link in a sticky sidebar can outperform a polished button buried at the bottom of a tag archive page.
The mechanism is straightforward. Reader intent peaks at specific moments. The end of an article (after the reader has consumed value) is a moment of peak engagement. The site footer (after the reader has decided to leave) is the moment of lowest engagement. The button design barely matters when intent is at the floor; placement determines whether you catch intent at the peak.
The implication: design the button after you've picked the placement. A 10-minute placement decision is worth more than a 10-hour design iteration in a low-intent spot.
Placement 1: End of Every Article
The single highest-converting placement Brass-SEO has observed. A reader who has finished an article has demonstrated topical interest, spent measurable time on your site, and has not bounced. That reader is the prime candidate for designating you as a Preferred Source. Capture them at the moment of peak engagement.
The implementation:
- Place the button immediately after the closing paragraph of every article
- Use a styled card or box (not a plain text link) to make it visually distinct from the article content
- Include 1-2 sentences of context above the button explaining what it does and why it benefits the reader
- Make the button color match your primary CTA color so it reads as a deliberate action, not a footer afterthought
Example structure:
<div class="preferred-source-cta">
<h3>Like this kind of analysis?</h3>
<p>Add us as a Preferred Source on Google so our coverage shows
up first in your AI search results.</p>
<a href="https://google.com/preferences/source?q=yourdomain.com"
target="_blank" rel="noopener" class="button-primary">
Add us as a Preferred Source
</a>
</div>
The friction this placement removes: the reader doesn't have to scroll, search, or remember to come back later. The button is right there at the moment they're most willing to act.
For the broader context on capturing reader intent at peak moments, see Internal Linking: The Free SEO Tactic You're Ignoring.
Placement 2: Sticky Sidebar or Hello Bar
A secondary placement that catches readers on long pages and on pages where the end-of-article placement is far from the fold. The sticky element follows the reader's scroll position, keeping the button visible whenever the reader pauses to consider where to go next.
The implementation choices:
- Sticky sidebar widget (desktop): A right-rail card that scrolls with the reader, containing the button plus a brief headline. Best for content sites with traditional 2-column layouts.
- Sticky hello bar (full-width): A thin bar at the top or bottom of the viewport that stays visible across scroll. Best for mobile-first sites where sidebars don't render well on small screens.
- Slide-in panel triggered at 70% scroll depth: An overlay that appears once the reader has demonstrated they're engaged with the article. Highest conversion of the three sticky options but also highest annoyance risk.
Brass-SEO's recommendation between the three depends on your site's existing CTA pattern. Sites that already use sticky sidebars for newsletter signups should add the Preferred Sources CTA there. Sites that don't use any sticky elements should add a hello bar rather than introducing a new sticky pattern alongside other CTAs.
The friction this placement removes: the reader who hasn't yet finished the article gets the option presented at any scroll moment. The cost: a small amount of screen real estate is taken up permanently across the session.
Placement 3: Newsletter Confirmation Page
The least-considered but highest-converting placement Brass-SEO has tracked. Readers who have just confirmed a newsletter subscription are at peak goodwill — they've just made a deliberate decision to receive more from you. Adding the Preferred Sources button on the confirmation page captures that goodwill before it dissipates.
The implementation:
- Add the button to your newsletter confirmation page (the page users land on after clicking the confirm link in the welcome email)
- Frame the button as a complementary action: "While you're here, you can also pin our coverage at the top of your Google AI search results"
- Position the button below the confirmation message but above the "Return to homepage" link
Conversion rates Brass-SEO has observed on this placement are dramatically higher than on article-level placements because the audience is pre-qualified. The reader has just opted in to your content. They're more likely than any random visitor to want your content prioritized in search results.
The limit: only readers who go through your newsletter flow see this placement. If your newsletter is small or you don't run one, this placement isn't available.
For more on the newsletter-as-conversion-anchor pattern, see Topical Authority: Why One Post Isn't Enough.
The Two Underperforming Placements
Brass-SEO's review identifies two placements that underperform consistently and aren't worth the screen real estate.
Site footer. The lowest-converting placement across every site type tested. By the time a reader reaches the site footer, they've either consumed everything they wanted and are leaving, or they're scanning for contact information. Neither audience converts on Preferred Source CTAs. Sites that put the button only in the footer report click-through rates 5-10x lower than the article-end placement.
Homepage hero or top of homepage. This sounds like a high-visibility placement but underperforms because the homepage visitor hasn't yet consumed content. They're evaluating whether to engage with your site at all. Asking a first-time visitor to make a Google personalization commitment before they've read a single article is asking for trust they haven't yet decided to give.
For sites that have only one slot for the button, the article-end placement wins. Site footer and homepage hero are not worth the trade-off against other CTAs that compete for those spots (email signup, social follow, contact links).
The Copy Question
Three button copy variants Brass-SEO has tracked in publisher implementations, ranked by observed conversion:
- "Add us as a Preferred Source on Google" — direct, descriptive, neutral. Highest baseline conversion.
- "See our coverage first in Google AI search" — benefits-oriented, frames the user value. Slightly higher conversion than the direct version, especially with audiences less familiar with the Preferred Sources feature.
- "Get a Preferred badge on our citations" — feature-focused. Lowest conversion of the three; readers don't care about badges.
The official Google badge uses copy in the first style ("Add [publisher] as a Preferred Source on Google"). Using the official asset is a reasonable default. If you're A/B testing custom copy, the benefits-oriented frame typically wins by 10-20% over the descriptive frame in Brass-SEO's tracking.
Avoid copy that:
- Promises specific traffic or visibility outcomes ("Get 2x more clicks!") — Google's claim, not yours
- Asks for trust before establishing context ("Trust us as your source")
- Uses technical SEO terms ("Improve our AI citation rate") — readers don't know what this means
A/B Testing Methodology
For publishers with enough traffic to test, the simple A/B method:
- Pick two placements (article-end vs. sticky sidebar, or two copy variants in the same placement)
- Route 50% of traffic to each variant using a simple cookie-based split or your existing testing tool
- Track
preferred_source_clickevents in GA4 with a custom dimension capturing the variant assigned - Run for at least 14 days or until each variant has captured 200+ button clicks
- Compare conversion rate (clicks / unique visitors to that placement)
Stop the test when either: one variant wins by 20%+ on the click-through metric with statistical significance, or 30 days have passed regardless of result. Brass-SEO has observed that placement tests usually conclude within 21 days; copy tests sometimes need 45 days for clear results.
For the broader GA4 tracking setup that enables this measurement, see How to Track Preferred Sources Conversions in GA4.
Frequently Asked Questions
Should I add the button to every article or just key ones?
Every content article. The cost is negligible (one styled card at the end of the post template) and the benefit compounds across all your traffic. Some publishers exclude transactional pages (pricing, checkout, contact) and only include the button on editorial content. That's a reasonable carve-out.
Does the button hurt page speed?
Negligibly. The button is a single anchor tag with optional image. If you use Google's official badge, the image is a few KB. The page-speed impact is well under 100ms even with the image loaded. Lazy-load the image if you're optimizing aggressively, but most sites don't need to.
Will users get annoyed by the button appearing site-wide?
Probably not, if the placement is reasonable. The most-annoying placements are the high-friction ones: pop-up overlays, scroll-jacking interstitials, and modals that block the article. The end-of-article and sticky sidebar placements both fall well below the threshold where users perceive the button as intrusive.
Should I A/B test against not showing the button at all?
Not necessary. The button has near-zero cost to display and only positive expected value (some readers click). The interesting tests are between placement variants, not between displaying and not displaying.
What if my CMS doesn't support custom button placements in the article template?
Most CMS platforms allow you to inject HTML into the post template. WordPress themes typically expose this through the single.php file or theme customizer. Ghost themes use Handlebars partials. Webflow uses Custom Code in the Designer. If your CMS truly doesn't allow article-template customization, the sticky hello bar is the universal fallback — it works site-wide regardless of template.