This rings true for me, and reminds me of my early experience learning about machining and CNC machines. There are a lot of very low quality googleable sources out there for that field (mostly dealing with the hobbyist side of it) that crowded out the information I needed for professional development and troubleshooting.
Eventually, as my knowledge of the field increased I learned the "pro" terminology for certain objects and processes, which improved my ability to search useful info. I also discovered through chance or personal recommendation some very useful pro-level online sources, which don't have a large presence on search engines. There was a long grind of several years before I got to the point where I could search online for machining information and solutions online with confidence that I could find useful results and assess their reliability. Even then, there is a lot that I need to find in books/manuals or in conversation with experts.
While this is a process that takes place when learning about any technical topic, in my experience its easier in programming (and to a lesser degree general IT topics) than in fields that exist primarily in the world of physical objects. IMO, this has something to do with the tendency of programming problems to "self-define" themselves in specific textual language (I.E. compiler errors you can copy and paste into google) and also with origins and focuses of the largest internet knowledge bases.