You can build a Python prototype that searches YouTube for terms such as semaglutide, tirzepatide, and BPC-157, groups brand-name matches with generic names, and saves the results to CSV without an API key. But the tutorial’s method reads YouTube’s search page and parses undocumented page data; YouTube’s policies prohibit scraping YouTube applications and using undocumented APIs without express permission. Treat it as a description of an unsupported approach, not a policy-cleared substitute for the documented YouTube Data API.
What the no-key method counts—and what it cannot tell you
Omar Eldeeb’s tutorial describes sending searches for peptide and GLP-1-related terms, matching compound names and aliases in surfaced video titles or snippets, removing duplicate video IDs, and recording daily counts in a CSV file. Its examples map Ozempic and Wegovy to semaglutide, and Mounjaro and Zepbound to tirzepatide. A video may match more than one compound.
As an Amazon Associate I earn from qualifying purchases.
This is a count of matching videos returned by search, not a census of YouTube. Search results are ranked and may vary from one request to another; the tutorial also cautions that YouTube can change its page structure. A match means text surfaced in a result, not that the video discusses the compound in depth or makes a valid medical claim.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The tutorial reports that three repeated runs on September 29, 2026 returned 45, 48, and 117 unique matching videos. These are the tutorial author’s observations for those runs, not an independently reproduced result, a platform-wide estimate, or evidence of demand, treatment use, safety, or efficacy.
#1 Best Overall
Important: page scraping is not an officially supported API
The no-key approach parses embedded ytInitialData from YouTube search pages. YouTube’s API Services Developer Policies state: “You must not, and you must not encourage, enable, or require others to, directly or indirectly, scrape YouTube Applications or Google Applications, or obtain scraped YouTube data or content.” The same policy says, “You must not use undocumented APIs without express permission.”
Those restrictions make the tutorial’s page-parsing workflow a policy concern, even if it can be useful as a learning exercise or an experimental prototype. Review current YouTube policy before collecting data, and do not treat the absence of an API key as permission to automate access to YouTube pages.
Choose between page parsing and the documented Data API
| Approach | Policy support | Credentials and quota | Stability and meaning of results |
|---|---|---|---|
| No-key page parsing | YouTube policy prohibits scraping YouTube applications and using undocumented APIs without express permission. | The tutorial avoids an API key; that does not remove the policy restriction. | Depends on page structure that can change. Returns ranked search matches, not all videos. |
| Documented YouTube Data API | The documented route for supported YouTube search access. See the YouTube Data API documentation and current policies. | The tutorial says this route requires a Google Cloud key and has a daily quota; the available information does not establish the current quota amount. YouTube policy says public video search does not require user authorization, but that does not mean credentials are never needed for API access or that every API action is public. | Uses a documented interface rather than parsing page internals. Search results remain search results, not a complete count of YouTube content. |
For a supported automated workflow, consult the current Data API documentation and configure access through Google Cloud. YouTube’s policy distinction is important: a public search does not require user authorization, but API access can still require a key, and other actions may require authorization.
Free tools Windows power users keep installed
One-click scans. No signup required.
How to interpret a peptide or GLP-1 mention
Alias matching can make a tracker more useful: searches or text rules can associate brand names with a generic compound name. It can also widen the kinds of results that count. A match in a title or snippet only establishes that the text appeared in a surfaced search result; it does not verify the video’s accuracy, establish a clinical outcome, or show how common a belief or behavior is.
Keep the drug category clear when reporting findings. FDA’s February 6, 2026 statement concerned intended steps to restrict certain GLP-1 active pharmaceutical ingredients intended for non-FDA-approved compounded drugs being mass-marketed by companies. It warned against misleading equivalence and clinical-result claims. That statement does not make a search-result count evidence about an FDA-approved product or a compounded product’s safety or effectiveness. See the FDA statement for its scope.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Dependencies and learning resources
The tutorial uses Python’s Requests library for HTTP requests and writes output to CSV. Requests’ official documentation describes it as a Python HTTP library and specifies Python 3.10 or later support. The narrow workflow does not require buying a book; readers seeking broader beginner automation instruction may also consider Al Sweigart’s Automate the Boring Stuff with Python, 3rd Edition, listed by No Starch Press.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
