How can we help?

Install the extension from the Chrome Web Store, then pin it from Chrome’s Extensions menu so it is always easy to reach.

Open the invitation link and select Join review. If you received a code instead, paste it into the extension. Invitation links can be project-specific, so use the latest one from your host.

Guests can enter a display name and start reviewing immediately. Use a name your team will recognize; an account is only needed to manage your own projects and access them later from another device.

Select the Foplink icon in Chrome. If the panel does not appear, open Chrome’s side panel menu and choose Foplink Reviews from the list.

Navigate to the website under review and select Annotate. Move your pointer over the page; the element currently targeted for feedback will be highlighted.

Choose the smallest element that clearly identifies the issue, such as the button, image, heading, or form field itself. Avoid selecting an entire page section when the feedback concerns only one item.

State what you see, what you expected, and the requested change. For example: “This button wraps on mobile. Keep the label on one line at 375 px.”

Mention the browser, screen size, signed-in state, or steps that trigger the issue when they matter. Never include passwords, access tokens, or private customer data.

Open the side panel on the exact reviewed URL. Select a comment in the list to locate its pin and inspect the referenced element on the page.

Scan the existing comments before adding a new one. If the same issue is already reported, reply in that thread with extra details instead of creating another pin.

Share the project invitation link supplied by the project owner. Ask reviewers to use a recognizable display name so replies and decisions remain easy to follow.

Use replies for questions, clarifications, and progress updates related to the original pin. This preserves the full decision history beside the element it concerns.

Create one comment per requested change. Separate threads make ownership clearer and prevent one resolved point from hiding an unfinished issue.

Refresh both the website and the Foplink panel after a new build is deployed. Revisit the original pin and add a short reply confirming whether the change works.

Send teammates the complete URL, including its path and relevant query parameters. Comments are connected to a specific page address, not only to the website domain.

Confirm the tab uses an http:// or https:// address and that you joined a valid project. Chrome blocks extensions on internal pages, browser settings, and the Chrome Web Store.

Check that the current address exactly matches the page where the comment was created. Then refresh the extension or close and reopen the side panel.

Open chrome://extensions and confirm Foplink Reviews is installed and enabled. If it is enabled, pin it from Chrome’s Extensions menu.

Refresh the website after installing or updating the extension. If the page was already open, Chrome may not have loaded the extension into that tab yet.

Use the panel’s refresh action, then reload the page. Also confirm you are viewing the intended project and not a previous review of the same website.

For local development, make sure the page is served over HTTP rather than opened as a file:// document. On restricted sites, ask the site administrator whether browser extensions are allowed.

Open Foplink and sign in with the same email address you used for your account. Guest access does not automatically transfer between devices; request a fresh invitation if needed.

Email support@foplink.com with the project name, page URL, Chrome version, extension version, and a short sequence of steps that reproduces the problem. A screenshot is helpful when it contains no sensitive data.

Email privacy@foplink.com from the address connected to your account and describe your request. Learn more in the Privacy Policy.