Profile cover photo
Profile photo
Kerstin Reichert
SEO Consultant, Technical Trainer, Writer & Speaker
SEO Consultant, Technical Trainer, Writer & Speaker


Post has shared content
HTTP/2 & You? I occasionally hear webmasters ask about HTTP/2 and their site + web-search. The good news is that HTTP/2 doesn't change the core concepts of HTTP, it doesn't change the URLs, and is transparently supported for users & crawlers if they ask for it. Its primary differences focus on improved performance. Your hoster could add support for HTTP/2 and you might not even notice -- who knows, maybe they support it already :). Additionally:

# HTTP/2 has no impact on SEO. Search engine crawlers (even if they don't support HTTP/2 yet, like Googlebot) will continue to work normally, you don't have to set up redirects, change links, add markup, or make any changes in Search Console.

# Most browsers only support HTTP/2 together with HTTPS. That's when users will usually see improvements. Already on HTTPS? Awesome, you're all set.

# HTTP/2 is ready for use now, and supported in lots of website server setups.

In short, from a search point of view, there's nothing to hold you back from adding support for HTTP/2! Curious about more? Check out these links:


Post has attachment
Happy #FirstDayofSpring! Happy #InternationalDayofHappiness! And #HappySunday everyone! Yes, that's a lot :D

Post has shared content
An update (March 2016) on the current state & recommendations for JavaScript sites / Progressive Web Apps [1] in Google Search. We occasionally see questions about what JS-based sites can do and still be visible in search, so here's a brief summary for today's state:

# Don't cloak to Googlebot. Use "feature detection" & "progressive enhancement" [2] techniques to make your content available to all users. Avoid redirecting to an "unsupported browser" page. Consider using a polyfill or other safe fallback where needed. The features Googlebot currently doesn't support include Service Workers, the Fetch API, Promises, and requestAnimationFrame.

# Use rel=canonical [3] when serving content from multiple URLs is required.

# Avoid the AJAX-Crawling scheme on new sites. Consider migrating old sites that use this scheme soon. Remember to remove "meta fragment" tags when migrating. Don't use a "meta fragment" tag if the "escaped fragment" URL doesn't serve fully rendered content. [4]

# Avoid using "#" in URLs (outside of "#!"). Googlebot rarely indexes URLs with "#" in them. Use "normal" URLs with path/filename/query-parameters instead, consider using the History API for navigation.

# Use Search Console's Fetch and Render tool [5] to test how Googlebot sees your pages. Note that this tool doesn't support "#!" or "#" URLs.

# Ensure that all required resources (including JavaScript files / frameworks, server responses, 3rd-party APIs, etc) aren't blocked by robots.txt. The Fetch and Render tool will list blocked resources discovered. If resources are uncontrollably blocked by robots.txt (e.g., 3rd-party APIs) or otherwise temporarily unavailable, ensure that your client-side code fails gracefully.

# Limit the number of embedded resources, in particular the number of JavaScript files and server responses required to render your page. A high number of required URLs can result in timeouts & rendering without these resources being available (e.g., some JavaScript files might not be loaded). Use reasonable HTTP caching directives.

# Google supports the use of JavaScript to provide titles, description & robots meta tags, structured data, and other meta-data. When using AMP, the AMP HTML page must be static as required by the spec, but the associated web page can be built using JS/PWA techniques. Remember to use a sitemap file with correct "lastmod" dates for signaling changes on your website.

# Finally, keep in mind that other search engines and web services accessing your content might not support JavaScript at all, or might support a different subset.

Looking at this list, none of these recommendations are completely new & limited to today -- and they'll continue to be valid for foreseeable future. Working with modern JavaScript frameworks for search can be a bit intimidating at first, but they open up some really neat possibilities to make fast & awesome sites!

I hope this was useful! Let me know if I missed anything, or if you need clarifications for any part.

[1] PWA:
[2] Progressive enhancement:
[3] rel=canonical:
[4] AJAX Crawling scheme:

Post has attachment
Tag der offenen Tür bei +video2brain

Der Countdown läuft: 

Zur Feier des Schaltjahres öffnet die Online Plattform für Video-Trainings am 28.02.2016 ihre Tore. 48h lang können alle Kurse gratis geschaut werden. Die umfassende Bibliothek umfasst Trainings aus den Bereichen   #Programmierung , #Marketing , #Video , #Audio , #Design , #BusinessSkills  und vieles mehr.

Schau vorbei und entdecke 69.810 Videos, 6.146 Stunden, 1.568 Kurse.


Post has shared content

Post has shared content
Googlebot's getting ready to jam with #AMP. If you've started setting up your site's news'y content for AMP-HTML, check out Search Console. We just added a preview of AMP error reporting to make it easier for you to find issues in your AMP implementation across the site. There's still time enough to fix those errors before the public launch :).

Find out more at

Post has shared content
The Google Knowledge Graph Search API has arrived

Google's replacement for the Freebase API, the Knowledge Graph Search API, is up and running.

The API allows users to query the Knowledge Graph for entities, with responses in JSON-LD format.

The query can be restricted to return only entities matching specific types, and a new property, resultScore (provided as an external extension), allows returned entities to be ranked.

#knowledgegraph #schemaorg #jsonld #apis

Post has shared content
New in Google Search Console we are happy to announce that we have just launched a new filter in the Search Analytics Report called Search Appearance .

Currently, you can use that filter to see data about your 'install app' button in Google mobile search results. Thanks to this, you can now see which queries your users typed to see the install button for your app, and also filter by country to see where most of your app users come from.

Let us know what you think of it in the comments :)

Note: this feature doesn't show how many users actually completed the download process once in the play store

Post has shared content
#WebmasterNews Our app indexing docs have been spruced up with streamlined overview and instructions (there are no implementation changes) →

Post has shared content
If you want to prepare for next year's hottest new website technology, dig into Accelerated Mobile Pages (AMP) when you have a moment. These videos are perfect for an insightful lunch at your laptop or phone .. and you can even accelerate them on YouTube to watch them faster :-)).

You're sure to hear a lot more on this topic come next year; if you're a web-developer, you'll almost certainly be asked about it, so check it out early on and think about where & how it might make sense within the sites that you work on.

Edit ... here are some of the newer docs:
.. and a getting-started guide:
Wait while more posts are being loaded