You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
urlNotifications:publish not replying with expected response #3560
Thanks for the reminder, this method had been working for us for over two years (up to now) despite our submissions being ordinary html pages.
It would be useful if the API call in question had started to return a relevant error message when the behaviour changed.
In terms of our use case, we'd been using it to get new URLs into our Google CSE that represent local government applications that must be publicly published. A sitemap did not seem appropriate in this case due to the large amount of historical applications covering decades.
Is there an endpoint / alternative method we can use to get new application pages indexed so that they are visible in short order to our CSE?
Activity
pretenderchen commentedon Oct 9, 2024
The Indexing API can only be used to crawl pages that contain a JobPosting or BroadcastEvent (nested in a VideoObject).
DevRCRun commentedon Oct 14, 2024
Thanks for the reminder, this method had been working for us for over two years (up to now) despite our submissions being ordinary html pages.
It would be useful if the API call in question had started to return a relevant error message when the behaviour changed.
In terms of our use case, we'd been using it to get new URLs into our Google CSE that represent local government applications that must be publicly published. A sitemap did not seem appropriate in this case due to the large amount of historical applications covering decades.
Is there an endpoint / alternative method we can use to get new application pages indexed so that they are visible in short order to our CSE?
sofisl commentedon Feb 4, 2025
Since this is an API question/bug, transferring over to Discussions - also, please feel free to post directly to the API issue tracker itself