# QA Evidence Standard for Local Listing Changes

Canonical: https://locallistingsmanagement.co/local-listing-change-qa-evidence
Published: 2026-09-16
Updated: 2026-09-16
Author: Asmit Choudhary

The proof to keep after publishing local listing changes: public place-card checks, timestamps, and tickets so submitted never equals done.

A **local listing change QA evidence standard** is the proof you keep after publishing NAP, hours, category, or status updates — public place-card checks, timestamps, and ticket links — so **local listing management** is verifiable, not "submitted equals done." Definition hub: [What is local listing management?](/what-is-local-listing-management).

This page defines the evidence bar for local profile changes. It is not a software product review.

## Why "submitted" is not done

Publishers can delay, reject, or partially apply edits. Aggregators redistribute old NAP. Teams that stop at the vendor dashboard leave customers on stale maps cards. Google's accuracy guidance in [Tips to improve your local ranking](https://support.google.com/business/answer/7091) and [representation guidelines](https://support.google.com/business/answer/3038177) only help if the **public** result matches the real world.

## Minimum evidence per material change

| Change type | Evidence to attach | Where to check |
| --- | --- | --- |
| Hours / special hours | Screenshot of public hours panel + date | Google/Apple/Bing place cards ([hours help](https://support.google.com/business/answer/15300403)) |
| NAP / suite / phone | Side-by-side source vs public card | Tier 1 publishers |
| Category | Public category string vs approved taxonomy | Google + major maps |
| Temporary / permanent closed | Public status label | Tier 1 + high-impact verticals |
| Duplicate cleanup | Before/after search screenshots | Maps search for old address |

Store evidence in the ticket or change log with location ID, editor name, and UTC timestamp.

## Suggested QA workflow

1. Edit from the approved source of truth only.
2. Publish to Tier 1 surfaces first ([publisher priority](/local-listing-management-publisher-priority)).
3. Wait for the publisher's normal propagation window; re-check the next business day.
4. Capture public proof; file exceptions if the card still mismatches.
5. Only then update secondary directories or aggregators.

## Pass / fail examples

| Result | Verdict |
| --- | --- |
| Vendor UI shows new hours; public Google card still old | **Fail** — keep ticket open |
| Public Google/Apple/Bing match source; Yelp pending | **Pass Tier 1** — track secondary separately |
| Screenshot missing location ID / date | **Fail evidence** — redo capture |

## Related reading (local cluster)

- [What is local listing management?](/what-is-local-listing-management)
- [Seasonal hours change control for local profiles](/local-listing-hours-change-control)
- [Open, move, and close playbook for local listings](/local-listing-open-move-close)
- [Local listing management RACI for multi-location teams](/local-listing-management-raci)
- Sibling term: [What is business listing management?](/what-is-business-listing-management)

## Frequently asked questions

### Do we need screenshots for every tiny punctuation fix?

No. Reserve the full evidence pack for material changes: phone, suite, hours, status, primary category, and duplicate work.

### Is this only for Google Business Profile?

No. **Local listing management** QA covers the priority local publishers your customers use for nearby discovery, usually including Apple Maps and Bing Places.