Regenerate Google Fonts locally css when a URL change is detected

Describe the Problem When my website was pushed from the development URL to the production URL, the css font path in Google Fonts locally was not a database file, so it could not be modified through the backup plugin, resulting in a large number of errors in the font files after the move. What’s worse is that if you don’t notice this problem and your website runs ads, it will be identified as a hacked website by the Google Ads backend and will not be able to run ads. Propose a Solution I suggest the following approach: The Load Google Fonts locally feature is disabled by default. or If the URL is different, regenerate the CSS file (this is technically feasible, otherwise why would you ask us to rebind the authorization, right? Additional Context <img width="917" alt="入侵" src=" /> Agreement • I confirm I have read and followed all the guidelines and instructions outlined in the Feature Request form. • I agree that my discussion …