Google will say why a profile edit was rejected

On November 2, 2026, Google added a way for software that uses the Business Profile API to see what happened to an edit. The note is in the API updates log under that date: edit status for locations and attributes, in the v1alpha version of the Business Information API. The methods named are locations.getExtended and locations.attributes.getExtended. Google says partners can retrieve the merchant's view, the consumer's view, the stage of each field's latest edit, where the edit came from, and the policy reason if an edit was rejected.

This is not a new screen Google announced for every owner inside the Business Profile app. It is an API, on the alpha channel, documented for developers. A dentist will not see a new "rejection reason" button appear on November 2 because of this note. The change matters because the tools and agencies that edit listings through Google's API can now read a status instead of guessing. The full behavior is in Check edit status for locations and attributes.

Two versions of the same listing

Google's documentation says an edit made through the API or through the Business Profile interface goes through moderation before it shows on Search and Maps. It also says Google may change details based on user reports or licensed data. The new calls return three ideas at once: what the business last submitted, what customers currently see, and a record for each top-level field.

The examples of fields Google gives are the name (title), phone numbers, website, storefront address, and regular hours. Keys are the top-level field, not a nested piece of it. Attributes are a second call. Google's sample responses include a wheelchair-accessible entrance and a Wi-Fi setting, with the public value sometimes different from the value the business sent. Those samples are documentation, not a news report about a real shop.

The gap is the thing owners already feel. You set Saturday hours and Maps still shows Friday. You add a promotional phrase to the business name and customers never see it. Until now, a person staring at the two screens could not tell whether the edit was waiting, blocked, or overwritten. The API response is built to answer that.

The stages Google defined

Google's edit-status page lists six lifecycle values and a recommended next step for each.

Accepted means the edit was approved and can be shown. Google says nothing further is required.

Pending means the edit is in review and is not on the public listing yet. Google's instruction is to wait, and not to send the same edit again while it is pending.

Rejected means the edit was not accepted. The response can include a policy-violation reason. Google says to fix that problem and submit a new update.

Updated by Google means the public value was changed by Google, for example from user reports or outside data, and it differs from what the business submitted. Google says to review the public value and either accept it or override it.

Draft means the edit is saved but not live, including on a location that is not verified. Google says to finish verification.

Unspecified means Google does not have a stage to report.

The source field says whether the edit came through the API or through the Business Profile website or app. Google also has an unspecified source.

Why an edit gets rejected

When the stage is rejected, Google says the reason is a policy-violation value. The documentation groups examples. It does not present them as the full list, and it points to a PolicyViolation reference for every value.

Profile and account examples include a suspended account, a location that is not eligible, a location that still needs verification, and a PO box. Editing-restriction examples include illegal hours edits, an identity change, and a geographic move. Content examples include misrepresentation, off-topic text, personal information, gibberish, obscenity, and generic low-quality text.

A name like "Best HVAC in Dallas" is the kind of wording that runs into misrepresentation rules owners already live with. The Business Profile policies say content has to represent the location and follow Google's rules, and that Google can restrict content or the profile when it does not. The November 2 API does not create that rule. It gives software a specific reason code when an edit fails the rule.

What to do if you do not have API access

Compare the public Maps listing with what you believe you saved. If they differ, do not click the same edit in a loop. Google's pending state exists so repeated identical edits are not the next step while a review is open. If the public hours or phone number changed and you did not change them, that matches the "updated by Google" stage: someone or some data source moved the field. Check the live listing before you argue with a screenshot.

If the profile was never verified, Google's draft stage says the listing is not live until verification is done. Hours you typed into an unverified profile are not a promise that customers can see them.

Reviews are a different system. This November 2 note is about location fields and attributes, not about the text of a customer review. Asking for reviews still belongs to the review policy, which the review guide covers, along with the review link and QR code tool. The listing itself, including name, hours, and service area, is the subject of how to rank on Google Maps. A schema generator helps the website say the same facts the profile says. An HVAC company that shows one set of hours on the site and another on Maps is the situation this API was built to explain, once a tool can read it.

Until your software shows the new status, the owner-facing habit is the same comparison the API encodes: what you submitted, what a customer sees, and whether the difference is a wait, a policy block, or a change Google made.