What URLs does BugHerd support?

  • Last updated on July 21, 2021 at 12:36 AM

BugHerd supports most standard URLs and IP addresses. BugHerd can also handle URLs containing:

  • subdomains
  • pathnames
  • query strings/parameters (question marks, equals, commas)
  • fragments and anchors (hashtag)
  • spaces
  • unicode characters

Here's a quick breakdown of those terms:

URLs.png

 

When do I need to add additional or special URLs?

Much of the time, you may be able to set BugHerd up with just one URL based on your main website or domain, e.g.

  • https://www.mywebsite.com

However, you may want to add other URLs to your project to collect feedback on specific pages, or pages that aren't live. You can add other URLs to your project such as:

 

Subdomains

If you want feedback on a staging or testing site, you can add a URL that includes a subdomain to your project.

  • https://staging.mywebsite.com
  • https://dev.mywebsite.com

Pathnames

  • https://staging.myagency.com/clientwebsite1/
  • https://elearning.com/courses/mycourse101/ 

Querystring parameters 

Some preview sites for new webpages (such as those created in Hubspot, Webflow or Figma) rely on querystrings to identify the page. You'll need to include the querystring parameter that identifies the site or page with the URL to ensure the feedback is sent to the correct BugHerd project.

  • https://mywebsite.com/landing-page?hs_preview=oCoIBvJv-10427322061
  • https://preview.webflow.com/preview/mywebsite?preview=298f18541f987c749b8f3208b6790627

If you're creating online learning, modules may also be identified by querystrings, such as in Moodle.

  • https://school.moodledemo.net/course/view.php?id=37

You may also have querystrings if you are translating your site into multiple languages.

  • https://mywebsite.com/?language=ja

Note: Wildcards (*) are not supported.

 

Fragments and anchors

Another common method identifying a page is a hash tag followed by a path-like name.  

  • https://staging.myagency.com/#/issue/autumn-2019

 

What about local hosts and internal websites? Does BugHerd work on those?

Yes. BugHerd will work on any site that you can view in a browser. For internal sites and local developer domains, just make sure the anyone you share your BugHerd project with also has access to the site.

  • 192.168.0.1:3000

Are there any URLs BugHerd doesn’t support?

There are a couple of URLs that BugHerd doesn't support:

  • Wildcards (e.g. https://*.bugherd.com.au/) are not supported.
  • Variations on a pathname e.g. if your project URL is set to https://bugherd.com/path1 then any variations on this won’t be recognised as separate, e.g. https://bugherd.com/path123 or https://bugherd.com/path1tea

 

⚠️ Note for Firefox users:

Due to recent changes to the Firefox add-on store, this feature isn’t available for our Firefox extension. We’re working to rectify this issue but for now we recommend using Chrome, Edge, or Safari browser extensions if you’d like to make use of this feature.

 

 

Quick Links

Guide to setting up website URLs for your BugHerd projects

How to add, remove or edit URLs in your project settings