{"id":24183,"date":"2009-08-10T00:00:00","date_gmt":"2009-08-10T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/optimize-your-crawling-and-indexing\/"},"modified":"2009-08-10T00:00:00","modified_gmt":"2009-08-10T00:00:00","slug":"optimize-your-crawling-and-indexing","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/optimize-your-crawling-and-indexing\/","title":{"rendered":"Optimize your crawling and indexing"},"content":{"rendered":"<p class=\"gargardate\">Monday, August 10, 2009<\/p>\n<aside class=\"key-point\">It&#8217;s been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore). For current information, check out our <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/how-search-works\/\">Advanced guide to how Search works<\/a>.<\/aside>\n<p>\n  Many questions about website architecture, crawling and indexing, and even ranking issues can be<br \/>\n  boiled down to one central issue:<br \/>\n  <strong>How easy is it for search engines to crawl your site?<\/strong><br \/>\n  We&#8217;ve spoken on this topic at a number of recent events, and below you&#8217;ll find our presentation<br \/>\n  and some key takeaways on this topic.\n<\/p>\n<p>\n  <a href=\"https:\/\/googleblog.blogspot.com\/2008\/07\/we-knew-web-was-big.html\" class=\"external-link\">The Internet is a <em>big<\/em>place<\/a>;<br \/>\n  new content is being created all the time. Google has a finite number of resources, so when faced<br \/>\n  with the nearly-infinite quantity of content that&#8217;s available online, Googlebot is only able to<br \/>\n  find and crawl a percentage of that content. Then, of the content we&#8217;ve crawled, we&#8217;re only able<br \/>\n  to index a portion.\n<\/p>\n<p>\n  URLs are like the bridges between your website and a search engine&#8217;s crawler: crawlers need to be<br \/>\n  able to find and cross those bridges (that is, find and crawl your URLs) in order to get to your<br \/>\n  site&#8217;s content. If your URLs are complicated or redundant, crawlers are going to spend time<br \/>\n  tracing and retracing their steps; if your URLs are organized and lead directly to distinct<br \/>\n  content, crawlers can spend their time accessing your content rather than crawling through empty<br \/>\n  pages, or crawling the same content over and over via different URLs.\n<\/p>\n<p>\n  In the slides above you can see some examples of what <em>not<\/em> to do\u2014real-life examples<br \/>\n  (though names have been changed to protect the innocent) of homegrown URL hacks and encodings,<br \/>\n  parameters masquerading as part of the URL path, infinite crawl spaces, and more. You&#8217;ll also<br \/>\n  find some recommendations for straightening out that labyrinth of URLs and helping crawlers find<br \/>\n  more of your content faster, including:\n<\/p>\n<ul>\n<li>\n    <strong>Remove user-specific details from URLs.<\/strong> URL parameters that don&#8217;t change the<br \/>\n    content of the page\u2014like session IDs or sort order\u2014can be removed from the URL and put into a<br \/>\n    cookie. By putting this information in a cookie and<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/redirects-and-google\/\"><code>301<\/code> redirecting<\/a><br \/>\n    to a &#8220;clean&#8221; URL, you retain the information and reduce the number of URLs pointing to that same<br \/>\n    content.\n  <\/li>\n<li>\n    <strong>Rein in infinite spaces.<\/strong> Do you have a calendar that links to an infinite<br \/>\n    number of past or future dates (each with their own unique URL)? Do you have paginated data<br \/>\n    that returns a<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/how-http-status-codes-affect-googles-crawlers\/\">status code of <code>200<\/code><\/a><br \/>\n    when you add <code>&amp;page=3563<\/code> to the URL, even if there aren&#8217;t that many pages of<br \/>\n    data? If so, you have an<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/to-infinity-and-beyond-no\/\">infinite crawl space<\/a> on your<br \/>\n    website, and crawlers could be wasting their (and your!) bandwidth trying to crawl it all.<br \/>\n    Consider<br \/>\n    <a href=\"https:\/\/www.google.com\/support\/webmasters\/bin\/answer.py?answer=76401\" class=\"external-link\">these tips<\/a><br \/>\n    for reining in infinite spaces.\n  <\/li>\n<li>\n    <strong>Disallow actions Googlebot can&#8217;t perform.<\/strong> Using your<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/robots-txt-intro\/\">robots.txt file<\/a>, you can disallow crawling of<br \/>\n    login pages, contact forms, shopping carts, and other pages whose sole functionality is<br \/>\n    something that a crawler can&#8217;t perform. (Crawlers are notoriously cheap and shy, so they don&#8217;t<br \/>\n    usually &#8220;Add to cart&#8221; or &#8220;Contact us.&#8221;) This lets crawlers spend more of their time crawling<br \/>\n    content that they can actually do something with.\n  <\/li>\n<li>\n    <strong>One man, one vote. One URL, one set of content.<\/strong> In an ideal world, there&#8217;s a<br \/>\n    one-to-one pairing between URL and content: each URL leads to a unique piece of content, and<br \/>\n    each piece of content can only be accessed via one URL. The closer you can get to this ideal,<br \/>\n    the more streamlined your site will be for crawling and indexing. If your CMS or current site<br \/>\n    setup makes this difficult, you can<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/specify-canonical\/\">use the <code>rel=\"canonical\"<\/code> element<\/a><br \/>\n    to indicate the preferred URL for a particular piece of content.\n  <\/li>\n<\/ul>\n<p>\n  If you have further questions about optimizing your site for crawling and indexing, check out some<br \/>\n  of our <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/google-search-crawling-and-indexing-faq\/\">previous writing<\/a> on the subject, or stop by<br \/>\n  our<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/community\" class=\"external-link\">Help Forum<\/a>.<\/p>\n<p class=\"byline-author\">\n  Posted by<br \/>\n  <a href=\"https:\/\/developers.google.com\/search\/blog\/authors\/susan-moskwa\" rel=\"author\" class=\"external-link\">Susan Moskwa<\/a>,<br \/>\n  Webmaster Trends Analyst<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Monday, August 10, 2009 It&#8217;s been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore). For current information, check out our Advanced guide to how Search works. Many questions about website architecture, crawling and indexing, [&hellip;]<\/p>\n","protected":false},"menu_order":85534,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-24183","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-blog"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24183","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/24183\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/26722"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=24183"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=24183"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=24183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}