[[["เข้าใจง่าย","easyToUnderstand","thumb-up"],["แก้ปัญหาของฉันได้","solvedMyProblem","thumb-up"],["อื่นๆ","otherUp","thumb-up"]],[["ไม่มีข้อมูลที่ฉันต้องการ","missingTheInformationINeed","thumb-down"],["ซับซ้อนเกินไป/มีหลายขั้นตอนมากเกินไป","tooComplicatedTooManySteps","thumb-down"],["ล้าสมัย","outOfDate","thumb-down"],["ปัญหาเกี่ยวกับการแปล","translationIssue","thumb-down"],["ตัวอย่าง/ปัญหาเกี่ยวกับโค้ด","samplesCodeIssue","thumb-down"],["อื่นๆ","otherDown","thumb-down"]],[],[[["\u003cp\u003e404 errors on your site generally do not negatively impact your site's search ranking in Google.\u003c/p\u003e\n"],["\u003cp\u003eSoft 404 errors, where a page displays a 404 message but returns a success code like 200, can negatively impact your site's indexing and should be addressed.\u003c/p\u003e\n"],["\u003cp\u003eIf you move content to a new URL, implement a 301 redirect to guide users and search engines to the correct location.\u003c/p\u003e\n"],["\u003cp\u003eYou can safely ignore 404 errors for URLs that never existed on your site, as Google might crawl linked URLs regardless of their existence.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's URL removal tool is not designed for removing 404 errors from Webmaster Tools but rather for removing specific URLs from search results.\u003c/p\u003e\n"]]],["`404` errors are normal and don't directly harm a site's search ranking. Ensure old content returns a `404` or `410` code, and redirect misspelled URLs with `301` to capture traffic. Soft `404` errors, where a non-404 code is used for non-existent pages, should be avoided. If content is moved, use `301` redirects; otherwise, use `404` or `410`. Ignore `404` errors for URLs that never existed. Fixing errors can be confirmed using \"Fetch as Googlebot.\" The URL removal tool doesn't affect Webmaster Tools' error reports.\n"],null,["# Do 404 errors hurt my site?\n\nMonday, May 02, 2011\n\n\nSo there you are, minding your own business, using Webmaster Tools to check out how awesome your\nsite is... but, wait! The\n[Crawl errors](https://support.google.com/webmasters/answer/7440203)\npage is full of\n[`404 (Not found)` errors](/search/blog/2008/08/its-404-week-at-webmaster-central)!\n*Is disaster imminent??*\n\n\nFear not, my young padawan. Let's take a look at `404` errors and how they do (or do\nnot) affect your site:\n\n\n**Q: Do the `404` errors reported in Webmaster Tools affect my site's ranking?** \n\nA: `404` errors are a perfectly normal part of the web; the Internet is always\nchanging, new content is born, old content dies, and when it dies it (ideally) returns a\n`404` HTTP response code. Search engines are aware of this; we have `404`\nerrors on our own sites, as you can see above, and we find them all over the web. In fact, we\nactually *prefer* that, when you get rid of a page on your site, you make sure that it\nreturns a proper `404` or `410` response code (rather than a `soft\n404`). Keep in mind that in order for our crawler to see the HTTP response code of a\nURL, it has to be able to crawl that URL---if the URL is blocked by your robots.txt file we won't be\nable to crawl it and see its response code. The fact that some URLs on your site no longer exist or\nreturn `404` errors does not affect how your site's other URLs (the ones that return\n[`200 (Success)`\nstatus codes](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes)) perform in our search results.\n\n\n**Q: So `404` errors don't hurt my website at all?** \n\nA: If some URLs on your site `404`, this fact alone does not hurt you or count against\nyou in Google's search results. However, there may be other reasons that you'd want to address\ncertain types of `404` errors. For example, if some of the pages that\n`404` are pages you actually care about, you should look into why we're seeing\n`404` errors when we crawl them! If you see a misspelling of a legitimate URL\n(www.example.com/awsome instead of www.example.com/awesome), it's likely that someone intended to\nlink to you and simply made a typo. Instead of returning a `404`, you could\n`301` redirect the misspelled URL to the correct URL and capture the intended traffic\nfrom that link. You can also make sure that, when users do land on a `404` page on\nyour site, you\n[help them find what they were looking for](/search/docs/crawling-indexing/http-network-errors#pagegone)\nrather than just saying \"`404` Not found.\"\n\n\n**Q: Tell me more about \"`soft 404` errors.\"** \n\nA: A\n[`soft 404`](/search/docs/crawling-indexing/http-network-errors#soft-404-errors)\nis when a web server returns a response code other than `404` (or `410`) for\na URL that doesn't exist. A common example is when a site owner wants to return\n[a pretty `404` page with helpful information for their users](/search/blog/2008/08/make-your-404-pages-more-useful),\nand thinks that in order to serve content to users, they have to return a `200`\nresponse code. Not so! You can return a `404` response code *while* serving\nwhatever content you want. Another example is when a site redirects any unknown URLs to their\nhome page instead of returning `404` errors. Both of these cases can have negative\neffects on our understanding and indexing of your site, so we recommend making sure your server\nreturns the proper response codes for nonexistent content. Keep in mind that *just because a\npage **says** \"`404` Not Found,\" doesn't mean it's actually returning a\n`404` HTTP response code* ---use the\n[Fetch as Googlebot](https://www.google.com/support/webmasters/bin/answer.py?answer=158587)\nfeature in Webmaster Tools to double-check. If you don't know how to configure your server to\nreturn the right response codes, check out your web host's help documentation.\n\n\n**Q: How do I know whether a URL should `404`, or `301`, or\n`410`?** \n\nA: When you remove a page from your site, think about whether that content is moving somewhere\nelse, or whether you no longer plan to have that type of content on your site. If you're moving\nthat content to a new URL, you should `301` redirect the old URL to the new URL---that\nway when users come to the old URL looking for that content, they'll be automatically redirected\nto something relevant to what they were looking for. If you're getting rid of that content\nentirely and don't have anything on your site that would fill the same user need, then the old URL\nshould return a `404` or `410`. Currently Google treats\n`410 (Gone)` the same as `404 (Not found)`, so it's immaterial to us whether\nyou return one or the other.\n\n\n**Q: Most of my `404` errors are for bizarro URLs that never existed on my site.\nWhat's up with that? Where did they come from?** \n\nA: If Google finds a link somewhere on the web that points to a URL on your domain, it may try to\ncrawl that link, whether any content actually exists there or not; and when it does, your server\n*should* return a `404` if there's nothing there to find. These links could be\ncaused by someone making a typo when linking to you, some type of misconfiguration (if the links\nare automatically generated, for example, by a CMS), or by Google's increased efforts to recognize\nand crawl links embedded in JavaScript or other embedded content; or they may be part of a quick\ncheck from our side to see how your server handles unknown URLs, to name just a few. If you see\n`404` errors reported in Webmaster Tools for URLs that don't exist on your site, you\ncan safely ignore them. We don't know which URLs are important to you vs. which are supposed to\n`404`, so we show you *all* the `404` errors we found on your site and\nlet you decide which, if any, require your attention.\n\n\n**Q: Someone has scraped my site and caused a bunch of `404` errors in the\nprocess. They're all \"real\" URLs with other code tacked on, like\n`https://www.example.com/images/kittens.jpg\" width=\"100\" height=\"300\" alt=\"kittens\"/\u003e`\nWill this hurt my site?** \n\nA: Generally you don't need to worry about \"broken links\" like this hurting your site. We\nunderstand that site owners have little to no control over people who scrape their site, or who\nlink to them in strange ways. If you're a whiz with the\n[regex](https://www.google.com/search?q=define:regex),\nyou could consider\n[redirecting these URLs](/search/docs/crawling-indexing/301-redirects), but generally\nit's not worth worrying about. Remember that you can also file a\n[takedown request](https://www.google.com/dmca)\nwhen you believe someone is stealing original content from your website.\n\n\n**Q: Last week I fixed all the `404` errors that Webmaster Tools reported, but\nthey're still listed in my account. Does this mean I didn't fix them correctly? How long will it\ntake for them to disappear?** \n\nA: Take a look at the 'Detected' column on the Crawl errors page---this is the most recent date on\nwhich we detected each error. If the date(s) in that column are from before the time you fixed the\nerrors, that means we haven't encountered these errors since that date. If the dates are more\nrecent, it means we're continuing to see these `404` errors when we crawl.\n\n\nAfter implementing a fix, you can check whether our crawler is seeing the new response code by\nusing\n[Fetch as Googlebot](https://www.google.com/support/webmasters/bin/answer.py?answer=158587).\nTest a few URLs and, if they look good, these errors should soon start to disappear from your\nlist of Crawl errors.\n\n\n**Q: Can I use Google's URL removal tool to make `404` errors disappear from my\naccount faster?**\n\n\nA: No; the URL removal tool removes URLs from Google's search results, not from your Webmaster\nTools account. It's designed for urgent removal requests only, and using it isn't necessary when a\nURL already returns a `404`, as such a URL will drop out of our search results\nnaturally over time. See the bottom half of\n[this blog post](/search/blog/2010/05/url-removal-explained-part-iv-tracking)\nfor more details on what the URL removal tool can and can't do for you.\n\n\nStill want to know more about `404` errors? Check out\n[`404` week](/s/results/search/blog?q=%22404+week%22) from our blog, or drop\nby our\n[Webmaster Help Forum](https://support.google.com/webmasters/community).\n\n\nPosted by\n[Susan Moskwa](/search/blog/authors/susan-moskwa),\nWebmaster Trends Analyst"]]
