Documentation

Your first review

1. Create a project with the production website URL. Add a staging URL when the team reviews a staging site too.
2. Invite reviewers from Manage team and choose the access each person needs.
3. Download your personal extension package from app.opmerk.io/extension (opmerk.app opens the same page) and install it in Chrome.
4. Open the project website, select Start review, then choose Comment and click an element.
5. Add a title and description, choose a priority and send. The pin, screenshot and page context appear in the project Inbox.

How the workspace fits together

What a pin contains

• A title, rich-text description and screenshot, with optional image attachments.
• The page URL, CSS selector and element text.
• Viewport and environment details from the review.
• A project-specific issue number, status, priority, assignee and conversation.

When to use feedback

Use a pin for a misaligned button, an incorrect heading or a broken visual detail. Open the Inbox to filter, inspect and discuss the item. After a redesign removes the original element, check the pin’s position and create a new pin if the old context no longer applies.

Turn findings into work

1. Open a feedback item and choose Add to to-do, or create a task directly.
2. Give the task a Markdown description and an assignee. Link related feedback so the original reports remain accessible.
3. Move the task through To do, In progress and Done. Completing a task resolves its linked open feedback.

Choose the right place

Ownership

A task’s assignee is separate from the assignees of its linked pins. Reopen feedback from the Inbox if completing the task did not solve the reported issue.

The seven feedback states

Triage the next action

Choose Critical, High, Medium or Low priority. Assign the person who should act next, then use Inbox filters to review open work or collect items ready for sign-off. Status changes are recorded in the activity log; keep the reasoning in the thread.

Keep the discussion in context

• Write rich-text replies with formatting, lists and images. Replies can nest one level.
• Mention teammates with @handle to draw their attention to a comment or task.
• Edit or delete your own comments. Project Admins can moderate comments.
• Record the reason for a decision before changing a status, so the next reviewer can follow what happened.

A shared review session

• See active reviewers and their avatars in the extension toolbar.
• Follow named live cursors anchored to page elements, even when reviewers use different viewport sizes.
• See pins and discussions update without refreshing the page.
• Use the dashboard’s Team view to see who is reviewing which project page.

When the connection drops

Realtime activity is available on Pro projects while review mode is on. If a colleague misses a live update, confirm that both reviewers are on the same project and page, then check the connection and refresh. Cursor activity is for the review team; it is not visitor analytics.

Manage your notifications

• Open the extension’s Settings → Notifications to enable, disable or test notifications.
• Click a notification to open the related item in the dashboard.
• Your own activity is excluded. Several new events may be combined into one digest.

Delivery

The extension checks for updates periodically, so a notification may arrive after the live feedback update. Check Chrome notification permissions if the test notification does not appear.

Install or update

1. Sign in at app.opmerk.io and open Extension setup (opmerk.app is a shortcut). Download your personal ZIP; it is tied to app.opmerk.io, so packages downloaded from older addresses must be replaced.
2. Extract it into a permanent folder.
3. Open chrome://extensions, enable Developer mode and choose Load unpacked. Select the folder containing manifest.json.
4. Open a connected website and start review mode. When updating, replace the extracted files and reload the extension from chrome://extensions.

The toolbar

Useful controls

Esc exits the active tool. Cmd/Ctrl + Enter sends a pin. In Settings, edit your display name, choose a live cursor style and colour, and manage notifications. Feedback needs a connected domain and a role with review access; local SEO inspection is also available on other HTTP and HTTPS pages.

Browser analysis · Core & Pro

The extension checks metadata, canonical and robots directives, social cards, headings, content, links, image attributes, structured data and keyword placement. Highlight a finding on the page or turn it into feedback. Connected project audits sync to the workspace; analysis on an unconnected site stays local.

Cloud scans & AI visibility · Pro

Use Scan site now in the dashboard’s SEO view to discover public pages through robots.txt, sitemaps and same-site links. Review site-level scores, recurring issues, duplicate titles and descriptions, and failed pages. AI visibility adds checks for how content is exposed to AI search and answer engines. Pro also includes full SEO report downloads.

Information disclosure · Core & Pro

Both the browser audit and cloud scans read what a page leaks to anyone who views its source: developer notes, passwords, keys or tokens left in HTML and CSS comments, e-mail addresses, local file paths, private or staging hostnames, theme and template fingerprints (asset paths, CSS headers, template-branded class names, the generator tag), version parameters on scripts and stylesheets, and source-map references. The cloud scan also reads up to four same-origin stylesheets and checks whether referenced .map files are actually served. Findings appear in the Disclosure category; a credential or a public source map is Critical.

Read and act on results

• Start with Critical issues, then Warnings and Notices.
• Review the recommended fix and create a task when the change spans several pages.
• Ignore an issue when it is intentional. Findings that disappear on the next audit can resolve and reopen if they return.
• Use audit history to compare page scores and findings over time.

Scan coverage

Cloud scans cover up to 60 public pages and follow links up to three levels deep. Pages behind forms, sign-in or JavaScript-only navigation may need a browser audit. Domain verification is required after the project’s initial verification window to keep cloud scans running.

Review the live page

1. Select Attention in the extension toolbar on a connected Pro project.
2. Inspect component rankings, attention shares and the reasons behind each result. The model considers layout, position, contrast, colour, typography and other visual signals.
3. Use the heat overlay and Show to locate a component. Pin as feedback carries the result into the review conversation.
4. Save a labelled snapshot, make the change and save another snapshot at a comparable viewport width.

