A redesign can change more than appearance. Compare the current public version with the last known working version: URLs, menus, redirects, page visibility, mobile layout, forms, and ad code. Check whether the new theme moved or removed policy links, changed the posts page, or applied maintenance mode. Google’s site-not-ready guide lists access, code, policy, content, and experience as areas to investigate.
Make a short diff table with “old behavior,” “new behavior,” “evidence,” and “repair.” For instance, a redesign may send every old article URL to the homepage; restore relevant routes or map each old page to a close replacement. Test while logged out and on mobile, because administrators often see controls unavailable to visitors.
Run SiteReadyScore on the current public version to identify pages for review, then compare those findings with your change log. Do not assume the redesign caused the rejection unless evidence supports that connection. Check the account’s specific message and request review through AdSense when appropriate.