#59487 closed defect (bug) (invalid)
WordPress files exposed to Google robots
Reported by: | nouha88 | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
Dear Sir/Madam,
I hope this message finds you well. I am reaching out for the first time to seek assistance regarding a matter concerning the WordPress Core. I hope I have directed my inquiry to the appropriate channel.
Upon conducting an examination using Google Search Console, I have observed that Google's web crawlers have identified certain JavaScript (JS) files originating from the "wp-includes" directory within WordPress. I have attached a screenshot to illustrate the specific files that Google's robots are detecting :
https://drive.google.com/file/d/1WotGVXHYqnPMu2AkLGptMGFAs8uZF8oi/view
I would greatly appreciate it if you could kindly inform me whether this is indicative of an issue and, if not, provide guidance on how to prevent Google from detecting these files.
Thank you in advance for your assistance.
Best regards,
Hi and welcome to WordPress Core Trac!
Those scripts are listed in the "Crawled - currently not indexed" report. #28604 stopped blocking access to the
wp-includes
directory so search engines can crawl all resources related to each page.If your concern is because of the URL, you probably could combine scripts into fewer files. I think you already have the WP Rocket plugin, and their documentation includes file optimization.
https://docs.wp-rocket.me/article/1351-javascript-minify-combine
If you do not want those specific scripts to be crawled, it might be better to remove them entirely from the page. The 'wp-hooks' and polyfill scripts are dependencies of the WooCommerce 'woo-tracks' script.
Additional information:
https://yoast.com/google-panda-robots-css-js/
https://yoast.com/wordpress-robots-txt-example/
For any further assistance with your site, please use the support forums:
https://wordpress.org/support/forum/how-to-and-troubleshooting/
I'll close this ticket as this is not a Core bug.