O
by
jaimepaezv
1 (0 reviews)
Open Growth Preferred Source Button for Google
Adds Google's Preferred Source integration to WordPress with the standard Google button or a custom site control.
Open Growth Preferred Source Button for Google ranks #67,616 among WordPress.org plugins with 1+ active installations, a 1/5 rating from 0 reviews, and was last updated Oct 13, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.1.5
Current Version v1.1.5
Updated 2 weeks ago
Last Update on 13 Oct, 2026
Refreshed 2 days ago
Last Refreshed on
Actively maintained
Rank
#67,616
—
No change
Active Installs
1+
—
No change
KW Avg Position
135
1 worse
Downloads
113
+3 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
54,679
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 9 more installs to reach 10+
Rank Changes
Current
#67,616
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
1.0
0 reviews
Overall
20%
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.5
- Last Updated
- Oct 13, 2026
- Requires WP
- 6.5+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- jaimepaezv
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- 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 Open Growth Preferred Source Button for Google
No. Independent plugin, not affiliated with or endorsed by Google.
No. Check that your site appears in Google's Preferred Sources tool; this plugin cannot make a site eligible. Preferred Sources tool: https://www.google.com/preferences/source Google documentation: https://developers.google.com/search/docs/appearance/preferred-sources
Google documents eligibility at the domain and subdomain level only. A URL such as example.com/blog/ is not independently eligible. The settings screen shows a warning when home_url() contains a subdirectory path.
The editor intentionally displays a stable placeholder. Google's external library is not loaded into the editor merely to provide a preview. The live button renders on the front end.
The plugin uses WordPress the_content by default and includes dedicated frontend-output integration for Elementor (elementor/frontend/the_content) and Bricks (bricks/frontend/render_data, content area only). This covers builder layouts that bypass the normal WordPress content pass while preserving the same eligibility, duplicate, password, and per-content visibility checks. Oxygen does not apply WordPress the_content to Oxygen-designed singular content by default. Oxygen provides its own setting to enable that filter. If you keep that setting disabled, place the plugin shortcode where you want the button. For LiveCanvas and other builders, automatic placement works when the builder ultimately runs the_content; otherwise use the shortcode in the builder output. The plugin does not modify another builder's settings. Dynamic content inserted after Google's library has initialized is still subject to Google's standard declarative-mode limitation described below.
Yes. Set Reserved minimum height to 0 in Settings > Preferred Source Button. The ogpsb_button_min_height filter can still override the stored value.
Uninstall removes the plugin option and _ogpsb_hide post meta from every site in batches of 100. This avoids loading the complete site list into memory, but WordPress uninstall runs synchronously. On exceptionally large networks, host execution-time limits can interrupt cleanup before every site has been processed. If that applies to your network, run uninstall from a maintenance window or remove the two plugin data keys with a network-aware administrative process.
Google's standard implementation scans the DOM when its library initializes, so declarative buttons inserted later may not be rendered automatically. The plugin's Custom control mode uses Google's documented manual/programmatic API plus delegated click handling, so matching custom triggers added later can work without a DOM re-scan.
Use ordinary HTML and keep your existing Bootstrap classes. For example: <button type="button" class="btn btn-primary" data-ogpsb-preferred-source>Add to preferred sources</button>. The plugin uses native JavaScript and its own data-ogpsb-preferred-source attribute; it does not depend on jQuery or Bootstrap JavaScript and does not use Bootstrap's data-bs-* namespace.
Custom triggers can live outside post content—in a header, footer, template, popup, builder partial, or markup inserted later by JavaScript—so the plugin cannot reliably predict server-side which URLs contain a trigger. Custom control mode therefore loads Google's library and the small trigger controller on normal frontend pages by design. If site-wide loading is not appropriate for your site, use the standard implementation or conditionally dequeue the integration in site-specific code.