SEO Impact of HTTP 206 Status Code

HTTP 206 status code means the server has successfully delivered only a requested portion of a resource. It is commonly used for video streaming, PDF files, large downloads, and other resources that support partial downloads.

However, there is an important difference between a browser requesting a small part of a video and a crawler receiving only part of an HTML document.

Let’s look at how HTTP 206 works, its possible SEO impact, and how you can investigate it without treating every occurrence as a technical SEO issue.

What is HTTP 206 Partial Content?

HTTP 206 is a successful HTTP response status code. A server returns it when a client requests a specific portion of a resource instead of the entire resource.

This usually happens through an HTTP request header called Range.

For example, imagine you have a 20 MB PDF file. A visitor wants to download it, but their internet connection gets interrupted after downloading 5 MB.

Instead of downloading the entire file again, their browser or download manager can request the remaining portion.

The server responds with HTTP 206 and sends the requested bytes.

This saves bandwidth and allows the client to resume downloads or access specific parts of large files.

206 response indicates that the server has successfully fulfilled a range request.

How does an HTTP 206 response work?

Suppose you have a PDF file with a total size of 10,000 bytes.

A browser sends this request:

GET /technical-seo-guide.pdf HTTP/1.1
Host: example.com
Range: bytes=0-999

The Range header tells the server that the client wants bytes 0 to 999, rather than the entire PDF.

The server responds:

HTTP/1.1 206 Partial Content
Content-Type: application/pdf
Content-Range: bytes 0-999/10000
Content-Length: 1000
Accept-Ranges: bytes

[First 1000 bytes of the PDF]

Here is what the response tells us:

HeaderMeaning
HTTP 206The partial request was successful
Content-TypeThe requested resource is a PDF
Content-RangeBytes 0–999 were delivered out of 10,000
Content-LengthThe response contains 1,000 bytes
Accept-RangesThe server supports byte-range requests

Note: The browser can request additional portions until it has enough data to complete the file.

Why do websites return HTTP 206?

A 206 response is not something that happens randomly. It usually appears because a browser, media player, download manager, or another client requests a specific portion of a resource.

Here are some common situations.

1. Video streaming

Video players often request specific portions of video files instead of downloading the entire video before playback.

For example, a visitor watching a 500 MB video might jump directly to the 10-minute mark.

The browser can request the required portion of the video using a Range header. The server responds with 206 Partial Content if it successfully fulfils the request.

This allows visitors to seek through videos without downloading the entire file first.

2. Audio streaming

Audio players can also use range requests.

Imagine someone listening to a long podcast. They skip the introduction and move directly to the middle of the recording.

The player may request a particular byte range from the audio file.

The server returns the requested portion with a 206 response.

3. PDF files

PDF viewers may request specific sections of a document rather than downloading the complete file before displaying anything.

This is particularly useful for large technical manuals, research papers, product catalogues, and documentation.

4. Resuming interrupted downloads

This is another common use case.

Suppose someone is downloading a 100 MB software package, but their connection drops after 60 MB.

The download manager can request the remaining bytes instead of starting again.

The server responds with 206 if the requested range is available.

5. Large images and other downloadable files

Some clients request portions of large resources to reduce unnecessary data transfer.

This can happen with large images, archives, and other files that support byte-range requests.

Note: HTTP 206 is generally associated with resource delivery, not the normal delivery of an entire HTML webpage.

What is the SEO impact of HTTP 206?

HTTP 206 belongs to the 2xx success category. Google explains that content returned with a 2xx status code may be considered for processing, including indexing.

However, a successful HTTP response does not automatically mean that Google will index the content.

Therefore, we should not claim that every 206 response is harmless or that every 206 response causes indexing problems.

Instead, the SEO impact depends on what was requested and what the server actually delivered.

When HTTP 206 does not create an SEO problem

Suppose your page contains:

  • HTML content
  • Images
  • CSS files
  • JavaScript files
  • A downloadable PDF

A visitor opens the article and starts watching an embedded video.

