by
hoorayplugins
0 (0 reviews)
Hooray SourceSignal for Google Preferred Sources
Add Google Preferred Sources to your WordPress site in minutes — no coding or developer required.
Hooray SourceSignal for Google Preferred Sources ranks #53,531 among WordPress.org plugins with 0+ active installations, and was last updated Sep 21, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.2
v1.1.1
Current Version v1.1.1
Updated 2 days ago
Last Update on 21 Sep, 2026
Refreshed 7 hours ago
Last Refreshed on
Actively maintained
Rank
#53,531
—
No change
Active Installs
0+
-2%
KW Avg Position
36.5
1.5 worse
Downloads
174
+4 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
33,791
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 7 more installs to reach 10+
Rank Changes
Current
#53,531
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.1.1
- Last Updated
- Sep 21, 2026
- Requires WP
- 6.5+
- Tested Up To
- 7.1.2
- PHP Version
- 7.4 or higher
- Author
- hoorayplugins
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Hooray SourceSignal for Google Preferred Sources
Install this plugin, answer the setup questions, look at the preview, and press Turn it on. You can also drop the Preferred Sources button block into a post (search “preferred sources” in the editor), or use the [preferred_source] shortcode.
No. The plugin loads Google's publisher library on pages that need it, and leaves it off pages that do not.
Yes. Install it, choose where it appears and how it looks, preview it, and turn it on. No PHP, no JavaScript, no templates.
Google's official button is drawn by Google, in each reader's own language, and changes when Google changes it. The compact pill sits in a byline or next to a date; the promotional card is a house-ad panel for mid-article or the end of a story — both are drawn by the plugin and carry Google's G. The plain card, inline button, text link and the card in your own colours carry no Google logo and follow your theme. Every one of them opens the same Google screen; the settings screen previews each before you save.
Yes. Every visitor gets the same HTML, and whether a particular reader sees the prompt is decided in their browser. Clear your cache after you change a setting.
Yes. Automatic placement can run before or after articles, on the post types you choose, and — for posts — only in, or except in, the categories you choose. You can also place a block or shortcode by hand and leave automatic placement off.
Yes. Tick "Open the preferred sources card" on a core Button block, or give a page-builder button the class psfp-trigger. You can also choose "Card, your own colours" in the plugin's block.
It inherits your theme's fonts and colors and sets nothing globally. For a page-builder button, use the class psfp-trigger. Tested with Twenty Twenty-Five, Twenty Twenty-Four and Twenty Twenty-One, and exercised with Kadence.
Readers get a link to Google's Source Preferences page instead, opened in a new tab. If JavaScript is off entirely, that link is what they see in the first place.
How often each prompt was on screen (half of it visible for a second — the same rule ad servers use), how often it was pressed, how often Google's flow was opened, and how often it was closed, as day-by-day totals for the last thirty days. They are first-party counts of what happened on your own pages, not audited, and not comparable to Google's own reporting. Google's own button is drawn and handled by Google, so its presses cannot be counted here and its row shows only how often it was on screen.