Skip to main content
FHAVI

Research · Merchant Center

What to write in a review request — and where there is nowhere to write it

Most Merchant Center re-review flows take a request and a status, not an essay. Where free text is accepted, what belongs in it, and why the document you keep offline still decides the outcome.

3 min read

In brief

  • Many re-review flows accept a request with no free-text field at all — so the written case you prepare is often evidence for yourself, not a message to Google.
  • Where text is accepted, it is read as a claim to verify: dates, links and specifics, not explanation or apology.
  • The document that matters either way is the change record — what was wrong, what changed, when — because that is what makes the account state defensible.

First, the uncomfortable part

A lot of advice on this subject assumes a text box that does not always exist. Depending on the flow and the reason, requesting review can be a button and a status, sometimes with a short description field, sometimes with a document upload, sometimes with nothing. If you have prepared a two-page letter and the interface offers one button, the letter is not going to be read — and believing otherwise leads people to resubmit repeatedly, which is the actual damage.

So the first question is not 'what do I write'. It is 'what does this flow accept'. Open it, look, and only then decide what to prepare.

  • Request only — a button, a confirmation, a status. Your case exists only as the state of the store when it is reviewed.
  • Request with a short field — a few sentences, sometimes character-limited. Specifics win; narrative loses.
  • Request with documents — an upload path, usually for eligibility or verification, where a correctly formatted document matters more than any prose.

Where text is accepted, what belongs in it

Assume a reviewer reads it once, quickly, looking for something to check. Every sentence should either name a fact or point at something they can open.

  1. 1

    One sentence on what was wrong

    The specific finding, in Google's own words, and the date. Not 'we had some issues with our feed'.

  2. 2

    One sentence per fix, with a date

    What changed, where, and when it went live. Three bullet lines beat three paragraphs.

  3. 3

    Links, not descriptions

    The policy page, a product URL, the checkout. A reviewer should be able to verify each claim in one click.

  4. 4

    What is outside your control, stated plainly

    If a supplier's data caused it, say so and say what you changed in your process. Do not blame and do not omit.

  5. 5

    Nothing about intent, effort or competitors

    None of it is checkable, and all of it takes space from the facts.

Length

If a field allows a paragraph, write a paragraph. Long submissions are not more persuasive; they are just more likely to bury the one date that would have carried the case.

The document to keep whether or not there is a text box

Write the change record anyway: finding, cause, fix, date, verification. Keep it with the account health log. It does three things a submission cannot — it forces you to establish that the cause is actually fixed before you request anything, it gives you the material for the next problem, and it stops you resubmitting an unchanged store, which is the most common way a recoverable suspension becomes a pattern.

  • Do not request review until every line in the record has a date and a verification.
  • Do not request twice within the same store state. If nothing changed, the answer will not change.
  • Keep rejected requests in the record with their dates. The pattern is the argument you are trying not to create.

Find out what the flow accepts before you write anything. Where there is a field, fill it with dates and links. Where there is not, the only submission you have is the state of the store — which is why the change record is the document that actually decides the outcome.

Questions

Asked about this directly

Is there always a place to explain?
No. Several re-review flows are a request and a status with no free text. Confirm what the interface accepts before preparing anything, and let the state of the store carry the case where there is nowhere to write.
Should I write about how much this has cost me?
No. Cost, urgency and frustration are not verifiable and not part of the policy question. They consume the limited space that should carry dates and links.
Do documents help?
For eligibility and verification flows, a correct document is often the entire request. For policy findings, documents rarely substitute for a fixed store — the store is the evidence.

Keep reading

Other pieces in the library

All research

Numbers first, promises second

Send your store and we will tell you which of these failure modes is already happening — before you pay for a fix.

Prefer email? Write to md@fhavi.com