The browser requests a portion of the video file, and the server responds with 206.

Meanwhile, the main HTML page returns 200 OK.

In this situation, the 206 response is normal. The HTML page is still available as a complete document.

There is no reason to change the response status code simply because the video returns 206.

The same applies to legitimate partial requests for PDFs and other downloadable resources.

When HTTP 206 deserves investigation

Now consider a different situation.

A search engine crawler requests an important HTML page, but the server responds with only a portion of its content.

For example:

  • The original HTML document contains 50 KB of content.
  • The server sends only the first 10 KB.
  • The response is 206 Partial Content.
  • Important page content, internal links, or metadata may be missing from the returned portion.

This is not the same as a normal video range request.

If the client receives an incomplete HTML representation and cannot retrieve the remaining bytes, it may not have access to the complete page.

That could affect how the page is understood, how its links are discovered, and how its content is processed.

However, this is a potential implementation problem, not evidence that HTTP 206 itself carries a ranking penalty.

My recommendation: Investigate unexpected 206 responses on important HTML URLs, but don’t waste time fixing legitimate partial responses from media and downloadable resources.

Does Googlebot treat HTTP 206 as a successful response?

Yes, HTTP 206 is part of the 2xx success category. Google’s general guidance says that when a server responds with a 2xx status code, the received content may be considered for indexing.

This means we should distinguish between two things:

  • HTTP success: The server successfully fulfilled the requested range.
  • SEO success: The search engine has enough relevant content to understand and potentially index the page.

These are not the same thing.

For example, if Googlebot requests a PDF resource and receives a valid byte range, that is a legitimate HTTP operation.

But if an important HTML page is consistently delivered incompletely, you should investigate whether the crawler can access the complete page.

Do not assume that Googlebot will automatically combine every partial HTML response into a complete document. The HTTP specification describes how clients can process and combine range responses, but that does not establish how Google’s indexing pipeline handles every such situation.

HTTP 206 vs other HTTP status codes

SEO professionals often confuse 206 with other successful HTTP responses. Understanding the differences makes server-log analysis much easier.

Status codeMeaningTypical use
200OKComplete successful response
206Partial ContentRequested portion of a resource
304Not ModifiedReuse previously stored content
204No ContentRequest successful, no response body
416Range Not SatisfiableRequested byte range cannot be fulfilled

The most important distinction is between 200 and 206.

A 200 response generally delivers the complete selected representation, while a 206 response delivers the requested portion.

A 304 response is different again. It tells the client that its previously stored representation can be reused when the resource has not changed.

What is the difference between HTTP 206 and HTTP 416?

These two responses are closely related.

A 206 response means the requested range can be fulfilled.

A 416 response means the requested range cannot be fulfilled.

For example, suppose a file contains 10,000 bytes.

A client requests:

Range: bytes=0-999

The server can fulfil this request and return 206.

But if the client requests:

Range: bytes=15000-20000

The requested bytes are outside the file’s available range.

The server can return:

HTTP/1.1 416 Range Not Satisfiable
Content-Range: bytes */10000

This tells the client that the resource is 10,000 bytes long and the requested range is unavailable.

A 416 response is not automatically an SEO problem either. You need to establish why the range was requested and whether the underlying resource is working correctly.

How to check HTTP 206 responses on your website

You don’t need an expensive SEO tool to investigate this status code.

You can use browser developer tools, cURL, or server logs to identify the cause.

Here are three practical methods.

Method 1: Check using Chrome DevTools

This is one of the easiest ways to identify which resource is returning 206.

Follow these steps:

  1. Open your website in Google Chrome.
  2. Right-click anywhere on the page and select Inspect.
  3. Open the Network tab.
  4. Reload the webpage.
  5. Look at the Status column.
  6. Filter requests by status code 206.

When you find a 206 response, click the request and inspect the following information:

  • Request URL
  • Request method
  • Status code
  • Request headers
  • Response headers
  • Content-Type
  • Content-Range

