Documentation
Page Health is Adnine's daily diagnostic for the landing pages behind your Google Ads. It combines 404 and redirect detection, keyword presence audits, and custom text match checks, all prioritized by impression volume so you fix the pages that affect the most traffic first. Instead of discovering a broken destination after budget has run, Page Health surfaces the problem before users and wasted spend pile up.
- Best for
- Landing-page reliability, relevance, and compliance checks
- Core audits
- 404 and redirect, keyword presence, and text match
- Crawl methods
- Fast HTTP checks plus browser simulation
- Refresh cadence
- Automated daily audit refresh
- Prioritization
- URL, campaign, ad group, account, and impressions
#What Page Health checks
Page Health runs three distinct audits against the landing pages connected to your Google Ads account. Each audit answers a different question: Is the page reachable? Does the page match the keywords sending traffic there? Is the required text still visible on the page?
The three audits at a glance
Each audit targets a different failure mode and points to a different owner for the fix.
| Audit | What it detects | Typical fix |
|---|---|---|
| 404 and redirect check | Landing pages that return a 404 not-found response, redirect to a different URL, or fail in a real browser session. | Fix the final URL, restore the page, update tracking, pause traffic, or route to the correct destination. |
| Keyword presence audit | Active Google Ads keywords that do not appear on their associated landing pages. | Update page copy, move the keyword to a better-matched page, or tighten the ad-group-to-page pairing. |
| Text match audit | Required snippets (offers, disclaimers, or other expected copy) that are missing from important pages. | Add the missing text, update the expected snippet, or correct which page the rule applies to. |
All three audits run automatically every day and results are attached to campaign, ad group, account, and impression context. Every finding already tells you how much traffic is affected and where it comes from, so you can sort by impact rather than by issue count.
#Who should use it
Page Health is useful for any role that owns or monitors Google Ads performance: a paid search specialist reviewing account health, a client services manager preparing a weekly review, or a web team verifying that a CMS release did not break live destinations.
Common use cases
Pre-launch QA
Confirm that every landing page is live, contains the correct keywords, and shows required promotional or legal copy before a campaign goes live.
Post-deploy verification
After a site migration, template update, or CMS edit, use Page Health to confirm no live pages broke, redirected unexpectedly, or dropped required text.
Ongoing account hygiene
Use daily results to catch regressions as they appear: out-of-stock pages, tracking redirects, or content changes that create relevance gaps.
Spend protection
Identify high-impression broken or redirected pages and pause or reroute traffic before budget continues to flow to a destination users cannot convert on.
#How crawling works
Page Health connects to your Google Ads account and collects landing page URLs with their associated campaign, ad group, and impression data. It then crawls each URL using a two-method approach: a fast HTTP check for speed, and a browser simulation layer that catches failures hidden behind JavaScript rendering, client-side redirects, or dynamic page states.
- Pull URLs and context Page Health fetches all active landing pages from your connected Google Ads account, along with their campaign, ad group, and impression data.
- Run the fast HTTP check A lightweight crawler visits each URL and records the response status, any redirects, and the final destination. This pass is designed for speed across large account structures.
- Run browser simulation A second pass using browser emulation visits pages that require JavaScript rendering, following client-side redirects and rendering the page as a user would see it. This catches failures that the HTTP check alone would miss.
- Check keyword presence For pages with active keywords, the crawled content is compared against the keyword list for that page. Keywords that do not appear in the rendered page content are flagged.
- Verify required text Any text match rules you have configured are evaluated against the crawled page content. Pages that are missing the required snippets are flagged with the matched rule and impression context.
- Store and prioritize results All findings are saved with URL, campaign, ad group, account, and impression context. Results appear in the dashboard, in alerts, and in logs for review and filtering.
#Issue reference
The table below covers every issue type Page Health can surface. Use it as a quick reference when reviewing results: the meaning column explains what the finding actually represents, and the action column gives the most common next step.
Page Health issue types
| Issue | Meaning | Recommended action |
|---|---|---|
| 404 not found | The landing page URL returns a page-not-found response. Users clicking the ad land on a broken destination. | Fix the URL in the ad or keyword, restore the page, or pause the affected traffic until the page is live. |
| Unexpected redirect | The URL redirects to a different destination than the one attached to the ad. The final page may not match the ad promise, keyword intent, or tracking setup. | Confirm whether the redirect is intentional. Update the final URL in the ad, fix the tracking template, or route to the correct destination. |
| JavaScript-rendered failure | The page appears healthy under a basic HTTP check but shows a broken or unusable state once fully rendered in a browser: a client-side error, blank section, or blocked content. | Open the page in a browser with the same conditions and confirm the user experience. Fix the rendering issue or update the landing page assignment. |
| Possible out-of-stock or unavailable product (crawl-inferred) | The page loads, but the product or offer being advertised appears unavailable, sold out, or hidden. Users cannot complete the intended conversion. | Pause traffic to the page, redirect to a substitute or category page, or update the ad to reflect current availability. |
| Keyword missing from page | An active keyword does not appear in the crawled content of its associated landing page. The page may technically load but lacks the relevance signal tied to the keyword. | Improve the page copy to reflect the keyword theme, move the keyword to a better-matched page, or tighten the ad group and page pairing. |
| Required text missing | A text snippet you configured as required (such as an offer, disclaimer, or compliance statement) is absent from the crawled page content. | Restore the missing text, update the snippet to reflect the current wording, or review whether a template change removed it. |
#Keyword presence in detail
The keyword presence audit collects every active keyword from your Google Ads account, maps each to its associated landing page, crawls the rendered page content, and flags any keyword that does not appear on the page. The goal is not word-for-word matching across every headline. It is identifying cases where the topic your ads are buying traffic for has no visible representation on the page users land on.
How to read keyword presence results
| Result | What it suggests | Review question |
|---|---|---|
| Keyword found on page | The page content contains the keyword or a closely related phrase. Basic content alignment is in place. | Does the page also match the search intent, the offer, and the conversion path the user expects? |
| Keyword missing from page | The ad is sending traffic to a page that does not visibly support the keyword theme. This creates a relevance gap that can weaken Quality Score and reduce conversion confidence. | Should the keyword point to a better page, or should the page copy be updated to reflect the keyword theme? |
| High-impression missing keyword | The relevance gap affects a large volume of traffic and deserves faster review. The quality and cost impact is proportionally larger. | Can fixing this relevance gap improve Quality Score, lower CPC, or improve conversion rate for this traffic segment? |
| Recurring issue across ad groups | The same page or keyword theme is misaligned across multiple parts of the account. This may indicate a structural problem rather than a one-off copy issue. | Is this a landing-page issue, a keyword targeting issue, or a campaign structure issue that needs a broader fix? |
#Text match checks
Text match checks let you define snippets that must appear on specific landing pages. Use them for promotional claims, legal disclaimers, financing language, delivery promises, or any copy that has to be visible for operational, compliance, or conversion reasons. Page Health crawls the pages and flags wherever the expected text is absent.
The audit prioritizes pages with the most impressions and uses a two-pass system to balance crawl speed against accuracy, which is useful for accounts with large numbers of landing pages.
What to check with text match rules
| Text type | Use it for | Action when missing |
|---|---|---|
| Offer copy | Promotions, discounts, trial messaging, bundles, or sale claims referenced in active ads. | Add the offer back to the page or remove the claim from the ad to avoid a mismatch. |
| Compliance text | Required disclaimers, pricing conditions, legal language, or regulated copy that must appear on the page. | Restore the text immediately or hold traffic until the page is compliant. |
| Product or service language | Key product names, service categories, availability claims, or feature promises the ad promotes. | Route traffic to the correct page or update the destination content to reflect what the ad says. |
| Trust and conversion copy | Guarantees, delivery promises, certification claims, or other text users expect to see before converting. | Check whether a template or CMS change removed the copy and restore it. |
- Define the snippet Choose text specific enough to confirm the required message is present, but not so brittle that a minor wording change creates constant noise.
- Choose the page set Apply the check to the landing pages where the claim, disclaimer, or offer must be visible, not to every page in the account.
- Review missing matches Open the flagged page, confirm whether the text is genuinely absent, and decide whether the page or the expected snippet needs to change.
- Monitor after updates Use the next daily refresh to confirm that CMS edits, template changes, or product-page updates did not remove the required copy again.
#Reading and filtering results
Every Page Health result includes enough Google Ads context to make the finding immediately actionable. The fields below appear in dashboards, logs, and alert notifications. Use them to move from a full crawl result set to the specific rows that need attention today.
Result fields and how to use them
| Field | What it tells you | How to use it |
|---|---|---|
| Landing page URL | The destination being crawled and validated. | Open the URL, inspect the final destination, and confirm whether the ad should still send traffic there. |
| Issue type | Whether the row is about a 404, redirect, keyword presence gap, text match failure, or availability problem. | Route the fix to the right owner: web team for broken URLs, paid search for relevance gaps, content or legal for missing text. |
| Campaign and ad group | Where the affected traffic comes from in Google Ads. | Prioritize fixes that affect active, high-spend, or strategically important parts of the account. |
| Impressions | How much ad visibility is attached to the flagged URL or keyword. | Sort descending to work high-impact issues first. A 404 with 50 impressions matters less than one with 50,000. |
| Redirect destination | The final URL users land on after the original URL redirects, when detected. | Confirm the final page matches the ad promise, keyword intent, tracking setup, and conversion goal. |
| Account | Which connected Google Ads account the result belongs to. | Use this before exporting, assigning fixes, or discussing results with a client or team. |
Recommended dashboard filters
| Filter | Use it to find | Good starting view |
|---|---|---|
| Issue type = 404 or redirect | Pages that are broken or sending users somewhere unexpected. | Start here: these are the clearest sources of wasted spend. |
| Impressions descending | The highest-traffic problems in the full result set. | Sort this way for any planning or prioritization session. |
| Campaign | Problems tied to a specific campaign, launch, or seasonal effort. | Filter to active campaigns with current spend before a review call. |
| URL | Repeated failures on the same page template, product category, or tracking URL. | Group by URL to spot a single page causing many account rows. |
| Account | Issues scoped to one connected Google Ads account. | Use before exporting or assigning results to a client or team. |
#Review workflow
Use the following sequence when processing Page Health results during a routine account review or after a flagged alert. The steps move from highest-impact issues down to relevance and content checks.
- Start with broken and redirected pages Review 404, unavailable, out-of-stock, and unexpected redirect results first. These are usually the clearest source of immediate wasted spend and lost conversions.
- Sort by impressions Within each issue type, sort by impressions descending so the highest-traffic problems appear first. A high-impression 404 is worth fixing before ten low-impression keyword gaps.
- Open the live destination Check both the original ad URL and the final page a user lands on after redirects or JavaScript rendering. The final destination is what matters for users and Quality Score.
- Assign the fix to the right owner Send technical URL failures to the web team, relevance gaps to paid search or content owners, and missing required text to whoever owns the claim or the compliance rule.
- Update ads, pages, or routing Fix the URL, restore the page, swap to a better landing page, update keyword groupings, or pause spend while the fix is in progress.
- Confirm on the next daily refresh Because Page Health refreshes every day, use the next result update to confirm the issue has cleared. Do not mark a fix as done until the audit confirms the page is healthy.
#Limits and known constraints
Page Health is thorough, but there are a few scenarios where results need extra interpretation.
Edge cases and how to handle them
| Scenario | What happens | Recommended approach |
|---|---|---|
| Intentional redirect | A URL that intentionally redirects (for example, a tracking template or vanity URL) may be flagged as a redirect issue. | Confirm the final destination matches the ad promise and tracking requirements. If it does, treat the result as informational and note it in your workflow. |
| Login-gated pages | Pages behind authentication walls cannot be fully crawled. The crawler may see a login screen rather than the intended content. | Verify gated pages manually or ensure ads send unauthenticated users to a publicly accessible landing page. |
| Very new pages | Pages published shortly before the daily crawl may not yet have had their first audit pass. | Wait for the next daily refresh to appear in results. Do not assume a missing result means the page is healthy. |
| Keyword match type nuance | Broad or phrase match keywords may reach pages where the exact keyword phrase does not appear because the landing page covers a broader topic. | Evaluate missing-keyword results in context. A broad match keyword that converts well on its landing page may not need a copy change. |
| Dynamic or personalized content | Pages that show different content based on user session, cookie, or geo context may not reflect what a typical user sees during the crawl. | Supplement Page Health results with manual spot checks for known dynamic or personalized destinations. |
#Frequently asked questions
How often does Page Health run?
Does Page Health crawl every URL every day?
Can I use Page Health on accounts with thousands of landing pages?
A keyword shows as missing but the page clearly covers the topic. Should I change the page?
What counts as a redirect issue?
How specific should a text match snippet be?
Does Page Health make any changes to my Google Ads campaigns?
How do I know which issues are most urgent?
#Best practices
- Run a Page Health check before major campaign launches, site migrations, sale events, and tracking changes.
- Review high-impression 404 and redirect issues before lower-volume content or relevance mismatches.
- Treat redirects as intentional only after confirming the final URL, offer, tracking, and conversion path are all correct.
- Use keyword presence results to improve relevance naturally, not to add forced or awkward keyword repetition to pages.
- Keep text match snippets stable and update them when legal, promotional, or compliance copy changes on purpose.
- Group recurring URL issues by page template so a single web team fix can clear many Page Health rows at once.
- Set up alerts for urgent failures like 404s and use daily dashboard review for keyword and text match monitoring.
- After fixing a page, wait for the next daily refresh to confirm the issue is resolved before closing the task.