- Free website feedback widget with
+ Free GitHub Issues feedback widget with
screenshots in 30 seconds
- BugDrop is an open-source website feedback widget that creates GitHub
- Issues with screenshots, annotations, system info, and redaction
- controls. Add one script tag to any site.
+ BugDrop is an open-source website feedback widget for visual bug
+ reporting. Capture screenshots, annotations, browser metadata, and
+ privacy redactions, then create GitHub Issues from one script tag.
+ Bookmarklet version for repeated own-site previews.
+
+
+
+
+ ) : null}
+
+
+
+
+
+
+ );
+}
diff --git a/src/content/use-cases/client-website-feedback-tool.mdx b/src/content/use-cases/client-website-feedback-tool.mdx
new file mode 100644
index 0000000..70cb1f8
--- /dev/null
+++ b/src/content/use-cases/client-website-feedback-tool.mdx
@@ -0,0 +1,27 @@
+# Client Website Feedback Tool
+
+BugDrop is a client website feedback tool for agencies, freelancers, and product teams that need structured review notes during design QA, staging review, and launch prep. Clients can report issues from the page they are reviewing without needing a GitHub account.
+
+## The Client Review Problem
+
+Client feedback often arrives as screenshots in email threads, comments in documents, chat messages, or vague notes like "the homepage looks odd on my phone." Those reports are hard to track and harder to convert into developer-ready tasks.
+
+BugDrop turns client feedback into GitHub Issues with screenshots, annotations, page URLs, browser metadata, and labels. Developers get a task they can reproduce and close.
+
+## Useful During
+
+- Staging site review
+- Pre-launch QA
+- Design implementation review
+- Content and copy review
+- Post-launch bug collection
+
+## No GitHub Account Required
+
+Clients should not need to understand your repository, issue templates, or triage workflow. They use the feedback widget on the website, and BugDrop creates the GitHub Issue behind the scenes.
+
+## Keep Feedback Close to Delivery
+
+Once the issue is in GitHub, your team can assign it, label it, link it to a pull request, discuss the fix, and close it when shipped. The client gets a simple reporting experience; the team gets a normal engineering workflow.
+
+Start with the [installation guide](/docs/installation) and review [configuration](/docs/configuration) for labels, widget placement, screenshots, and submitter fields.
diff --git a/src/content/use-cases/free-website-feedback-widget.mdx b/src/content/use-cases/free-website-feedback-widget.mdx
new file mode 100644
index 0000000..253461d
--- /dev/null
+++ b/src/content/use-cases/free-website-feedback-widget.mdx
@@ -0,0 +1,29 @@
+# Free Website Feedback Widget
+
+BugDrop gives teams a free website feedback widget that creates GitHub Issues instead of locking reports inside a hosted feedback dashboard. It is built for teams that want quick setup, screenshot context, and a workflow developers already use.
+
+## When a Free Feedback Widget Is Enough
+
+Many early-stage products, open-source projects, agencies, and internal teams do not need a full customer-feedback suite. They need a button that lets someone report a bug, capture the page state, and route the issue to the right repository.
+
+BugDrop is a strong fit when your goal is:
+
+- Collect bug reports from a public website
+- Let users submit feedback without creating an account
+- Capture screenshots and browser metadata
+- Keep triage in GitHub Issues
+- Avoid paying for another feedback inbox before the workflow is proven
+
+## What You Get
+
+BugDrop reports can include screenshots, annotations, redactions, page URLs, viewport size, browser, operating system, labels, and category fields. Developers see the report in GitHub and can assign, comment, label, prioritize, and close it in the normal issue workflow.
+
+## How It Compares to Paid Tools
+
+Tools like Userback, Marker.io, BugHerd, and Usersnap are useful when you need hosted dashboards, account management, team workflows, and broad integrations. BugDrop is narrower: it focuses on fast GitHub-native website feedback with screenshot context.
+
+That narrower scope is the point. If your team already lives in GitHub, a free widget that creates useful issues can be more efficient than adopting another product.
+
+## Start Free
+
+Install BugDrop from GitHub Marketplace, add the widget script, and test a report on a staging page. The [getting started guide](/docs/getting-started) covers the fastest path.
diff --git a/src/content/use-cases/open-source-feedback-widget.mdx b/src/content/use-cases/open-source-feedback-widget.mdx
new file mode 100644
index 0000000..9a7cca6
--- /dev/null
+++ b/src/content/use-cases/open-source-feedback-widget.mdx
@@ -0,0 +1,25 @@
+# Open-Source Feedback Widget
+
+BugDrop is an open-source feedback widget for teams that want to inspect, adapt, and self-host their feedback workflow. It is designed around GitHub Issues, so reports land where maintainers already track bugs and feature requests.
+
+## Why Open Source Matters for Feedback
+
+Feedback widgets sit on public websites and sometimes inside authenticated apps. Teams should be able to understand what the widget loads, what it captures, where data goes, and how screenshots are handled. An open-source widget makes that review possible.
+
+Open source is also useful when your workflow is specific. You may want custom labels, masking rules, issue templates, styling, or deployment constraints that do not fit a generic hosted tool.
+
+## Best Fits
+
+- Open-source projects that want community reports in GitHub
+- Developer tools with public docs and examples
+- Internal teams that need auditability
+- Agencies that want a repeatable client feedback workflow
+- Startups that want to avoid feedback-tool lock-in
+
+## GitHub Issues as the Feedback Backend
+
+BugDrop uses GitHub Issues as the system of record for feedback. That means maintainers can use labels, projects, assignees, milestones, comments, notifications, and automation without syncing from another dashboard.
+
+## Add It to Your Project
+
+Install the GitHub App, add the widget script, and configure labels, screenshots, masking, and submitter fields. The [self-hosting guide](/docs/self-hosting) covers teams that want more control over deployment.
diff --git a/src/content/use-cases/screenshot-feedback-widget.mdx b/src/content/use-cases/screenshot-feedback-widget.mdx
new file mode 100644
index 0000000..5ac178f
--- /dev/null
+++ b/src/content/use-cases/screenshot-feedback-widget.mdx
@@ -0,0 +1,30 @@
+# Screenshot Feedback Widget
+
+BugDrop is a screenshot feedback widget for teams that need users to show the problem, not just describe it. A report can include the current page screenshot, annotations, redacted regions, the page URL, and browser metadata.
+
+## Why Screenshots Matter
+
+Website bugs are often visual: clipped text, broken spacing, missing images, wrong colors, hidden buttons, mobile overflow, dark-mode issues, or browser-specific rendering problems. A written report like "the page looks broken" rarely gives developers enough context.
+
+A screenshot turns the report into a concrete artifact. An annotation points to the exact area, and metadata explains the environment where it happened.
+
+## BugDrop Screenshot Reports Include
+
+- Page screenshot
+- User annotation
+- Manual redaction before submit
+- Developer-controlled masking with `data-bugdrop-mask`
+- Page URL
+- Viewport size
+- Browser and operating system
+- Feedback category and labels
+
+## Privacy Controls
+
+Screenshots can expose private information. BugDrop supports user redaction and developer-defined masking for sensitive elements. Password and payment fields should be treated carefully, and teams should review [screenshot masking](/docs/security#screenshot-masking) before deploying the widget to authenticated product pages.
+
+## GitHub-Native Output
+
+Instead of sending screenshots to a separate dashboard, BugDrop creates a GitHub Issue. That keeps visual bug reports close to the code, release process, assignees, labels, and comments developers already use.
+
+Start with [installation](/docs/installation), then configure screenshot behavior in [configuration](/docs/configuration).
diff --git a/src/content/use-cases/website-feedback-widget.mdx b/src/content/use-cases/website-feedback-widget.mdx
new file mode 100644
index 0000000..280ee94
--- /dev/null
+++ b/src/content/use-cases/website-feedback-widget.mdx
@@ -0,0 +1,25 @@
+# Website Feedback Widget
+
+BugDrop is a website feedback widget for teams that want actionable reports without asking users to leave the page. Visitors click the widget, describe what they saw, attach or annotate a screenshot, and BugDrop sends the report to GitHub Issues with the page URL and browser context.
+
+## What Makes a Feedback Widget Useful?
+
+A feedback widget should reduce friction for the reporter and reduce ambiguity for the developer. Text-only reports often miss the page state, viewport, browser, and reproduction context. BugDrop captures those details at submit time so the issue starts with enough information to triage.
+
+## Best-Fit Workflows
+
+- Marketing pages where layout or copy issues affect conversion
+- Documentation sites where examples, tabs, and navigation need quick feedback
+- SaaS apps where users can report broken UI states from inside the product
+- Internal tools where teammates need a low-friction way to report bugs
+- Client review sites where non-technical stakeholders should not need GitHub accounts
+
+## Why Send Feedback to GitHub Issues?
+
+Most development teams already use GitHub for triage, assignment, labels, discussion, and release tracking. A separate feedback inbox creates another place to check. BugDrop keeps website feedback in the same workflow as engineering work.
+
+Each report can include a description, screenshot, annotations, feedback type, page URL, browser, operating system, viewport size, and labels. That makes the GitHub Issue useful immediately.
+
+## Add It to a Site
+
+Install the GitHub App, add the script tag from the [installation guide](/docs/installation), and configure the widget with [configuration options](/docs/configuration). For sensitive pages, review [security and screenshot masking](/docs/security) before launch.
diff --git a/src/lib/links.ts b/src/lib/links.ts
index b42f682..77a04fb 100644
--- a/src/lib/links.ts
+++ b/src/lib/links.ts
@@ -18,6 +18,7 @@ export const DEMO_PATH = "/demo";
export const DEMO_URL = "https://bugdrop-widget-test.vercel.app";
-export const WIDGET_URL = "https://bugdrop.neonwatty.workers.dev/widget.js";
+export const WIDGET_URL =
+ process.env.NEXT_PUBLIC_BUGDROP_WIDGET_URL ?? "https://bugdrop.neonwatty.workers.dev/widget.js";
export const SAMPLE_DEMO_REPO = "mean-weasel/bugdrop-widget-test";
diff --git a/src/lib/seo.ts b/src/lib/seo.ts
index 8913e64..c44db40 100644
--- a/src/lib/seo.ts
+++ b/src/lib/seo.ts
@@ -11,10 +11,10 @@ import {
export const SITE_URL = "https://bugdrop.dev";
export const SITE_NAME = "BugDrop";
-export const SITE_UPDATED = "2026-05-11";
+export const SITE_UPDATED = "2026-05-13";
export const homeDescription =
- "Free, open source website feedback widget by mean-weasel. Users report bugs with screenshots and annotations — issues are created in GitHub automatically. One script tag, zero config.";
+ "Free, open-source website feedback widget for GitHub Issues. Capture bug reports with screenshots, annotations, browser metadata, and privacy controls from one script tag.";
export function absoluteUrl(path = "/") {
if (path.startsWith("https://")) return path;
@@ -95,11 +95,6 @@ export function softwareApplicationSchema() {
url: SITE_URL,
applicationCategory: "DeveloperApplication",
operatingSystem: "Web",
- offers: {
- "@type": "Offer",
- price: "0",
- priceCurrency: "USD",
- },
author: {
"@type": "Organization",
name: "mean-weasel",
@@ -126,6 +121,13 @@ export function softwareApplicationSchema() {
GITHUB_PROFILE_URL,
],
award: "Product Hunt #6 Product of the Day, May 9, 2026",
+ offers: {
+ "@type": "Offer",
+ price: "0",
+ priceCurrency: "USD",
+ availability: "https://schema.org/InStock",
+ url: MARKETPLACE_URL,
+ },
featureList: [
"Screenshot capture",
"Annotation tools",
@@ -133,6 +135,8 @@ export function softwareApplicationSchema() {
"Developer-configured privacy masking",
"Automatic password and credit-card field masking",
"Automatic system info",
+ "Browser metadata",
+ "GitHub Marketplace installation",
"GitHub issue creation",
"Fully stylable widget",
"Shadow DOM isolation",
diff --git a/src/lib/use-cases-nav.ts b/src/lib/use-cases-nav.ts
index 1851aee..0ff0223 100644
--- a/src/lib/use-cases-nav.ts
+++ b/src/lib/use-cases-nav.ts
@@ -34,6 +34,27 @@ export const useCasesNav: UseCaseLink[] = [
"Collect website feedback as structured GitHub Issues with screenshots, labels, browser info, and page URLs.",
icon: "📋",
},
+ {
+ slug: "website-feedback-widget",
+ title: "Website Feedback Widget",
+ description:
+ "Add a lightweight website feedback widget that sends screenshots, page context, and user notes to GitHub Issues.",
+ icon: "💬",
+ },
+ {
+ slug: "free-website-feedback-widget",
+ title: "Free Website Feedback Widget",
+ description:
+ "Use a free feedback widget for public sites, docs, SaaS apps, and internal tools without adding another inbox.",
+ icon: "Free",
+ },
+ {
+ slug: "screenshot-feedback-widget",
+ title: "Screenshot Feedback Widget",
+ description:
+ "Capture screenshots, annotations, browser metadata, and page URLs when users report UI bugs.",
+ icon: "📸",
+ },
{
slug: "visual-bug-reporting",
title: "Visual Bug Reporting",
@@ -48,4 +69,18 @@ export const useCasesNav: UseCaseLink[] = [
"Add BugDrop to a Next.js site with one script tag and send user feedback directly to GitHub Issues.",
icon: "▲",
},
+ {
+ slug: "open-source-feedback-widget",
+ title: "Open-Source Feedback Widget",
+ description:
+ "Choose an open-source feedback widget that can be inspected, self-hosted, and adapted to your GitHub workflow.",
+ icon: "OSS",
+ },
+ {
+ slug: "client-website-feedback-tool",
+ title: "Client Website Feedback Tool",
+ description:
+ "Give clients a simple way to report website issues with screenshots during review, QA, and launch prep.",
+ icon: "QA",
+ },
];