Google Analytics Best Practices For Landing Pages

Whether your marketing landing pages are hosted on the same domain as your website or live on a separate domain, there are a few best practices that you should follow to make sure you’re accurately tracking landing page performance, conversion, and attribution. In almost any industry, companies use dedicated marketing landing pages to drive traffic towards a specific objective or ultimately increase traffic to your website.

Marketing landing pages are typically targeted to certain audiences and focused on encouraging specific actions. Maybe you have a team of internal designers and developers who build your landing pages, or maybe you pay an outside vendor to create them. Either way, a lot of resources can go into developing many different variations of those landing pages, so it’s important to track these properly in Google Analytics with your actual site.

Tracking Together is Always Better

Since landing page construction and testing is often a separate process or sometimes even separate team from the main website, there can be a temptation to track these pages into a separate Google Analytics property. It’s easy to set up a new property and sometimes we can just get that done without bothering anyone else. Perhaps another company or tool is helping with these landing pages, so they’ve suggested setting up separate tracking or even gone ahead and taken care of that for you.

That’s fine – but it’s just not the best. For several reasons, we want your landing pages to be tracked together with your main website. That doesn’t mean you can’t also have separate tracking on there; it’s totally fine to have multiple Google Analytics properties tracked on the same page.

In the examples below, we’ll talk about some of the common types of marketing landing pages. Specifically for pages that include links or call-to-actions that take the user back to the main website, you’ll want to make sure all of that traffic is tracked together and attributed properly. This is so important because often we spend more money and time driving traffic to our landing pages, so we want to make sure those campaigns and traffic sources get the credit they deserve.

In addition, this extra setup work will help prepare you for the fun stuff that comes next – things like using Google Optimize to test and tweak your Landing Pages!

Landing Page Challenge: What’s the Point?

Take a good look at your landing page and determine what it takes to call this page a success. Likely you’ll have something you want a person to do, referred to as a call-to-action, like Submit This Form, Watch This Video, or Call Us Today!

The next question is how will you be able to report on whether the landing page was successful? Or, how will you be able to tell which traffic source was more successful?

Let’s go through some of the common goals for a landing page.

Conversion on Landing Page

If the goal of your landing page is to drive people towards conversion on this particular page, such as submitting their information through a form or clicking on a high-value call-to-action button, then your number one job is tracking that engagement on the page itself. Remember that Google Analytics only measures page load by default.

A common anecdote from training attendees and clients is that their landing pages have extremely high bounce rates. Well, if everything happens all on the landing page, then Google Analytics only knows that they loaded the page, not what else happens after the page loads. Of course you’ll have a high bounce rate if they’ve only loaded one page.

The key here is to set up Event Tracking for Google Analytics. If you’re using a tool like Google Tag Manager (and you should be!), you can easily set up Google Analytics event tracking for key actions such as:

  • Form Submissions (Lead Generation)
  • Main Call-to-Action Button Clicks
  • Video Engagement
  • Contact Us links
  • Clicks on Download Links

These will help separate users who arrived on your page and left immediately versus those that arrived and did the thing you care about. Check out our Google Tag Manager recipes, designed to help make it easier to track these types of interactions.

Specifically for the important ones, like filling out a form, you would want to track these into Google Analytics with Events, then set these up as Goals inside of Google Analytics. Remember that you have 20 separate Goals per View, so it may be helpful to split your landing page traffic into its own View if you want to define custom Goals.

Using Events as Goals in Google Analytics

You should always measure some kind of high-value interaction, because otherwise, why have targeted landing pages? Put them to work.

Link to Main Site, Conversion on Main Site

Here’s a common challenge – what if one of the goals (or the only goal) of your landing page is to get people to the main website? How can we prove how effective this is?

There are lots of ways people attempt to measure this, but our recommendation would be to use events again. Set up event tracking on those links or, if the links are going to particularly important page, set up a Google Analytics goal for the end pages you’ve linked to. This will give you just the info you need, how many clicks did we have on our links to the main site (Total Events) or how many sessions included a click to our main site (Unique Events.)

