I doubt this is the actual cause, but I can’t think of any other plausible explanation. One possibility is that repeatedly requesting manual indexing in GSC (Google Search Console), while the same URLs were also being discovered automatically through the sitemap, may have unintentionally triggered a spam or quality signal in Google’s indexing system.
This kind of duplicated or aggressive indexing behavior could be misinterpreted by the algorithm, even if the content itself was legitimate.
But I still have a few questions. What is WordPress’s default behavior? Does it prevent files uploaded to the media library from having public URLs? Are they only public once they are inserted into a published post? Images make sense because they are embedded, but what about a PDF linked inside a post? My understanding is that media files become publicly accessible as soon as they are uploaded, as long as someone knows or guesses the URL. I mean, the leak could have happened even without the plugin?
Hopefully this translates into clearer direction for Firefox and better execution across the company, instead of pushing multiple micro products that are likely destined to fail, as Mozilla has done over the past 5+ years.
From his LinkedIn profile [1], his recent roles have been consistently centered on Firefox:
Chief Executive Officer
Dec 2025 - Present · 1 mo
-------
General Manager of Firefox
Jul 2025 - Dec 2025 · 6 mos
-------
SVP of Firefox
Dec 2024 - Jul 2025 · 8 mos
-------
He appears to have a solid background in product thinking, feature development, and UX. If his main focus remains on Firefox, that could be a positive sign for the product and its long term direction.
[1] https://www.linkedin.com/in/anthonyed/