Landing Pages

The Landing Pages node connects paid search performance to the final URLs users land on after clicking your ads.

​

When to use this node

Use the Landing Pages node for tasks such as:

• Prioritize Profound optimization: identify which landing pages are actively receiving Google Ads traffic, then prioritize Profound optimization work on those pages
• Find visibility gaps: surface high-spend or high-conversion landing pages with weak AI visibility, citation coverage, or answer-engine performance
• Audit destination URLs: check whether ad traffic is going to the right pages, especially if campaigns have destination URL sprawl
• Spot content mismatches: compare landing page messaging against the keywords and ad groups driving traffic to identify gaps
• Feed Profound workflows: send landing pages into downstream Agent nodes for content refreshes, page analysis, or competitive visibility checks

​

Node configuration

​

Google Integration (required)

Select a previously connected Google account, or click + Add integration and follow the prompts to connect one. This is a one-time setup. Once you add an integration, it’s available in all future sessions until you remove it in Profound Settings > Integrations.

​

Google Ads Account (required)

Select the Google Ads customer account from the dropdown. The picker handles both Manager accounts and sub-account selection.

​

Campaigns

Select the ad campaigns from the dropdown. To include every active campaign, leave the field empty.

​

Ad Groups

Select the ad groups from the dropdown. To include every ad group within selected campaigns, leave the field empty. To see the ad group options in the dropdown, select at least one campaign in the Campaigns field.

​

Date Range (required)

Select the date range to pull search term performance over. Choose from available presets (today, yesterday, last 7 days, and others) or set a custom range.

​

Output Fields

Select the fields to include in the output. The options include metrics and campaign details, such as Impressions, Clicks, Conversions, Campaign Type, and Bid Strategy Type. To return output unfiltered, leave this field empty.

​

Output label

Enter a descriptive label for this step’s output, for example landing_pages_data_past_month. The label becomes the variable name you reference in later nodes.

​

Output

The node outputs landing page data in JSON format, including:

• Campaign and ad group attribution
• Performance metrics: clicks, conversions, and others
• Page-experience metrics: mobile-friendly clicks %, speed score, and valid AMP clicks %

Pass the output to:

• Prompt LLM node to analyze underperforming pages and generate optimization recommendations
• Web Page Scrape node to scrape content from flagged pages for deeper LLM analysis
• Slack to deliver the optimization report to your team

​

Example usage: Weekly paid landing page health report

Set up an Agent to surface landing pages with page-experience problems or poor conversion efficiency, and post a weekly digest to your paid search channel. 1. Landing Pages node

• Select your Google Integration and set Google Ads Account to your Google Ads account
• Set Date Range to Last 7 days
• Set Campaigns, Ad Groups, and Output Fields filters as needed
• Set Output label to landing_page_data

2. Prompt LLM node

• Enter the prompt:
  You are a paid search analyst. Review this landing page data:
  {{landing_page_data}}:
  
  - Identify pages with speed score below 50, poor mobile-friendly 
  rate, or high spend but low conversions.
  - Summarize optimization priorities, ordered by estimated impact.
  
  Keep the report short and actionable.
  

  See all 9 lines
• Set Output label to landing_page_report

3. Slack node

• Select the Slack workspace and channel to receive updates
• Input the message text and use the landing_page_report variable in the Message field

Schedule the Agent to run weekly.

​

Best practices

​

Scope by campaign and ad group

Pulling all landing page data from all campaigns and ad groups at once can return an unmanageably large dataset. Use the built-in campaign and ad group filtering to scope results before passing them to subsequent nodes. Use List Campaigns node to discover the active campaign set first, map campaign names to IDs, or fan out the workflow across every campaign dynamically.

​

Pair with Web Page Scrape node

Scraping the actual content of flagged pages using Web Page Scrape node gives the LLM what it needs to generate specific, actionable recommendations rather than generic ones.