Take care in how you set up your Event Category, Action, and Label to make sure you’ll have exactly what you need after everything is tracked and that you’ll be able to reuse some of those for your next landing page.

Things to Avoid – Stealing Traffic Info

While yes, you want to know how people move from your landing page to your main site, you want to be careful to not confuse this with your Traffic Source reporting. Remember, your Acquisition reports in Google Analytics are answering the question “Which traffic source should get credit for this particular session?” If you’re using Google AdWords, social media, or targeted email campaigns to drive traffic to your landing page, and then ultimately to your main site, then you want to see those traffic sources in your main site’s reporting. You don’t want to see the Landing Page as a traffic source.

This means we need to set up our tracking properly so that we 1) track the same user from our landing page to our main site and 2) maintain accurate traffic sources. We do not want to see these landing pages show up as referrals to our main site.

And here’s another big one, do not add UTM parameters on links to your main site from your landing pages. This will cause your current session (from whatever traffic source) to end, and start a new session from your landing page, making attribution reporting more difficult.

Landing Page Challenge: Where Does it Live?

Often, marketing landing pages live on the same domain as your website. Even if they use a separate template from the other pages on your site or are even built on a separate platform if the address of these pages looks like they’re on the same domain, how they were built doesn’t change how we’ll track these pages.

Where a page lives will change the steps needed to set up the correct tracking and to enable easy reporting.

Same Domain, Subdirectory Landing Page

As you consider Analytics and reporting, the easiest and best scenario would be to place these pages in their own subdirectories, like Trust us, this will save time and headache. Pages on the same domain will automatically be able to share cookies with the rest of the website, so all you need to do is make sure you have the same Google Analytics tracking ID on this page. If you need to report on these separately, they’ll automatically be split out in the All Pages or Content Drilldown report, and it’s easy to create a new View inside of Google Analytics with a subdirectory filter to monitor the success of these pages.

Same Domain, Subdomain Landing Page

If your landing pages are on a subdomain, like, that’s fine – but it will take a little more work. If users go between the landing page and your main site, you’ll want to follow the instructions to make sure your Subdomain Tracking is set up correctly.

Two Steps to Correctly Tracking Subdomains in Google Analytics

Note that with the appropriate subdomain tracking set up, you will not see referrals from your subdomain to your main website. This is a good thing! While it may have been an easy way to measure how much traffic came from your landing page to your main site, instead, you’ll be able to more easily see the original source information, like the campaign that brought them to your landing page in the first place. We talked above about other ways to measure landing page traffic to the main site.

Additionally, you’ll have a reporting challenge if you combine this with your regular tracking. When you go to report on the success of this landing page, your All Pages report in Google Analytics may combine this landing page together with your main site’s home page.

Remember that the All Pages report by default just shows the Page Path, so if you have and, they’ll both show up in your All Pages report as /. You can fix this by either faking the Page parameter in your tracking and passing in a fake page name, like /promo, or by using an Advanced Filter on your View to alter what values appear in the page path.

Different Domain, Page or Directory

If you’re building marketing landing pages through another platform, such as Marketo, Salesforce, or Hubspot, sometimes these pages will actually be hosted on a different domain, for instance, your website might be and your landing pages might be on By itself, this isn’t a problem.

However, remember above when we talked about the goal of your landing pages. If your landing page links directly to your main website and especially if your main goal is to drive traffic to your main site, then it’s imperative that you have cross-domain tracking correctly in place. Basically, from a tracking perspective, you want to treat your landing pages just like any other page on your website and you want to make sure the users are counted as the same user throughout their entire journey.

Cross-domain tracking is necessary for Google Analytics when you want to track users across multiple domains into one property. Double check that this applies to you by following the flowchart in Jim’s post:

Do I Need Cross-Domain Tracking?

