Essential Sitecore Bookmarklets for Content Editors and Authors

If you spend your day creating or reviewing content in Sitecore, you probably switch between editing, previewing, and published views constantly. Bookmarklets—small bits of JavaScript saved as browser bookmarks—can make those tasks nearly instant.

You don’t need admin access or special permissions to use them. Just drag, drop, and click.

What Are Bookmarklets?

A bookmarklet is a browser bookmark that runs a small JavaScript command when clicked. In Sitecore, they’re great for:

• Jumping directly into Experience Editor from a live page
• Switching between Edit and Preview modes
• Copying the content path or item ID for QA and reporting
• Checking how a page looks on the published site
• Quickly finding the item in the Content Editor

These simple tools save time and reduce the need to log in or navigate the Sitecore backend for routine actions.

How to Add a Bookmarklet

1. Copy one of the snippets below.
2. In your browser, create a new bookmark.
3. Paste the JavaScript snippet into the URL field.
4. Name it (for example, “Open in Experience Editor”).
5. Save it to your bookmarks bar for one-click access.

Top Sitecore Bookmarklets for Content Editors

1. Open Page in Experience Editor

Switch from a live or preview page directly into Sitecore’s Experience Editor for quick updates.

javascript:(function(){
  var url = window.location.href.replace(/(\?|&)sc_mode=preview/g, '');
  if(url.indexOf('?')>-1){url += '&sc_mode=edit';} else {url += '?sc_mode=edit';}
  window.location.href = url;
})();

When to use it:
After viewing the published site, click this bookmarklet to open the same page in edit mode instantly.

2. Switch to Preview Mode

View the current page in preview mode without logging into Sitecore.

javascript:(function(){
  var url = window.location.href.replace(/(\?|&)sc_mode=edit/g, '');
  if(url.indexOf('?')>-1){url += '&sc_mode=preview';} else {url += '?sc_mode=preview';}
  window.location.href = url;
})();

When to use it:
Before publishing, check how your changes appear in preview.

3. View Published (Live) Version

Remove all Sitecore editing or preview parameters to load the live, published version of the page.

javascript:(function(){
  window.location.href = window.location.href.split('?')[0];
})();

When to use it:
Quickly verify that your changes are visible on the live site after publishing.

4. Copy Sitecore Item Path

Copies the Sitecore content path of the current page to your clipboard (useful for tickets or QA notes).

javascript:(function(){
  var match=document.documentElement.innerHTML.match(/sitecore\/content[^\"]+/i);
  if(match){navigator.clipboard.writeText(match[0]); alert('Copied: ' + match[0]);}
  else{alert('No Sitecore path found on this page.');}
})();

When to use it:
Need to send a link to a teammate or log a ticket? Click to copy the item path instantly.

5. Jump to the Content Editor

Opens the Content Editor for the page you’re viewing (requires Sitecore login).

javascript:(function(){
  var idMatch = document.documentElement.innerHTML.match(/\{[0-9A-F\-]{36}\}/i);
  if(idMatch){
    window.open('/sitecore/shell/Applications/Content Editor.aspx?sc_bw=1&id=' + idMatch[0],'_blank');
  } else {
    alert('Item ID not found. Make sure you are viewing a Sitecore-rendered page.');
  }
})();

When to use it:
Quickly edit metadata, workflow, or shared fields in the Content Editor without manually searching for the item.

6. Toggle Between Staging and Production

If your organization uses consistent host naming (for example, www.site.com for production and staging.site.com for staging), you can jump between environments easily.

javascript:(function(){
  var newUrl = window.location.href.replace('www.site.com','staging.site.com');
  window.location.href = newUrl;
})();

When to use it:
Compare how a page looks in staging versus live.

Optional: Create a Team Bookmarklet Library

If you manage multiple editors, create a Sitecore Bookmarklet Library Page (an internal HTML page) listing all approved bookmarklets. Team members can simply drag each link to their bookmarks bar.

Sections to include:

• Editing shortcuts
• Preview and QA tools
• Content reporting helpers

This approach ensures consistency across your authoring team and reduces training time.

Best Practices for Editors

• Only use bookmarklets on your organization’s Sitecore environments.
• Always verify you’re logged into the correct environment (CM vs. CD).
• Bookmarklets work best in Chrome, Edge, or Firefox.
• Use preview or staging for testing before using production URLs.

Start Using These Bookmarklets Today

Bookmarklets might be small, but they can save Sitecore authors a lot of time. Instead of digging through menus or typing query strings, one click lets you open the Experience Editor, switch to preview, or copy a content path for a teammate.

Encourage your editorial team to keep these shortcuts handy in their browsers. They make everyday tasks faster and help new authors feel more comfortable navigating between edit, preview, and live environments. Once you start using them, you’ll wonder how you ever worked without them.