How keywords meet custom pages

One intent per page#

Give every custom page a single job: one audience, one intent, one set of searches. A page serving both brand searchers and category explorers serves neither, because the proof each needs differs completely. When harvests surface a fresh cluster of converting terms with shared language, that cluster earns its own page rather than stretching an existing one. Discipline here pays twice: shoppers see matching proof and reporting stays readable per page.

Start from the Apple Ads hub for the family view, then use the discovery and brand split to decide which intents deserve dedicated pages first.

Relevance is the multiplier#

When page text and screenshots echo the search terms landing on them, tap through rises and conversion follows, since shoppers feel understood before they read a word. Write page copy around the cluster's language: the verbs searchers use, the outcomes they name, the doubts they voice. Screenshots should show the exact use case the terms imply, not generic product tours. Apple own custom product page docs set the creative frame; relevance fills it with meaning.

The relevancy guide details the signal, and CPP setup builds the pages that carry it.

Match types feed the mapping#

Exact terms map cleanly to dedicated pages, since each term's intent is known and the proof can mirror it precisely. Broad and Search Match surface fresh clusters worth harvesting into new pages once volume proves they convert, rather than on first sighting. Negatives protect the mapping by keeping stray intents off pages built for someone else. Review search term reports on a fixed rhythm and promote repeat converters into their own page and term set.

Use exact match for the control mapping, Search Match for discovery, and the harvesting guide for the promotion path.

Localised terms need localised pages#

A translated term set landing on an unlocalised page wastes its promise: the shopper searches in local language, then meets foreign proof. Pair localised keyword sets with localised pages carrying local faces, currency and use cases, prioritising markets by revenue behind the 91 market footprint. Remember product pages serve 90 markets, unavailable mainland China, so page investment follows reachable revenue. Native writers should own both term lists and page copy so language stays natural on both sides of the tap.

Coordinate with localised keyword thinking and the screenshots guide for matching frames.

Measure per page, prune per quarter#

Read each page on tap through and conversion against the default page, then tie results back to the term set that feeds it. Pages that never beat the default despite tuned terms face retirement, while winners earn broader traffic and fresh term harvests. Seasonal intent shifts deserve dated pages rather than edits to evergreen ones, so history stays clean. Ad variation reporting per page, as Apple own ad variation docs describe, shows which intent and proof combinations truly pay.

When page counts approach the 70 page ceiling, ask our team for a prune and prioritise review that keeps winners live.

HelloFresh style seasonal mapping#

Seasonal advertisers illustrate the mapping well: vendor write ups share directional examples such as HelloFresh style meal planning pushes where seasonal terms met seasonal pages and results moved with the calendar. Treat all such vendor figures as directional, never as promises for your account, yet copy the method: dated pages, matched terms, prompt retirement after the peak. Evergreen pages stay untouched while seasonal variants borrow their structure.

The seasonal playbook times the calendar, and creative reporting proves which seasonal pages earned a return berth.

Frequently asked questions#