Pay special attention to the Request Headers section.

If you find something like:

Range: bytes=0-1023

the client is requesting a specific byte range.

Now inspect the response headers:

HTTP/1.1 206 Partial Content
Content-Range: bytes 0-1023/500000
Content-Type: video/mp4

This is a normal example of a partial video response.

However, if the same thing happens to the main HTML document, investigate further.

Method 2: Test using cURL

If you prefer working from the command line, cURL makes it easy to test partial responses.

First, check the normal response:

curl -I https://example.com/technical-seo-guide/

Then send a request with a Range header:

curl -i \
-H "Range: bytes=0-999" \
https://example.com/technical-seo-guide/

If the server supports range requests for that resource and fulfils the request, you may receive:

HTTP/2 206
Content-Range: bytes 0-999/50000
Content-Length: 1000

The important thing is to compare both responses.

TestWhat to check
Normal requestDoes the URL return 200?
Range requestDoes it return 206 when supported?
Content-RangeDoes it identify the correct byte range?
Content-LengthDoes it match the returned response body?

Remember that a server may ignore a Range header and return the full resource with 200. That is also valid HTTP behaviour.

Method 3: Analyse server logs

This is particularly useful when you want to understand whether search engine crawlers are receiving 206 responses.

Your server logs should ideally contain:

  • Requested URL
  • HTTP response status
  • User agent
  • Request method
  • Request headers, where available
  • Response size
  • Timestamp

Look for requests returning 206 and identify the corresponding user agents.

For example:

URLUser agentStatusResource
/videos/seo-guide.mp4Chrome206Video
/files/seo-manual.pdfChrome206PDF
/technical-seo/Googlebot200HTML
/images/banner.webpChrome206Image

This is a perfectly reasonable pattern.

But imagine your logs show:

URLUser agentStatusResource
/technical-seo/Googlebot206HTML
/seo-guide/Googlebot206HTML
/seo-audit/Googlebot206HTML

Now you have something worth investigating.

Check whether Googlebot actually sent a Range header, whether the response contained the complete representation, and whether the same URLs return 200 to normal requests.

Also verify that the requests genuinely came from Googlebot. User-agent strings can be spoofed. Use Google’s documented crawler verification methods before concluding crawler behaviour.

Google recommends using server logs to investigate crawling activity and the URL Inspection and Crawl Stats tools to diagnose crawling issues.

What should you do if important HTML pages return HTTP 206?

First, don’t change the status code blindly.

A 206 response is not necessarily incorrect. The goal is to understand why the server is returning it.

Here is how I would approach the investigation.

1. Check whether the request contains a Range header

Look at the original request.

If it contains:

Range: bytes=0-1023

the client is explicitly requesting a portion of the resource.

If there is no Range header but the server returns 206, investigate the application, CDN, reverse proxy, or server configuration.

A 206 response without a corresponding range request is not automatically proof of a fault, but it deserves closer inspection.

2. Check the Content-Range header

The Content-Range header tells you exactly which portion of the resource was delivered.

For example:

Content-Range: bytes 0-999/50000

This means the response contains bytes 0 through 999 from a representation with a total length of 50,000 bytes.

Check whether the returned range matches the request.

Also remember that the total representation length is not necessarily the same as the response’s Content-Length.

3. Compare the normal and partial responses

Request the URL without a Range header and compare it with the response containing the Range header.

Check:

  • Whether the normal request returns the complete HTML.
  • Whether the partial response contains the requested bytes.
  • Whether the content is consistent across both responses.
  • Whether the ETag and other relevant validators are handled correctly.

4. Check your CDN and server configuration

If important HTML pages are unexpectedly returning partial responses, review the configuration of:

  • Web servers such as Apache and Nginx.
  • CDNs and reverse proxies.
  • Application-level response handlers.
  • Caching layers.
  • Custom middleware that processes Range requests.

Look for rules that might be applying partial-content behaviour to resources that should be served as complete HTML documents.

5. Verify the page using Google Search Console

