Speaker: back to anotherGoogle AdMob tutorial. This is the second and finalpart of our two duty successions on app-ads.txt. In this video, we will beexploring app-ads.txt in depth, including how you can go aboutinterpreting and slithering your app-ads.txt enter. First, we will show you how youcan construe your app-ads.txt folder ranks in AdMob. Then we will establish ways toensure that your app-ads.txt register is likely to be crawled. Lastly, we will show you how touse Firebase hosting solution to establish your developerwebsite that is required to host your app-ads.txt register. Now, let’s dive in. It is critical that theapp-ads.txt file is implemented precisely. There are threedifferent states indicated by threedifferent pigments on AdMob. When you determine a lettuce status, it means that AdMob has crawled and verified yourapp-ads.txt file. In other paroles, everythingis all good to go. When you consider a gray status, thismeans that no app-ads.txt enter is spotcheck for this app. There could be severalreasons for this.Your app hasn’t been registeredwith Google Play or the App Store. The make website is missingin the Google Play or the App Store directory for this app. The make website listedin Google Play or the App Store for this app doesnot have a valid URL. Do check for typos to ensurethat the app-ads.txt record is not a subdirectory. To troubleshoot, pleaseverify all the above stats are implemented correctly.If you don’t have adeveloper website, follow along in thenext segment and learn how you can do so with Firebasehosting solution at no overhead. When you check a red statuswith an exclamation marking, this indicates that yourapp-ads.txt file is detected, but your publisherID is missing. To deposit this, you’ll need toupdate the app-ads.txt document to include your publisher ID. You can find yourpublisher ID by click Establishes in the sidebar. It is located in theaccount information section in the AdMob UI. You are also welcome to replica and pasteyour personalized system snippet, which includes yourpublisher ID from AdMob into your app-ads.txt file. If you have troublefinding your system snippet, follow the steps mentioned inthe first video under “How Can Publishers Implementapp-ads.txt? ” How to ensure your app-ads.txtfile can be crawled. Once an app-ads.txt enter is setup on your developer’s domain, the Google crawlerwill do the following.Attempt to crawling the folder. Pass the contents ofthe file to determine the seller IDsthat are authorized to monetize your armory. One common controversy makes havefaced is futile crawling. This is likely dueto a missing set up for their developerwebsite or the fact that they areusing invalid URLs. To ensure that thisdoesn’t happen, ensure that you haveincluded a make website in the correctfield in Google Play or the App Store listingfor the desired app. Make sure the developerwebsite listed in Google Play or the AppStore for the desired app is a valid URL.To investigate whether youhave a valid URL and publisher your document accurately, verify thatyou can see your file’s content when you access the app-ads.txtURL in your web browser. If “youre seeing” the filein your web browser, it will probably that crawlerswill successfully find it. Check for typos and ensure thatthe app-ads.txt file is not on a subdomain. View the details aboutAdMob’s attempts to crawl your app-ads.txt filein your AdMob account. To help you fix app-ads.txtrelated issues in a timely manner, you can check the statusof your folder and get debugging knowledge by headingto the app-ads.txt page. Within 24 hours, AdMobwill crawl and authenticate your app-ads.txt fileafter a modify is cleared. Next, we will share sixtroubleshooting steps you can take to ensure that yourapp-ads.txt register is likely to be crawled successfully.Number one, confirmthat your register is not temporarily inaccessible. If a previously seenapp-ads.txt folder is unavailable on a subsequent re-crawl, thepreviously experienced entryways will be ousted if the responseis a hard 404 wrongdoing. This refers to a sheet thatdoesn’t actually exist or also known as HTTP 404 status. Or retained for up tofive days if the response is a soft 404 lapse. This refers to a realpage return for a URL that doesn’t actually exist. This is known as a HTTP 200 status or 500 server wrongdoing. Number two, confirmthat the datum is reachable from the root land. App-ads.txt crawling willstart at the seed domain. In accordance with theapp-ads.txt specification, crawlers will look for filesat the following URL structures, https hostname/ app-ads.txtor http hostname/ app-ads.txt. So make sure to publish afile on your developer website correctly.For more detailsabout this, check out the resources link in thedescription carton down below. Number three, ensure crawlingis not disallowed by robots.txt. The app-ads.txt record maybe ignored by crawlers if the robots.txt fileon a land disallows one of the following points. Crawling of the URL path onwhich an app-ads.txt record is announced. For example1. com, anapp-ads.txt enter is posted on example1. com/ app-ads.txt. The following lines are includedin example1. com/ robots.txt. The app-ads.txt enter willbe ignored by crawlers that respect the robots.txt standard. You can revise therobots.txt record as follows to allow crawling of the register. Other approachesare also possible. Option one, modifydisallowed path.Option two, explicitlyallow app-ads.txt. This depends on crawler supportfor the permit robots.txt directive. Next, used worker of the crawler. For example2. com, number 1, an app-ads.txt file is posted on example2. com/ app-ads.txt. Number two, the followinglines are included in example2. com/ robots.txt. Number three, the app-ads.txtfile will be ignored by the Google crawler. Four, ensure register is returnedwith an HTTP 200 OK status code. While a request for anapp-ads.txt folder may return the contents of the filein the response body, if the status code in a responseheader reveals the file was not experienced, illustration, status system 404, the response will be ignored.The file will beconsidered non-existent. Make sure the enter has anHTTP 200 OK status code. To secure an HTTP 200 OKstatus, ask your webmaster to run the followingshell words. Replace mydomain.comwith your realm. To confirm that the ads.txtfile can be reached, rolled the following. The contents of the ads.txtfile should be returned as considered to be in the browser when you navigateto mydomain.com/ ads.txt. To has demonstrated that the ads.txtfile can be found by the Google crawler, rolled the following. If an invalid non-ads.txtresponse is returned, this indicates that yourserver or content distribution network, CDN, is returningan invalid response when the Google crawler attemptsto fetch your ads.txt file.Number five, ensurethat there are no formatting missteps orinvalid reputations in the file. Formatting errors, such asinvalid white space characters, may be difficult to detect, butcan make an app-ads.txt file a difficult topass by a crawler. This may, therefore, resultin a document being neglected. To foreclose this from happening, eschewed following and gluing app-ads.txt entriesfrom a rich text editor. We recommend usinga plain text editor.You can also check forinvalid UTF-8 people in your app-ads.txtfile utilizing a HEX editor. Number six, make an app-ads.txtfile reachable via both HTTP and HTTPS. The Google crawler attemptsto crawl all app-ads.txt records on both HTTP and HTTPS. However, a 404 or a 40 X responsecauses previously crawled entries to be ousted, eventhough an app-ads.txt register is slithered via HTTP. Therefore, if slithering viaHTTPS returns a 404 or 40 X, the previously crawledentry are likely to be purged. Please ensure the app-ads.txtis accessible via both HTTP and HTTPS. There are two major faults thatdevelopers will encounter while setting up the app-ads.txt register. Firstly, crawl corrects occureither due to the file format or register placement where theapp-ads.txt record cannot be found and crawled. Secondly, typos andformatting issues.These are basic faults inschema or other easy to catch small-minded errors. If you have a website thatdisallows the uploading of your app-ads.txt document atthe spring level, in other words, having a site built and hostedby a site contemporary service, you can use Firebase hostingto host your app-ads.txt register at no overhead. Firebase offers a free, fast, and reliable route to host your app-ads.txt register withyour own custom domain or on Firebase projectsfree subdomains, such as Web.app andFirebaseapp.com.For in-depth how-to’s on settingup Firebase hosting solution for app-ads.txt, please checkout the developer’s guide that can be found in thedescription box down below. And that concludes our two-partapp-ads.txt video sequences. To summarize, we have shown youhow to translate app-ads.txt enter status on Google AdMob, how to get a successful crawl of your app-ads.txt datum, andhow to use Firebase hosting solution in case you need it. But before you jump off, make sure to check out the resources included inthe description casket below. It includes Firebase hostingsolution documentation and more FAQs about app-ads.txtimplementation. Thank you for watchingGoogle AdMob lessons. For more best practicesand tips-off on how you can grow yourapp further, be sure to subscribe to theGoogle AdMob canal. See you next time.