Google's Rich Results Test Displays No More Than 102 Objects for One JSON-LD Entity and Accepts an Invalid eventStatus Value

Imagine a library where every book is described not just by its title and author, but by a detailed map of its contents, its connections to other books, and the specific facts it holds. This is how modern search engines understand the web. Instead of just reading words on a page, they look for a special kind of code hidden within the site's structure. This code, written in a format called JSON-LD, acts as a structured map of the information on that page. It tells the search engine exactly who runs the site, what topics it covers, and how different pieces of information relate to one another. For website owners, this is a powerful tool. By providing these clear, organized facts, they hope their pages will appear in search results with richer details, such as star ratings, event dates, or direct answers to questions, making it easier for people to find what they need.

However, there is a gap between what website owners provide and what the tools used to check that information actually show them. A recent study by Brian R. Hatten, an orthopedic surgeon and the founder of an educational website for knee replacement patients, uncovered two silent failures in Google's primary testing tool, the Rich Results Test. This tool is designed to let webmasters paste their code and see how Google will interpret it. Hatten discovered that the tool has a hidden ceiling: it will only display the first 102 pieces of information for a single person or organization, silently ignoring everything that comes after. Furthermore, the tool fails to catch certain types of errors, accepting invalid data that should have been rejected. These findings matter because they mean a website owner can receive a "green check" of approval from the tool, believing their data is perfect and complete, while in reality, a significant portion of their information is being hidden from view or is technically incorrect.

The story of this discovery began with Hatten's own website, My Knee Guide. In 2026, he decided to build a comprehensive structured data map for his site to help search engines and artificial intelligence systems understand his work and his credentials. He created a digital profile, known as a "Physician" entity, that described his career, his affiliations, the articles he wrote, and the events he taught. As he added more details, this profile grew to include 121 distinct pieces of information. When he ran this profile through Google's Rich Results Test to see how it would appear, the tool showed him a clean, valid result. But when Hatten compared the tool's output against his original file, he realized something was missing. The tool had displayed exactly 102 items and then stopped. It had not shown the final 19 pieces of information he had included.

What made this discovery particularly tricky was that the tool gave no warning. It did not flash an error message or a red light to indicate that data had been cut off. The summary screen showed a green checkmark, suggesting everything was fine. Hatten had to manually compare the text of his original file with the text the tool displayed to realize that the last part of his profile was simply gone from the view. He conducted a series of tests to confirm this behavior. He created files with varying numbers of items and found that whenever an entity exceeded 102 items, the tool consistently displayed only the first 102. It did not matter if the items were short or long; the limit was based on the number of items, not the amount of text. Even more surprisingly, the tool seemed to apply this limit to each person or organization individually. If a page contained two different organizations, the tool would show the first 102 items for the first organization and the first 102 for the second, rather than stopping after 102 items total for the whole page.

Hatten also found that the tool was not always checking the quality of the information it displayed. In his profile, he included an event that had already finished and marked its status as "EventCompleted." According to the official rules for this type of data, the valid options for an event's status are specific terms like "EventScheduled" or "EventCancelled," but "EventCompleted" is not on that list. When Hatten ran his file through Google's tool, it gave him a green check, accepting the invalid term without complaint. However, when he ran the exact same file through a different, independent validator, that tool correctly flagged the error and rejected the term. This meant that for months, Hatten's website carried a piece of data that was technically incorrect, yet the primary tool used by webmasters to verify their work told him it was perfect.

The implications of these findings are significant for anyone trying to manage their digital presence. The Rich Results Test is the standard way for website owners to verify that their structured data is working correctly. If the tool silently drops information or accepts invalid values, owners are left with a false sense of security. They might believe their rich results will appear as intended, only to find that search engines are missing key details or that the data they provided does not meet the strict standards required for indexing. Hatten's study suggests that the tool is not a complete check. It can validate that a file is readable, but it cannot guarantee that the entire file is displayed or that every value is correct according to the official definitions.

To navigate these hidden limitations, Hatten recommends a more cautious approach. Website owners should not rely solely on the green checkmarks from the Rich Results Test. Instead, they should manually count the number of items in their data to ensure they stay under the 102-item threshold for any single entity. They should also cross-check their files with independent validators to catch errors that Google's tool might miss. Perhaps most importantly, they should treat the tool's display as a sample rather than a full report. If an item is not shown in the tool's preview, it does not necessarily mean the search engine has ignored it, but it does mean the owner cannot be sure what is being seen. The study concludes that until Google updates its tools to report these limits and errors clearly, the responsibility falls on the website builder to verify their own data against multiple sources, ensuring that the digital map they create is both complete and accurate.