Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

urlNotifications:publish not replying with expected response #3560

Open
DevRCRun opened this issue Sep 20, 2024 · 2 comments
Open

urlNotifications:publish not replying with expected response #3560

DevRCRun opened this issue Sep 20, 2024 · 2 comments
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@DevRCRun
Copy link

DevRCRun commented Sep 20, 2024

Environment details

  • OS: Windows 11
  • Node.js version: v18.20.4
  • npm version: npm@10.7.0
  • googleapis version: 144.0.0

Steps to reproduce

  1. Over the last couple of weeks the POST https://indexing.googleapis.com/v3/urlNotifications:publish action has started returning the urlNotificationMetadata without the documented latestUpdate property shown at https://developers.google.com/search/apis/indexing-api/v3/reference/indexing/rest/v3/UrlNotificationMetadata breaking existing code. The status of the response is 200 and the statusText 'OK'. So it doesn't appear that the request / authorisation is being rejected best I can see. A preceding call to inspect the indexing status of the URL is working without issue.

Data submitted

data: { type: 'URL_UPDATED', url: 'https://www.theurlwesubmitted.com/path/page.html' },

Response:

{ urlNotificationMetadata: { url: 'https://www.theurlwesubmitted.com/path/page.html' } }

@DevRCRun DevRCRun added priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Sep 20, 2024
@pretenderchen
Copy link

The Indexing API can only be used to crawl pages that contain a JobPosting or BroadcastEvent (nested in a VideoObject).

@DevRCRun
Copy link
Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

2 participants