Send feedback

You clicked Feedback in a tool or in the extension, and it brought you here. This page tells you what to send so it actually changes something.

Feedback is not only bug reports

Bugs and feature requests already have their own pages. Feedback is everything in between — the things people usually shrug off instead of mentioning, which are often the most useful:

• A tool worked, but the result surprised you. Nothing crashed, the numbers just did not match what you expected.
• You could not tell what an option did. A label, a toggle or a default that reads one way and behaves another.
• It was slower than it should have been, or it struggled on the size of list you actually work with.
• It almost fitted your workflow. You still had to clean something up in a spreadsheet afterwards.
• The page did not answer your question, so you went looking elsewhere. That is a documentation bug and it counts.
• It saved you real time. Genuinely worth knowing — it decides what gets built next.

Feedback on a tool on the site

Two lines is enough to be useful. If you can, add:

• The tool URL, so there is no guessing which one you mean.
• What you were trying to get done — the real job, not the button you pressed.
• A sample input: a few URLs, a keyword, a slice of the list you pasted.
• Your browser and device, if it looked wrong on screen.

Every tool runs in your browser, so nothing about your input reaches us unless you paste it into the email yourself. Send only what you are comfortable sharing.

Feedback on the Chrome extension

The rank-checker extension runs against live Google results, so what it saw matters as much as what it did. Useful details:

• The keyword and the location you had set.
• What the extension reported, and what you saw when you searched manually.
• Whether it happened once or every time.
• Your Chrome version, and whether other extensions were running.

If the extension is working well for you, a Chrome Web Store review helps more than an email — it is the only signal new users see before installing.

Sending it somewhere more specific

• Something is broken. The Contact page has the checklist that gets a bug fixed in one round trip.
• You want a tool or a feature that does not exist. Start at Request a feature.
• A question about your data. The Privacy Policy covers what is stored and how to have it deleted.
• Anything else. Use the button below — it all lands in the same inbox either way.

What happens to it

One person reads every message, normally replying within two working days. Small copy and label fixes tend to ship the same week. Anything larger turns into a change on the tool itself, and you get told when it is live. There is no newsletter and no auto-reply.

Last updated: 28 July 2026