Meaningful changes
New, updated, redirected, restored, and removed public pages.
Search discovery operations
Tell search systems when important information changes.
Search Freshness detects meaningful website updates, checks that the page is safe to submit, delivers the change to participating search systems, and gives owners a clear record of what happened.
Preflight checks
Canonical, robots, noindex, status, hostname, and verification.
Controlled delivery
Deduplicated IndexNow batches with retries and rate-limit protection.
Owner clarity
Accepted changes and actionable problems in plain language.
Free readiness check
See whether a website is ready for controlled change delivery.
Check one public website for the essentials Search Freshness relies on. This is a live technical check, not an SEO score or a promise of indexing.
The check reads public website files only. It does not change the website or submit any URL.
SF
Five checks. No mystery score.
You will see the page response, canonical, robots access, sitemap, and ownership-key status separately.
Why it matters
Publishing is not the same as being discovered.
Search engines can eventually find changes through ordinary crawling, but the timing is uncertain. Search Freshness creates a controlled change record and delivers eligible URLs when the update is real.
Service and location pages
Deliver new services, meaningful offer changes, corrected business information, and updated local pages when they actually go live.
Articles and resource libraries
Notify participating search systems when an article is published or substantively improved without repeatedly submitting unchanged archives.
Redirects and removals
Record moved and deleted URLs so stale search results can be revisited instead of waiting for an uncertain future crawl.
Multi-site operations
Give owners and agencies one view across WordPress, Vercel, and other sitemap-based websites while keeping each business isolated.
The operating record
From page change to an honest delivery status.
Search Freshness separates notification from indexing. Owners can see what Apex Blue controlled and what remains each search engine's decision.
Detect the change
A publishing connector or sitemap reconciliation identifies a page that was added, materially updated, redirected, restored, or removed.
Check the page
Search Freshness checks the production hostname, response, canonical, robots instructions, noindex state, and site verification before delivery.
Notify participating systems
Eligible URLs are deduplicated, grouped by website, and delivered through IndexNow with retries and rate-limit protection.
Show what happened
Owners see which changes were accepted, which were blocked, and the exact issue that needs attention without reading protocol logs.
Built for owners
One view across every managed website.
The dashboard shows healthy sites, accepted changes, blocked pages, broken verification, overdue reconciliation, and the next action that deserves attention.
Healthy
The verification key works and recent eligible changes were accepted.
Needs attention
A canonical, noindex, robots, response, or connector problem requires review.
Reconciled
The current sitemap and recorded changes agree.
Connected sources
WordPress, production deployment events, manual changes, or sitemap monitoring.
Clear boundaries
Faster notification without invented certainty.
Search Freshness uses the open IndexNow protocol to notify participating systems, including Microsoft Bing, when public URLs change. A successful response confirms receipt; it does not guarantee a crawl, index entry, ranking, visit, lead, or AI citation.
XML sitemaps, internal links, useful content, technical search hygiene, Google Search Console, and Bing Webmaster Tools remain part of a complete search visibility program.
Product questions
What Search Freshness controls—and what it does not.
Does Search Freshness guarantee indexing or rankings?
No. A successful delivery means a participating system received the change notification. Each search engine still decides whether and when to crawl, index, and rank a page based on accessibility, quality, duplication, authority, and its own systems.
Does it replace an XML sitemap or Google Search Console?
No. Search Freshness uses event-driven notifications for meaningful changes and keeps sitemap reconciliation as a coverage safeguard. Google Search Console remains important for Google performance and inspection because Google is not currently an IndexNow participant.
Will it submit every page repeatedly?
No. Search Freshness fingerprints changes, debounces repeat events, and checks whether a URL is eligible before delivery. Cosmetic deploys, previews, drafts, admin pages, tracking URLs, and unchanged content are excluded.
Which websites can connect?
Apex Blue supports a direct WordPress connector, production deployment notifications for supported website builds, and sitemap reconciliation for other public websites. Existing IndexNow delivery from a host or plugin is reviewed first to prevent duplicate submissions.
Search Freshness setup
Start with the websites that change most often.
Share the websites, publishing platforms, and kinds of pages that change. Apex Blue will identify existing IndexNow delivery, prevent duplicate submitters, and recommend the smallest useful setup.