The document provides an overview of important SEO elements including HTML tags, metadata, URLs, and more. It covers topics such as title tags, meta descriptions, image optimization, HTTP status codes, and XML sitemaps. Guidelines are given for issues like duplicate content, canonicalization, and internationalization.
The document provides an overview of important SEO elements including HTML tags, metadata, URLs, and more. It covers topics such as title tags, meta descriptions, image optimization, HTTP status codes, and XML sitemaps. Guidelines are given for issues like duplicate content, canonicalization, and internationalization.
Original Description:
SEO Cheat Sheet for the web developers & web masters.
The document provides an overview of important SEO elements including HTML tags, metadata, URLs, and more. It covers topics such as title tags, meta descriptions, image optimization, HTTP status codes, and XML sitemaps. Guidelines are given for issues like duplicate content, canonicalization, and internationalization.
The document provides an overview of important SEO elements including HTML tags, metadata, URLs, and more. It covers topics such as title tags, meta descriptions, image optimization, HTTP status codes, and XML sitemaps. Guidelines are given for issues like duplicate content, canonicalization, and internationalization.
Some of the key takeaways from the document include focusing on descriptive page titles and meta descriptions, using keywords appropriately in content and links, and implementing strategies like canonicalization and internationalization.
Some important HTML elements for SEO mentioned are the <title> tag, <meta> description tag, and image alt attributes. Proper use of these elements can help with search engine optimization.
Some common HTTP status codes mentioned are 200 (OK), 301 (permanent redirect), 302 (temporary redirect), 404 (not found), and 500 (server error). The document provides brief explanations of the meanings of these status codes.
The Web Developers
SEO Cheat Sheet
Important HTML Elements Title tag Meta Description Tag Image Best Practices HTTP Status Codes Canonicalization 200 OK/Success 301 Permanent Redirect 302 Temporary Redirect 404 Not Found 410 Gone (permanently removed) 500 Server Error 503 Unavailable (retry later) Webmaster Tools <head> <title>Page Title</title> </head> <head> <meta name="description" content="This is an example."> </head> No longer than 60-80 characters Important keywords near the beginning Each title should be unique No longer than 155 characters Each description should be unique Well written descriptions influence click-through rate Hyperlinks Text Link SEO Tips for URLs Common Duplicate Homepage URLs NoFollowed Link Image Link Hyperlinking Best Practices Google Webmaster Tools Bing Webmaster Tools Yandex Webmaster Tools Canonicalized URL Best Practices <a href="http://www.example.com/ webpage.html">Keyword in Anchor Text</a> <a href="http://www.example.com/webpage.html"><img src="img/ keyword.jpg" alt="keyword" width="100" height="100"></a> <a href="http://www.example.com/ webpage.html" rel="nofollow"> Keyword in Anchor Text</a> Limit links per page to roughly 150 Use "nofollow" for paid links and untrusted content For image links, the alt attribute serves as anchor text http://www.example.com/ rel="canonical" <link href="http://www.example.com/" rel="canonical" /> <img src="img/keyword.jpg" alt="keyword" width="100" height="100"> http://www.example.com http://example.com http://www.example.com/index.html http://example.com/index.html http://example.com/index.html&sessid=123 1. Protocol 2. Subdomain 3. Root Domain 4. Top-Level Domain 5. Subfolder/Path 6. Page 7. Parameter 8. Named Anchor Use descriptive keywords in URLs Watch for duplicate content when using multiple parameters When possible, place content on the same subdomain to preserve domain authority Recommended: http://example.com/blog Less Ideal: http://blog.example.com https://www.google.com/webmasters/tools/home http://www.bing.com/toolbox/webmaster/ http://webmaster.yandex.com/ URL Best Practices Common URL Elements ht tp://store.example.com/category/keyword?id=123#top 1 2 3 4 5 6 7 8 V2. 2 | moz.com | 2013-2014 SEOmoz More information at http://mz.cm/HTTP-codes More information at http://mz.cm/canonical V2. 2 | moz.com | 2013-2014 SEOmoz 2 The Web Developers SEO Cheat Sheet Important User-agents Robot Control Syntax Sitemap Syntax For robots.txt, robots meta tags & X-Robots-Tag Googlebot (can be used as default for most Google crawlers) Googlebot-News Googlebot-Image Mediapartners (Adsense) Bingbot Yandexbot Rogerbot Baiduspider FacebookExternalHit Googlebot (Mobile Smartphones) Googlebot-Mobile Mediapartners-Google (Mobile Adsense) or Mediapartners User-agent in HTTP(S) requests Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) While robots.txt may restrict crawling, only Meta Robots and X-Robots will remove URLs from search results. Nofollow (do not follow links) Noindex (do not index) Noarchive (do not archive) NoODP (Do not show Open Directory Project description) ...Or combined (noindex, nofollow) If the robots <META> tag is not defined, the default is "INDEX,FOLLOW" Googlebot-News Googlebot-Image/1.0 Mediapartners-Google Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots) Mozilla/5.0 (compatible; rogerBot/1.0; UrlCrawler; http://moz.com/help/pro/ rogerbot-crawler) Mozilla/5.0 (compatible; Baiduspider/2.0; +/web/20130307230956/http://www. baidu.com/search/spider.html) facebookexternalhit/1.1 (+http://www. facebook.com/externalhit_uatext.php) Mozilla/5.0 (iPhone; CPU iPhone OS 6_0 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A5376e Safari/8536.25 (compatible; Googlebot/2.1; +http://www. google.com/bot.html) [various mobile device types] (compatible; Googlebot-Mobile/2.1; +http://www. google.com/bot.html) [various mobile device types] (compatible; Mediapartners-Google/2.1; +http://www. google.com/bot.html) Robots.txt Robots Best Practices Arguments can be: X-Robots <?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <url> <loc>http://www.example.com/</loc> <lastmod>1970-01-01</lastmod> <changefreq>monthly</changefreq> <priority>0.8</priority> </url> </urlset> <?xml version="1.0" encoding="UTF-8"?> <sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <sitemap> <loc>http://www.example.com/sitemap1.xml.gz</loc> <lastmod>2004-10-01T18:23:17+00:00</lastmod> </sitemap> <sitemap> <loc>http://www.example.com/sitemap2.xml.gz</loc> <lastmod>2005-01-01</lastmod> </sitemap> </sitemapindex> XML Sitemaps Sitemap Index File Meta Robots Location: http://example.com/robots.txt Location: Sent in the HTTP headers Location: In the html <head> More information at http://www.robotstxt.org/robotstxt.html More information at http://noarchive.net/xrobots/ More information at http://www.robotstxt.org/meta.html User-agent: googlebot Disallow: /no-google.html Sitemap: http://example.com/sitemap.xml X-Robots-Tag: noindex <meta name="ROBOT NAME" content="ARGUMENTS" /> http://www.example.com/sitemap.xml http://www.example.com/sitemap.xml.gz http://www.example.com/sitemap.gz Default Locations Mobile News Image Video Other Common Sitemap Types: V2. 2 | moz.com | 2013-2014 SEOmoz 3 The Web Developers SEO Cheat Sheet Important Metadata Google Authorship & Publisher Pagination <head> <meta property="og:title" content="Title Goes Here"> <meta property="og:description" content="description-goes-here"> <meta property="og:type" content="your-content-type-goes-here"> (e.g., "article") <meta property="og:url" content="http://www.your-site.com/"> <meta property="og:image" content="http://www.your-site.com/image.jpg"> <meta property="og:site_name" content="your-site-name"> <meta property="fb:admins" content="your-Facebook-page-user-ID"> </head> <a href="[profile_ url]?rel=author">Google</a> <a href="[profile_ url]?rel=publisher">Google</a> <head> <meta name="twitter:card" content="summary"> <meta name="twitter:url" content="http://www.example.com/your-url-goes-here/"> <meta name="twitter:title" content="Title Goes Here"> <meta name="twitter:description" content="Your description goes here."> <meta name="twitter:image" content="http://example.com/image.jpg"> </head> <html itemscope itemtype="http://schema.org/Article"> <head> <meta itemprop="name" content="Title Goes Here"> <meta itemprop="description" content="Description Goes Here"> <meta itemprop="image" content="http://example.com/image.jpg"> </head> Facebook Open Graph Twitter Cards Google+ Google+ Authorship Google+ Publisher More information at https://dev.twitter.com/docs/cards More information at https://developers.google.com/+/web/snippet/ More information at https://developers.facebook.com/docs/opengraph/ More information at http://mz.cm/google-author More information at http://mz.cm/rel-next More information at http://mz.cm/google-publisher Google+ will extract information from Open Graph properties, title and meta description tags, or Schema.org microdata (recommended). author information in Google search results: Use rel="next" and rel="prev" in the <head> section to indicate the relationship between paginated URLs First Page - http://example.com/article <link rel="next" href="http://example.com/article?pg=2"> Second Page - http://example.com/article?pg=2 <link rel="prev" href="http://example.com/article"> <link rel="next" href="http://example.com/article?pg=3"> Final Page - http://example.com/article?pg=3 <link rel="prev" href="http://example.com/article?pg=2"> businesses, brands, products and organizations: Link your content to your Google+ profile Link your homepage to your Google+ profile Link to your website from your Google+ page's profile Link back to your site from the Contributor section of your Google+ profile 1 For 2 V2. 2 | moz.com | 2013-2014 SEOmoz 4 The Web Developers SEO Cheat Sheet Targeting Multiple Languages Mobile Web Development Declare language attribute in the HTML element Responsive Design Separate URLs HTML version in <head> Sitemap version Annotate alternate language & country versions of content 1 3 ccTLDs (Country Level Only) Subdirectories with gTLDS Subdomains with gTLDS example.de example.com/de/ de.example.com/ URL Structures for Country & Language Targeting rel="alternate" hreflang="x" <html lang="fr"> <link rel="alternate" hreflang="x-default" href="http://www.example.com/" /> (Specifies Default) <link rel="alternate" hreflang="de" href="http://example.com/de/" /> (Specifies Language) <link rel="alternate" hreflang="de-ES" href="http://example.com/de-es/" /> (Specifies Language + Region) <?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"> <url> <loc>http://example.com/english</loc> <xhtml:link rel="alternate" hreflang="de" href="http://example.com/deutsch/" /> <xhtml:link rel="alternate" hreflang="en" href="http://example.com/english/" /> </url> <url> <loc>http://example.com/deutsch/</loc> <xhtml:link rel="alternate" hreflang="en" href="http://example.com/english/" /> <xhtml:link rel="alternate" hreflang="de" href="http://www.example.com/deutsch/" /> </url> </urlset> Uses CSS to alter the rendering of the page on the device using media queries /* Phones */ @media (max-width: 767px) { ... } /* Tablets to Desktops */ @media (min-width: 768px) and (max-width: 992px) { ... } /* Large devices */ @media (min-width: 1200px) { ... } Identify mobile and desktop versions using rel="alternate" and rel="canonical" Example: Desktop page: http://example.com/ <link rel="alternate" media="only screen and (max- width: 640px)" href="http://m.example.com/"/> Mobile page: http://m.example.com/ <link rel="canonical" href="http://example.com/"/> Popular Languages Popular Regions zh Chinese es Spanish en English ar Arabic hi Hindi CN China US United States IN India JP Japan BR Brazil More language codes can be found at http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes More region codes can be found at http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 Dynamic Serving via Vary HTTP Header 2 Serves different HTML and CSS on the same URL, varied by user agent (...rest of HTTP response headers...) HTTP/1.1 200 OK Content-Type: text/html Vary: User-Agent Content-Length: 5710