Sticky Tags

Premium Feature

Introduction #

Sticky tags are like any other tags except, they stick, automatically. All a user has to do is define a tag as sticky, and they will automatically attach themselves to any new bookmarks that are created based on the content of the bookmarks.

How do they work #

Sticky tags work on a keyword matching algorithm and therefore are ideally used for specific terms & topics since creating them as too generic might result in too many items being tagged which are not relevant.

Suppose we have a tag “SEO” (for Search Engine Optimization), we can make this tag sticky and it will automatically tag any bookmarks that have the word “SEO” in their metadata (title, description, content etc). It’s also possible to define aliases (or synonyms) for a term, so in this case, for SEO we can define an alias “Search Engine Optimization” or any bookmarks with “Search Engine Optimization” will be automatically tagged with “SEO“.

Note: Both tags and aliases are case insensitive, upper or lowercase doesn't matter.

It is best not to use too generic tags like “inspiration”, “idea” etc as the meaning of these tags vary from bookmark to bookmark and will result in false positives.

Some good examples for sticky tags are

  • Technologies: Ansible, CloudFormation, Terraform, Vue, JavaScript, etc
  • Digital Marketing: SEO, CPC, SEM, etc

How to create a sticky tag #

Sticky tags are easy to enable, simply create or edit an existing tag, in our case using the example above:

  • Create a tag “SEO” from the tags tab
  • Select tag’s context menu and select “Edit”
  • Enable the “Sticky” switch
  • Enter an alias, for example, “Search Engine Marketing” (case doesn’t matter)
  • Press Add/Update

Now, when a new bookmark is added either from a board or from the browser extension, Clipd’s algorithm will evaluate its metadata and content and if the tag’s term or one of its aliases is found, that link will be tagged with the tag.

sticky tags

Powered by BetterDocs

Leave a Reply

Your email address will not be published. Required fields are marked *