Pen Settings

CSS Base

Vendor Prefixing

Add External Stylesheets/Pens

Any URL's added here will be added as <link>s in order, and before the CSS in the editor. If you link to another Pen, it will include the CSS from that Pen. If the preprocessor matches, it will attempt to combine them before processing.

+ add another resource

You're using npm packages, so we've auto-selected Babel for you here, which we require to process imports and make it all work. If you need to use a different JavaScript preprocessor, remove the packages in the npm tab.

Add External Scripts/Pens

Any URL's added here will be added as <script>s in order, and run before the JavaScript in the editor. You can use the URL of any other Pen and it will include the JavaScript from that Pen.

+ add another resource

Use npm Packages

We can make npm packages available for you to use in your JavaScript. We use webpack to prepare them and make them available to import. We'll also process your JavaScript with Babel.

⚠️ This feature can only be used by logged in users.

Code Indentation


Save Automatically?

If active, Pens will autosave every 30 seconds after being saved once.

Auto-Updating Preview

If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.

HTML Settings

Here you can Sed posuere consectetur est at lobortis. Donec ullamcorper nulla non metus auctor fringilla. Maecenas sed diam eget risus varius blandit sit amet non magna. Donec id elit non mi porta gravida at eget metus. Praesent commodo cursus magna, vel scelerisque nisl consectetur et.

              /* Machine-Readable Entity ID Bookmarklet */
	Welcome! Thanks for checking this out. This JavaScript bookmarklet will help you easily find the MREID (when available) on a Google SERP. Questions can be left as comments at: https://www.upbuild.io/blog/machine-readable-entity-ids-seo/

// First, try to grab the DOM  element that contains the MREID. NOTE: This _will_ break when/if Google changes the markup of their SERPs. 
var knowledgeNode = document.querySelector("#rhs .kno-ftr > .kno-fb > div[data-async-context]"); 
// Second, check that something was actually found above. If we try this on a null variable, we'll have issues so we need to avoid doing that. 
if (knowledgeNode !== null) {
	// A. cardID will be equal to a cleaned up MREID. 
	var cardId = unescape(document.querySelector("#rhs .kno-ftr > .kno-fb > div[data-async-context]").getAttribute("data-async-context").split("card_id:")[1].split(";")[0]);
	// B. Print a success message to the console. 
	console.log("%cSuccess! An MREID was found!","color: green; font-size: large");
	console.log("The machine-readable entity ID for\nthis search entitiy is " + cardId);
	// C. Print a success message to the SERP itself. So meta!
	var node = document.createElement("strong");
	var text = document.createTextNode("MREID is " + cardId + " | ");
	var link = document.createElement("a");
	link.setAttribute("href","https://trends.google.com/trends/explore?q=" + cardId);
	var linkText = document.createTextNode("Check via Google Trends"); 

	// D. Worth noting, we finde the element where Google reports "About X results" and append our message to that. 
// Third (AKA, fallback "Second"), we do something if no MREID was found on the SERP.
else if (knowledgeNode == null) {
	// See B above.
	console.log("%cSorry! No MREID found!","color: red; font-size: large");
	console.log("No machine-readable entity ID was found on this page. This is likely not an entity Google recognizes.");
	// See C above.
	var node = document.createElement("strong");
	var text = document.createTextNode("No MREID found");
	// See D above.
🕑 One or more of the npm packages you are using needs to be built. You're the first person to ever need it! We're building it right now and your preview will start updating again when it's ready.