🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 26 (from laksa114)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa026.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://www.semrush.com/blog/http-status-codes/\')), getAhrefsUnparsedNoserviceFromURL(\'https://www.semrush.com/blog/http-status-codes/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/www.semrush.com\/blog\/http-status-codes\/","crawl_time":1774635702,"first_indexed_time":0,"http_code":200,"src_unparsed":"com,semrush!www,\/blog\/http-status-codes\/ s443","src_root_hash":"7464484988195878426","history_drop_reason":null,"meta_title":"HTTP Status Codes Explained: Full List & Impact on SEO","meta_descriptions":["Learn what HTTP status codes are, what different codes mean, and how they impact search visibility."],"attrs_boilerpipe_text":"What Are HTTP Status Codes?\nHTTP status codes are three-digit numbers servers generate in response to a client (e.g., a browser) request. They indicate whether the request was completed successfully.\nFor example, a 404 error is a common HTTP status code you might have seen.\nIf you’re a website owner, HTTP status codes give you important information for improving your website’s functionality and user experience. And they can impact your SEO.\nCategories of HTTP Status Codes\nThere are five categories of HTTP status codes:\n1XX (informational codes)\n: The server received the request and is processing it\n2XX (success codes)\n: The server successfully received and processed the request\n3XX (redirection codes)\n:The server received the request, but there’s a redirect to another destination (\n301 or 302\nare common)\n4XX (client error codes)\n:The requested resource couldn’t be found or reached due to a client error\n5XX (server error codes)\n: The server ran into an error when processing the request\nA Complete List of HTTP Status Codes\nCode\nMeaning\n1XX: Informational Responses\n100: Continue\nThe server has received the initial request and is ready for the client to send the rest if it hasn’t already\n101: Switching protocols\nThe server agrees to accept the client’s request to change to a different protocol\n102: Processing\nThe server has received the request but hasn’t completed it. This code has been deprecated.\n103: Early hints\nThe server sends hints about the expected final response while the response is still being processed\n2XX: Success Codes\n200: OK\nThe request was successful. The specific response depends on the request method (GET, PUT, etc.).\n201: Created\nThe request worked, so a new resource was created\n202: Accepted\nThe request was accepted but hasn’t been processed\n203: Non-authoritative information\nThe data returned is from a third party rather than from the original server\n204: No content\nThe request was successful, but there's no content\n205: Reset content\nThe request was successful, and the user agent (e.g., browser) should reset the document\n206: Partial content\nThe server is only sending part of the requested resource\n207: Multi status\nProvides the statuses of multiple operations within a single response\n208: Already reported\nTells the client that a resource’s information has already been included earlier in the response and won’t be repeated\n226: IM used (HTTP delta encoding)\nThe server successfully handled the request and returned a version of the resource that includes only the changes—not the full resource\n3XX: Redirection Codes\n300: Multiple choices\nIndicates there are multiple possible responses, and the user or client needs to choose one \n301: Moved permanently\nThe resource has permanently moved to a new web address. The server provides the new URL.\n302: Found\nThe resource has temporarily moved to a different web address. But it might move again.\n303: See other\nThe server is telling the client to get the resource from another location using a standard GET request\n304: Not modified\nThe response hasn’t changed, so the client can keep using the cached version\n305: Use proxy\nIndicates the client should use a proxy to access the resource. This code has been deprecated.\n307: Temporary redirect\nThe resource has temporarily moved, and the client should use the same HTTP method (e.g., POST) as in the previous request\n308: Permanent redirect\nThe resource has permanently moved, and the client must use the same HTTP method as in the previous request\n4XX: Client Error Codes\n400: Bad request\nThe server can’t process the request because of a client error\n401: Unauthorized\nThe client doesn’t have the proper credentials to access the resource\n402: Payment required\nOriginally meant to indicate the requested resource requires payment, but it’s rarely used and doesn’t have a standard purpose\n403: Forbidden\nThe client isn’t authorized to access the resource, even though the server knows the client’s identity\n404: Not found\nThe server can’t find the resource. Often because a browser is requesting an incorrect URL or the content no longer exists.\n405: Method not allowed\nThe request method (e.g., GET) isn’t allowed for the specified resource\n406: Not acceptable\nThe server can’t provide a response in any format the client specified\n407: Proxy authentication required\nA proxy server needs to authenticate the client before the request can be processed\n408: Request timeout\nThe server gave up waiting because the client didn’t complete the request fast enough\n409: Conflict\nThe request conflicts with what’s already on the server (e.g., two people editing the same content at the same time)\n410: Gone\nThe requested resource has been permanently deleted. And there’s no forwarding address.\n411: Length required\nThe server didn’t accept the request because it didn’t specify how much data is being sent\n412: Precondition failed\nA condition set in the request wasn’t met, so the server didn’t process it\n413: Content too large\nThe amount of data the client is sending is too big for the server to handle\n414: URI too long\nThe requested web address is too long for the server to manage\n415: Unsupported media type\nThe server doesn’t support the format the request is using\n416: Range not satisfiable\nThe requested part of a resource isn’t within the server’s available range\n417: Expectation failed\nThe server couldn’t meet a requirement specified in the request\n421: Misdirected request\nThe request went to the wrong server—one that isn’t set up to handle it\n422: Unprocessable content\nThe server understands the request format but is unable to process it because of issues with the actual data (e.g., wrong values)\n423: Locked\nThe requested resource is locked and inaccessible\n424: Failed dependency\nThe request failed because a related request also failed\n425: Too early\nThe server didn’t process the request because it was too early and might be replayed\n426: Upgrade required\nThe server won’t process the request unless the client switches to a newer or different protocol (like HTTPS)\n428: Precondition required\nThe server requires the request to include certain conditions to ensure safe updates\n429: Too many requests\nThe user sent too many requests too quickly\n431: Request header fields too large\nThe request headers contain too much information for the server to process\n451: Unavailable for legal reasons\nThe requested resource is blocked due to legal reasons\n5XX: Server Error Codes\n500: Internal server error\nThe server encountered an error and couldn’t complete the request\n501: Not implemented\nThe server doesn’t support the request method\n502: Bad gateway\nThe gateway server received an invalid or no response from another server\n503: Service unavailable\nThe server is temporarily unavailable—usually because it’s down for maintenance or overloaded\n504: Gateway timeout\nThe gateway server didn’t get a response from another server in time\n505: HTTP version not supported\nThe server doesn’t support the HTTP version used in the request\n506: Variant also negotiates\nA misconfiguration caused the server to get stuck in a loop when trying to choose between different versions of the resource\n507: Insufficient storage\nThe server doesn’t have enough space to save or process the request\n508: Loop detected\nThe server detects an endless loop while trying to process the request\n510: Not extended\nThe request is missing extensions the server requires for processing\n511: Network authentication required\nThe client needs to authenticate to gain network access\nHow to Check a Webpage’s HTTP Status Codes\nYou can easily check a page’s HTTP status codes using Google Chrome.\nGo to the webpage you want to check.\nRight-click anywhere on the page and select \"\nInspect\n” to open the Developer Tools. Or press “Ctrl + Shift + I” (Windows\/Linux) or “Cmd + Option + I” (Mac).\nClick on the \"\nNetwork\n\" tab in the Developer Tools panel.\nRefresh the page (select “F5” or “Ctrl + R”).\nLook at the list of network requests. \nThe “Status” column shows you a list of HTTP status codes for the page. The first one in the list is the page’s HTML document. \nIt’s also a good idea to audit your site for HTTP status code errors. You can do this easily in Semrush’s\nSite Audit\ntool.\nSimply run a crawl and click on “\nCrawled Pages\n.” \nThe “Status” column will show you the status code of each page so you can see if there are any errors that need fixing.\nThe Implications of Common HTTP Status Codes for SEO\nHere’s what some of the most common status codes mean for your SEO:\n200 (OK)\nA 200 response code is what you’ll want most of your webpages to return. \nIt indicates that a webpage works and is accessible to both people and search engines.\n301 (Moved Permanently)\nA\n301 code\nmeans you’ve permanently moved a page to a new URL. And signals to Google that the old URL in its index should be replaced with the new one. \nImportantly, a 301 redirect also transfers link equity from the old page to the new one. Which preserves your visibility.\n302 (Found\/Temporary Redirect)\nA\n302 redirect\nis a temporary redirect. It can preserve links and rankings while a webpage is temporarily unavailable.\nFor example, if you’re doing website maintenance and want to send users to a temporary holding page. Or you’re carrying out A\/B testing.\nIf a 302 redirect is in place for a long time, Google may start treating it as a 301 redirect. Meaning the old URL will be replaced by the new one in Google’s index.\n404 (Not Found) and 410 (Gone)\nBoth 404 and 410 status codes tell search engines that a page no longer exists, which typically leads to it being removed from the index. \nWhile both ultimately lead to deindexing, a 410 more clearly communicates that the page is gone for good. This can speed up its removalfrom search engine indexes. \n5XX (Server Errors)\nSearch engines have trouble accessing pages with 5XX errors, which can lead to problems with crawling, indexing, and the user experience.\nOver time, this can negatively impact visibility in search results. So it’s important to monitor and resolve 5XX errors promptly.\nThe Impact of HTTP Status Codes on LLMs\nIt’s important to make sure your content’s accessible to tools built on large language models (LLMs), like Google’s AI Overviews, ChatGPT, Perplexity, and Claude. Because it’ll help you gain more visibility in those AI responses. \nStatus codes that signal errors—like 404s and 500s—can block LLMs from seeing your content. Because LLMs find and understand website content similar to traditional search engines. \nWeb developer and AI engineer\nVincent Schmalbach\nnotes: \n“Sites with frequent HTTP status code errors may find their content underrepresented in both search results and AI-generated responses, since both systems require reliable access to index and utilize content effectively.”\nVincent adds the following when talking specifically about 4XX and 5XX status codes:\n“Both 404 and 410 responses mean no content is available, so those pages don't contribute to training data. Server errors like 500s cause crawlers to retry later, but persistent errors result in content being skipped entirely.”\nToby Basalla\n, Founder and Principal Data Consultant at data analytics consultancy Synthelize, warns that a website with unintentional redirect status codes can skew data used to train the actual models if it's scraped all at once. Because those mistakes are difficult to spot among so much data.\nHe reflects on a notable experience running a custom-trained LLM that relied on a scraped dataset: \n“In one case, a client had 180 landing pages misflagged as temporary redirects, and none of it made it into our scraped dataset. Which means, in effect, those pages did not exist to the model.”\nCheck Your Website for HTTP Status Code Errors\nYou should check your website’s HTTP status codes regularly to stay on top of any errors. \nSemrush’s\nSite Audit\ntool makes it easy to identify any of these problems. So you can swiftly address issues and boost your SEO performance.","attrs_markdown":"Products\n\nStart Here\n\n[Semrush One](https:\/\/www.semrush.com\/one\/?utm_source=blog&utm_medium=header&src=header)[Enterprise](https:\/\/enterprise.semrush.com\/?utm_source=blog&utm_medium=header&src=header)[Features](https:\/\/www.semrush.com\/features\/?utm_source=blog&utm_medium=header&src=header)[Request a Demo](https:\/\/www.semrush.com\/kb\/request-demo\/?utm_source=blog&utm_medium=header&src=header)[Talk to Sales](https:\/\/www.semrush.com\/company\/sales\/?utm_source=blog&utm_medium=header&src=header)\n\nFind the Right Tools\n\n[AI Visibility Toolkit](https:\/\/www.semrush.com\/ai-seo\/overview\/?utm_source=blog&utm_medium=header&src=header)[SEO Toolkit](https:\/\/www.semrush.com\/seo\/?utm_source=blog&utm_medium=header&src=header)[Traffic & Market Toolkit](https:\/\/www.semrush.com\/analytics\/traffic\/?utm_source=blog&utm_medium=header&src=header)[Content Toolkit](https:\/\/www.semrush.com\/content\/?utm_source=blog&utm_medium=header&src=header)[Local Toolkit](https:\/\/www.semrush.com\/local-business\/start\/?utm_source=blog&utm_medium=header&src=header)[Social Toolkit](https:\/\/www.semrush.com\/social-media\/?utm_source=blog&utm_medium=header&src=header)[Advertising Toolkit](https:\/\/www.semrush.com\/advertising\/?utm_source=blog&utm_medium=header&src=header)[PR Toolkit](https:\/\/www.semrush.com\/pr-toolkit\/?utm_source=blog&utm_medium=header&src=header)\n\nPlatform\n\n[Integrations](https:\/\/www.semrush.com\/company\/partner-integrations\/?utm_source=blog&utm_medium=header&src=header)[App Center](https:\/\/www.semrush.com\/apps\/?utm_source=blog&utm_medium=header&src=header)[API](https:\/\/developer.semrush.com\/api\/?utm_source=blog&utm_medium=header&src=header)[Data Sources](https:\/\/www.semrush.com\/kb\/997-semrush-data?utm_source=blog&utm_medium=header&src=header)\n\nTop Apps\n\n[AdClarity](https:\/\/www.semrush.com\/apps\/adclarity-advertising-intelligence\/?utm_source=blog&utm_medium=header&src=header)[Exploding Topics](https:\/\/www.semrush.com\/apps\/exploding-topics\/?utm_source=blog&utm_medium=header&src=header)[Other apps](https:\/\/www.semrush.com\/apps\/collection\/most-popular\/?utm_source=blog&utm_medium=header&src=header)\n\n[Pricing](https:\/\/www.semrush.com\/pricing\/?utm_source=blog&utm_medium=header&src=header)\n\nResources\n\nGrow with Semrush\n\n[Blog](https:\/\/www.semrush.com\/blog\/?utm_source=blog&utm_medium=header&src=header)[Knowledge Base](https:\/\/www.semrush.com\/kb\/?utm_source=blog&utm_medium=header&src=header)[Academy](https:\/\/www.semrush.com\/academy\/)[Success Stories](https:\/\/www.semrush.com\/company\/stories\/?utm_source=blog&utm_medium=header&src=header)[AI Visibility Index](https:\/\/ai-visibility-index.semrush.com\/?utm_source=blog&utm_medium=header&src=header)[Webinars](https:\/\/www.semrush.com\/academy\/webinars\/?utm_source=blog&utm_medium=header&src=header)[News](https:\/\/www.semrush.com\/news\/?utm_source=blog&utm_medium=header&src=header)\n\nExplore Free Tools\n\n[AI Visibility Checker](https:\/\/www.semrush.com\/free-tools\/ai-search-visibility-checker\/?utm_source=blog&utm_medium=header&src=header)[SEO Checker](https:\/\/www.semrush.com\/siteaudit\/?utm_source=blog&utm_medium=header&src=header)[Website Traffic Checker](https:\/\/www.semrush.com\/website\/?utm_source=blog&utm_medium=header&src=header)[Keyword Tool](https:\/\/www.semrush.com\/analytics\/keywordmagic\/?utm_source=blog&utm_medium=header&src=header)[Backlink Checker](https:\/\/www.semrush.com\/analytics\/backlinks\/?utm_source=blog&utm_medium=header&src=header)[Top Websites by Traffic](https:\/\/www.semrush.com\/website\/top\/?utm_source=blog&utm_medium=header&src=header)[Explore Other Free Tools](https:\/\/www.semrush.com\/free-tools\/?utm_source=blog&utm_medium=header&src=header)\n\nAbout Semrush\n\n[About Us](https:\/\/www.semrush.com\/company\/?utm_source=blog&utm_medium=header&src=header)[Stats and Facts](https:\/\/www.semrush.com\/stats\/?utm_source=blog&utm_medium=header&src=header)[Affiliate Program](https:\/\/www.semrush.com\/lp\/affiliate-program\/en\/?utm_source=blog&utm_medium=header&src=header)[Contact Us](https:\/\/www.semrush.com\/company\/contacts\/?utm_source=blog&utm_medium=header&src=header)\n\n[Enterprise](https:\/\/enterprise.semrush.com\/?utm_source=blog&utm_medium=header&src=header)\n\n[Login](https:\/\/www.semrush.com\/login\/?utm_source=blog&utm_medium=header&src=header&redirect_to=%2Fblog%2F)[Sign up](https:\/\/www.semrush.com\/signup\/?utm_source=blog&utm_medium=header&src=header)\n\nProducts\n\n[Pricing](https:\/\/www.semrush.com\/pricing\/?utm_source=blog&utm_medium=header&src=header)\n\nResources\n\n[Enterprise](https:\/\/enterprise.semrush.com\/?utm_source=blog&utm_medium=header&src=header)\n\n[Login](https:\/\/www.semrush.com\/login\/?utm_source=blog&utm_medium=header&src=header&redirect_to=%2Fblog%2F)[Sign up](https:\/\/www.semrush.com\/signup\/?utm_source=blog&utm_medium=header&src=header)\n\n[Blog](https:\/\/www.semrush.com\/blog\/)\n\n[SEO](https:\/\/www.semrush.com\/blog\/category\/seo\/)\n\n[Marketing](https:\/\/www.semrush.com\/blog\/category\/marketing\/)\n\n[News & Research](https:\/\/www.semrush.com\/blog\/category\/news\/)\n\n[Product](https:\/\/www.semrush.com\/blog\/category\/product\/)\n\n[Try it for FREE for 7 days](https:\/\/www.semrush.com\/signup\/?custom=ai-seo&redirect_to=%2Fai-seo%2Foverview%2F)Don’t miss out. Try 55+ products for free.\n\n[SEO](https:\/\/www.semrush.com\/blog\/category\/seo\/)\n\n[General SEO](https:\/\/www.semrush.com\/blog\/category\/seo\/general-seo\/)[Keyword Research](https:\/\/www.semrush.com\/blog\/category\/seo\/keyword-research\/)[On-page SEO](https:\/\/www.semrush.com\/blog\/category\/seo\/on-page-seo\/)[Link Building](https:\/\/www.semrush.com\/blog\/category\/seo\/link-building\/)[Local SEO](https:\/\/www.semrush.com\/blog\/category\/seo\/local-seo\/)[Technical SEO](https:\/\/www.semrush.com\/blog\/category\/seo\/technical-seo\/)[Frequently Asked Questions](https:\/\/www.semrush.com\/blog\/category\/seo\/faq\/)\n\n[Marketing](https:\/\/www.semrush.com\/blog\/category\/marketing\/)\n\n[General Marketing](https:\/\/www.semrush.com\/blog\/category\/marketing\/general-marketing\/)[Content](https:\/\/www.semrush.com\/blog\/category\/marketing\/content\/)[Social Media](https:\/\/www.semrush.com\/blog\/category\/marketing\/social-media\/)[Competitor Intelligence & Research](https:\/\/www.semrush.com\/blog\/category\/marketing\/competitor-intelligence-and-research\/)[AI](https:\/\/www.semrush.com\/blog\/category\/marketing\/ai\/)[Paid Advertising](https:\/\/www.semrush.com\/blog\/category\/marketing\/paid-advertising\/)[Video Marketing](https:\/\/www.semrush.com\/blog\/category\/marketing\/video-marketing\/)[Ecommerce](https:\/\/www.semrush.com\/blog\/category\/marketing\/ecommerce\/)[Analytics](https:\/\/www.semrush.com\/blog\/category\/marketing\/analytics\/)\n\n[News & Research](https:\/\/www.semrush.com\/blog\/category\/news\/)\n\n[Original Research & Studies](https:\/\/www.semrush.com\/blog\/category\/news\/original-research-and-studies\/)[Industry News](https:\/\/www.semrush.com\/blog\/category\/news\/industry-news\/)\n\n[Product](https:\/\/www.semrush.com\/blog\/category\/product\/)\n\n[Semrush Enterprise](https:\/\/www.semrush.com\/blog\/category\/product\/semrush-enterprise\/)\n\n[Create free account](https:\/\/www.semrush.com\/signup\/?custom=ai-seo&redirect_to=%2Fai-seo%2Foverview%2F)\n\n1. [Semrush](https:\/\/www.semrush.com\/)\n2. [Blog](https:\/\/www.semrush.com\/blog\/)\n3. [SEO](https:\/\/www.semrush.com\/blog\/category\/seo\/)\n4. [Technical SEO](https:\/\/www.semrush.com\/blog\/category\/seo\/technical-seo\/)\n# HTTP Status Codes Explained: Full List & Impact on SEO\nExpert reviewed\n\nOur subject matter experts have reviewed this article to ensure it meets the highest standard for accurate information and guidance. Learn more about our [editorial standards and process](https:\/\/www.semrush.com\/blog\/editorial-standards\/).\n\nAuthor:[Carlos Silva](https:\/\/www.semrush.com\/blog\/user\/carlos\/)\n\n8 min read\n\nJul 08, 2025\n\nContributor: [Christine Skopec](https:\/\/www.semrush.com\/blog\/user\/205718513\/)\n\nTable of contents\n\n## What Are HTTP Status Codes?\nHTTP status codes are three-digit numbers servers generate in response to a client (e.g., a browser) request. They indicate whether the request was completed successfully.\n\nFor example, a 404 error is a common HTTP status code you might have seen.\n\n![A URL returns a 404 error page.](https:\/\/static.semrush.com\/blog\/uploads\/media\/81\/c2\/81c2c9105fe4a38571c5291d60299a69\/82d45f4b44e16d95fc1551e16f38b6d9\/AD_4nXcVEnCXbIk9M40jL80nMXv4Z-6IzP5icb4e-yjcmbjgz37gPymIwW6ympon2pdzCbhaANz3VqXJUoDUDDsB4qJRKuGODrLfcVNTJYG0kK5tDWpwnzNbJNRWLEy2MT6NJf3Qnts9sw.png)\n\nIf you’re a website owner, HTTP status codes give you important information for improving your website’s functionality and user experience. And they can impact your SEO.\n\n## Categories of HTTP Status Codes\nThere are five categories of HTTP status codes:\n\n- **1XX (informational codes)**: The server received the request and is processing it\n- **2XX (success codes)**: The server successfully received and processed the request\n- **3XX (redirection codes)**:The server received the request, but there’s a redirect to another destination ([301 or 302](https:\/\/www.semrush.com\/blog\/301-vs-302-redirect\/) are common)\n- **4XX (client error codes)**:The requested resource couldn’t be found or reached due to a client error\n- **5XX (server error codes)**: The server ran into an error when processing the request\n## A Complete List of HTTP Status Codes\n|   |   |\n|---|---|\n| **Code** | **Meaning** |\n| **1XX: Informational Responses** |   |\n| 100: Continue | The server has received the initial request and is ready for the client to send the rest if it hasn’t already |\n| 101: Switching protocols | The server agrees to accept the client’s request to change to a different protocol |\n| 102: Processing | The server has received the request but hasn’t completed it. This code has been deprecated. |\n| 103: Early hints | The server sends hints about the expected final response while the response is still being processed |\n| **2XX: Success Codes** |   |\n| 200: OK | The request was successful. The specific response depends on the request method (GET, PUT, etc.). |\n| 201: Created | The request worked, so a new resource was created |\n| 202: Accepted | The request was accepted but hasn’t been processed |\n| 203: Non-authoritative information | The data returned is from a third party rather than from the original server |\n| 204: No content | The request was successful, but there's no content |\n| 205: Reset content | The request was successful, and the user agent (e.g., browser) should reset the document |\n| 206: Partial content | The server is only sending part of the requested resource |\n| 207: Multi status | Provides the statuses of multiple operations within a single response |\n| 208: Already reported | Tells the client that a resource’s information has already been included earlier in the response and won’t be repeated |\n| 226: IM used (HTTP delta encoding) | The server successfully handled the request and returned a version of the resource that includes only the changes—not the full resource |\n| **3XX: Redirection Codes** |   |\n| 300: Multiple choices | Indicates there are multiple possible responses, and the user or client needs to choose one |\n| 301: Moved permanently | The resource has permanently moved to a new web address. The server provides the new URL. |\n| 302: Found | The resource has temporarily moved to a different web address. But it might move again. |\n| 303: See other | The server is telling the client to get the resource from another location using a standard GET request |\n| 304: Not modified | The response hasn’t changed, so the client can keep using the cached version |\n| 305: Use proxy | Indicates the client should use a proxy to access the resource. This code has been deprecated. |\n| 307: Temporary redirect | The resource has temporarily moved, and the client should use the same HTTP method (e.g., POST) as in the previous request |\n| 308: Permanent redirect | The resource has permanently moved, and the client must use the same HTTP method as in the previous request |\n| **4XX: Client Error Codes** |   |\n| 400: Bad request | The server can’t process the request because of a client error |\n| 401: Unauthorized | The client doesn’t have the proper credentials to access the resource |\n| 402: Payment required | Originally meant to indicate the requested resource requires payment, but it’s rarely used and doesn’t have a standard purpose |\n| 403: Forbidden | The client isn’t authorized to access the resource, even though the server knows the client’s identity |\n| 404: Not found | The server can’t find the resource. Often because a browser is requesting an incorrect URL or the content no longer exists. |\n| 405: Method not allowed | The request method (e.g., GET) isn’t allowed for the specified resource |\n| 406: Not acceptable | The server can’t provide a response in any format the client specified |\n| 407: Proxy authentication required | A proxy server needs to authenticate the client before the request can be processed |\n| 408: Request timeout | The server gave up waiting because the client didn’t complete the request fast enough |\n| 409: Conflict | The request conflicts with what’s already on the server (e.g., two people editing the same content at the same time) |\n| 410: Gone | The requested resource has been permanently deleted. And there’s no forwarding address. |\n| 411: Length required | The server didn’t accept the request because it didn’t specify how much data is being sent |\n| 412: Precondition failed | A condition set in the request wasn’t met, so the server didn’t process it |\n| 413: Content too large | The amount of data the client is sending is too big for the server to handle |\n| 414: URI too long | The requested web address is too long for the server to manage |\n| 415: Unsupported media type | The server doesn’t support the format the request is using |\n| 416: Range not satisfiable | The requested part of a resource isn’t within the server’s available range |\n| 417: Expectation failed | The server couldn’t meet a requirement specified in the request |\n| 421: Misdirected request | The request went to the wrong server—one that isn’t set up to handle it |\n| 422: Unprocessable content | The server understands the request format but is unable to process it because of issues with the actual data (e.g., wrong values) |\n| 423: Locked | The requested resource is locked and inaccessible |\n| 424: Failed dependency | The request failed because a related request also failed |\n| 425: Too early | The server didn’t process the request because it was too early and might be replayed |\n| 426: Upgrade required | The server won’t process the request unless the client switches to a newer or different protocol (like HTTPS) |\n| 428: Precondition required | The server requires the request to include certain conditions to ensure safe updates |\n| 429: Too many requests | The user sent too many requests too quickly |\n| 431: Request header fields too large | The request headers contain too much information for the server to process |\n| 451: Unavailable for legal reasons | The requested resource is blocked due to legal reasons |\n| **5XX: Server Error Codes** |   |\n| 500: Internal server error | The server encountered an error and couldn’t complete the request |\n| 501: Not implemented | The server doesn’t support the request method |\n| 502: Bad gateway | The gateway server received an invalid or no response from another server |\n| 503: Service unavailable | The server is temporarily unavailable—usually because it’s down for maintenance or overloaded |\n| 504: Gateway timeout | The gateway server didn’t get a response from another server in time |\n| 505: HTTP version not supported | The server doesn’t support the HTTP version used in the request |\n| 506: Variant also negotiates | A misconfiguration caused the server to get stuck in a loop when trying to choose between different versions of the resource |\n| 507: Insufficient storage | The server doesn’t have enough space to save or process the request |\n| 508: Loop detected | The server detects an endless loop while trying to process the request |\n| 510: Not extended | The request is missing extensions the server requires for processing |\n| 511: Network authentication required | The client needs to authenticate to gain network access |\n## How to Check a Webpage’s HTTP Status Codes\nYou can easily check a page’s HTTP status codes using Google Chrome.\n\nGo to the webpage you want to check.\n\nRight-click anywhere on the page and select \"**Inspect**” to open the Developer Tools. Or press “Ctrl + Shift + I” (Windows\/Linux) or “Cmd + Option + I” (Mac).\n\n![Inspect is highlighted in the right-click menu.](https:\/\/static.semrush.com\/blog\/uploads\/media\/aa\/95\/aa9516794d12beb900e226bb0fb0fc79\/78f5eebd4d8269f38693b57673bc7e38\/AD_4nXdrNGDyEzSOTjveTyCw_QxYjqy3Aad-8yqFRvpJs98mXQLIvNmlsl8EtPvQENQ-AyJ2rLhE4D0JomkOqjDUDMPUbobdVsFs5cDnTRs-20l4sIU7aSrzSCe3QChhDXLaV1AMU7hraQ.png)\n\nClick on the \"**Network**\" tab in the Developer Tools panel.\n\nRefresh the page (select “F5” or “Ctrl + R”).\n\nLook at the list of network requests.\n\nThe “Status” column shows you a list of HTTP status codes for the page. The first one in the list is the page’s HTML document.\n\n![The HTTP status code column is highlighted in the tool.](https:\/\/static.semrush.com\/blog\/uploads\/media\/2a\/22\/2a22a56d8b6c659776b8bf12a272d924\/3eeb364f2e438db8ab62548f45bfb22c\/AD_4nXcZbfMoZNBijFOVMj_GwvET-D_u-yodoNwDsX7qaXYXoDDrTh1o4lAvsCviVWBsMHxpAK8CDVNXjbewzGU2IeqWxXDHVl-pl2LP1gdAnSQFPpHho8frx2vE0DmY92Hkq04RNDe7.png)\n\nIt’s also a good idea to audit your site for HTTP status code errors. You can do this easily in Semrush’s [Site Audit](https:\/\/www.semrush.com\/siteaudit\/) tool.\n\nSimply run a crawl and click on “**Crawled Pages**.”\n\nThe “Status” column will show you the status code of each page so you can see if there are any errors that need fixing.\n\n![The HTTP status code column is highlighted for the list of crawled pages.](https:\/\/static.semrush.com\/blog\/uploads\/media\/ff\/21\/ff2149146cfd67bb8902fde8055d560e\/8581ed3ddd72f1210e56481eb2238b22\/AD_4nXcS7lMhybffl42RA8Bzo-ylta5HGeujc6ElsQDnn-YIPzd7vqozZV5Ib3Cdu4t-gPmM3CCK2QhFqstF0J-ev5jpjVUQoknGxxb9M8bTs9nYc-uw13SnDimG-lI5D03LgFNL-IQt.png)\n\n## The Implications of Common HTTP Status Codes for SEO\nHere’s what some of the most common status codes mean for your SEO:\n\n### 200 (OK)\nA 200 response code is what you’ll want most of your webpages to return.\n\nIt indicates that a webpage works and is accessible to both people and search engines.\n\n### 301 (Moved Permanently)\nA [301 code](https:\/\/www.semrush.com\/blog\/301-redirects\/) means you’ve permanently moved a page to a new URL. And signals to Google that the old URL in its index should be replaced with the new one.\n\nImportantly, a 301 redirect also transfers link equity from the old page to the new one. Which preserves your visibility.\n\n![Two webpages link to the same page. These links pass link equity to that page and its 301 redirected page.](https:\/\/static.semrush.com\/blog\/uploads\/media\/bc\/26\/bc26230ee334d04c563cb51df4084779\/9434b30f663eec6b32691af1a5ac0d03\/AD_4nXcMj88QqFzbw4c-FIIy3n8G6cIavzBTDSLBL_qy4ODOaN6B9xne_K1SPqMYarRPT8gIG65cBUXOKKYBEZAWmT02T2xunhfveHf21cdTkTZkPXU46saTVu9iMKOvjrMW1JXqmc-65Q.png)\n\n### 302 (Found\/Temporary Redirect)\nA [302 redirect](https:\/\/www.semrush.com\/blog\/302-redirect\/) is a temporary redirect. It can preserve links and rankings while a webpage is temporarily unavailable.\n\nFor example, if you’re doing website maintenance and want to send users to a temporary holding page. Or you’re carrying out A\/B testing.\n\nIf a 302 redirect is in place for a long time, Google may start treating it as a 301 redirect. Meaning the old URL will be replaced by the new one in Google’s index.\n\n### 404 (Not Found) and 410 (Gone)\nBoth 404 and 410 status codes tell search engines that a page no longer exists, which typically leads to it being removed from the index.\n\nWhile both ultimately lead to deindexing, a 410 more clearly communicates that the page is gone for good. This can speed up its removalfrom search engine indexes.\n\n### 5XX (Server Errors)\nSearch engines have trouble accessing pages with 5XX errors, which can lead to problems with crawling, indexing, and the user experience.\n\nOver time, this can negatively impact visibility in search results. So it’s important to monitor and resolve 5XX errors promptly.\n\n## The Impact of HTTP Status Codes on LLMs\nIt’s important to make sure your content’s accessible to tools built on large language models (LLMs), like Google’s AI Overviews, ChatGPT, Perplexity, and Claude. Because it’ll help you gain more visibility in those AI responses.\n\nStatus codes that signal errors—like 404s and 500s—can block LLMs from seeing your content. Because LLMs find and understand website content similar to traditional search engines.\n\nWeb developer and AI engineer [Vincent Schmalbach](https:\/\/www.linkedin.com\/in\/vschmalbach\/) notes:\n\n> “Sites with frequent HTTP status code errors may find their content underrepresented in both search results and AI-generated responses, since both systems require reliable access to index and utilize content effectively.”\n\nVincent adds the following when talking specifically about 4XX and 5XX status codes:\n\n> “Both 404 and 410 responses mean no content is available, so those pages don't contribute to training data. Server errors like 500s cause crawlers to retry later, but persistent errors result in content being skipped entirely.”\n\n[Toby Basalla](https:\/\/www.linkedin.com\/in\/toby-basalla\/), Founder and Principal Data Consultant at data analytics consultancy Synthelize, warns that a website with unintentional redirect status codes can skew data used to train the actual models if it's scraped all at once. Because those mistakes are difficult to spot among so much data.\n\nHe reflects on a notable experience running a custom-trained LLM that relied on a scraped dataset:\n\n> “In one case, a client had 180 landing pages misflagged as temporary redirects, and none of it made it into our scraped dataset. Which means, in effect, those pages did not exist to the model.”\n## Check Your Website for HTTP Status Code Errors\nYou should check your website’s HTTP status codes regularly to stay on top of any errors.\n\nSemrush’s [Site Audit](https:\/\/www.semrush.com\/siteaudit\/) tool makes it easy to identify any of these problems. So you can swiftly address issues and boost your SEO performance.\n\nShare\n\n[Carlos Silva](https:\/\/www.semrush.com\/blog\/user\/201654769\/)\n\nCarlos Silva is a content marketer with 10+ years of experience in both in-house and agency roles. His expertise encompasses content strategy, SEO, content creation, and email marketing, with a focus on AI-enhanced content production. Carlos brings a comprehensive understanding of both traditional and AI-assisted digital marketing to his current role at Semrush, where he researches, edits, and writes for the English blog, helping readers navigate the evolving landscape of online marketing.\n\nCarlos Silva\n\nCarlos Silva is a content marketer with 10+ years of experience spanning both in-house and agency roles. His expertise spans content strategy, SEO, and AI-enhanced content creation. At Semrush, he researches, edits, and writes for the English blog.\n\nShare\n\n## More on this\n##### [SEO Checklist: 41 Tips to Optimize Your Website](https:\/\/www.semrush.com\/blog\/seo-checklist\/ \"SEO Checklist: 41 Tips to Optimize Your Website\")\nUse this SEO checklist to improve your website’s search engine rankings.\n\n[General SEO](https:\/\/www.semrush.com\/blog\/category\/general-seo\/)19 min read\n\n##### [301 Redirects: How to Use Them & How They Affect SEO](https:\/\/www.semrush.com\/blog\/301-redirects\/ \"301 Redirects: How to Use Them & How They Affect SEO\")\nA 301 redirect sends users and search engines from an old URL to a new one, passing on the SEO value.\n\n[Technical SEO](https:\/\/www.semrush.com\/blog\/category\/technical-seo\/)11 min read\n\n##### [Redirects: What They Are & How to Use Them](https:\/\/www.semrush.com\/blog\/redirects\/ \"Redirects: What They Are & How to Use Them\")\nA redirect is a way to send users and search engines to a different URL than the one they requested.\n\n[Technical SEO](https:\/\/www.semrush.com\/blog\/category\/technical-seo\/)12 min read\n\n##### [What Is Website Architecture? (& How to Improve it for SEO)](https:\/\/www.semrush.com\/blog\/website-structure\/ \"What Is Website Architecture? (& How to Improve it for SEO)\")\nWebsite architecture refers to the structure of websites. Learn best practices for organizing your site for SEO.\n\n[Technical SEO](https:\/\/www.semrush.com\/blog\/category\/technical-seo\/)8 min read\n\n## GET STARTED WITH SEMRUSH TODAY\nTry Semrush free for seven days. Cancel anytime.\n\n[Start free trial](https:\/\/www.semrush.com\/signup\/get-free-trial)\n\nSemrush\n\n- [Semrush One](https:\/\/www.semrush.com\/one\/)\n- [Features](https:\/\/www.semrush.com\/features\/)\n- [Pricing](https:\/\/www.semrush.com\/pricing\/)\n- [Compare Semrush](https:\/\/www.semrush.com\/vs\/)\n- [Success Stories](https:\/\/www.semrush.com\/company\/stories\/)\n- [Stats and Facts](https:\/\/www.semrush.com\/stats\/)\n- [Affiliate Program](https:\/\/www.semrush.com\/lp\/affiliate-program\/en\/?utm_source=semrush&utm_medium=footer)\n\nMore tools\n\n- [Enterprise SEO](https:\/\/enterprise.semrush.com\/?utm_source=semrush&utm_medium=footer)\n- [Enterprise AIO](https:\/\/www.semrush.com\/lp\/enterprise-aio\/en\/)\n- [Enterprise SI](https:\/\/www.semrush.com\/lp\/site-intelligence\/en\/)\n- [Insights24](https:\/\/www.semrush.com\/lp\/insights\/en\/?utm_source=semrush&utm_medium=footer)\n- [Mfour](https:\/\/www.semrush.com\/lp\/mfour\/en\/?utm_source=semrush&utm_medium=footer)\n- [App Center](https:\/\/www.semrush.com\/apps\/?utm_source=semrush&utm_medium=footer)\n- [Top Websites](https:\/\/www.semrush.com\/website\/top\/?utm_source=semrush&utm_medium=footer)\n- [Free Tools](https:\/\/www.semrush.com\/free-tools\/?utm_source=semrush&utm_medium=footer)\n- [Sensor](https:\/\/www.semrush.com\/sensor\/?utm_source=semrush&utm_medium=footer)\n\nCompany\n\n- [About Us](https:\/\/www.semrush.com\/company\/)\n- [News](https:\/\/www.semrush.com\/news\/)\n- [Careers](https:\/\/careers.semrush.com\/)\n- [Partners](https:\/\/www.semrush.com\/company\/partners\/)\n- [For Investors](https:\/\/investors.semrush.com\/)\n- [Semrush Select](https:\/\/www.semrush.com\/company\/semrush-select\/)\n- [Global Issues Index](https:\/\/www.semrush.com\/company\/global-issues\/)\n- [Contact Us](https:\/\/www.semrush.com\/company\/contacts\/)\n\nSupport\n\n- [Knowledge Base](https:\/\/www.semrush.com\/kb\/)\n- [Academy](https:\/\/www.semrush.com\/academy\/)\n- [Semrush API](https:\/\/www.semrush.com\/api-documentation\/)\n\nCommunity\n\n- [Semrush Blog](https:\/\/www.semrush.com\/blog\/)\n- [Webinars](https:\/\/www.semrush.com\/academy\/webinars\/)\n- [Ambassador Program](https:\/\/www.semrush.com\/lp\/semrush-circle\/en\/?utm_source=semrush&utm_medium=footer)\n\nLegal\n\n- [Privacy Policy](https:\/\/www.semrush.com\/company\/legal\/privacy-policy\/)\n- [Terms of Service](https:\/\/www.semrush.com\/company\/legal\/)\n- [Cookies Settings](https:\/\/www.semrush.com\/blog\/http-status-codes\/)\n\nEnglish\n\n- [English](https:\/\/www.semrush.com\/blog\/)\n- [Español](https:\/\/es.semrush.com\/blog\/)\n- [Deutsch](https:\/\/de.semrush.com\/blog\/)\n- [Français](https:\/\/fr.semrush.com\/blog\/)\n- [Italiano](https:\/\/it.semrush.com\/blog\/)\n- [Português (Brasil)](https:\/\/pt.semrush.com\/blog\/)\n- [日本語](https:\/\/ja.semrush.com\/blog\/)\n\n© 2008 - 2026 Semrush. All rights reserved.\n\n- [Privacy Policy](https:\/\/www.semrush.com\/company\/legal\/privacy-policy\/)\n- [Terms of Service](https:\/\/www.semrush.com\/company\/legal\/)\n- [Cookies Settings](https:\/\/www.semrush.com\/blog\/http-status-codes\/)\n\nEnglish\n\n- English\n- Español\n- Deutsch\n- Français\n- Italiano\n- Português (Brasil)\n- 日本語","attrs_readable_markdown":"## What Are HTTP Status Codes?\nHTTP status codes are three-digit numbers servers generate in response to a client (e.g., a browser) request. They indicate whether the request was completed successfully.\n\nFor example, a 404 error is a common HTTP status code you might have seen.\n\n![A URL returns a 404 error page.](https:\/\/static.semrush.com\/blog\/uploads\/media\/81\/c2\/81c2c9105fe4a38571c5291d60299a69\/82d45f4b44e16d95fc1551e16f38b6d9\/AD_4nXcVEnCXbIk9M40jL80nMXv4Z-6IzP5icb4e-yjcmbjgz37gPymIwW6ympon2pdzCbhaANz3VqXJUoDUDDsB4qJRKuGODrLfcVNTJYG0kK5tDWpwnzNbJNRWLEy2MT6NJf3Qnts9sw.png)\n\nIf you’re a website owner, HTTP status codes give you important information for improving your website’s functionality and user experience. And they can impact your SEO.\n\n## Categories of HTTP Status Codes\nThere are five categories of HTTP status codes:\n\n- **1XX (informational codes)**: The server received the request and is processing it\n- **2XX (success codes)**: The server successfully received and processed the request\n- **3XX (redirection codes)**:The server received the request, but there’s a redirect to another destination ([301 or 302](https:\/\/www.semrush.com\/blog\/301-vs-302-redirect\/) are common)\n- **4XX (client error codes)**:The requested resource couldn’t be found or reached due to a client error\n- **5XX (server error codes)**: The server ran into an error when processing the request\n## A Complete List of HTTP Status Codes\n|   |   |\n|---|---|\n| **Code** | **Meaning** |\n| **1XX: Informational Responses** |   |\n| 100: Continue | The server has received the initial request and is ready for the client to send the rest if it hasn’t already |\n| 101: Switching protocols | The server agrees to accept the client’s request to change to a different protocol |\n| 102: Processing | The server has received the request but hasn’t completed it. This code has been deprecated. |\n| 103: Early hints | The server sends hints about the expected final response while the response is still being processed |\n| **2XX: Success Codes** |   |\n| 200: OK | The request was successful. The specific response depends on the request method (GET, PUT, etc.). |\n| 201: Created | The request worked, so a new resource was created |\n| 202: Accepted | The request was accepted but hasn’t been processed |\n| 203: Non-authoritative information | The data returned is from a third party rather than from the original server |\n| 204: No content | The request was successful, but there's no content |\n| 205: Reset content | The request was successful, and the user agent (e.g., browser) should reset the document |\n| 206: Partial content | The server is only sending part of the requested resource |\n| 207: Multi status | Provides the statuses of multiple operations within a single response |\n| 208: Already reported | Tells the client that a resource’s information has already been included earlier in the response and won’t be repeated |\n| 226: IM used (HTTP delta encoding) | The server successfully handled the request and returned a version of the resource that includes only the changes—not the full resource |\n| **3XX: Redirection Codes** |   |\n| 300: Multiple choices | Indicates there are multiple possible responses, and the user or client needs to choose one |\n| 301: Moved permanently | The resource has permanently moved to a new web address. The server provides the new URL. |\n| 302: Found | The resource has temporarily moved to a different web address. But it might move again. |\n| 303: See other | The server is telling the client to get the resource from another location using a standard GET request |\n| 304: Not modified | The response hasn’t changed, so the client can keep using the cached version |\n| 305: Use proxy | Indicates the client should use a proxy to access the resource. This code has been deprecated. |\n| 307: Temporary redirect | The resource has temporarily moved, and the client should use the same HTTP method (e.g., POST) as in the previous request |\n| 308: Permanent redirect | The resource has permanently moved, and the client must use the same HTTP method as in the previous request |\n| **4XX: Client Error Codes** |   |\n| 400: Bad request | The server can’t process the request because of a client error |\n| 401: Unauthorized | The client doesn’t have the proper credentials to access the resource |\n| 402: Payment required | Originally meant to indicate the requested resource requires payment, but it’s rarely used and doesn’t have a standard purpose |\n| 403: Forbidden | The client isn’t authorized to access the resource, even though the server knows the client’s identity |\n| 404: Not found | The server can’t find the resource. Often because a browser is requesting an incorrect URL or the content no longer exists. |\n| 405: Method not allowed | The request method (e.g., GET) isn’t allowed for the specified resource |\n| 406: Not acceptable | The server can’t provide a response in any format the client specified |\n| 407: Proxy authentication required | A proxy server needs to authenticate the client before the request can be processed |\n| 408: Request timeout | The server gave up waiting because the client didn’t complete the request fast enough |\n| 409: Conflict | The request conflicts with what’s already on the server (e.g., two people editing the same content at the same time) |\n| 410: Gone | The requested resource has been permanently deleted. And there’s no forwarding address. |\n| 411: Length required | The server didn’t accept the request because it didn’t specify how much data is being sent |\n| 412: Precondition failed | A condition set in the request wasn’t met, so the server didn’t process it |\n| 413: Content too large | The amount of data the client is sending is too big for the server to handle |\n| 414: URI too long | The requested web address is too long for the server to manage |\n| 415: Unsupported media type | The server doesn’t support the format the request is using |\n| 416: Range not satisfiable | The requested part of a resource isn’t within the server’s available range |\n| 417: Expectation failed | The server couldn’t meet a requirement specified in the request |\n| 421: Misdirected request | The request went to the wrong server—one that isn’t set up to handle it |\n| 422: Unprocessable content | The server understands the request format but is unable to process it because of issues with the actual data (e.g., wrong values) |\n| 423: Locked | The requested resource is locked and inaccessible |\n| 424: Failed dependency | The request failed because a related request also failed |\n| 425: Too early | The server didn’t process the request because it was too early and might be replayed |\n| 426: Upgrade required | The server won’t process the request unless the client switches to a newer or different protocol (like HTTPS) |\n| 428: Precondition required | The server requires the request to include certain conditions to ensure safe updates |\n| 429: Too many requests | The user sent too many requests too quickly |\n| 431: Request header fields too large | The request headers contain too much information for the server to process |\n| 451: Unavailable for legal reasons | The requested resource is blocked due to legal reasons |\n| **5XX: Server Error Codes** |   |\n| 500: Internal server error | The server encountered an error and couldn’t complete the request |\n| 501: Not implemented | The server doesn’t support the request method |\n| 502: Bad gateway | The gateway server received an invalid or no response from another server |\n| 503: Service unavailable | The server is temporarily unavailable—usually because it’s down for maintenance or overloaded |\n| 504: Gateway timeout | The gateway server didn’t get a response from another server in time |\n| 505: HTTP version not supported | The server doesn’t support the HTTP version used in the request |\n| 506: Variant also negotiates | A misconfiguration caused the server to get stuck in a loop when trying to choose between different versions of the resource |\n| 507: Insufficient storage | The server doesn’t have enough space to save or process the request |\n| 508: Loop detected | The server detects an endless loop while trying to process the request |\n| 510: Not extended | The request is missing extensions the server requires for processing |\n| 511: Network authentication required | The client needs to authenticate to gain network access |\n## How to Check a Webpage’s HTTP Status Codes\nYou can easily check a page’s HTTP status codes using Google Chrome.\n\nGo to the webpage you want to check.\n\nRight-click anywhere on the page and select \"**Inspect**” to open the Developer Tools. Or press “Ctrl + Shift + I” (Windows\/Linux) or “Cmd + Option + I” (Mac).\n\n![Inspect is highlighted in the right-click menu.](https:\/\/static.semrush.com\/blog\/uploads\/media\/aa\/95\/aa9516794d12beb900e226bb0fb0fc79\/78f5eebd4d8269f38693b57673bc7e38\/AD_4nXdrNGDyEzSOTjveTyCw_QxYjqy3Aad-8yqFRvpJs98mXQLIvNmlsl8EtPvQENQ-AyJ2rLhE4D0JomkOqjDUDMPUbobdVsFs5cDnTRs-20l4sIU7aSrzSCe3QChhDXLaV1AMU7hraQ.png)\n\nClick on the \"**Network**\" tab in the Developer Tools panel.\n\nRefresh the page (select “F5” or “Ctrl + R”).\n\nLook at the list of network requests.\n\nThe “Status” column shows you a list of HTTP status codes for the page. The first one in the list is the page’s HTML document.\n\n![The HTTP status code column is highlighted in the tool.](https:\/\/static.semrush.com\/blog\/uploads\/media\/2a\/22\/2a22a56d8b6c659776b8bf12a272d924\/3eeb364f2e438db8ab62548f45bfb22c\/AD_4nXcZbfMoZNBijFOVMj_GwvET-D_u-yodoNwDsX7qaXYXoDDrTh1o4lAvsCviVWBsMHxpAK8CDVNXjbewzGU2IeqWxXDHVl-pl2LP1gdAnSQFPpHho8frx2vE0DmY92Hkq04RNDe7.png)\n\nIt’s also a good idea to audit your site for HTTP status code errors. You can do this easily in Semrush’s [Site Audit](https:\/\/www.semrush.com\/siteaudit\/) tool.\n\nSimply run a crawl and click on “**Crawled Pages**.”\n\nThe “Status” column will show you the status code of each page so you can see if there are any errors that need fixing.\n\n![The HTTP status code column is highlighted for the list of crawled pages.](https:\/\/static.semrush.com\/blog\/uploads\/media\/ff\/21\/ff2149146cfd67bb8902fde8055d560e\/8581ed3ddd72f1210e56481eb2238b22\/AD_4nXcS7lMhybffl42RA8Bzo-ylta5HGeujc6ElsQDnn-YIPzd7vqozZV5Ib3Cdu4t-gPmM3CCK2QhFqstF0J-ev5jpjVUQoknGxxb9M8bTs9nYc-uw13SnDimG-lI5D03LgFNL-IQt.png)\n\n## The Implications of Common HTTP Status Codes for SEO\nHere’s what some of the most common status codes mean for your SEO:\n\n### 200 (OK)\nA 200 response code is what you’ll want most of your webpages to return.\n\nIt indicates that a webpage works and is accessible to both people and search engines.\n\n### 301 (Moved Permanently)\nA [301 code](https:\/\/www.semrush.com\/blog\/301-redirects\/) means you’ve permanently moved a page to a new URL. And signals to Google that the old URL in its index should be replaced with the new one.\n\nImportantly, a 301 redirect also transfers link equity from the old page to the new one. Which preserves your visibility.\n\n![Two webpages link to the same page. These links pass link equity to that page and its 301 redirected page.](https:\/\/static.semrush.com\/blog\/uploads\/media\/bc\/26\/bc26230ee334d04c563cb51df4084779\/9434b30f663eec6b32691af1a5ac0d03\/AD_4nXcMj88QqFzbw4c-FIIy3n8G6cIavzBTDSLBL_qy4ODOaN6B9xne_K1SPqMYarRPT8gIG65cBUXOKKYBEZAWmT02T2xunhfveHf21cdTkTZkPXU46saTVu9iMKOvjrMW1JXqmc-65Q.png)\n\n### 302 (Found\/Temporary Redirect)\nA [302 redirect](https:\/\/www.semrush.com\/blog\/302-redirect\/) is a temporary redirect. It can preserve links and rankings while a webpage is temporarily unavailable.\n\nFor example, if you’re doing website maintenance and want to send users to a temporary holding page. Or you’re carrying out A\/B testing.\n\nIf a 302 redirect is in place for a long time, Google may start treating it as a 301 redirect. Meaning the old URL will be replaced by the new one in Google’s index.\n\n### 404 (Not Found) and 410 (Gone)\nBoth 404 and 410 status codes tell search engines that a page no longer exists, which typically leads to it being removed from the index.\n\nWhile both ultimately lead to deindexing, a 410 more clearly communicates that the page is gone for good. This can speed up its removalfrom search engine indexes.\n\n### 5XX (Server Errors)\nSearch engines have trouble accessing pages with 5XX errors, which can lead to problems with crawling, indexing, and the user experience.\n\nOver time, this can negatively impact visibility in search results. So it’s important to monitor and resolve 5XX errors promptly.\n\n## The Impact of HTTP Status Codes on LLMs\nIt’s important to make sure your content’s accessible to tools built on large language models (LLMs), like Google’s AI Overviews, ChatGPT, Perplexity, and Claude. Because it’ll help you gain more visibility in those AI responses.\n\nStatus codes that signal errors—like 404s and 500s—can block LLMs from seeing your content. Because LLMs find and understand website content similar to traditional search engines.\n\nWeb developer and AI engineer [Vincent Schmalbach](https:\/\/www.linkedin.com\/in\/vschmalbach\/) notes:\n\n> “Sites with frequent HTTP status code errors may find their content underrepresented in both search results and AI-generated responses, since both systems require reliable access to index and utilize content effectively.”\n\nVincent adds the following when talking specifically about 4XX and 5XX status codes:\n\n> “Both 404 and 410 responses mean no content is available, so those pages don't contribute to training data. Server errors like 500s cause crawlers to retry later, but persistent errors result in content being skipped entirely.”\n\n[Toby Basalla](https:\/\/www.linkedin.com\/in\/toby-basalla\/), Founder and Principal Data Consultant at data analytics consultancy Synthelize, warns that a website with unintentional redirect status codes can skew data used to train the actual models if it's scraped all at once. Because those mistakes are difficult to spot among so much data.\n\nHe reflects on a notable experience running a custom-trained LLM that relied on a scraped dataset:\n\n> “In one case, a client had 180 landing pages misflagged as temporary redirects, and none of it made it into our scraped dataset. Which means, in effect, those pages did not exist to the model.”\n## Check Your Website for HTTP Status Code Errors\nYou should check your website’s HTTP status codes regularly to stay on top of any errors.\n\nSemrush’s [Site Audit](https:\/\/www.semrush.com\/siteaudit\/) tool makes it easy to identify any of these problems. So you can swiftly address issues and boost your SEO performance.","meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