You’ll need to match the instructions for setting up cross-domain tracking with the way your Google Analytics is implemented – there are different sets of instructions for using the JavaScript snippet vs Google Tag Manager, etc. Of course, we’d recommend Google Tag Manager, and have a handy guide to setting up cross-domain tracking.

Cross Domain Tracking with Google Tag Manager

With cross-domain tracking properly set up, Google Analytics will share cookies as a user moves from the domain with your landing pages to your main website domain (don’t forget that you may also need to add both domains to your Referral Exclusion list in GA). This will provide you with correct attribution reports.

Different Domain, Subdomain or Root Directory

Lastly – just another note of caution here. If your landing page appears looks like the following, or, then you may have one additional consideration. Since it’s on an entirely different domain, you’ll want to set up cross-domain tracking, just like above. However, when you go to report on the success of this landing page, your All Pages report in Google Analytics may combine this landing page together with your main site’s home page.

Remember that the All Pages report by default just shows the Page Path, so if you have and, they’ll both show up in your All Pages report as /. You can fix this by either faking the Page parameter in your tracking and passing in a fake pagename, like /promo, or by using an Advanced Filter on your View.

Put It All Together

Ultimately, marketing landing pages can be extremely valuable for getting your target audiences to do what you want them to do, from providing you with their contact information to encouraging them to explore more pages on your main website. But you need to take a few extra steps to ensure that you’re tracking engagement properly and maintaining traffic information, so that you’re able to measure your landing pages’ effectiveness and use those insights for future efforts.

Webdesign für die Anwälte der IGBL. Die International Group of Business Lawyers (IGBL) wurde 2016 mit dem Ziel gegründet, eine enge berufliche Verbindung zwischen unabhängigen wirtschaftsrechtlichen Anwaltskanzleien für Geschäftskunden und Unternehmer herzustellen. Die Mitglieder sind ausschließlich in den wichtigsten Geschäftszentren in ganz Europa ansässig.

IGBL-Mitglieder treffen sich regelmäßig in den wichtigsten Städten Europas, darunter Frankfurt, London, Madrid und Mailand. Diese Treffen ermöglichen es unseren Mitgliedern, Informationen, Neuigkeiten und Ideen aktiv zu fördern und auszutauschen, juristisches Wissen und Erfahrungen auszutauschen und sowohl berufliche als auch persönliche Beziehungen aufzubauen.

Ziel der IGBL ist es, das Verständnis für das innerstaatliche Recht des jeweils anderen zu vertiefen, gemeinsame Rechtsprojekte zu bearbeiten und gewerbliche Mandanten aneinander zu verweisen.

Die Arbeitsschwerpunkte liegen im Gesellschafts-, Handels-, Arbeits- und Eigentumsrecht sowie im Wirtschaftsrecht. Die IGBL strebt an, alle europäischen Länder abzudecken, und würde Anwaltskanzleien aus allen europäischen Ländern mit ähnlichen Fähigkeiten begrüßen, um sich unserem internationalen Netzwerk anzuschließen.

Unsere Leistungen sind sowohl das Webdesign und die Realisierung der Webseite mit WordPress. Neben einem responsiven Design und der Reibungslosen Darstellung auf mobilen Geräten steht die Optimierung für Suchmaschinen in englischer Sprache im Vordergrund.

WordPress Landing Page, Webdesign Agentur, Webdesign Frankfurt.

Sicher, leistungsstark u. kostengünstig. Bringen Sie Ihr Unternehmen mit der GCE voran — 100% is just the beginning!

Responsive Webdesign, WordPress Website, WordPress Shop und Kontaktformular

Webseiten Erstellung, WordPress Website, Responsive Webdesign, Website bei Google anmelden.

SSZ Deutschland


WordPress Blog.

A list of everything that *could* go in the <head> of your document

Table of Contents

Below are the essential tags for basic, minimalist websites:

<meta charset="utf-8">
<meta http-equiv="x-ua-compatible" content="ie=edge"> <!-- † -->
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags.

