/technical-seo591 words

Google Kills Data Feed Validation Tool for Book Actions

Google confirms its Data Feed validation tool for Book actions structured data is "turned down"; the feed-validator URL now serves a 502 and docs point to a manual error checklist.

Google Data Feed Validation Tool Has Been Turned Down
Google Data Feed Validation Tool Has Been Turned DownPexels / pixabay
  • Google stated "The Data Feed validation tool has been turned down and is no longer available."
  • The tool's URL, actions.google.com/tools/feed-validator, now returns a 502 server header.
  • The tool likely launched between October 2016 and December 2017 with the Actions on Google platform.
  • Google replaced the docs section with a two-point manual checklist covering @type spelling and @context values.
  • The @context must be "https://schema.org" for both ReadAction and BorrowAction.

Google has confirmed it "turned down" its Data Feed validation tool, leaving the Book actions structured data help documentation without an automated way for publishers to test their feeds. The tool's URL, actions.google.com/tools/feed-validator, now returns a 502 server header.

The change is a confirmed Google statement, not tool-signal speculation. Google's own changelog entry for the documentation reads plainly: "The Data Feed validation tool has been turned down and is no longer available." That sentence is the whole story — an automated validation endpoint is gone, and publishers who relied on it now have to check their feeds by hand.

What changed in the documentation?

Google removed the section titled "Test your feed with the Data Feed validation tool" from the Book actions help documentation and deleted the link to the tool itself. In its place, the company added a new section called "Check your feed for common errors."

The replacement section is a short manual checklist. It instructs publishers to do two things before hosting a feed:

  • Verify that the value of @type is spelled correctly.
  • Make sure the value of @context is set properly. Google specifies that it should be set to "@context": "https://schema.org" for both ReadAction and BorrowAction.

That's the entire substitute for what was previously an automated testing process. Google's documentation change is dated language is minimal — the company framed the swap simply as a replacement of one documentation section for another, plus the removal of the tool link.

What was the tool, and who used it?

The Data Feed validation tool lived within Google's broader Actions on Google developer platform, the ecosystem that powered structured-data-driven actions such as Book actions (a schema.org markup format letting publishers surface ReadAction and BorrowAction entries for e-books and library lending in Google surfaces).

The tool's exact launch date is unclear, but it most likely surfaced sometime between October 2016 and December 2017, alongside the broader rollout of the Actions on Google developer platform. That makes it a roughly seven-to-nine-year-old utility at the time of its retirement.

The audience hit hardest is niche but specific: ebook retailers and library-lending platforms that implement Book actions structured data. For them, the workflow has shifted from "paste your feed into Google's validator" to "review your JSON-LD by hand against a two-point checklist." The checklist covers the two most common feed-level mistakes — a misspelled @type value and an incorrectly configured @context — but nothing beyond that.

The @context check matters because both action types in the Book actions feed, ReadAction (marking a book as readable) and BorrowAction (marking a book as borrowable, typically from a library), must carry the schema.org context string exactly as specified for Google to parse the feed.

Is there a replacement validator?

Not in the documentation. Google's new section points only to the manual pre-hosting checklist; it does not name an alternative automated validator for Book actions feeds. The generic Rich Results Test remains Google's tool for other forms of structured data, but the removed documentation did not direct publishers to it, and the source material makes no mention of a substitute endpoint.

For now, publishers debugging a rejected or ignored Book actions feed are on their own for everything past the two listed checks. Watch the Book actions documentation for further changelog entries — if Google follows up with a designated replacement tool or expands the checklist, that revision will land there first.

via developers.google.com (Original)

More from James Calloway

James Calloway

Show full bio

Market editor covering money, funding and market shifts around Search rankings and algorithm updates, generative engine optimization at SERP Journal.

231 articles