Profile cover photo
Profile photo
Simon Vreeman
393 followers -
Web Analyst at The Next Web
Web Analyst at The Next Web

393 followers
About
Simon's posts

Post has shared content
Will TheNextWeb succeed in out-structuring TheNewYorkTimes?

As +Kingsley Idehen recently noted on Linkedin, more and more "top-tier Web players" are embedding more and more structured data markup at "alarming rates".

Something the SEOs over at +The Next Web noted as well and so they seriously upped their semantic game, by attempting to out do one of the biggest international top tiers in the publishing industry, namely +The New York Times

Truth be said that measuring oneself to an organization like TNYT isn't completely fair game as I believe there are very few in this world that have access to the (semantic) resources TNYT has. Nevertheless, I think TNW did an awesome job and I can't wait to see the results of their future endevours, like being able to add schema.org/VideoObject markup to their articles (yes, even TNW has a development backlog that can't always be resolved immediately).

And since I'm curious to find out where TNW stands, does anybody know of a crawling tool that let's one measure the amount of triples a site contains?

Hi there,

I have a question about the container script. Why has the script to be placed immediate after the opening <body> tag?

One of the reasons is probably the <noscript> with the iframe, that will cause problems in some browsers.
But what if I move the <script> part of the container to the <head> en keep the <noscript> in the <body>? Does it have any effect on the data collection?

Why would I want that?
I want to execute the GTM container before the rendering of the page, because I use GTM to modify elements on the page. Currently the custom HTML tag with the JavaScript is placed in the bottom. So it is loaded and excuted later, and because of that I have a flickering effect. 
My hypothese is that when the <script> part is in the <head> the problem will be less. Just like a/b tools such as VWO & Optimizely. 

I love to hear your comments. And yes, I'm going to test it myself! :)

Thanks,
Simon

Post has shared content
You may have noticed that Google Search on desktop looks a little different today.

Towards the end of last year we launched some pretty big design improvements for Search on mobile and tablet devices (mobile first! :-). Today we've carried over several of those changes to the desktop experience.

We've increased the size of result titles, removed the underlines, and evened out all the line heights. This improves readability and creates an overall cleaner look. We've also brought over our new ad labels from mobile, making the multi-device experience more consistent.

Improving consistency in design across platforms makes it easier for people to use Google Search across devices and it makes it easier for us to develop and ship improvements across the board.

Post has attachment
Great post on the new golden age of journalism by Jonah Peretti, founder & CEO of BuzzFeed.

Post has attachment

Post has attachment

Post has shared content

Post has attachment
Mmm mmm mmm mmmmh

Post has shared content

Post has shared content
On the Matter of Why Bitcoin Matters — The Magazine on Medium — Medium
Wait while more posts are being loaded