† Use the content="ie-edge" tag if your project must support Internet Explorer prior to version 11.

<title>Page Title</title>

⬆ back to top


Valid <head> elements include meta, link, title, style, script, noscript, and base.

<!-- Meta tags provide information for how a document should be perceived, and rendered, by other technologies. e.g. bots, search engines, browsers, etc. -->
<meta charset="utf-8">

<!-- Set the document's title -->
<title>Page Title</title>

<!-- Base URL to use for all relative URLs contained within the document -->
<base href="">

<!-- Link to external CSS file -->
<link rel="stylesheet" href="styles.css">

<!-- Used for adding in-document CSS -->
/* ... */

<!-- JavaScript & No-JavaScript tags -->
<script src="script.js"></script>
// function(s) go here
<!-- No JS alternative -->

⬆ back to top


<meta charset="utf-8"> <!-- Set character encoding for the document -->
<meta http-equiv="x-ua-compatible" content="ie=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->

<!-- Allows control over where resources are loaded from -->
<meta http-equiv="Content-Security-Policy" content="default-src 'self'">
<!-- Place as early in the document as possible -->
<!-- Only applies to resources below this tag -->

<!-- Name of web application (only should be used if the website is used as an app) -->
<meta name="application-name" content="Application Name">

<!-- Short description of the document (limit to 150 characters) -->
<!-- In *some* situations this description is used as a part of the snippet shown in the search results. -->
<meta name="description" content="A description of the page">

<!-- Control the behavior of search engine crawling and indexing -->
<meta name="robots" content="index,follow"><!-- All Search Engines -->
<meta name="googlebot" content="index,follow"><!-- Google Specific -->

<!-- Tells Google not to show the sitelinks search box -->
<meta name="google" content="nositelinkssearchbox">

<!-- Tells Google not to provide a translation for this document -->
<meta name="google" content="notranslate">

<!-- Verify website ownership -->
<meta name="google-site-verification" content="verification_token"><!-- Google Search Console -->
<meta name="yandex-verification" content="verification_token"><!-- Yandex Webmasters -->
<meta name="msvalidate.01" content="verification_token"><!-- Bing Webmaster Center -->
<meta name="alexaVerifyID" content="verification_token"><!-- Alexa Console -->
<meta name="p:domain_verify" content="code_from_pinterest"><!-- Pinterest Console-->
<meta name="norton-safeweb-site-verification" content="norton_code"><!-- Norton Safe Web -->

<!-- Identify the software used to build the document (i.e. - WordPress, Dreamweaver) -->
<meta name="generator" content="program">

<!-- Short description of your document's subject -->
<meta name="subject" content="your document's subject">

<!-- Gives a general age rating based on the document's content -->
<meta name="rating" content="General">

<!-- Allows control over how referrer information is passed -->
<meta name="referrer" content="no-referrer">

<!-- Disable automatic detection and formatting of possible phone numbers -->
<meta name="format-detection" content="telephone=no">

<!-- Completely opt out of DNS prefetching by setting to "off" -->
<meta http-equiv="x-dns-prefetch-control" content="off">

<!-- Stores a cookie on the client web browser for identification purposes -->
<meta http-equiv="set-cookie" content="name=value; expires=date; path=url">

<!-- Specifies the document to appear in a specific frame -->
<meta http-equiv="Window-Target" content="_value">

<!-- Geo tags -->
<meta name="ICBM" content="latitude, longitude">
<meta name="geo.position" content="latitude;longitude">
<meta name="geo.region" content="country[-state]"><!-- Country code (ISO 3166-1): mandatory, state code (ISO 3166-2): optional; eg. content="US" / content="US-NY" -->
<meta name="geo.placename" content="city/town"><!-- eg. content="New York City" -->

⬆ back to top

<!-- Points to an external CSS style sheet -->
<link rel="stylesheet" href="">

<!-- Helps prevent duplicate content issues -->
<link rel="canonical" href="">

