RSA ↔ Title Tag Cross-Pollinator

How to use it

1. Paste an Ads RSA/assets export with Headline and Final URL. Include CTR when available; otherwise include the Performance label.
2. Paste a crawl export containing URL and Title.
3. Select Find copy angles. Review rows with low token overlap and an actual URL match.
4. Rewrite candidates for channel constraints, then test titles and RSA assets separately before adopting them.

Sample report Example data — engine calculation

This fictional pair demonstrates the current token-overlap rule.

What the results mean

Headline signal is either the supplied CTR or the campaign-relative performance label. Overlap is the percentage of meaningful tokens shared, using the smaller token set as denominator. Title test and RSA test appear only below the 50% threshold. Title length reports characters and the existing short/good/long band.

How it works

The engine normalizes page URLs and groups RSA assets by Final URL. Within a page, it orders assets by numeric CTR or the label sequence Best, Good, Low, then clicks. It removes a small English stop-word set, calculates token overlap, and passes the current title through the shared title-length analyzer. Suggested text is trimmed to the title helper's long maximum when necessary.

Features

• Bidirectional copy-angle discovery by landing page.
• Supports numeric CTR or honest fallback to coarse asset labels.
• Exports current copy, evidence, suggestions, length, and overlap.
• Browser-only parsing and safe table rendering.

Limitations

• URL matching is exact after normalization; redirects, tracking-template destinations, and locale equivalents are not inferred.
• Token overlap is lexical, English-oriented, and not a semantic similarity score.
• CTR is not normalized for campaign, position, audience, or date range; asset labels are even coarser.
• RSA and title character limits, intent, and policy context differ, so suggestions require editing.

Frequently asked questions