Compare and share

The dashboard’s Attention Review page compares snapshots to show rank changes, new or removed components and attention above the fold. Export JSON or open the print-ready client report and save it as a PDF from the browser.

Understand the result

This is a heuristic prediction from the rendered page, not recorded eye tracking or visitor behaviour. It adds no visitor-tracking script. Use the explanations to guide a design review and validate important decisions with users. Rankings depend on the viewport.

Local previews

An account with Pro access can preview attention on unconnected pages. Saving snapshots and pinning findings still require a connected Pro project.

How a measurement works

1. Add prompts in the project’s AI Visibility view: the questions a customer would ask an assistant, each with a language, market and category. “Brand” prompts are also asked without web search to test whether the model knows the business at all.
2. Choose Measure now, or wait for the weekly run every Monday. Each prompt is asked through ChatGPT and Perplexity with web search on, twice per engine, and every answer is stored with the providers named, their rank and the cited pages.
3. Read the Overview: share of voice per engine (this week and the four-week average), the recognition result, who gets named instead of you, and the domains the answers cite most.
4. Open a prompt to read every answer, or open Sources to see which pages an answer, a listing or a mention would need to reach.

What the numbers mean

Every figure is the result of your own prompt list, asked through each provider’s API on the dates shown and with the sample size shown. It is not a measurement of what every user sees, and answers vary from day to day, which is why shares are averaged over four weeks and the methodology is printed on every screen. Nobody can guarantee a mention; the product shows where you are absent and what the engines read instead.

Competitors

• Add competitors by name and domain. Names the engines recommend instead of you are a good starting list.
• Their public ads are captured from the Meta Ads Library and the Google Ads Transparency Center: active ads, creatives, texts, platforms, first and last seen, and Meta’s EU reach where published. Ads not seen in the latest capture are marked ended, never deleted.
• Add the search terms customers use, with a country and language; the top ten organic results and the ads above them are captured, with your site and your competitors highlighted.
• Spend is not published by any platform, so Opmerk shows ad activity and never estimates a budget.

Quotas and availability

AI Visibility is enabled per project by a System Admin with a monthly quota of engine calls, estimated cost and competitor captures; counters reset every month and a run stops when a limit would be exceeded. A second run in the same week reuses the answers already collected, so it costs nothing. Measurements need the answer-engine keys configured on the workspace.

Connect from project settings

1. Open a Pro project, then Settings → AI agents.
2. Generate your personal agent token. It is shown once and can be rotated or revoked from the same screen.
3. Use the portal’s setup for Claude Code, Codex, Cursor or VS Code. The connection uses the portal’s /api/mcp endpoint with bearer-token authentication.
4. Open your repository in the agent and ask it to list your projects, inspect a feedback item and implement the requested change.

Available MCP tools

Prompts and screenshots

The fix_feedback prompt provides the complete feedback brief and screenshot. The work_task prompt includes the task and its linked feedback briefs. Screenshots are available as opmerk://projects/{projectId}/feedback/{feedbackId}/screenshot resources for clients that can read images.

Keep review ownership clear

Agent actions use your existing project permissions and Pro access. Writes require Editor or Admin access. Ask the agent to add a comment and set the item to Ready for review after a fix; the reporter should confirm it on the live site. The agent works in your repository through its own development environment—Opmerk provides the review context.

A brief without a connection

Copy AI brief, available on Pro feedback items in the Inbox and extension panel, copies a Markdown handoff with the page, selector, discussion, environment and screenshot link. Paste it into your preferred assistant when you do not want to connect MCP.

Project roles

Invite and manage members

Use Manage team on the project card. Invitations expire after seven days; new members may receive a temporary password. Projects keep at least one active Admin. Removing access or changing a role also changes what the account can do through the extension and MCP.

Verify a domain

In Settings → Domain, publish the verification token as a DNS TXT record at _opmerk.<domain> or a file at /.well-known/opmerk-verify.txt, then choose Verify domain. New or changed production domains have a two-day verification window for cloud scanning. Feedback, tasks and extension reviews remain available while verification is pending.

Included features

What is coming next

AI Insights, automatic summaries, more answer engines (Gemini, Claude) and agency-branded reports are next. The AI Insights preview is illustrative, not an active analysis of project data. Public pricing and self-serve subscriptions have not been announced; ask your System Admin about enabling Pro or AI Visibility.

Feedback is off on this site

Ask a Project Admin to confirm the production or staging domain and your review access. Reload the page after connecting the domain. Local SEO inspection can still work on an unconnected site.

A teammate cannot see my pin

Confirm that both reviewers are using the same workspace, project and page. Check review mode and the realtime connection, then refresh the page or Inbox.

Attention or MCP is unavailable

Check that the selected project is Pro. Update the extension to use newly released tools. For MCP, confirm the endpoint and personal token, and reconnect after rotating it. A token does not grant access beyond your role.

The cloud scan is incomplete

Check domain verification, robots.txt and sitemaps. Scan limits and public-page access can exclude pages. Use the extension to inspect pages reached through sign-in, forms or client-side navigation.

AI Visibility is off or a measurement failed

A System Admin enables AI Visibility per project. If a run ends as failed, open a prompt to read the error on its answers: a missing provider key or a provider rejection shows there. A run marked partial stopped at the monthly quota; the remaining prompts are asked next week or after the quota is raised.

A queued item has not synced

Restore the connection to the workspace and check the extension panel’s sync state. Open the related project in the dashboard to confirm that the item arrived before sending it again.