<!-- Used to be included before the icon link, but it has been deprecated -->
<link rel="shortlink" href="">

<!-- Links to an AMP HTML version of the current document -->
<link rel="amphtml" href="">

<!-- Links to a JSON file that specifies "installation" credentials for the web applications -->
<link rel="manifest" href="manifest.json">

<!-- Links to information about the author(s) of the document -->
<link rel="author" href="humans.txt">

<!-- Refers to a copyright statement that applies to the link's context -->
<link rel="license" href="copyright.html">

<!-- Gives a reference to a location in your document that may be in another language -->
<link rel="alternate" href="" hreflang="es">

<!-- Provides information about an author or another person -->
<link rel="me" href="" type="text/html">
<link rel="me" href="">
<link rel="me" href="sms:+15035550125">

<!-- Links to a document that describes a collection of records, documents, or other materials of historical interest -->
<link rel="archives" href="">

<!-- Links to top level resource in an hierarchical structure -->
<link rel="index" href="">

<!-- Provides a self reference - useful when the document has multiple possible references -->
<link rel="self" type="application/atom+xml" href="">

<!-- The first, next, previous, and last documents in a series of documents, respectively -->
<link rel="first" href="">
<link rel="next" href="">
<link rel="prev" href="">
<link rel="last" href="">

<!-- Used when a 3rd party service is utilized to maintain a blog -->
<link rel="EditURI" href="" type="application/rsd+xml" title="RSD">

<!-- Forms an automated comment when another WordPress blog links to your WordPress blog or post -->
<link rel="pingback" href="">

<!-- Notifies a URL when you link to it on your document -->
<link rel="webmention" href="">

<!-- Enables posting to your own domain using a Micropub client -->
<link rel="micropub" href="">

<!-- Loads in an external HTML file into the current document -->
<link rel="import" href="/path/to/component.html">

<!-- Open Search -->
<link rel="search" href="/open-search.xml" type="application/opensearchdescription+xml" title="Search Title">

<!-- Feeds -->
<link rel="alternate" href="" type="application/rss+xml" title="RSS">
<link rel="alternate" href="" type="application/atom+xml" title="Atom 0.3">

<!-- Prefetching, preloading, prebrowsing -->
<link rel="dns-prefetch" href="//">
<link rel="preconnect" href="">
<link rel="prefetch" href="">
<link rel="prerender" href="">
<link rel="preload" href="image.png" as="image">
<!-- More info: -->

⬆ back to top


<!-- For IE 10 and below -->
<!-- Place favicon.ico in the root directory - no tag necessary -->

<!-- For IE 11, Chrome, Firefox, Safari, Opera -->
<link rel="icon" type="image/png" sizes="16x16" href="/path/to/favicon-16x16.png">
<link rel="icon" type="image/png" sizes="32x32" href="/path/to/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="96x96" href="/path/to/favicon-96x96.png">

⬆ back to top


Facebook Open Graph

<meta property="fb:app_id" content="123456789">
<meta property="og:url" content="">
<meta property="og:type" content="website">
<meta property="og:title" content="Content Title">
<meta property="og:image" content="">
<meta property="og:description" content="Description Here">
<meta property="og:site_name" content="Site Name">
<meta property="og:locale" content="en_US">
<meta property="article:author" content="">

Twitter Card

<meta name="twitter:card" content="summary">
<meta name="twitter:site" content="@site_account">
<meta name="twitter:creator" content="@individual_account">
<meta name="twitter:url" content="">
<meta name="twitter:title" content="Content Title">
<meta name="twitter:description" content="Content description less than 200 characters">
<meta name="twitter:image" content="">

Google+ /

<link href="" rel="publisher">
<meta itemprop="name" content="Content Title">
<meta itemprop="description" content="Content description less than 200 characters">
<meta itemprop="image" content="">


Pinterest lets you prevent people from saving things from your website, according to their help center. The description is optional.

<meta name="pinterest" content="nopin" description="Sorry, you can't save from my website!">

