LOCAL

Apple, Bing and in-car map listings

Use when everything has gone into Google and the other map surfaces still show details from three years ago.

non-google-map-profiles.md

Download .md

You are planning listings on the map platforms that are not Google. You cannot see any of them and you must not assert what a platform currently requires.

Canonical name, address, phone, hours and website: {{CANONICAL_DETAILS}}
Country we trade in: {{COUNTRY}}
What we found when we checked each platform: {{PLATFORMS_CHECKED}}
How customers find us, including devices and in-car navigation: {{CUSTOMER_DEVICES}}
Time available for this work: {{TIME_AVAILABLE}}

Produce:

1. A platform table: Platform, Status in {{PLATFORMS_CHECKED}}, How to claim it, How the claim is verified, Fields it wants that Google does not, Effort. Only list platforms that plausibly operate in {{COUNTRY}}.

2. A priority order argued from {{CUSTOMER_DEVICES}} rather than from platform size, with one line on what each platform feeds that a customer of ours would actually see.

3. A field mapping showing where each part of {{CANONICAL_DETAILS}} goes, and any platform where the correct entry differs from our canonical string.

4. A four week plan sized to {{TIME_AVAILABLE}}.

Rules:
- Mark [VERIFY] against any claim route, field or requirement you are not certain still exists. I will act on anything left unmarked.
- Do not assert which aggregator feeds which platform unless {{PLATFORMS_CHECKED}} shows it.
- Do not recommend a paid sync subscription without saying what happens to the listings when it lapses.
- No em dashes.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{CANONICAL_DETAILS}}
{{COUNTRY}}
{{PLATFORMS_CHECKED}}
{{CUSTOMER_DEVICES}}
{{TIME_AVAILABLE}}

Getting a better result

Check each platform on a device in the country you trade in. Desktop views and travel modes show different data.
Verify every [VERIFY] line yourself. Claim routes on these platforms change without announcement.
Do the platforms your customers actually use first, even where a bigger one is easier to claim.

Questions about this prompt

When is this worth the time?

When Google is in order and the other surfaces still show details from three years ago. Reach for it rather than a general citation plan, because map platforms have their own claim routes, their own verification and fields Google never asks for, and in car navigation pulls from them rather than from Google.

What do I need before I start?

A settled canonical name, address, phone, hours and website, the {{COUNTRY}} you trade in, what you actually saw when you checked each platform, and {{CUSTOMER_DEVICES}} including in car navigation. Check on a device in that country first, because desktop views and travel modes show different data and produce a status you cannot rely on.

What comes back?

A platform table with claim route, verification method and the extra fields each wants, a priority order argued from your customers rather than platform size, a field mapping against your canonical details, and a four week plan. The priority order is the useful part: the easiest platform to claim is rarely the one your customers use.

What is the mistake?

Acting on a [VERIFY] line without checking it. Claim routes on these platforms change without announcement, and an unmarked line only means the model was confident, not that it is current. If a paid sync subscription comes up, ask what happens to the listings when it lapses before signing anything.