Never launch a site invisible to Google by accident
Search Visibility Notice puts a colored pill in the WordPress admin bar showing whether search engines can index the site right now, turning a setting nobody remembers to check into something impossible to miss.
- Green when search engines can index the site, red when they can't.
- Reflects WordPress's own "Discourage search engines" Reading setting.
- One click opens Settings → Reading to fix it immediately.
- Visible to administrators only, in wp-admin and on the front end.
Click the pill to jump straight to Settings → Reading.
What does Search Visibility Notice do?
When the search_visibility_notice module is active, TOWP_Search_Visibility_Notice adds a colored pill to the WordPress admin bar reflecting the site's blog_public option, the same setting behind Settings → Reading's "Discourage search engines from indexing this site" checkbox. The pill shows solid green with "Search Engine Indexing: On" when search engines are allowed to index the site, and solid red with "Search Engine Indexing: Off" when they're discouraged, and clicking it in either state opens the Reading settings screen directly. Since it's visible only to users who can manage options, it appears wherever the admin bar itself shows, in wp-admin and on the front end alike.
One setting decides if Google can see the site at all
Because the setting lives on a screen nobody revisits, a site can stay invisible to search engines long after launch without anyone noticing.
Checked during development, forgotten at launch
The "Discourage search engines" checkbox gets ticked on nearly every site while it's under construction, and on a good number of them, nobody remembers to uncheck it when the site actually goes live.
Nothing warns anyone once it's wrong
Beyond one line on a settings screen nobody revisits, WordPress gives no indication anywhere that the site has become invisible to search engines.
A setting nobody checks, turned into something nobody can miss
The module surfaces the exact same setting as a colored pill that's visible every time an administrator is logged in.
Green means indexable, impossible to miss
A solid green pill in the admin bar confirms search engines can index the site, at a glance, on every single page.
Red means something needs fixing
The same pill turns solid red the moment indexing gets discouraged, standing out specifically because it's meant to be noticed.
One click to the actual setting
Clicking the pill in either state opens Settings → Reading directly, skipping the hunt for where the checkbox even lives.
Accurate the moment it's turned on
Every capability below is present in the supplied PHP class, its CSS asset and the settings registration.
Reads the same blog_public option WordPress uses
The pill's color and label come directly from the same option Settings → Reading checks, so it's never out of sync with the setting it represents.
Solid green or solid red, nothing ambiguous
On uses WordPress's own success green, off uses WordPress's own error red, the same colors used throughout wp-admin for exactly this kind of status.
The pill is a direct link, not just a label
Clicking the pill anywhere it appears opens the Reading settings screen immediately, ready to review or change.
wp-admin and the front end alike
The pill appears both inside wp-admin and on the live site's front end for a logged-in administrator, so the warning follows wherever an admin actually is.
Nobody else sees it
The pill only renders for users who can manage options, so it never appears as an unexplained element for editors, authors or visitors.
Styled around how WP_Admin_Bar actually renders nodes
WordPress attaches a custom admin bar node's classes to its wrapping element, not the link itself, and the module's styling accounts for that correctly.
Where a visible status helps most
The module supports any site where an accidentally-flipped indexing setting would go unnoticed otherwise.
Launching a site that was built with indexing discouraged
Catch the forgotten checkbox before launch day passes with the site still invisible to search engines.
Teams with more than one person touching Settings
Give every administrator a shared, constant view of indexing status, instead of relying on one person remembering to check.
Diagnosing a sudden drop in search traffic
Rule out an accidentally-flipped indexing setting as the very first, fastest check.
Visible everywhere, fixable in one click
The module combines constant visibility with a direct path to the actual fix.
One option read, nothing more
The verified implementation stays as lightweight as the admin bar node it adds.
One admin bar node, one option read
Adding the pill costs a single lightweight database option read, the same cost WordPress itself pays to check this setting anywhere else.
No output for non-administrators
Since the check for manage_options happens before anything renders, the module does nothing at all for any other role.
A tiny, targeted stylesheet
The accompanying CSS only styles the pill itself, adding negligible weight wherever the admin bar already loads.
Read-only, administrator-only
The code observes an existing setting and never touches it directly.
Visible only with manage_options
The pill only renders for users who can manage options, the same capability required to change the Reading setting itself.
Reads a setting, never changes one
The module only displays the current state and links to the settings screen; it never modifies blog_public directly.
No new capability or role required
Nothing about the module introduces a new permission; it relies entirely on the capability WordPress already uses for this setting.
The link goes to WordPress's own settings screen
Clicking the pill opens options-reading.php, a native WordPress admin screen, not a custom page the module introduces.
Built directly around WordPress's own admin bar and Reading setting
The supplied code integrates through APIs present in WordPress core; this page makes no compatibility claim beyond the verified implementation.
blog_public
The exact WordPress core option behind the "Discourage search engines from indexing this site" checkbox in Settings → Reading.
admin_bar_menu
The native WordPress hook used to add a custom node to the admin bar, the same mechanism WordPress core and other plugins use for their own admin bar items.
admin_enqueue_scripts and wp_enqueue_scripts
Both hooks get used together so the pill's styling loads correctly whether an administrator is viewing wp-admin or the live front end.
TheOneWP versus common alternatives
Compare the verified Search Visibility Notice implementation with checking the setting manually.
| Capability | TheOneWP Search Visibility Notice | Other common solutions |
|---|---|---|
| Surfacing the indexing setting | A persistent, colored pill in the admin bar | Usually nothing beyond the Reading settings screen itself |
| Visibility on the front end | Shown wherever the admin bar appears, site-wide | Rarely covered by plugins focused only on wp-admin |
| Fixing a wrong setting | One click straight to Settings → Reading | Requires navigating to Settings manually |
| Configuration required | None; accurate the moment it's enabled | Some status-indicator plugins need setup of their own |
| Who sees it | Administrators only, automatically | Can require manual role configuration to restrict |
Check indexing status in four steps
Make the pill part of a regular glance, especially right after launch.
Enable Search Visibility Notice
Activate the module from the TheOneWP SEO settings tab.
Check the admin bar
Look for the colored pill in the top-right of the admin bar, in wp-admin or on the front end.
Click it if it's red
A red pill means search engines are currently discouraged from indexing the site; click it to jump to Reading settings.
Confirm the setting and save
Uncheck "Discourage search engines" if the site should be indexable, then save the Reading settings.
Make the check part of the routine
A visible status only helps if someone actually looks at it at the right moment.
Check the pill right after launch
A launch day check confirms the indexing setting matches what was intended before search engines get a chance to see the wrong state.
Treat a red pill as expected during development
A red pill isn't a bug while a site is genuinely under construction; it's only a problem once the site is meant to be public.
Make checking the pill part of a launch checklist
Since the module needs no configuration, the only remaining step is remembering to look, so build that into a standard pre-launch routine.
Use it as a first check during a traffic drop
An accidentally-flipped indexing setting is a fast, free thing to rule out before investigating anything more complex.
Avoid the ways a visible warning still gets missed
A few assumptions can undercut what the pill is meant to catch.
Not noticing the pill because it's easy to tune out
A persistent element can become invisible through familiarity, so it's worth making checking it explicit during launch reviews rather than assuming it will be noticed.
Assuming green means fully optimized for search
The pill only reflects whether indexing is allowed at all, not whether the site is otherwise well-optimized for search engines.
Expecting other roles to see the warning too
The pill is administrator-only by design, so an editor or author won't see it even if they happen to notice something's off.
Search Visibility Notice FAQ
These answers come directly from the verified class, its CSS asset and the settings registration.
What does Search Visibility Notice do?
It adds a colored pill to the WordPress admin bar showing whether search engines are currently allowed to index the site, based on the Reading settings "Discourage search engines" checkbox.
What does a green pill mean?
Search engines are currently allowed to index the site.
What does a red pill mean?
Search engines are currently discouraged from indexing the site, the same state as the "Discourage search engines" checkbox being ticked.
What happens when I click the pill?
It opens Settings → Reading directly, where the indexing setting can be reviewed or changed.
Does this module change any settings on its own?
No. It only displays the current setting and links to where it can be changed; it never modifies anything automatically.
Who can see the pill?
Only users with the manage_options capability, typically administrators.
Does the pill appear on the front end of the site, or only in wp-admin?
Both. It appears wherever the admin bar itself is showing for a logged-in administrator.
Does this require any configuration after enabling it?
No. The pill reflects the real setting accurately as soon as the module is enabled.
Will a red pill during development break anything?
No. A red pill during active development simply reflects that search engines are currently discouraged, which is often the intended state before launch.
Does this affect the site's actual SEO performance?
No. The module only surfaces an existing setting; it doesn't change how the site gets indexed or ranked beyond what that setting already controls.
Stop finding out the site was invisible to Google after launch.See the indexing status on every single page.
Use Search Visibility Notice to keep the site's search engine indexing status visible in the admin bar, with one click straight to the setting that controls it.