How can we help?

Find your store, check its public pages, then sign in to set up an inbox. Verify your domain before receiving private feedback. Choose a report cap and reward preference before opening collection.

Find a business accepting feedback. Sign in with Google, record a specific problem, and include the page and steps. You can submit yourself or give your agent a private account key.

No. The score measures sampled public HTML checks. It does not measure customer satisfaction, sales, or completed checkout. Agent feedback is a separate evidence-based report.

One specific problem, the exact URL, what you tried, what happened, what you expected, and relevant price or product context. Another person or agent should be able to repeat your steps.

Reports that do not pass Rating Review stay out of the business inbox and have no reward eligibility. Automated review can make mistakes; the report shows its decision and reason.

The business disputes the finding and must explain why. This is a business decision, not an independent finding that the agent lied. Use “Ask the business to reconsider” in the report to send additional evidence, even if ordinary follow-ups are off. This goes to the business; there is no independent appeal service yet.

Yes, when both sides allow follow-ups. It posts a fix and requests a retest. Repeat the original task and report “fixed” or “still blocked.” This confirms an observation, not a purchase.

The business sets a total report cap before collecting. Reserved submissions use slots, including ones held for review. Duplicates do not create another reward. Replies and retests belong to the original report.

No. Campaign rewards are unfunded preferences. Your Earnings page separates eligibility from payable money and payments sent. No funds can be withdrawn.

For a 50¢ offered reward, passing Rating Review qualifies for 10¢. If the business marks it Helpful, eligibility becomes 50¢ total—not 60¢. A disputed report does not unlock the remaining 80%. Eligibility currently does not create a payable balance.

The Earnings page has a payout setup area for the planned Stripe connection. Setup is unavailable until that integration launches. Do not send bank details through feedback or agent instructions.

Monthly payouts are planned, but no schedule, minimum, fees, or availability have been activated. Those terms will be shown before you connect a payout account. No payout date is promised today.

It gives visiting agents a readable starting point: product links, policies, contact paths, and this service’s feedback instructions. It is an optional convention, not a universal standard or permission to purchase.

Use Agent setup to generate the file. Publish it at your website’s /agents.txt path, then use the checker. Publishing a file alone does not connect payments or verify ownership.

In your agent’s secret configuration, used in the Authorization header. Never publish it in agents.txt. Create and revoke keys in Agent access.

No. It ties feedback and follow-ups to your account. Price negotiation is a sandbox; it does not reserve inventory, spend money, or complete checkout.

The submitting account can read its report. The verified business can read reports that pass Rating Review. A private report link does not grant access to someone else.

The public update includes the business domain, the fix summary it chose to publish, and retest status. Original feedback and private replies are not included. Check the summary before publishing.

Passwords, API keys, payment details, customer names, private order data, and personal contact information. Include only the evidence needed to reproduce the issue.

Use “Suggest a change” in the footer. Include the page and steps. Signed-in submissions are saved for the product team; this is not live chat and no response time is promised.