13 days ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	0.4 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://www.semrush.com/blog/http-status-codes/
Last Crawled	2026-03-27 18:21:42 (13 days ago)
First Indexed	not set
HTTP Status Code	200
Meta Title	HTTP Status Codes Explained: Full List & Impact on SEO
Meta Description	Learn what HTTP status codes are, what different codes mean, and how they impact search visibility.
Meta Canonical	null
Boilerpipe Text	What Are HTTP Status Codes? HTTP status codes are three-digit numbers servers generate in response to a client (e.g., a browser) request. They indicate whether the request was completed successfully. For example, a 404 error is a common HTTP status code you might have seen. If you’re a website owner, HTTP status codes give you important information for improving your website’s functionality and user experience. And they can impact your SEO. Categories of HTTP Status Codes There are five categories of HTTP status codes: 1XX (informational codes) : The server received the request and is processing it 2XX (success codes) : The server successfully received and processed the request 3XX (redirection codes) :The server received the request, but there’s a redirect to another destination ( 301 or 302 are common) 4XX (client error codes) :The requested resource couldn’t be found or reached due to a client error 5XX (server error codes) : The server ran into an error when processing the request A Complete List of HTTP Status Codes Code Meaning 1XX: Informational Responses 100: Continue The server has received the initial request and is ready for the client to send the rest if it hasn’t already 101: Switching protocols The server agrees to accept the client’s request to change to a different protocol 102: Processing The server has received the request but hasn’t completed it. This code has been deprecated. 103: Early hints The server sends hints about the expected final response while the response is still being processed 2XX: Success Codes 200: OK The request was successful. The specific response depends on the request method (GET, PUT, etc.). 201: Created The request worked, so a new resource was created 202: Accepted The request was accepted but hasn’t been processed 203: Non-authoritative information The data returned is from a third party rather than from the original server 204: No content The request was successful, but there's no content 205: Reset content The request was successful, and the user agent (e.g., browser) should reset the document 206: Partial content The server is only sending part of the requested resource 207: Multi status Provides the statuses of multiple operations within a single response 208: Already reported Tells the client that a resource’s information has already been included earlier in the response and won’t be repeated 226: IM used (HTTP delta encoding) The server successfully handled the request and returned a version of the resource that includes only the changes—not the full resource 3XX: Redirection Codes 300: Multiple choices Indicates there are multiple possible responses, and the user or client needs to choose one 301: Moved permanently The resource has permanently moved to a new web address. The server provides the new URL. 302: Found The resource has temporarily moved to a different web address. But it might move again. 303: See other The server is telling the client to get the resource from another location using a standard GET request 304: Not modified The response hasn’t changed, so the client can keep using the cached version 305: Use proxy Indicates the client should use a proxy to access the resource. This code has been deprecated. 307: Temporary redirect The resource has temporarily moved, and the client should use the same HTTP method (e.g., POST) as in the previous request 308: Permanent redirect The resource has permanently moved, and the client must use the same HTTP method as in the previous request 4XX: Client Error Codes 400: Bad request The server can’t process the request because of a client error 401: Unauthorized The client doesn’t have the proper credentials to access the resource 402: Payment required Originally meant to indicate the requested resource requires payment, but it’s rarely used and doesn’t have a standard purpose 403: Forbidden The client isn’t authorized to access the resource, even though the server knows the client’s identity 404: Not found The server can’t find the resource. Often because a browser is requesting an incorrect URL or the content no longer exists. 405: Method not allowed The request method (e.g., GET) isn’t allowed for the specified resource 406: Not acceptable The server can’t provide a response in any format the client specified 407: Proxy authentication required A proxy server needs to authenticate the client before the request can be processed 408: Request timeout The server gave up waiting because the client didn’t complete the request fast enough 409: Conflict The request conflicts with what’s already on the server (e.g., two people editing the same content at the same time) 410: Gone The requested resource has been permanently deleted. And there’s no forwarding address. 411: Length required The server didn’t accept the request because it didn’t specify how much data is being sent 412: Precondition failed A condition set in the request wasn’t met, so the server didn’t process it 413: Content too large The amount of data the client is sending is too big for the server to handle 414: URI too long The requested web address is too long for the server to manage 415: Unsupported media type The server doesn’t support the format the request is using 416: Range not satisfiable The requested part of a resource isn’t within the server’s available range 417: Expectation failed The server couldn’t meet a requirement specified in the request 421: Misdirected request The request went to the wrong server—one that isn’t set up to handle it 422: Unprocessable content The server understands the request format but is unable to process it because of issues with the actual data (e.g., wrong values) 423: Locked The requested resource is locked and inaccessible 424: Failed dependency The request failed because a related request also failed 425: Too early The server didn’t process the request because it was too early and might be replayed 426: Upgrade required The server won’t process the request unless the client switches to a newer or different protocol (like HTTPS) 428: Precondition required The server requires the request to include certain conditions to ensure safe updates 429: Too many requests The user sent too many requests too quickly 431: Request header fields too large The request headers contain too much information for the server to process 451: Unavailable for legal reasons The requested resource is blocked due to legal reasons 5XX: Server Error Codes 500: Internal server error The server encountered an error and couldn’t complete the request 501: Not implemented The server doesn’t support the request method 502: Bad gateway The gateway server received an invalid or no response from another server 503: Service unavailable The server is temporarily unavailable—usually because it’s down for maintenance or overloaded 504: Gateway timeout The gateway server didn’t get a response from another server in time 505: HTTP version not supported The server doesn’t support the HTTP version used in the request 506: Variant also negotiates A misconfiguration caused the server to get stuck in a loop when trying to choose between different versions of the resource 507: Insufficient storage The server doesn’t have enough space to save or process the request 508: Loop detected The server detects an endless loop while trying to process the request 510: Not extended The request is missing extensions the server requires for processing 511: Network authentication required The client needs to authenticate to gain network access How to Check a Webpage’s HTTP Status Codes You can easily check a page’s HTTP status codes using Google Chrome. Go to the webpage you want to check. Right-click anywhere on the page and select " Inspect ” to open the Developer Tools. Or press “Ctrl + Shift + I” (Windows/Linux) or “Cmd + Option + I” (Mac). Click on the " Network " tab in the Developer Tools panel. Refresh the page (select “F5” or “Ctrl + R”). Look at the list of network requests. The “Status” column shows you a list of HTTP status codes for the page. The first one in the list is the page’s HTML document. It’s also a good idea to audit your site for HTTP status code errors. You can do this easily in Semrush’s Site Audit tool. Simply run a crawl and click on “ Crawled Pages .” The “Status” column will show you the status code of each page so you can see if there are any errors that need fixing. The Implications of Common HTTP Status Codes for SEO Here’s what some of the most common status codes mean for your SEO: 200 (OK) A 200 response code is what you’ll want most of your webpages to return. It indicates that a webpage works and is accessible to both people and search engines. 301 (Moved Permanently) A 301 code means you’ve permanently moved a page to a new URL. And signals to Google that the old URL in its index should be replaced with the new one. Importantly, a 301 redirect also transfers link equity from the old page to the new one. Which preserves your visibility. 302 (Found/Temporary Redirect) A 302 redirect is a temporary redirect. It can preserve links and rankings while a webpage is temporarily unavailable. For example, if you’re doing website maintenance and want to send users to a temporary holding page. Or you’re carrying out A/B testing. If a 302 redirect is in place for a long time, Google may start treating it as a 301 redirect. Meaning the old URL will be replaced by the new one in Google’s index. 404 (Not Found) and 410 (Gone) Both 404 and 410 status codes tell search engines that a page no longer exists, which typically leads to it being removed from the index. While both ultimately lead to deindexing, a 410 more clearly communicates that the page is gone for good. This can speed up its removalfrom search engine indexes. 5XX (Server Errors) Search engines have trouble accessing pages with 5XX errors, which can lead to problems with crawling, indexing, and the user experience. Over time, this can negatively impact visibility in search results. So it’s important to monitor and resolve 5XX errors promptly. The Impact of HTTP Status Codes on LLMs It’s important to make sure your content’s accessible to tools built on large language models (LLMs), like Google’s AI Overviews, ChatGPT, Perplexity, and Claude. Because it’ll help you gain more visibility in those AI responses. Status codes that signal errors—like 404s and 500s—can block LLMs from seeing your content. Because LLMs find and understand website content similar to traditional search engines. Web developer and AI engineer Vincent Schmalbach notes: “Sites with frequent HTTP status code errors may find their content underrepresented in both search results and AI-generated responses, since both systems require reliable access to index and utilize content effectively.” Vincent adds the following when talking specifically about 4XX and 5XX status codes: “Both 404 and 410 responses mean no content is available, so those pages don't contribute to training data. Server errors like 500s cause crawlers to retry later, but persistent errors result in content being skipped entirely.” Toby Basalla , Founder and Principal Data Consultant at data analytics consultancy Synthelize, warns that a website with unintentional redirect status codes can skew data used to train the actual models if it's scraped all at once. Because those mistakes are difficult to spot among so much data. He reflects on a notable experience running a custom-trained LLM that relied on a scraped dataset: “In one case, a client had 180 landing pages misflagged as temporary redirects, and none of it made it into our scraped dataset. Which means, in effect, those pages did not exist to the model.” Check Your Website for HTTP Status Code Errors You should check your website’s HTTP status codes regularly to stay on top of any errors. Semrush’s Site Audit tool makes it easy to identify any of these problems. So you can swiftly address issues and boost your SEO performance.
Markdown	Products Start Here [Semrush One](https://www.semrush.com/one/?utm_source=blog&utm_medium=header&src=header)[Enterprise](https://enterprise.semrush.com/?utm_source=blog&utm_medium=header&src=header)[Features](https://www.semrush.com/features/?utm_source=blog&utm_medium=header&src=header)[Request a Demo](https://www.semrush.com/kb/request-demo/?utm_source=blog&utm_medium=header&src=header)[Talk to Sales](https://www.semrush.com/company/sales/?utm_source=blog&utm_medium=header&src=header) Find the Right Tools [AI Visibility Toolkit](https://www.semrush.com/ai-seo/overview/?utm_source=blog&utm_medium=header&src=header)[SEO Toolkit](https://www.semrush.com/seo/?utm_source=blog&utm_medium=header&src=header)[Traffic & Market Toolkit](https://www.semrush.com/analytics/traffic/?utm_source=blog&utm_medium=header&src=header)[Content Toolkit](https://www.semrush.com/content/?utm_source=blog&utm_medium=header&src=header)[Local Toolkit](https://www.semrush.com/local-business/start/?utm_source=blog&utm_medium=header&src=header)[Social Toolkit](https://www.semrush.com/social-media/?utm_source=blog&utm_medium=header&src=header)[Advertising Toolkit](https://www.semrush.com/advertising/?utm_source=blog&utm_medium=header&src=header)[PR Toolkit](https://www.semrush.com/pr-toolkit/?utm_source=blog&utm_medium=header&src=header) Platform [Integrations](https://www.semrush.com/company/partner-integrations/?utm_source=blog&utm_medium=header&src=header)[App Center](https://www.semrush.com/apps/?utm_source=blog&utm_medium=header&src=header)[API](https://developer.semrush.com/api/?utm_source=blog&utm_medium=header&src=header)[Data Sources](https://www.semrush.com/kb/997-semrush-data?utm_source=blog&utm_medium=header&src=header) Top Apps [AdClarity](https://www.semrush.com/apps/adclarity-advertising-intelligence/?utm_source=blog&utm_medium=header&src=header)[Exploding Topics](https://www.semrush.com/apps/exploding-topics/?utm_source=blog&utm_medium=header&src=header)[Other apps](https://www.semrush.com/apps/collection/most-popular/?utm_source=blog&utm_medium=header&src=header) [Pricing](https://www.semrush.com/pricing/?utm_source=blog&utm_medium=header&src=header) Resources Grow with Semrush [Blog](https://www.semrush.com/blog/?utm_source=blog&utm_medium=header&src=header)[Knowledge Base](https://www.semrush.com/kb/?utm_source=blog&utm_medium=header&src=header)[Academy](https://www.semrush.com/academy/)[Success Stories](https://www.semrush.com/company/stories/?utm_source=blog&utm_medium=header&src=header)[AI Visibility Index](https://ai-visibility-index.semrush.com/?utm_source=blog&utm_medium=header&src=header)[Webinars](https://www.semrush.com/academy/webinars/?utm_source=blog&utm_medium=header&src=header)[News](https://www.semrush.com/news/?utm_source=blog&utm_medium=header&src=header) Explore Free Tools [AI Visibility Checker](https://www.semrush.com/free-tools/ai-search-visibility-checker/?utm_source=blog&utm_medium=header&src=header)[SEO Checker](https://www.semrush.com/siteaudit/?utm_source=blog&utm_medium=header&src=header)[Website Traffic Checker](https://www.semrush.com/website/?utm_source=blog&utm_medium=header&src=header)[Keyword Tool](https://www.semrush.com/analytics/keywordmagic/?utm_source=blog&utm_medium=header&src=header)[Backlink Checker](https://www.semrush.com/analytics/backlinks/?utm_source=blog&utm_medium=header&src=header)[Top Websites by Traffic](https://www.semrush.com/website/top/?utm_source=blog&utm_medium=header&src=header)[Explore Other Free Tools](https://www.semrush.com/free-tools/?utm_source=blog&utm_medium=header&src=header) About Semrush [About Us](https://www.semrush.com/company/?utm_source=blog&utm_medium=header&src=header)[Stats and Facts](https://www.semrush.com/stats/?utm_source=blog&utm_medium=header&src=header)[Affiliate Program](https://www.semrush.com/lp/affiliate-program/en/?utm_source=blog&utm_medium=header&src=header)[Contact Us](https://www.semrush.com/company/contacts/?utm_source=blog&utm_medium=header&src=header) [Enterprise](https://enterprise.semrush.com/?utm_source=blog&utm_medium=header&src=header) [Login](https://www.semrush.com/login/?utm_source=blog&utm_medium=header&src=header&redirect_to=%2Fblog%2F)[Sign up](https://www.semrush.com/signup/?utm_source=blog&utm_medium=header&src=header) Products [Pricing](https://www.semrush.com/pricing/?utm_source=blog&utm_medium=header&src=header) Resources [Enterprise](https://enterprise.semrush.com/?utm_source=blog&utm_medium=header&src=header) [Login](https://www.semrush.com/login/?utm_source=blog&utm_medium=header&src=header&redirect_to=%2Fblog%2F)[Sign up](https://www.semrush.com/signup/?utm_source=blog&utm_medium=header&src=header) [Blog](https://www.semrush.com/blog/) [SEO](https://www.semrush.com/blog/category/seo/) [Marketing](https://www.semrush.com/blog/category/marketing/) [News & Research](https://www.semrush.com/blog/category/news/) [Product](https://www.semrush.com/blog/category/product/) [Try it for FREE for 7 days](https://www.semrush.com/signup/?custom=ai-seo&redirect_to=%2Fai-seo%2Foverview%2F)Don’t miss out. Try 55+ products for free. [SEO](https://www.semrush.com/blog/category/seo/) [General SEO](https://www.semrush.com/blog/category/seo/general-seo/)[Keyword Research](https://www.semrush.com/blog/category/seo/keyword-research/)[On-page SEO](https://www.semrush.com/blog/category/seo/on-page-seo/)[Link Building](https://www.semrush.com/blog/category/seo/link-building/)[Local SEO](https://www.semrush.com/blog/category/seo/local-seo/)[Technical SEO](https://www.semrush.com/blog/category/seo/technical-seo/)[Frequently Asked Questions](https://www.semrush.com/blog/category/seo/faq/) [Marketing](https://www.semrush.com/blog/category/marketing/) [General Marketing](https://www.semrush.com/blog/category/marketing/general-marketing/)[Content](https://www.semrush.com/blog/category/marketing/content/)[Social Media](https://www.semrush.com/blog/category/marketing/social-media/)[Competitor Intelligence & Research](https://www.semrush.com/blog/category/marketing/competitor-intelligence-and-research/)[AI](https://www.semrush.com/blog/category/marketing/ai/)[Paid Advertising](https://www.semrush.com/blog/category/marketing/paid-advertising/)[Video Marketing](https://www.semrush.com/blog/category/marketing/video-marketing/)[Ecommerce](https://www.semrush.com/blog/category/marketing/ecommerce/)[Analytics](https://www.semrush.com/blog/category/marketing/analytics/) [News & Research](https://www.semrush.com/blog/category/news/) [Original Research & Studies](https://www.semrush.com/blog/category/news/original-research-and-studies/)[Industry News](https://www.semrush.com/blog/category/news/industry-news/) [Product](https://www.semrush.com/blog/category/product/) [Semrush Enterprise](https://www.semrush.com/blog/category/product/semrush-enterprise/) [Create free account](https://www.semrush.com/signup/?custom=ai-seo&redirect_to=%2Fai-seo%2Foverview%2F) 1. [Semrush](https://www.semrush.com/) 2. [Blog](https://www.semrush.com/blog/) 3. [SEO](https://www.semrush.com/blog/category/seo/) 4. [Technical SEO](https://www.semrush.com/blog/category/seo/technical-seo/) # HTTP Status Codes Explained: Full List & Impact on SEO Expert reviewed Our subject matter experts have reviewed this article to ensure it meets the highest standard for accurate information and guidance. Learn more about our [editorial standards and process](https://www.semrush.com/blog/editorial-standards/). Author:[Carlos Silva](https://www.semrush.com/blog/user/carlos/) 8 min read Jul 08, 2025 Contributor: [Christine Skopec](https://www.semrush.com/blog/user/205718513/) Table of contents ## What Are HTTP Status Codes? HTTP status codes are three-digit numbers servers generate in response to a client (e.g., a browser) request. They indicate whether the request was completed successfully. For example, a 404 error is a common HTTP status code you might have seen. ![A URL returns a 404 error page.](https://static.semrush.com/blog/uploads/media/81/c2/81c2c9105fe4a38571c5291d60299a69/82d45f4b44e16d95fc1551e16f38b6d9/AD_4nXcVEnCXbIk9M40jL80nMXv4Z-6IzP5icb4e-yjcmbjgz37gPymIwW6ympon2pdzCbhaANz3VqXJUoDUDDsB4qJRKuGODrLfcVNTJYG0kK5tDWpwnzNbJNRWLEy2MT6NJf3Qnts9sw.png) If you’re a website owner, HTTP status codes give you important information for improving your website’s functionality and user experience. And they can impact your SEO. ## Categories of HTTP Status Codes There are five categories of HTTP status codes: - 1XX (informational codes): The server received the request and is processing it - 2XX (success codes): The server successfully received and processed the request - 3XX (redirection codes):The server received the request, but there’s a redirect to another destination ([301 or 302](https://www.semrush.com/blog/301-vs-302-redirect/) are common) - 4XX (client error codes):The requested resource couldn’t be found or reached due to a client error - 5XX (server error codes): The server ran into an error when processing the request ## A Complete List of HTTP Status Codes \| \| \| \|---\|---\| \| Code \| Meaning \| \| 1XX: Informational Responses \| \| \| 100: Continue \| The server has received the initial request and is ready for the client to send the rest if it hasn’t already \| \| 101: Switching protocols \| The server agrees to accept the client’s request to change to a different protocol \| \| 102: Processing \| The server has received the request but hasn’t completed it. This code has been deprecated. \| \| 103: Early hints \| The server sends hints about the expected final response while the response is still being processed \| \| 2XX: Success Codes \| \| \| 200: OK \| The request was successful. The specific response depends on the request method (GET, PUT, etc.). \| \| 201: Created \| The request worked, so a new resource was created \| \| 202: Accepted \| The request was accepted but hasn’t been processed \| \| 203: Non-authoritative information \| The data returned is from a third party rather than from the original server \| \| 204: No content \| The request was successful, but there's no content \| \| 205: Reset content \| The request was successful, and the user agent (e.g., browser) should reset the document \| \| 206: Partial content \| The server is only sending part of the requested resource \| \| 207: Multi status \| Provides the statuses of multiple operations within a single response \| \| 208: Already reported \| Tells the client that a resource’s information has already been included earlier in the response and won’t be repeated \| \| 226: IM used (HTTP delta encoding) \| The server successfully handled the request and returned a version of the resource that includes only the changes—not the full resource \| \| 3XX: Redirection Codes \| \| \| 300: Multiple choices \| Indicates there are multiple possible responses, and the user or client needs to choose one \| \| 301: Moved permanently \| The resource has permanently moved to a new web address. The server provides the new URL. \| \| 302: Found \| The resource has temporarily moved to a different web address. But it might move again. \| \| 303: See other \| The server is telling the client to get the resource from another location using a standard GET request \| \| 304: Not modified \| The response hasn’t changed, so the client can keep using the cached version \| \| 305: Use proxy \| Indicates the client should use a proxy to access the resource. This code has been deprecated. \| \| 307: Temporary redirect \| The resource has temporarily moved, and the client should use the same HTTP method (e.g., POST) as in the previous request \| \| 308: Permanent redirect \| The resource has permanently moved, and the client must use the same HTTP method as in the previous request \| \| 4XX: Client Error Codes \| \| \| 400: Bad request \| The server can’t process the request because of a client error \| \| 401: Unauthorized \| The client doesn’t have the proper credentials to access the resource \| \| 402: Payment required \| Originally meant to indicate the requested resource requires payment, but it’s rarely used and doesn’t have a standard purpose \| \| 403: Forbidden \| The client isn’t authorized to access the resource, even though the server knows the client’s identity \| \| 404: Not found \| The server can’t find the resource. Often because a browser is requesting an incorrect URL or the content no longer exists. \| \| 405: Method not allowed \| The request method (e.g., GET) isn’t allowed for the specified resource \| \| 406: Not acceptable \| The server can’t provide a response in any format the client specified \| \| 407: Proxy authentication required \| A proxy server needs to authenticate the client before the request can be processed \| \| 408: Request timeout \| The server gave up waiting because the client didn’t complete the request fast enough \| \| 409: Conflict \| The request conflicts with what’s already on the server (e.g., two people editing the same content at the same time) \| \| 410: Gone \| The requested resource has been permanently deleted. And there’s no forwarding address. \| \| 411: Length required \| The server didn’t accept the request because it didn’t specify how much data is being sent \| \| 412: Precondition failed \| A condition set in the request wasn’t met, so the server didn’t process it \| \| 413: Content too large \| The amount of data the client is sending is too big for the server to handle \| \| 414: URI too long \| The requested web address is too long for the server to manage \| \| 415: Unsupported media type \| The server doesn’t support the format the request is using \| \| 416: Range not satisfiable \| The requested part of a resource isn’t within the server’s available range \| \| 417: Expectation failed \| The server couldn’t meet a requirement specified in the request \| \| 421: Misdirected request \| The request went to the wrong server—one that isn’t set up to handle it \| \| 422: Unprocessable content \| The server understands the request format but is unable to process it because of issues with the actual data (e.g., wrong values) \| \| 423: Locked \| The requested resource is locked and inaccessible \| \| 424: Failed dependency \| The request failed because a related request also failed \| \| 425: Too early \| The server didn’t process the request because it was too early and might be replayed \| \| 426: Upgrade required \| The server won’t process the request unless the client switches to a newer or different protocol (like HTTPS) \| \| 428: Precondition required \| The server requires the request to include certain conditions to ensure safe updates \| \| 429: Too many requests \| The user sent too many requests too quickly \| \| 431: Request header fields too large \| The request headers contain too much information for the server to process \| \| 451: Unavailable for legal reasons \| The requested resource is blocked due to legal reasons \| \| 5XX: Server Error Codes \| \| \| 500: Internal server error \| The server encountered an error and couldn’t complete the request \| \| 501: Not implemented \| The server doesn’t support the request method \| \| 502: Bad gateway \| The gateway server received an invalid or no response from another server \| \| 503: Service unavailable \| The server is temporarily unavailable—usually because it’s down for maintenance or overloaded \| \| 504: Gateway timeout \| The gateway server didn’t get a response from another server in time \| \| 505: HTTP version not supported \| The server doesn’t support the HTTP version used in the request \| \| 506: Variant also negotiates \| A misconfiguration caused the server to get stuck in a loop when trying to choose between different versions of the resource \| \| 507: Insufficient storage \| The server doesn’t have enough space to save or process the request \| \| 508: Loop detected \| The server detects an endless loop while trying to process the request \| \| 510: Not extended \| The request is missing extensions the server requires for processing \| \| 511: Network authentication required \| The client needs to authenticate to gain network access \| ## How to Check a Webpage’s HTTP Status Codes You can easily check a page’s HTTP status codes using Google Chrome. Go to the webpage you want to check. Right-click anywhere on the page and select "Inspect” to open the Developer Tools. Or press “Ctrl + Shift + I” (Windows/Linux) or “Cmd + Option + I” (Mac). ![Inspect is highlighted in the right-click menu.](https://static.semrush.com/blog/uploads/media/aa/95/aa9516794d12beb900e226bb0fb0fc79/78f5eebd4d8269f38693b57673bc7e38/AD_4nXdrNGDyEzSOTjveTyCw_QxYjqy3Aad-8yqFRvpJs98mXQLIvNmlsl8EtPvQENQ-AyJ2rLhE4D0JomkOqjDUDMPUbobdVsFs5cDnTRs-20l4sIU7aSrzSCe3QChhDXLaV1AMU7hraQ.png) Click on the "Network" tab in the Developer Tools panel. Refresh the page (select “F5” or “Ctrl + R”). Look at the list of network requests. The “Status” column shows you a list of HTTP status codes for the page. The first one in the list is the page’s HTML document. ![The HTTP status code column is highlighted in the tool.](https://static.semrush.com/blog/uploads/media/2a/22/2a22a56d8b6c659776b8bf12a272d924/3eeb364f2e438db8ab62548f45bfb22c/AD_4nXcZbfMoZNBijFOVMj_GwvET-D_u-yodoNwDsX7qaXYXoDDrTh1o4lAvsCviVWBsMHxpAK8CDVNXjbewzGU2IeqWxXDHVl-pl2LP1gdAnSQFPpHho8frx2vE0DmY92Hkq04RNDe7.png) It’s also a good idea to audit your site for HTTP status code errors. You can do this easily in Semrush’s [Site Audit](https://www.semrush.com/siteaudit/) tool. Simply run a crawl and click on “Crawled Pages.” The “Status” column will show you the status code of each page so you can see if there are any errors that need fixing. ![The HTTP status code column is highlighted for the list of crawled pages.](https://static.semrush.com/blog/uploads/media/ff/21/ff2149146cfd67bb8902fde8055d560e/8581ed3ddd72f1210e56481eb2238b22/AD_4nXcS7lMhybffl42RA8Bzo-ylta5HGeujc6ElsQDnn-YIPzd7vqozZV5Ib3Cdu4t-gPmM3CCK2QhFqstF0J-ev5jpjVUQoknGxxb9M8bTs9nYc-uw13SnDimG-lI5D03LgFNL-IQt.png) ## The Implications of Common HTTP Status Codes for SEO Here’s what some of the most common status codes mean for your SEO: ### 200 (OK) A 200 response code is what you’ll want most of your webpages to return. It indicates that a webpage works and is accessible to both people and search engines. ### 301 (Moved Permanently) A [301 code](https://www.semrush.com/blog/301-redirects/) means you’ve permanently moved a page to a new URL. And signals to Google that the old URL in its index should be replaced with the new one. Importantly, a 301 redirect also transfers link equity from the old page to the new one. Which preserves your visibility. ![Two webpages link to the same page. These links pass link equity to that page and its 301 redirected page.](https://static.semrush.com/blog/uploads/media/bc/26/bc26230ee334d04c563cb51df4084779/9434b30f663eec6b32691af1a5ac0d03/AD_4nXcMj88QqFzbw4c-FIIy3n8G6cIavzBTDSLBL_qy4ODOaN6B9xne_K1SPqMYarRPT8gIG65cBUXOKKYBEZAWmT02T2xunhfveHf21cdTkTZkPXU46saTVu9iMKOvjrMW1JXqmc-65Q.png) ### 302 (Found/Temporary Redirect) A [302 redirect](https://www.semrush.com/blog/302-redirect/) is a temporary redirect. It can preserve links and rankings while a webpage is temporarily unavailable. For example, if you’re doing website maintenance and want to send users to a temporary holding page. Or you’re carrying out A/B testing. If a 302 redirect is in place for a long time, Google may start treating it as a 301 redirect. Meaning the old URL will be replaced by the new one in Google’s index. ### 404 (Not Found) and 410 (Gone) Both 404 and 410 status codes tell search engines that a page no longer exists, which typically leads to it being removed from the index. While both ultimately lead to deindexing, a 410 more clearly communicates that the page is gone for good. This can speed up its removalfrom search engine indexes. ### 5XX (Server Errors) Search engines have trouble accessing pages with 5XX errors, which can lead to problems with crawling, indexing, and the user experience. Over time, this can negatively impact visibility in search results. So it’s important to monitor and resolve 5XX errors promptly. ## The Impact of HTTP Status Codes on LLMs It’s important to make sure your content’s accessible to tools built on large language models (LLMs), like Google’s AI Overviews, ChatGPT, Perplexity, and Claude. Because it’ll help you gain more visibility in those AI responses. Status codes that signal errors—like 404s and 500s—can block LLMs from seeing your content. Because LLMs find and understand website content similar to traditional search engines. Web developer and AI engineer [Vincent Schmalbach](https://www.linkedin.com/in/vschmalbach/) notes: > “Sites with frequent HTTP status code errors may find their content underrepresented in both search results and AI-generated responses, since both systems require reliable access to index and utilize content effectively.” Vincent adds the following when talking specifically about 4XX and 5XX status codes: > “Both 404 and 410 responses mean no content is available, so those pages don't contribute to training data. Server errors like 500s cause crawlers to retry later, but persistent errors result in content being skipped entirely.” [Toby Basalla](https://www.linkedin.com/in/toby-basalla/), Founder and Principal Data Consultant at data analytics consultancy Synthelize, warns that a website with unintentional redirect status codes can skew data used to train the actual models if it's scraped all at once. Because those mistakes are difficult to spot among so much data. He reflects on a notable experience running a custom-trained LLM that relied on a scraped dataset: > “In one case, a client had 180 landing pages misflagged as temporary redirects, and none of it made it into our scraped dataset. Which means, in effect, those pages did not exist to the model.” ## Check Your Website for HTTP Status Code Errors You should check your website’s HTTP status codes regularly to stay on top of any errors. Semrush’s [Site Audit](https://www.semrush.com/siteaudit/) tool makes it easy to identify any of these problems. So you can swiftly address issues and boost your SEO performance. Share [Carlos Silva](https://www.semrush.com/blog/user/201654769/) Carlos Silva is a content marketer with 10+ years of experience in both in-house and agency roles. His expertise encompasses content strategy, SEO, content creation, and email marketing, with a focus on AI-enhanced content production. Carlos brings a comprehensive understanding of both traditional and AI-assisted digital marketing to his current role at Semrush, where he researches, edits, and writes for the English blog, helping readers navigate the evolving landscape of online marketing. Carlos Silva Carlos Silva is a content marketer with 10+ years of experience spanning both in-house and agency roles. His expertise spans content strategy, SEO, and AI-enhanced content creation. At Semrush, he researches, edits, and writes for the English blog. Share ## More on this ##### [SEO Checklist: 41 Tips to Optimize Your Website](https://www.semrush.com/blog/seo-checklist/ "SEO Checklist: 41 Tips to Optimize Your Website") Use this SEO checklist to improve your website’s search engine rankings. [General SEO](https://www.semrush.com/blog/category/general-seo/)19 min read ##### [301 Redirects: How to Use Them & How They Affect SEO](https://www.semrush.com/blog/301-redirects/ "301 Redirects: How to Use Them & How They Affect SEO") A 301 redirect sends users and search engines from an old URL to a new one, passing on the SEO value. [Technical SEO](https://www.semrush.com/blog/category/technical-seo/)11 min read ##### [Redirects: What They Are & How to Use Them](https://www.semrush.com/blog/redirects/ "Redirects: What They Are & How to Use Them") A redirect is a way to send users and search engines to a different URL than the one they requested. [Technical SEO](https://www.semrush.com/blog/category/technical-seo/)12 min read ##### [What Is Website Architecture? (& How to Improve it for SEO)](https://www.semrush.com/blog/website-structure/ "What Is Website Architecture? (& How to Improve it for SEO)") Website architecture refers to the structure of websites. Learn best practices for organizing your site for SEO. [Technical SEO](https://www.semrush.com/blog/category/technical-seo/)8 min read ## GET STARTED WITH SEMRUSH TODAY Try Semrush free for seven days. Cancel anytime. [Start free trial](https://www.semrush.com/signup/get-free-trial) Semrush - [Semrush One](https://www.semrush.com/one/) - [Features](https://www.semrush.com/features/) - [Pricing](https://www.semrush.com/pricing/) - [Compare Semrush](https://www.semrush.com/vs/) - [Success Stories](https://www.semrush.com/company/stories/) - [Stats and Facts](https://www.semrush.com/stats/) - [Affiliate Program](https://www.semrush.com/lp/affiliate-program/en/?utm_source=semrush&utm_medium=footer) More tools - [Enterprise SEO](https://enterprise.semrush.com/?utm_source=semrush&utm_medium=footer) - [Enterprise AIO](https://www.semrush.com/lp/enterprise-aio/en/) - [Enterprise SI](https://www.semrush.com/lp/site-intelligence/en/) - [Insights24](https://www.semrush.com/lp/insights/en/?utm_source=semrush&utm_medium=footer) - [Mfour](https://www.semrush.com/lp/mfour/en/?utm_source=semrush&utm_medium=footer) - [App Center](https://www.semrush.com/apps/?utm_source=semrush&utm_medium=footer) - [Top Websites](https://www.semrush.com/website/top/?utm_source=semrush&utm_medium=footer) - [Free Tools](https://www.semrush.com/free-tools/?utm_source=semrush&utm_medium=footer) - [Sensor](https://www.semrush.com/sensor/?utm_source=semrush&utm_medium=footer) Company - [About Us](https://www.semrush.com/company/) - [News](https://www.semrush.com/news/) - [Careers](https://careers.semrush.com/) - [Partners](https://www.semrush.com/company/partners/) - [For Investors](https://investors.semrush.com/) - [Semrush Select](https://www.semrush.com/company/semrush-select/) - [Global Issues Index](https://www.semrush.com/company/global-issues/) - [Contact Us](https://www.semrush.com/company/contacts/) Support - [Knowledge Base](https://www.semrush.com/kb/) - [Academy](https://www.semrush.com/academy/) - [Semrush API](https://www.semrush.com/api-documentation/) Community - [Semrush Blog](https://www.semrush.com/blog/) - [Webinars](https://www.semrush.com/academy/webinars/) - [Ambassador Program](https://www.semrush.com/lp/semrush-circle/en/?utm_source=semrush&utm_medium=footer) Legal - [Privacy Policy](https://www.semrush.com/company/legal/privacy-policy/) - [Terms of Service](https://www.semrush.com/company/legal/) - [Cookies Settings](https://www.semrush.com/blog/http-status-codes/) English - [English](https://www.semrush.com/blog/) - [Español](https://es.semrush.com/blog/) - [Deutsch](https://de.semrush.com/blog/) - [Français](https://fr.semrush.com/blog/) - [Italiano](https://it.semrush.com/blog/) - [Português (Brasil)](https://pt.semrush.com/blog/) - [日本語](https://ja.semrush.com/blog/) © 2008 - 2026 Semrush. All rights reserved. - [Privacy Policy](https://www.semrush.com/company/legal/privacy-policy/) - [Terms of Service](https://www.semrush.com/company/legal/) - [Cookies Settings](https://www.semrush.com/blog/http-status-codes/) English - English - Español - Deutsch - Français - Italiano - Português (Brasil) - 日本語
Readable Markdown	## What Are HTTP Status Codes? HTTP status codes are three-digit numbers servers generate in response to a client (e.g., a browser) request. They indicate whether the request was completed successfully. For example, a 404 error is a common HTTP status code you might have seen. ![A URL returns a 404 error page.](https://static.semrush.com/blog/uploads/media/81/c2/81c2c9105fe4a38571c5291d60299a69/82d45f4b44e16d95fc1551e16f38b6d9/AD_4nXcVEnCXbIk9M40jL80nMXv4Z-6IzP5icb4e-yjcmbjgz37gPymIwW6ympon2pdzCbhaANz3VqXJUoDUDDsB4qJRKuGODrLfcVNTJYG0kK5tDWpwnzNbJNRWLEy2MT6NJf3Qnts9sw.png) If you’re a website owner, HTTP status codes give you important information for improving your website’s functionality and user experience. And they can impact your SEO. ## Categories of HTTP Status Codes There are five categories of HTTP status codes: - 1XX (informational codes): The server received the request and is processing it - 2XX (success codes): The server successfully received and processed the request - 3XX (redirection codes):The server received the request, but there’s a redirect to another destination ([301 or 302](https://www.semrush.com/blog/301-vs-302-redirect/) are common) - 4XX (client error codes):The requested resource couldn’t be found or reached due to a client error - 5XX (server error codes): The server ran into an error when processing the request ## A Complete List of HTTP Status Codes \| \| \| \|---\|---\| \| Code \| Meaning \| \| 1XX: Informational Responses \| \| \| 100: Continue \| The server has received the initial request and is ready for the client to send the rest if it hasn’t already \| \| 101: Switching protocols \| The server agrees to accept the client’s request to change to a different protocol \| \| 102: Processing \| The server has received the request but hasn’t completed it. This code has been deprecated. \| \| 103: Early hints \| The server sends hints about the expected final response while the response is still being processed \| \| 2XX: Success Codes \| \| \| 200: OK \| The request was successful. The specific response depends on the request method (GET, PUT, etc.). \| \| 201: Created \| The request worked, so a new resource was created \| \| 202: Accepted \| The request was accepted but hasn’t been processed \| \| 203: Non-authoritative information \| The data returned is from a third party rather than from the original server \| \| 204: No content \| The request was successful, but there's no content \| \| 205: Reset content \| The request was successful, and the user agent (e.g., browser) should reset the document \| \| 206: Partial content \| The server is only sending part of the requested resource \| \| 207: Multi status \| Provides the statuses of multiple operations within a single response \| \| 208: Already reported \| Tells the client that a resource’s information has already been included earlier in the response and won’t be repeated \| \| 226: IM used (HTTP delta encoding) \| The server successfully handled the request and returned a version of the resource that includes only the changes—not the full resource \| \| 3XX: Redirection Codes \| \| \| 300: Multiple choices \| Indicates there are multiple possible responses, and the user or client needs to choose one \| \| 301: Moved permanently \| The resource has permanently moved to a new web address. The server provides the new URL. \| \| 302: Found \| The resource has temporarily moved to a different web address. But it might move again. \| \| 303: See other \| The server is telling the client to get the resource from another location using a standard GET request \| \| 304: Not modified \| The response hasn’t changed, so the client can keep using the cached version \| \| 305: Use proxy \| Indicates the client should use a proxy to access the resource. This code has been deprecated. \| \| 307: Temporary redirect \| The resource has temporarily moved, and the client should use the same HTTP method (e.g., POST) as in the previous request \| \| 308: Permanent redirect \| The resource has permanently moved, and the client must use the same HTTP method as in the previous request \| \| 4XX: Client Error Codes \| \| \| 400: Bad request \| The server can’t process the request because of a client error \| \| 401: Unauthorized \| The client doesn’t have the proper credentials to access the resource \| \| 402: Payment required \| Originally meant to indicate the requested resource requires payment, but it’s rarely used and doesn’t have a standard purpose \| \| 403: Forbidden \| The client isn’t authorized to access the resource, even though the server knows the client’s identity \| \| 404: Not found \| The server can’t find the resource. Often because a browser is requesting an incorrect URL or the content no longer exists. \| \| 405: Method not allowed \| The request method (e.g., GET) isn’t allowed for the specified resource \| \| 406: Not acceptable \| The server can’t provide a response in any format the client specified \| \| 407: Proxy authentication required \| A proxy server needs to authenticate the client before the request can be processed \| \| 408: Request timeout \| The server gave up waiting because the client didn’t complete the request fast enough \| \| 409: Conflict \| The request conflicts with what’s already on the server (e.g., two people editing the same content at the same time) \| \| 410: Gone \| The requested resource has been permanently deleted. And there’s no forwarding address. \| \| 411: Length required \| The server didn’t accept the request because it didn’t specify how much data is being sent \| \| 412: Precondition failed \| A condition set in the request wasn’t met, so the server didn’t process it \| \| 413: Content too large \| The amount of data the client is sending is too big for the server to handle \| \| 414: URI too long \| The requested web address is too long for the server to manage \| \| 415: Unsupported media type \| The server doesn’t support the format the request is using \| \| 416: Range not satisfiable \| The requested part of a resource isn’t within the server’s available range \| \| 417: Expectation failed \| The server couldn’t meet a requirement specified in the request \| \| 421: Misdirected request \| The request went to the wrong server—one that isn’t set up to handle it \| \| 422: Unprocessable content \| The server understands the request format but is unable to process it because of issues with the actual data (e.g., wrong values) \| \| 423: Locked \| The requested resource is locked and inaccessible \| \| 424: Failed dependency \| The request failed because a related request also failed \| \| 425: Too early \| The server didn’t process the request because it was too early and might be replayed \| \| 426: Upgrade required \| The server won’t process the request unless the client switches to a newer or different protocol (like HTTPS) \| \| 428: Precondition required \| The server requires the request to include certain conditions to ensure safe updates \| \| 429: Too many requests \| The user sent too many requests too quickly \| \| 431: Request header fields too large \| The request headers contain too much information for the server to process \| \| 451: Unavailable for legal reasons \| The requested resource is blocked due to legal reasons \| \| 5XX: Server Error Codes \| \| \| 500: Internal server error \| The server encountered an error and couldn’t complete the request \| \| 501: Not implemented \| The server doesn’t support the request method \| \| 502: Bad gateway \| The gateway server received an invalid or no response from another server \| \| 503: Service unavailable \| The server is temporarily unavailable—usually because it’s down for maintenance or overloaded \| \| 504: Gateway timeout \| The gateway server didn’t get a response from another server in time \| \| 505: HTTP version not supported \| The server doesn’t support the HTTP version used in the request \| \| 506: Variant also negotiates \| A misconfiguration caused the server to get stuck in a loop when trying to choose between different versions of the resource \| \| 507: Insufficient storage \| The server doesn’t have enough space to save or process the request \| \| 508: Loop detected \| The server detects an endless loop while trying to process the request \| \| 510: Not extended \| The request is missing extensions the server requires for processing \| \| 511: Network authentication required \| The client needs to authenticate to gain network access \| ## How to Check a Webpage’s HTTP Status Codes You can easily check a page’s HTTP status codes using Google Chrome. Go to the webpage you want to check. Right-click anywhere on the page and select "Inspect” to open the Developer Tools. Or press “Ctrl + Shift + I” (Windows/Linux) or “Cmd + Option + I” (Mac). ![Inspect is highlighted in the right-click menu.](https://static.semrush.com/blog/uploads/media/aa/95/aa9516794d12beb900e226bb0fb0fc79/78f5eebd4d8269f38693b57673bc7e38/AD_4nXdrNGDyEzSOTjveTyCw_QxYjqy3Aad-8yqFRvpJs98mXQLIvNmlsl8EtPvQENQ-AyJ2rLhE4D0JomkOqjDUDMPUbobdVsFs5cDnTRs-20l4sIU7aSrzSCe3QChhDXLaV1AMU7hraQ.png) Click on the "Network" tab in the Developer Tools panel. Refresh the page (select “F5” or “Ctrl + R”). Look at the list of network requests. The “Status” column shows you a list of HTTP status codes for the page. The first one in the list is the page’s HTML document. ![The HTTP status code column is highlighted in the tool.](https://static.semrush.com/blog/uploads/media/2a/22/2a22a56d8b6c659776b8bf12a272d924/3eeb364f2e438db8ab62548f45bfb22c/AD_4nXcZbfMoZNBijFOVMj_GwvET-D_u-yodoNwDsX7qaXYXoDDrTh1o4lAvsCviVWBsMHxpAK8CDVNXjbewzGU2IeqWxXDHVl-pl2LP1gdAnSQFPpHho8frx2vE0DmY92Hkq04RNDe7.png) It’s also a good idea to audit your site for HTTP status code errors. You can do this easily in Semrush’s [Site Audit](https://www.semrush.com/siteaudit/) tool. Simply run a crawl and click on “Crawled Pages.” The “Status” column will show you the status code of each page so you can see if there are any errors that need fixing. ![The HTTP status code column is highlighted for the list of crawled pages.](https://static.semrush.com/blog/uploads/media/ff/21/ff2149146cfd67bb8902fde8055d560e/8581ed3ddd72f1210e56481eb2238b22/AD_4nXcS7lMhybffl42RA8Bzo-ylta5HGeujc6ElsQDnn-YIPzd7vqozZV5Ib3Cdu4t-gPmM3CCK2QhFqstF0J-ev5jpjVUQoknGxxb9M8bTs9nYc-uw13SnDimG-lI5D03LgFNL-IQt.png) ## The Implications of Common HTTP Status Codes for SEO Here’s what some of the most common status codes mean for your SEO: ### 200 (OK) A 200 response code is what you’ll want most of your webpages to return. It indicates that a webpage works and is accessible to both people and search engines. ### 301 (Moved Permanently) A [301 code](https://www.semrush.com/blog/301-redirects/) means you’ve permanently moved a page to a new URL. And signals to Google that the old URL in its index should be replaced with the new one. Importantly, a 301 redirect also transfers link equity from the old page to the new one. Which preserves your visibility. ![Two webpages link to the same page. These links pass link equity to that page and its 301 redirected page.](https://static.semrush.com/blog/uploads/media/bc/26/bc26230ee334d04c563cb51df4084779/9434b30f663eec6b32691af1a5ac0d03/AD_4nXcMj88QqFzbw4c-FIIy3n8G6cIavzBTDSLBL_qy4ODOaN6B9xne_K1SPqMYarRPT8gIG65cBUXOKKYBEZAWmT02T2xunhfveHf21cdTkTZkPXU46saTVu9iMKOvjrMW1JXqmc-65Q.png) ### 302 (Found/Temporary Redirect) A [302 redirect](https://www.semrush.com/blog/302-redirect/) is a temporary redirect. It can preserve links and rankings while a webpage is temporarily unavailable. For example, if you’re doing website maintenance and want to send users to a temporary holding page. Or you’re carrying out A/B testing. If a 302 redirect is in place for a long time, Google may start treating it as a 301 redirect. Meaning the old URL will be replaced by the new one in Google’s index. ### 404 (Not Found) and 410 (Gone) Both 404 and 410 status codes tell search engines that a page no longer exists, which typically leads to it being removed from the index. While both ultimately lead to deindexing, a 410 more clearly communicates that the page is gone for good. This can speed up its removalfrom search engine indexes. ### 5XX (Server Errors) Search engines have trouble accessing pages with 5XX errors, which can lead to problems with crawling, indexing, and the user experience. Over time, this can negatively impact visibility in search results. So it’s important to monitor and resolve 5XX errors promptly. ## The Impact of HTTP Status Codes on LLMs It’s important to make sure your content’s accessible to tools built on large language models (LLMs), like Google’s AI Overviews, ChatGPT, Perplexity, and Claude. Because it’ll help you gain more visibility in those AI responses. Status codes that signal errors—like 404s and 500s—can block LLMs from seeing your content. Because LLMs find and understand website content similar to traditional search engines. Web developer and AI engineer [Vincent Schmalbach](https://www.linkedin.com/in/vschmalbach/) notes: > “Sites with frequent HTTP status code errors may find their content underrepresented in both search results and AI-generated responses, since both systems require reliable access to index and utilize content effectively.” Vincent adds the following when talking specifically about 4XX and 5XX status codes: > “Both 404 and 410 responses mean no content is available, so those pages don't contribute to training data. Server errors like 500s cause crawlers to retry later, but persistent errors result in content being skipped entirely.” [Toby Basalla](https://www.linkedin.com/in/toby-basalla/), Founder and Principal Data Consultant at data analytics consultancy Synthelize, warns that a website with unintentional redirect status codes can skew data used to train the actual models if it's scraped all at once. Because those mistakes are difficult to spot among so much data. He reflects on a notable experience running a custom-trained LLM that relied on a scraped dataset: > “In one case, a client had 180 landing pages misflagged as temporary redirects, and none of it made it into our scraped dataset. Which means, in effect, those pages did not exist to the model.” ## Check Your Website for HTTP Status Code Errors You should check your website’s HTTP status codes regularly to stay on top of any errors. Semrush’s [Site Audit](https://www.semrush.com/siteaudit/) tool makes it easy to identify any of these problems. So you can swiftly address issues and boost your SEO performance.
Shard	26 (laksa)
Root Hash	7464484988195878426
Unparsed URL	com,semrush!www,/blog/http-status-codes/ s443