fix: move Google-Ads.txt to templates (#2868)

* fix: move Google-Ads.txt to templates

* feat: implement Google Ads verification endpoint and move Google-Ads.txt to static files

---------

Co-authored-by: Benjamin Oni <onibenjo@gmail.com>

Author: petesfrench

Google-Ads.txt

@@ -0,0 +1 @@
+GooGhywoiu9839t543j0s7543uw1. Please Modify Admin access for user "mohamed.elmasry@canonical.com" in Google Ads account 404-765-5407 - Date 08/18/2026.

static/files/Google-Ads.txt

@@ -59,6 +59,7 @@
     build_knowledge_index,
     build_knowledge_category_index,
     get_knowledge_sections,
+    google_ads_verification,
 )
 from webapp.application import application_bp
 from webapp.canonical_cla.views import (
@@ -229,6 +230,7 @@ def home_sitemap():
 
 
 app.add_url_rule("/asset/<file_name>", view_func=json_asset_query)
+app.add_url_rule("/Google-Ads.txt", view_func=google_ads_verification)
 
 
 # OpenStack resources blog section

webapp/app.py

@@ -558,3 +558,15 @@ def knowledge_category_index():
         )
 
     return knowledge_category_index
+
+
+def google_ads_verification():
+    """
+    Serve the Google Ads account-access verification token from the domain
+    root. Google fetches /Google-Ads.txt directly and does not reliably
+    follow redirects, so this is served in place rather than through a
+    redirects.yaml entry like robots.txt uses.
+    """
+    return flask.send_from_directory(
+        flask.current_app.static_folder, "files/Google-Ads.txt"
+    )