Introduction to Google’s Structured Data Documentation
Google recently removed outdated structured data documentation, which has caused some confusion among users. Instead of displaying a 404 error page, Google has chosen to redirect the old URLs to a changelog that links to the old URL, resulting in an infinite loop between the two pages. This approach is not typical of how SEOs handle missing web pages and 404 server responses.
What Happened to the Structured Data Documentation?
Google quietly published a changelog note announcing the removal of obsolete structured data documentation. An announcement was made three months ago in June, and the obsolete documentation was finally removed. The missing pages are for the following structured data that is no longer supported:
- Course info
- Estimated salary
- Learning video
- Special announcement
- Vehicle listing
The Redirect Loop
The usual procedure when removing web pages is to return a 404 Page Not Found server response. However, Google is returning a 301 redirect back to the changelog for some of the changed pages. This setup creates an infinite loop between the two pages, as the changelog links back to the missing web page, which then redirects back to the changelog.
Understanding the Redirect Loop
To illustrate this, consider the following example: the link to the "Course Info" structured data redirects to the changelog, which contains the link to the "Course Info" page. This creates an infinite loop, where the user is redirected back and forth between the two pages. This is not a good user experience and can also cause issues for crawlers.
Why Did Google Choose This Approach?
301 redirects are an option for pages that are missing, so Google is technically correct to use a 301 redirect. However, 301 redirects are generally used to point to a more accurate URL, which means a redirect to a replacement page that serves the same or similar purpose. In this case, the redirect creates an infinite loop, which may not be the best approach.
Alternative Solutions
It would have been a better user and crawler experience to link to the June 2025 blog post that explains why these structured data types are no longer supported, rather than creating an infinite loop. This approach would have provided a clearer explanation to users and avoided any potential issues for crawlers.
Conclusion
Google’s decision to redirect removed structured data documentation to a changelog, resulting in an infinite loop, is an unusual approach. While it is technically correct, it may not be the best solution for users and crawlers. A more straightforward approach, such as linking to a replacement page or a blog post explaining the changes, may have been more effective. As Google continues to update and refine its structured data documentation, it will be interesting to see how they handle similar situations in the future.