Use URL Inspection to test important URLs.

Check the last crawl information, indexing status, and available rendered-page information.

If the page is not indexed, don’t immediately blame HTTP 206.

Also investigate canonical tags, robots directives, rendering problems, internal links, content quality, and server availability.

Does HTTP 206 affect crawl budget?

There is no documented evidence that a legitimate 206 response automatically wastes Google’s crawl budget or creates a crawl-budget penalty.

However, unnecessary resource requests, inefficient delivery, and server availability problems can affect crawling efficiency.

For example, if a website has thousands of large media files, repeated resource requests may increase server workload and bandwidth usage.

But that does not mean every 206 response is harmful.

Google’s crawling documentation explains that crawling depends on factors such as server capacity, crawling demand, response speed, and resource availability.

My advice is to focus on the actual problem:

  • Are important HTML pages accessible?
  • Are resources unnecessarily requested multiple times?
  • Is the server responding efficiently?
  • Are important pages being crawled?
  • Are there genuine availability issues?

Don’t optimise a status-code report simply to reduce the number of 206 responses.

Common HTTP 206 mistakes SEO professionals should avoid

Here are a few mistakes I would avoid during a technical SEO audit.

Mistake 1: Treating every 206 response as an error.

A video or PDF returning 206 is often doing exactly what it should.

Mistake 2: Changing all 206 responses to 200.

This can break legitimate range requests, video seeking, and resumable downloads.

Mistake 3: Ignoring the Content-Range header.

The status code alone does not tell you which portion of the resource was delivered.

Mistake 4: Assuming Googlebot cannot process a 206 response.

Google categorises 206 under the 2xx success family, but its public documentation does not specify every detail of 206 processing.

Mistake 5: Confusing successful crawling with indexing.

Even a page returning 200 OK is not guaranteed to be indexed. The same distinction applies when investigating other successful responses.

FAQs about HTTP 206

1. Is HTTP 206 good or bad for SEO?

HTTP 206 is neither inherently good nor bad for SEO. It is a successful response used to deliver requested portions of resources. It becomes worth investigating when important HTML pages are unexpectedly delivered incompletely.

2. Is HTTP 206 an HTTP error?

No. HTTP 206 belongs to the 2xx success category. It indicates that the server has successfully fulfilled a partial-content request.

3. Can Google index pages returning HTTP 206?

Google considers 2xx responses for further processing, but its documentation does not explicitly describe all the details of indexing pages returned with 206. If an HTML page is only partially delivered, investigate whether the complete content is accessible to the crawler.

4. Why does my website return 206 instead of 200?

Your website may return 206 because a browser or another client has requested a specific byte range using the Range header. This is common with videos, audio files, PDFs, and large downloads.

5. How do I fix HTTP 206 errors?

You generally don’t need to fix legitimate 206 responses. If important HTML pages return unexpected partial responses, investigate the Range header, Content-Range, server configuration, CDN, and application-level response handling.

6. Does HTTP 206 affect crawl budget?

There is no established rule that legitimate 206 responses waste crawl budget. However, inefficient resource delivery and server availability problems can affect crawling efficiency.

7. What is the difference between HTTP 200 and 206?

HTTP 200 generally indicates that the complete selected resource was successfully returned. HTTP 206 indicates that the server successfully returned the requested portion of a resource.

8. What is the difference between HTTP 206 and 304?

HTTP 206 delivers a requested portion of a resource. HTTP 304 tells the client that its previously stored version can be reused because the resource has not changed.

My opinion

HTTP 206 is one of those status codes that can look concerning in an SEO audit but often has nothing to do with an actual SEO problem.

If your video, audio, or PDF files return 206, that is usually normal behaviour. You don’t need to change anything just to make the status code disappear.

However, if important HTML pages return unexpected partial responses, investigate them. Check the request headers, response headers, server logs, and the actual content delivered to crawlers.

Technical SEO is not about making every URL return 200. It is about making sure that search engines and users receive the right content through the right HTTP response.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top