Yes—if you treat schema as a machine-readability layer for your whole site rather than a shortcut to one SERP feature. Even when specific rich results change, consistent structured data helps search engines and AI systems understand your brand, offerings, and content with less ambiguity.

The organisations that benefit most are usually those that integrate schema into their templates, content models, and governance so it keeps paying off across redesigns and new channels.

There is no universal percentage. Instead, aim for full, valid coverage on the templates that matter most for your commercial goals—typically solution pages, key resources, and proof assets like case studies—before expanding to secondary templates. From there, treat schema coverage as an ongoing hygiene metric: any new template or major journey should have a clear plan for structured data from the design stage onward.

You will need engineering involvement to design and implement the initial template-based architecture, and whenever your schema model or components change in a significant way. Day-to-day schema hygiene, however, should be largely in the hands of content and SEO teams via structured fields in your CMS. When those teams can update key properties without code changes, your program becomes far more agile.

Timelines vary widely based on site size, stack, and governance. For many B2B organisations, a focused first wave that covers a handful of high-value templates can fit into a few development sprints once requirements are clear and prioritised. The more your schema model is aligned with existing content structures and systems, the faster you can move without creating long-term maintenance headaches.