Skip to main content

View Page Source

Fetches any public page and shows the raw HTML and response headers a crawler receives.

We fetch the page for you. Our server fetches the public address you enter and reads the response. Nothing you enter is stored. Free, no account.

How it works

You need the HTML the server actually sent, not the version a browser builds after scripts run. This tool requests the address from our server, follows redirects, and shows the HTML as it arrived, with line numbers, search, response headers, status code and redirect chain next to it.

  1. 1

    We request the address from our server, follow redirects, and show the HTML exactly as it arrived, with line numbers and search.

  2. 2

    The response headers, status code, redirect chain, compression and size are listed next to it.

  3. 3

    You can fetch as a desktop or a phone browser to see whether the site sends different HTML to each.

What it does not do

  • This is the HTML before any JavaScript runs. A page built in the browser will look almost empty here, which is exactly what crawlers that do not run scripts see.

  • Pages over 2 MB are cut at that size. Pages behind a login are not reachable.

When a source is busy or a site does not answer, this tool says so. It never fills the gap with a guess.

Questions

What do the response headers tell me?

They are the instructions the server sends before the HTML. The status code says whether the page exists, a redirect chain shows where the address leads, and headers such as X-Robots-Tag, Cache-Control and Content-Type decide whether a crawler may index the page and how long a browser keeps it. The tool lists them next to the source.

Why is the source nearly empty for my site?

This is the HTML before any JavaScript runs. If your page is built in the browser, most of its content arrives later, so the source looks bare. Crawlers that do not run scripts see the same bare page. Fetch as a phone or desktop browser to compare what each gets.

Can I view a page behind a login?

No. Pages behind a login are not reachable, because the fetch runs from our server without your session. For those, open the page while logged in and use View Source or the Network panel in your own browser. Pages over 2 MB are cut at that size.