Is adding Book markup to a page sufficient for Google's book actions?

Definition: No. Google's Book actions documentation describes page markup as part of a provider feed workflow. A provider must complete the documented interest and onboarding step, create and host the required feed, validate it, and submit it for review.

Key facts

• Google's Book actions documentation requires an interest form and onboarding, then distinguishes a Book feed for selling from separate Book and Library feeds for lending.
• Google's general structured data guidelines require a supported markup format, access for Googlebot, and structured data that represents visible page content.
• Schema.org's Book type documents bookEdition as the edition of a book and isbn as the ISBN of the book.

What does provider onboarding add?

Google limits the Book actions feature to book providers that have filled out the interest form and have been onboarded. If a site sells books, the provider must upload a Book feed, and a Google support team supplies details about where and how to upload it. If a site lends books, the provider must upload two separate feeds, a Book feed and a Library feed. Adding Book markup to a product page therefore leaves the provider and feed steps incomplete.

What must the feed contain?

The feed is a JSON data file whose entities use the Book actions schema. Google's example has a DataFeed root, a Book entity, a unique @id, a url, and a ReadAction target with a urlTemplate.

{
  "@context": "https://schema.org",
  "@type": "DataFeed",
  "dataFeedElement": [
    {
      "@context": "https://schema.org",
      "@type": "Book",
      "@id": "https://example.com/work/the_catcher_in_the_rye",
      "url": "https://example.com/work/the_catcher_in_the_rye",
      "potentialAction": {
        "@type": "ReadAction",
        "target": {
          "@type": "EntryPoint",
          "urlTemplate": "https://example.com/store/9787543321724"
        }
      }
    }
  ]
}

Google requires each feed entity to have a unique @id, url, and urlTemplate. Feed URLs and deep links must be production and canonical URLs, and the feed must exclude stale entities, including entities whose availabilityEnds date has passed. A single feed file uses the .json extension. A compressed feed can use formats such as zip, gz, tar, or tar.gz; a feed whose uncompressed size exceeds 1 GB must be split into multiple files.

How are hosting, validation, and review handled?

The feed must be hosted at a secure location that Google can fetch regularly. The documented hosting methods are Google Cloud Storage with Storage Object Viewer permission, HTTPS with username and password or HTTP client certificates, SFTP with a password or key and phrase, and AWS S3 with a key ID and access key.

Before submission, Google's Data Feed validation tool should be set to Books Action for the Book entity. The guide also tells providers to check the spelling of @type and to set "@context": "https://schema.org" for both ReadAction and BorrowAction. A Google support team reviews the quality of feed deep links. The review request includes the feed file URL and, where applicable, credentials that let Google retrieve it. Manual testing should confirm that a deep link opens the page where a user can buy or borrow the book.

Google's general structured data guidelines add page-level conditions: use JSON-LD, Microdata, or RDFa; do not block the structured data pages to Googlebot with robots.txt or noindex; and make the markup a true representation of content visible to readers. Those conditions apply to the page markup alongside the Book actions feed process.

What happens after submission?

In the guide last updated 10 December 2025, Google recommends updating the feed daily according to catalog changes. Google Search does not support real-time updates, fetches the feed once a day, and typically indexes its content within two days. A provider can use availabilityStarts and availabilityEnds for a foreseeable change in an edition's availability, and should remove an entity when it is no longer available.

Related terms

• Structured data
• JSON-LD
• XML sitemap

FAQ

Is Book JSON-LD alone enough?

No. It can be part of the page and feed representation, but Google's documented provider path also requires interest, onboarding, feed hosting, validation, and review.

Do lending sites submit the same feed as selling sites?

No. Google specifies a Book feed for a selling site and separate Book and Library feeds for a lending site.

Does Google publish a minimum catalog size for participation?

The page limits the feature to providers with a wide selection of available books, but it gives no numeric catalog threshold.

Sources

1. Google Search Central, "Book Schema for Google Search", 10 December 2025
2. Google Search Central, "General Structured Data Guidelines", 10 July 2026
3. Schema.org, "Book", 16 September 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer