Local and Press

Local measures location presence and customer-feedback workflows. Press manages an approved release from drafting through a provider submission and then connects placements to later crawler and citation evidence.

Local: add a business location

1. Open Local · GBP.
2. Add the business name, canonical address, phone, site, category, and coordinates.
3. Connect Google Business Profile when the platform credentials and Google quota are available.
4. Review the profile completeness and directory consistency audits.

Tailwin audits consistency; it does not resell an automated directory push-sync network.

Local rank grid

1. Select the location, keyword, center coordinate, grid size, and spacing.
2. Confirm the point count and expected metered nature of the scan.
3. Run the grid.
4. Read the map of pins. Each pin is a separate check at that latitude and longitude, out to the edge radius. Heatmap and pin views show the same points.
5. Play the briefing. It uses the stored average, the pins where the business is missing, and the names that show up most often. Sharpen and play rewrites that paragraph for speech and does not add ranks.
6. Compare with a later grid rather than treating one heatmap as a trend.

The grid uses DataForSEO Google Maps results and retains the resulting observations. Mock mode can produce representative development data; it must never be presented as a live customer measurement.

Area questions

1. Enter a seed keyword for the location.
2. Preview the probe list: the seed plus each letter, and question stems in the location city.
3. Collect phrases. That step is metered, cached for 12 hours, and stored as an observation. If the rail is not configured, Tailwin shows the probes and does not invent phrases.
4. Track the open phrases you want. They join the site query list, so the next collection counts them as covered and the rank grid can measure them.

Review-request campaign

1. Confirm the location’s public review destination.
2. Select or edit the email template.
3. Import only recipients the business is allowed to contact.
4. Review the send list and throttle.
5. Send and monitor delivery and landing-page activity.

SMS is not part of the current workflow. Do not imply that it was sent. Do not use selective routing to suppress negative feedback in a way that violates platform policy.

Press campaign lifecycle

1. Create the campaign and draft the release.
2. Edit factual claims, quotes, contacts, dates, and links.
3. Complete approval.
4. Select the explicitly available provider and tier.
5. Review the wholesale/retail terms and submit with a deliberate human action.
6. Monitor the provider status and imported placement URLs.
7. Review later crawler fetches and AI citations connected to those placements.

The repository implements PRNow and Pitchwire because they had usable publish contracts during the integration audit. Availability still depends on a configured key, funded account, and live provider response.

Status language

• Draft: no paid submission has happened.
• Approved: editorial approval exists; it is not yet proof of vendor acceptance.
• Submitted: the provider accepted a request or order.
• Distributed: the provider reports completion under its contract.
• Placement: a real URL was returned or verified.
• Cited: a later measured AI answer cited a placement.

Never convert “submitted” into “distributed” or create placeholder placement URLs. A provider outage or zero-credit account should remain an explicit failure.