Facebook Instant Articles

<meta charset="utf-8">
<meta property="op:markup_version" content="v1.0">

<!-- The URL of the web version of your article -->
<link rel="canonical" href="">

<!-- The style to be used for this article -->
<meta property="fb:article_style" content="myarticlestyle">


<link rel="alternate" type="application/json+oembed"
title="oEmbed Profile: JSON">
<link rel="alternate" type="text/xml+oembed"
title="oEmbed Profile: XML">

⬆ back to top

Browsers / Platforms

Apple iOS

<!-- Smart App Banner -->
<meta name="apple-itunes-app" content="app-id=APP_ID,affiliate-data=AFFILIATE_ID,app-argument=SOME_TEXT">

<!-- Disable automatic detection and formatting of possible phone numbers -->
<meta name="format-detection" content="telephone=no">

<!-- Add to Home Screen -->
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black">
<meta name="apple-mobile-web-app-title" content="App Title">

<!-- Touch Icons -->
<!-- In most cases, one 180×180px touch icon in the head is enough -->
<link rel="apple-touch-icon" href="/path/to/apple-touch-icon.png">

<!-- Startup Image ( Deprecated ) -->
<link rel="apple-touch-startup-image" href="/path/to/startup.png">

<!-- iOS app deep linking -->
<meta name="apple-itunes-app" content="app-id=APP-ID, app-argument=http/">
<link rel="alternate" href="ios-app://APP-ID/http/">

Apple Safari

<!-- Pinned Site -->
<link rel="mask-icon" href="/path/to/icon.svg" color="red">

Google Android

<meta name="theme-color" content="#E64545">

<!-- Add to home screen -->
<meta name="mobile-web-app-capable" content="yes">
<!-- More info: -->

<!-- Android app deep linking -->
<meta name="google-play-app" content="app-id=package-name">
<link rel="alternate" href="android-app://package-name/http/">

Google Chrome

<link rel="chrome-webstore-item" href="">

<!-- Disable translation prompt -->
<meta name="google" content="notranslate">

Google Chrome Mobile (Android Only)

Since Chrome 31, you can set up your web app to “app mode” like Safari.

<!-- Link to a manifest and define the manifest metadata -->
<!-- The example of manifest.json could be found in the link below -->
<link rel="manifest" href="manifest.json">

<!-- Define your web page as a web app -->
<meta name="mobile-web-app-capable" content="yes">

<!-- Homescreen Icon -->
<link rel="icon" sizes="192x192" href="/path/to/highres-icon.png">

Microsoft Internet Explorer

<meta http-equiv="x-ua-compatible" content="ie=edge">
<meta name="skype_toolbar" content="skype_toolbar_parser_compatible">

