I am seeking assistance in linking a specific app-ads.txt file to my domain ‘www.domain.com’ for Google AdMob verification purposes. To provide some context on my setup, I have my domain hosted with AWS Route 53 and a company website hosted on site.google.

Within Route 53, I currently have domain.com linked to my site.google website. Additionally, I have configured ‘www.domain.com’ to route to ‘domain.com’.

In my attempts to meet the Google AdMob requirements, I created a page named app-ads.txt on site.google. However, the resulting URL for this page appears as ‘www.domain.com/app-ads-txt’, which unfortunately is not discoverable by AdMob. Despite my efforts to create a custom path, site.google does not allow the use of periods in URLs.

I am looking to properly route ‘www.domain.com/app-ads-txt’ to ‘www.domain.com/app-ads.txt’ or establish a direct route that leads AdMob to the app-ads.txt file for crawling and review purposes.

I have experimented with various configurations in Route 53, such as routing www.domain.com/app-ads.txt to ‘www.domain.com/app-ads-txt’ or directing ‘www.domain.com/app-ads.txt’ to an S3 bucket containing the app-ads.txt file. However, I have encountered recurring challenges, including conflicts with the existing routing for www.domain.com that directs traffic to domain.com.

I would appreciate any guidance or suggestions on how to effectively resolve this routing issue and ensure that the app-ads.txt file is correctly linked and accessible for Google AdMob verification.