Welcome to the Q&A Forum

I agree that it doesn't make a lot of sense for Google to require the image itemprop - it's not the only example of Google requiring an itemprop that doesn't really make sense (for example, OperatingSystem is required for the WebApplication property, which doesn't make sense since it's...you know...a web application). For what it's worth, even though the documentation says it's required, BreadcrumbList code that doesn't include the image attribute validates just fine in the Structured Data Testing Tool, and pages without the image itemprop in place are still getting breadcrumb snippets in the SERPs. So it may not be as "required" as Google says it is.

Hey Ryan Just finally getting to this, thanks for reaching out on Twitter and asking for my input. It seems like everyone here has already helped you out, and I do agree Only thing I'd add, is remember 301 redirects are not only for engines but for the users so always be sure they make sense from a UX point of view. And also, be sure this doesn't create a chain of redirects. If 301s were already in place on the site you're redirecting from, always try to redirect from the original source, like this; DO THIS: www.one.com/original-page.html ----> www.two.com/real-page/ www.one.com/new-same-as-original/ ----> www.two.com/real-page/ NOT THIS: www.one.com/original-page.html ---> www.one.com/new-same-as-original/ ----> www.two.com/real-page/ Communicate this to IT as best as you can, as its been said by Cutts to avoid chains of 301s if possible. Hope this all helps, let us know! -Dan

Thanks, Phil! I really appreciate your insights.