Runs your top-spending landing pages through Google PageSpeed Insights (mobile) and flags the slow ones — page speed is a Quality Score component and a conversion killer.
by Google (original concept), Chiliad (rewrite)·web.archive.org/web/20231003054446/https://developers.google.com/google-ads/scripts/docs/solutions/mobile-pagespeed
Monitors your account for unexpected performance deviations by comparing today's stats against historical averages for the same weekday. Sends an alert email when impressions, clicks, conversions, or cost deviate beyond configurable thresholds.
One 0-100 score for the whole account, built from seven objective checks — tracking flatlines, disapprovals, serving status, budget losses, negative coverage and query hygiene — with the deduction breakdown as your fix list.
Finds the structural gaps that stop ad groups from serving: ad groups without active ads, without an RSA, without keywords, keyword-stuffed themes, and multi-RSA ad groups.
Generates a daily at-a-glance performance overview of your entire Google Ads account. Writes prior-day stats to a Google Sheet with running history and optionally emails a formatted comparison of yesterday vs. two days ago vs. one week ago.
Generates a Google Spreadsheet with ad performance stats segmented by headline and final URL, including distribution charts. Covers all ad types and optionally emails the report link weekly.
Maps every campaign's ad schedule and flags forgotten narrow serving windows, stale schedule bid modifiers that Smart Bidding ignores, and (optionally) campaigns running 24/7.
PageSpeed Insights Audit picks your top landing pages by ad spend and runs each through Google's PageSpeed Insights API with the mobile strategy, reporting the performance score and Largest Contentful Paint per page. Pages below your score threshold are flagged and emailed. Testing by spend means the pages costing you the most money get tested first — a slow page with real budget behind it is a compounding loss.
| Variable | Default |
|---|---|
API_KEY | (empty) |
DATE_RANGE | LAST_30_DAYS |
PAGES_TO_TEST | 10 |
SCORE_ALERT | 50 |
EMAIL_ADDRESS | (empty) |
Testing 10 top landing pages via PageSpeed Insights (mobile)... https://example.com/bestseller score: 78/100 LCP: 2.1 s spend: 3105.20 https://example.com/category/shoes score: 41/100 LCP: 4.8 s spend: 1840.10 === PageSpeed Audit: 1 of 10 pages below score 50 === Email sent to you@example.com
Lab scores vary run to run — treat below-40 as definitely slow, 40-60 as worth investigating, and trends as more meaningful than single runs. Each PSI call takes 10-20 seconds, so keep PAGES_TO_TEST within the script's 30-minute limit (10-30 pages is safe).