[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Robots.txt Unreachable

129 views · 1 like · 3 posts


Akashdeepsharma996 Gmailcom (@akashdeepsharma996-g) · 2024-08-08

```
HTTP/2 200 
accept-ranges: bytes
access-control-allow-origin: *
age: 0
cache-control: public, max-age=0, must-revalidate
content-disposition: inline
content-type: text/plain
date: Thu, 08 Aug 2024 12:43:58 GMT
etag: "e0fcb1056077197be574fe703c80743e"
server: Vercel
strict-transport-security: max-age=63072000
vary: RSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Url
x-matched-path: /robots.txt
x-vercel-cache: PRERENDER
x-vercel-id: bom1::7l4r2-1723121038658-afc4281b1078
content-length: 198
```
https://tabeer.ae/robots.txt
I am still getting Unreachable on Google Search Console


Pauline P. Narvas (@pawlean) · 2024-08-08 · ♥ 1

Hi, @akashdeepsharma996-g!

Does this solution help?

https://community.vercel.com/t/unreachable-robots-txt/386/5


Akashdeepsharma996 Gmailcom (@akashdeepsharma996-g) · 2024-08-08

The header will be added in next.config ?? right
```
/** @type {import('next').NextConfig} */
const nextConfig = {
  images: {
    remotePatterns: [
    ],
  },
  async headers() {
    return [
      {
        source: '/:path*',
        headers: [
          {
            key: 'Accept-Language',
            value: 'en-US,en;q=0.5', // Default language header
          },
        ],
      },
    ];
  },
};

export default nextConfig;

```