Hooray SourceSignal for Google Preferred Sources
| 开发者 |
hoorayplugins
jbyrne123 |
|---|---|
| 更新时间 | 2026年9月21日 03:36 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Add Google Preferred Sources without touching code. No snippets, no theme files, no CSS.
- Choose how it looks. Google's official button; a compact pill or a promotional card drawn by the plugin and carrying Google's G; a plain card, an inline button, a text link or a card in your own colours; or a button you already have.
- Choose where it appears. Automatically before or after articles, or place the Preferred Sources button 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 the settings screen draw the real prompt at phone, article or full width. Nothing changes for readers until you press Turn it on.
- See what readers do. Day-by-day counts of how often each prompt was on screen, pressed, and opened Google's flow — kept on your own site, with nothing about any reader in them. Optionally send the same counts to the Google Analytics tag your site already runs.
- Don't nag your readers. Choose how long to hide it after someone uses or closes it.
- Works with page caching and CDNs. Every visitor gets the same HTML; the reader's browser decides whether to show it.
- Still works if Google's script doesn't load. Readers get a link to Google's Source Preferences page instead.
安装:
- Install and activate the plugin. Nothing changes for readers yet.
- WordPress opens Set up Preferred Sources. (If it does not, open Preferred Sources → Setup from the admin menu.)
- Answer the questions — where it should appear, on what content, how it should look, what it should say — watching the preview beside them.
- Press Turn it on on the last step.
- If your site uses a caching plugin or a CDN, clear its cache.
屏幕截图:
常见问题:
How do I add Google Preferred Sources to WordPress?
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.
Do I need to add Google's JavaScript manually?
No. The plugin loads Google's publisher library on pages that need it, and leaves it off pages that do not.
Can I add Preferred Sources without a developer?
Yes. Install it, choose where it appears and how it looks, preview it, and turn it on. No PHP, no JavaScript, no templates.
Which presentation should I choose?
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.
Does it work with caching and CDNs?
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.
Can I control which posts or categories show it?
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.
Can I use a button I already have?
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.
Does it work with my theme or page builder?
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.
What happens if Google's script doesn't load?
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.
What does the Analytics tab count?
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.
Does SourceSignal know whether someone completed the final Google selection?
No. Google does not tell publishers that. SourceSignal can count that a prompt was on screen, pressed, or opened Google's flow, and remember in the reader's browser that it was pressed or closed. None of that is a confirmed add, and the plugin never reports one.
I upgraded from 1.0 and my articles look different.
They should not. 1.0 kept two presentation settings — one for automatic placement, one for the block and shortcode — and 1.1 has one. If your two 1.0 values were the same, nothing changed. If they differed, the upgrade kept the one your articles were already showing and the settings screen tells you once which one it kept, with the other one click away.
Can I promote Preferred Sources through email, social or print?
Not in the free plugin. It puts buttons and prompts on your WordPress site. SourceSignal Pro is being built for newsletters, social and print. It is coming, and it is not yet for sale.
更新日志:
- Fixed: an ad or video script that counts the article's paragraphs could insert its content inside the prompt. On a site running an ad partner that drops a video player a few paragraphs into the article, with the prompt set to the beginning of the post, the player could end up inside the prompt — between the text and the button. The prompt no longer puts a paragraph into the article body, so a script choosing its position by counting the article's paragraphs cannot pick one of ours. Nothing about how the prompt looks or reads changes. If your ad partner places by word count rather than by paragraph, this does not help and the end of the post is still the safe placement.
- Fixed: the setup wizard's wording step showed different words from the preview beside it. Choosing the promotional card and pressing "Use this" agreed to wording that was not on the screen and that no reader would have seen. The wizard, the settings screen and the block editor's sidebar now all show the words the presentation you have chosen will put on the page, and changing presentation changes them — including when you change presentation and save in one go, which used to store the previous presentation's wording as if you had typed it.
- Fixed: the compact pill was offered a heading and a body-text box, neither of which it puts on the page, and a button-label box showing a label it does not use. Boxes a presentation has no use for are now hidden, and hiding one no longer risks emptying it when you save.
- Better default wording. "Enjoy our reporting?" was written for a newspaper and read oddly on a parenting title, a listings guide or a small business. The shipped prompts now read "See more from [your publication] on Google" / "Add [your publication] as a preferred source and we're more likely to appear in your results." / "Add us on Google". If you have written your own wording, none of it changes — the improvement only reaches sites that never edited theirs, and nothing is written to your database either way.
- The preview of Google's own button now looks like Google's button instead of a dashed grey placeholder, so you can see what you are choosing. It is a drawing, clearly captioned as a preview, and nothing is loaded from Google inside wp-admin.
- Plainer wording across the settings screen and the wizard, with the long explanations cut. "Readers who are not on your site" is now "Promote Preferred Sources beyond your website"; "Where on the line should it sit?" is "Alignment"; "Placing it yourself" is "Add it yourself". Two help texts that listed the wrong presentations for the close button now list the right ones.
- A corrected plugin icon: the tallest bar of the mark was clipped at the right edge of the artwork in WordPress's plugin search.
- Two presentations drawn by the plugin and carrying Google's G: a compact pill that sits in a byline or a header, and a promotional card for mid-article or the end of a story. Google's own button, the card, the inline button, the text link and the card in your own colours are unchanged.
- Counting, on by default and switchable off: how many times each prompt was on screen (half of it visible for a second, the same rule your ad server uses), pressed, and opened Google's flow — kept as day-by-day totals in one table on your site, with nothing about any reader in it. The Analytics tab shows the last thirty days and says plainly what the numbers are not: Google does not report whether anyone completed the add, so there is no conversion rate and never will be. Google's own button is handled by Google, so its row shows impressions only rather than an invented click rate.
- Optional forwarding of the same events to the Google Analytics tag your site already runs — off by default, switched on with a checkbox on the Analytics tab or the
psfp_ga4_enabledfilter. It sends which prompt, where it sat and its position, and nothing about the reader. - Every event is also announced to other plugins through
psfp_event, with a documented, versioned shape, so a publisher's own logging can listen without this plugin knowing. - One presentation for the whole site. "Presentation" and "Which presentation" were two settings for the same thing — the preview followed one, articles followed the other. There is one now, chosen next to the preview; any block or shortcode can still be set differently, and the block's presentation control gained "Use the site default". A site whose two 1.0 values differed keeps what its articles showed and is told once, with the other value one click away. Developers who want automatic placement to differ have the
psfp_auto_stylefilter. - The settings screen is four tabs — Placement, Appearance, Analytics, Advanced — with the preview beside all of them. Controls that only apply to one presentation appear with it, and saving returns you to the tab you were on.
- The preview draws the prompt in a content column at a phone, an article or the full width, and, for Google's button, puts a labelled stand-in at the button's footprint. The stand-in is drawn by the plugin in its own words — no Google artwork, and still nothing loaded from Google inside wp-admin.
- Unticking "Draw a border around it" now changes the preview before you save.
- The block is now called "Preferred Sources button", and the screens say button, prompt and card rather than "invitation".
- The reporting table's styling arrives through the enqueued admin stylesheet, and the plugin's front-end bootstrap is printed through WordPress's own inline-script printer so content-security-policy nonces apply to it.
- A setup wizard: eight plain questions, a live preview, and a last step that turns it on. Nothing changes on your site until that step, and an existing install is never redirected into it.
- The preview on the settings screen and in the wizard now follows every change instantly, including the presentation, rendered by the same code as the front end.
- Automatic placement can be limited to, or kept out of, particular categories.
- A suggested privacy-policy paragraph under Settings → Privacy, written for the site's own settings.
- Alignment now moves Google's own button as well as the plugin's presentations.
- Nothing is written to a reader's browser when both "asking again" windows are set to "Keep showing it".
- The settings screen says what was corrected when a colour, domain or language tag could not be used, reminds you about page caches after a save, and states plainly when Google's library is being loaded on every page.
- Uninstalling now also removes the record of whether setup was run.
- A backslash typed into the heading, text or button label now survives saving; a suppression window set outside the dropdown's choices (for example from WP-CLI) is no longer reset to "Keep showing it" on the next save.
- Google's own button is left alone. The plugin no longer waits six seconds, guesses whether Google's control rendered, and adds its own link beside it — a live beta showed that guess was wrong on a working button in every browser it was tried in, including one already reading "Added to Preferred Sources".
- The link beside Google's button is now shown only when Google's library never loads at all, which is the one case where there is definitely no button to press.
- Asset version bumped so browsers and CDNs pick up the new script and stylesheet rather than a cached 0.1.0 copy.
- First release.
- Close button on the card and "your own design" presentations, so the "hide it after a reader closes it" setting has something to act on.
- Google's own button falls back to a link if the library never fills its slot.
- Automatic placement stays out of excerpts and out of query loops inside an article.
- Automatic placement stands down on an article that already contains a block or shortcode — the one the publisher placed wins.