內容簡介
Hooray SourceSignal for Google Preferred Sources 是一款讓 WordPress 使用者輕鬆添加 Google Preferred Sources 按鈕的外掛，無需編輯程式碼或聘請開發者，幫助讀者在 Google 搜尋中更容易看到您的內容。
【主要功能】
• 無需編碼即可添加 Google Preferred Sources
• 自訂按鈕外觀與顯示位置
• 控制顯示於特定文章類型與分類
• 預覽按鈕效果，確保無誤後啟用
• 避免重複訪客的干擾
• 與頁面快取及 CDN 相容
外掛標籤
開發者團隊
② 後台搜尋「Hooray SourceSignal for Google Preferred Sources」→ 直接安裝（推薦）
原文外掛簡介
Google Preferred Sources for WordPress — without the code
Google Preferred Sources can help readers see more of your content in Google Search.
SourceSignal makes it easy to add Preferred Sources buttons and prompts to your WordPress site — without editing code or hiring a developer.
Install the plugin, choose what you want the button to look like and where you want it to appear, and turn it on.
That’s it.
Built by a publisher, for publishers
I run a small independent publishing company. We don’t have an in-house development team.
When Google launched Preferred Sources, I wanted it on our sites. The basic Google code looked simple enough. Making it work the way I wanted across WordPress, different placements, mobile devices, caching and our existing site setup was another story.
So we built SourceSignal.
The goal was simple: make Google Preferred Sources something a publisher can set up in a few minutes instead of another project to send to a developer.
We use it on our own publishing sites, and we’ve tested it on real WordPress sites and browsers.
What you can do with SourceSignal
Add Google Preferred Sources without touching code. No snippets, no theme files, no CSS.
Choose how it looks. Google’s official button, a card, an inline button, a text link, your own design, or a button you already have.
Choose where it appears. Automatically before or after articles, or place a block or the [preferred_source] shortcode yourself.
Control where it shows. Limit automatic placement to the post types and categories you choose.
Preview everything before turning it on. The wizard and settings screen show the real button, not a mock-up. Nothing changes for readers until you press Turn it on.
Avoid annoying repeat visitors. Hide it for a while after someone uses it or closes it.
Works with page caching and CDNs. Every visitor gets the same HTML; the reader’s browser decides whether to show it.
Falls back gracefully if Google’s script isn’t available. Readers still get a link to Google’s Source Preferences page.
A note about Google
SourceSignal helps you promote Google’s Preferred Sources feature. Google controls the feature and the final selection happens on Google’s side.
Google does not provide publishers with confirmation that an individual reader completed the selection, so SourceSignal does not report clicks as confirmed Preferred Source adds.
SourceSignal is an independent publisher tool and is not affiliated with or endorsed by Google.
Want to promote Preferred Sources beyond your website?
We’re also building SourceSignal Pro for publishers who want to promote Preferred Sources through newsletters, social media and print.
Pro adds publisher-controlled campaign links, printable QR codes, campaign management and reporting for the parts of the funnel we can actually measure — including views, clicks and Google-flow launches.
Pro is coming soon.
External services
To open Google’s Preferred Sources screen, this plugin loads Google’s publisher library from https://news.google.com/swg/js/v1/publisher.js.
When it loads: on pages that carry a Preferred Sources button or prompt — or, if you switch on “Let buttons added outside the block editor open the card too”, on every page of your site. That setting is off unless you turn it on, and the settings screen tells you which state your site is in.
What Google receives: loading that file is a request to Google, so Google receives what any web request carries — the reader’s IP address, their browser, and the address of the page they are on. If you use Google’s own rendered button, Google also draws it inside a frame served from Google, and that frame receives the address of the article the reader is on.
The fallback: when Google’s library cannot load, or JavaScript is switched off, the prompt becomes a plain link to Google’s Source Preferences page, https://www.google.com/preferences/source?q=yourdomain.com. It is written into the page but only requested if a reader follows it.
Google’s handling of any of this is governed by Google’s own terms and privacy policy, not by this plugin:
Terms: https://policies.google.com/terms
Privacy: https://policies.google.com/privacy
Privacy
Nothing about readers is stored on your server. There is no reader table, no event log, no identifier, no analytics, and nothing is sent to the plugin’s author.
In the reader’s own browser, when they press or close a Preferred Sources button or prompt, the plugin saves a date stamp — in local storage and in a first-party cookie of the same name:
psfp_used_at — the reader pressed it.
psfp_closed_at — the reader closed it.
Each holds a date and nothing else: no name, no account, no identifier. The cookie is set with path=/ and SameSite=Lax, and expires by itself after the window you chose. Nothing is written merely because a reader was shown the prompt, and nothing at all is written if both windows are set to “Keep showing it”. Your server never reads either copy, which is what keeps page caching working — though the cookies travel with ordinary page requests the way every cookie does.
It is per browser, not per person: the same reader on a phone and a laptop counts twice, and clearing site data resets it.
WordPress’s Settings → Privacy screen carries a suggested paragraph for your own privacy policy, generated from your site’s own settings. It is a starting point, not legal advice.
The plugin’s settings live in two options, psfp_settings and psfp_setup, plus a 60-second marker after activation. Uninstalling removes all three, from every site on a network, and leaves your posts alone.