<!-- IE10: Disable link highlighting upon tap ( -->
<meta name="msapplication-tap-highlight" content="no">

<!-- Pinned sites ( -->
<meta name="application-name" content="Sample Title">
<meta name="msapplication-tooltip" content="A description of what this site does.">
<meta name="msapplication-starturl" content="">
<meta name="msapplication-navbutton-color" content="#FF3300">
<meta name="msapplication-window" content="width=800;height=600">
<meta name="msapplication-task" content="name=Task 1;action-uri=http://host/Page1.html;icon-uri=http://host/icon1.ico">
<meta name="msapplication-task" content="name=Task 2;action-uri=;icon-uri=http://host/icon2.ico">
<meta name="msapplication-badge" value="frequency=NUMBER_IN_MINUTES;polling-uri=">
<meta name="msapplication-TileColor" content="#FF3300">
<meta name="msapplication-TileImage" content="/path/to/tileimage.jpg">

<meta name="msapplication-config" content="">
<meta name="msapplication-notification" content="frequency=60;polling-uri=;polling-uri2=">
<meta name="msapplication-task-separator" content="1">

⬆ back to top

<!-- iOS -->
<meta property="al:ios:url" content="applinks://docs">
<meta property="al:ios:app_store_id" content="12345">
<meta property="al:ios:app_name" content="App Links">

<!-- Android -->
<meta property="al:android:url" content="applinks://docs">
<meta property="al:android:app_name" content="App Links">
<meta property="al:android:package" content="org.applinks">

<!-- Web Fallback -->
<meta property="al:web:url" content="">

⬆ back to top

Browsers (Chinese)

360 Browser

<!-- Select rendering engine order -->
<meta name="renderer" content="webkit|ie-comp|ie-stand">

QQ Mobile Browser

<!-- Locks the screen into the specified orientation -->
<meta name="x5-orientation" content="landscape/portrait">

<!-- Display this document in fullscreen -->
<meta name="x5-fullscreen" content="true">

<!-- Document will be displayed in "application mode" (full screen, etc.) -->
<meta name="x5-page-mode" content="app">

UC Mobile Browser

<!-- Locks the screen into the specified orientation -->
<meta name="screen-orientation" content="landscape/portrait">

<!-- Display this document in fullscreen -->
<meta name="full-screen" content="yes">

<!-- UC browser will display images even if in "text mode" -->
<meta name="imagemode" content="force">

<!-- Document will be displayed in "application mode"(full screen, forbidding gesture, etc.) -->
<meta name="browsermode" content="application">

<!-- Disabled the UC browser's "night mode" for this document -->
<meta name="nightmode" content="disable">

<!-- Simplify the document to reduce data transfer -->
<meta name="layoutmode" content="fitscreen">

<!-- Disable the UC browser's feature of "scaling font up when there are many words in this document" -->
<meta name="wap-font-scale" content="no">

⬆ back to top



Moving the href attribute to the beginning of an element improves compression when GZIP is enabled, because the href attribute is used in a, base, and link tags.


<link href=",700" rel="stylesheet">

⬆ back to top

Other Resources

⬆ back to top

⬆ back to top

Other Formats

⬆ back to top


⬆ back to top


Open an issue or a pull request to suggest changes or additions.


The HEAD repository consists of two branches:

1. master

This branch consists of the file that is automatically reflected on the website. All changes to the content of the cheat sheet as such should be directed to this file.

Please follow these steps for pull requests:

  • Modify only one tag, or one related set of tags at a time
  • Use double quotes on attributes
  • Don’t include a trailing slash in self-closing elements — the HTML5 spec says they’re optional
  • Consider including a link to documentation that supports your change

2. gh-pages

This branch is responsible for the website. We use Jekyll to deploy the Markdown file through GitHub Pages. All website related modifications must be directed here.

You may want to go through the Jekyll Docs and understand how Jekyll works before working on this branch.


Check out all the super awesome contributors.


Josh Buchea



⬆ back to top

Webdesign für Handwerk & Handwerksbetriebe




Frankfurt am Main. Webdesign für eine gemeinützige Organisation mit Sitz in Frankfurt am Main. Social Media Anbindung. WordPress. Webhosting. „Elternwahlrecht – Kampagne für ein politisches Elternwahlrecht“


Ein Corporate Blog, einfacher Firmenblog, kommuniziert die Kompetenzen von Mitarbeitern und Unternehmen für Kunden, Geschäftspartner und Öffentlichkeit. Der Mitarbeiter wird zum Blogger und fördert die Glaubwürdigkeit und Brand Awareness des Unternehmens.
Corporate Blogging fördert die Glaubwürdigkeit von Unternehmen, Mitarbeitern und deren Kompetenzen.

Corporate Blog

Gleichzeitig ist ein Corporate Blog zentraler Channel im Marketing Mix ihres Unternehmens für Publikationen unterschiedlichster Art: Content Marketing zielt die Sichtbarkeit, Online Visibility von Unternehmen im Internet durch Teilen von Beiträgen, Analysen, Infografiken, Podcasts, Videos, Bildergalerien oder Umfragen zu branchenrelevanten Inhalten – somit kommt Ihrem Firmen-Blog die Funktion einer Corporate Publishing Variante die gleichzeitig und nachhaltig die Bindung von Kunden sowie Lead-Generierung vorantreibt.

Damit ihr firmeneigener Blog sich reibungslos in den Kommunikationsmix des Unternehmens einfügt unterstützen unsere Webdesigner Sie von der Konzeption eines responsive Webdesigns über die Wahl eines Content Management Systems bis zur Erstellung einer Progressiven Web App. Ein Corporate Design muss mit den verschiedenen Webseiten des Unternehmens, mit Newslettern, E-Mail Kampagnen sowie mit reichweiten-starken Social Media Kanäle wie Twitter und Facebook eng vernetzt werden und troztdem die Identität des Unternehmens transportieren. Ein Corporate Webdesign entfaltet seine volle Wirkung wenn damit:

  • Kommunikations & Marketing Ziele realisiert werden können
  • eine Content Strategie umgesetzt werden kann
  • die Kommunikation des Unternehmens ausgebaut werden kann und letztlich
  • den steigenden technischen Anforderungen von Suchmaschinen standhält.

Wir unterstützen Unternehmen bei der Einrichtung eines zentralen Corporate Blogs. Wir realisieren die Planung und techn. Umsetzung Ihres Blog-Konzepts: von den ersten Anforderungen, der Themenfindung und Realisierung einer Content Strategie.

EDIFICIA Rechtsanwälte

WordPress Website, WordPress Multi Language, Responsive Webdesign, Website Optimierung, Website bei Google anmelden.
International Law Firm Frankfurt
International Law Firm Germany

Mit Material Design und Material Design Lite wird eine Library von Tools und Richtlinien diverser Web-Elemente für Entwickler bereit gestellt.
– alles an einem Ort

Website Design ist die Kunst der kontinuierlichen Problemlösung und Optimierung – ein aktiver Zyklus der Erforschung und Validierung von Bedürfnissen, Handwerk und Entwicklung von Ideen und die Schaffung von Lösungen. Im Laufe seines Lebens ist ein digitales Produkt von vielen Händen geprägt. Die Auswirkungen dieser Zusammenarbeit sind in der Qualität der Identität und Umsetzung eines Produktes sowie in der Stärke der von ihm erstellten Community zu sehen.

Google Material Design versucht für Designer und Entwicker eine gemeinsame Sprache zu etablieren, um Agenturen und Unternehmen dabei zu helfen, Stil, Branding, Interaktion und Bewegung unter einem zusammenhängenden Satz von Prinzipien zu vereinen.

Wir glauben, dass ein besserer Design-Prozess bessere Produkte liefert, weshalb wir Material erweitern, um ein System zu sein, das die Prinzipien des guten Designs unterstützt und die Kommunikation und Produktivität mit neuen Werkzeugen und Inspirationen stärkt. Wir hoffen, dass diese Ressourcen Teams helfen, ihr größtes Designpotential zu verwirklichen, und wir sind gespannt auf die Ergebnisse.

Google Material Design

  • Material Design Google icons
  • Material Design Examples
  • Material Design Website
  • Material Design Download
  • Material Design Android
  • Material Design deutsch
  • Material Design CSS 5
  • Material Design Demo

Material Design Android

Material Design Download

Material Design —
Material Design Lite —

WordPress Landing Page, WordPress Website, Responsive Webdesign, Website bei Google anmelden.  Top-Performer auf Immobilienscout 24
Frankfurt am Main

Responsive Webdesign, WordPress Website, Webdesign Frankfurt, Webdesign & Suchmaschinenoptimierung


Was ist ein One Pager?

One Pager Definition, Onepager Bedeutung. One Pager Erstellen, Onepager Website.

Onepager Examples, One Pager Vorlage

WordPress Website, Responsive Webdesign, Google AdWords, Landing Page Design, Conversion Optimierung.

Ein Schachbrett für jede Grundschulklasse