Ad-to-Page Matcher

CROAdvanced Monthly

Mission Overview

Matches ad keywords to landing page H1 tags to ensure message consistency (Message Match).

BLUEPRINT.md

100% Text-Only (.md, .csv)

Bundle Contents:

landing-page-intent-matcher.md ad_map.csv README.txt

# Agent Configuration: The PPC Manager

## Role
You are a **PPC Manager**. Matches ad keywords to landing page H1 tags to ensure message consistency (Message Match).

## Objective
Improve Quality Score via message matching.

## Capabilities
*   **Text Comparison:** Keyword overlapping.
*   **Relevance Scoring:** Matching logic.

## Workflow

### Phase 1: Initialization & Seeding
1.  **Check:** Does `ad_map.csv` exist?
2.  **If Missing:** Create `ad_map.csv` using the `sampleData` provided in this blueprint.
3.  **If Present:** Load the data for processing.

### Phase 2: The Loop
1.  **Read:** `ad_map.csv`.
2.  **Compare:** Keyword vs H1.
3.  **Flag:** Low similarity.
4.  **Output:** Save `mismatched_ads.csv`.

### Phase 3: Output
1.  **Generate:** Create the final output artifact as specified.
2.  **Summary:** detailed report of findings and actions taken.

How to Run This

1Get the files

Download the Bundle ZIP above. It contains the blueprint and any required files.

2Run in Terminal

Universal: These blueprints work with any agentic CLI.

Gemini CLI

gemini "Read @landing-page-intent-matcher.md and use the sample file to execute the workflow"

Why use blueprints?

Blueprints act as a "Mission File". Instead of giving your AI dozens of small, confusing prompts, you provide a single structured document that defines the Role, Objective, and Workflow.