Beginning April 30th, 2021, we will discontinue revenue sharing on the following search engine layouts:
The public URL - a link provided for a Google hosted public page for your engine that hosts both the search box and the search results
The Google hosted layout, in which only the search results are displayed on a Google-hosted webpage
Search engines that fall into the two above categories will continue to show ads, but no revenue will be shared.
What does this mean for me?
To continue sharing revenue, you’ll need to use the Search Element deployed on your own site, which will continue to allow for monetization. To deploy the search element tag, please review the developer page.
To change your search engine layout:
What should I do next?
Please visit the help center for help with any other questions / concerns.
We’re pleased to announce that search results URLs rendered by the Programmable Search Element will now use the more descriptive breadcrumb trails. This change will be rolling out over the next week.
Engine owners who prefer to show the full URL can configure this under the Result URL settings in Control Panel > Look and feel > Customize.
The Programmable Search Element offers a straightforward way to add Programmable Search to your website. Until now, the only version of the Search Element available to most customers has been the free ads-supported version.
Today we’re happy to announce a new ads-free configuration of the Search Element using the Programmable Search Element Paid API. By enabling this API and linking it to your search engine, you can opt to pay on a per-query basis ($5 per 1000 queries) instead of showing ads. No code changes on your website are necessary to switch from a free ads-supported Search Element to the paid ads-free version. You can switch back to the free ads-supported version of the Search Element at any time.
Setting a Paid Element key in the Control Panel:
Search Element results, ads-free:
Click here to learn more and get started with the Programmable Search Element Paid API.
Note that this does not affect the existing Custom Search JSON API, which continues to offer a programmatic ads-free way to access search results without using the Search Element. Click here to see a comparison of all Programmable Search offerings.
Search Results that are created using Programmable Search Engine may display “Enhanced by Google”. If the Search Box and Search Results are rendered through the Programmable Search Engine Search Element, then this will happen automatically.
Today, we're happy to announce that users using their own search box or the Custom Search JSON API may add this attribution using the new Programmable Search Attribution API. Simply include a single tag:
<script src="https://www.gstatic.com/prose/brand.js" targetId="divId"></script>
Everyone using Google branding in their own search box should use this new resource. For more information see the help pages on Attribution API and Branding Guidelines.
Many of you have requested a process to allow multiple users to own a Programmable Search Engine. For instance, you may have created, developed and customized your website's search experience under your Google account, but want the long-term management of the search engine to be performed by someone else.
Now, you can easily add a new owner to your search engine by simply selecting the Owner User Role when you add a user in the Users tab in the control panel.
The Custom Search JSON API lets you develop websites and applications to retrieve and display search results from Programmable Search Engine (formerly Google Custom Search) programmatically. Basic monitoring for the API has been available through Cloud Platform Console's API Dashboard.
Today, we’re excited to announce that the Custom Search JSON API is now integrated with Google Cloud's operations suite (formerly Stackdriver). Google Cloud's operations suite supports a wide variety of metrics, which you can combine with filters and aggregations for new and insightful views into your application performance. For example, you can combine a request count metric with a grouping on the HTTP Response Code to build a dashboard that shows error rates over time, or aggregate a latency metric at varying percentiles. Learn more about creating custom dashboards, setting up alerts, and accessing metrics data programmatically.
Example of a custom dashboard showing QPS and error rates:
Custom dashboard showing latency percentiles:
Defining an alert on a QPS threshold:
See Monitoring Your API Usage for a discussion of the different monitoring and alerting capabilities provided by the API Dashboard and the Google Cloud Operations suite.
