“We noticed you may be using an ad blocker. SEO Site Checker relies on ads to keep our SEO tools free. Please consider disabling your ad blocker to support us - thank you!”“We noticed you may be using an ad blocker. SEO Site Checker relies on ads to keep our SEO tools free. Please consider disabling your ad blocker to support us - thank you!”
Enter one public web page address and see the HTML our server received, with the HTTP status, redirect steps and response headers. Search it, copy it or save it as a text file.
Enter one public web page address. Our server downloads it and shows the HTML it received as plain text, with line numbers. Nothing on the page is run or displayed.
What this shows, and what it does not
The HTML our server received from the address, after following up to 10 redirects, as text. Only the first 2,000,000 bytes (about 2 MB) are read, and the page says when it was cut.
It is the source before JavaScript runs. Content that a script adds later is not in it, so a page built in the browser can look nearly empty here.
A site can answer our server differently from your browser. Our server identifies itself as SEOSiteCheckerBot, not as a browser or a search engine, and some sites send bots a block page, a challenge or a different page. When we recognize one, the result says so.
A meta refresh tag is reported but not followed, no cookies are kept between redirects, and nothing is rendered: the page is shown only as text.
A very large page is drawn in part to keep your browser fast: at most 50,000 lines, and fewer on a slow phone or computer. Search and the jump links cover the lines that are drawn. Copy and Download always give you everything we received.
Control characters and the invisible characters that can hide or reorder text (zero-width spaces, soft hyphens, tag characters, direction overrides and similar) are shown as visible markers such as the symbol for NUL or [U+202E]. A few that real text needs, such as joiners, plain left-to-right marks and emoji variation selectors, are left as they are.
Result
Source
This is the HTML our server received, before any JavaScript ran. A browser may be shown a different page.
Jump to
What Is a Website Source Code Viewer?
Quick answer: To view page source with this tool, type one public web page address and press View source. Our server downloads the page and shows its HTML source with line numbers, plus status, redirects and headers. Enter an address in the tool above.
Ctrl+U shows what your browser received. This page source viewer fetches the page from our server and shows the raw HTML from before any JavaScript ran. It also works on a phone, where the menu often hides the option.
It suits web developers, website owners and SEOs who debug a page or troubleshoot a stray noindex, wrong canonical or odd redirect.
How to View the Source of a Website Online
To view source of a website online, use one field and one button.
Enter the address. Type it into "Web page address". A bare domain such as example.com works; the tool adds https:// itself.
Press View source. The status line reads "Fetching example.com...". A site without HTTPS can stall the read for about 5 seconds; try http:// in front of the address.
Read the result. The tool moves you to the Result heading: status, redirects and size, a closed Response headers box, then the Source. After a redirect, the source belongs to the final address, so read Redirects first.
Search or save it. Use Search the source, Wrap lines, Copy or Download .txt.
Two questions come before any HTML markup: did it redirect, and what did the server say?
Result row
What it tells you
HTTP status
The HTTP status code as a badge, such as 200 OK. A 404 error page is shown too, with a note.
Redirects
"None, the address answered directly." or "1 redirect followed", then each hop of the redirect chain with status, address and time.
Response headers
Final response headers in the order received, repeats such as Set-Cookie kept, up to 200. Redirect steps list no headers.
Received
The size once the server's compression is undone.
On November 2, 2026, our home page over http gave a 301 redirect, then a 200 with 11 response headers, two of them Set-Cookie. Received read 142.9 KB after decompression; Content-Length, the gzip size, said about 29,000 bytes.
Jump to the Title, Canonical, Robots Meta, Hreflang and JSON-LD
Press a chip in the Jump to row to land on its line, and again for the next match.
Chip
What it finds
What to check
Title
Every <title> tag, SVG titles included
One real title
Robots meta
Meta tags named robots, googlebot, googlebot-news or bingbot
No stray noindex
Canonical
The <link rel="canonical"> tag only, not a Link header
The canonical URL you expect
Hreflang
<link rel="alternate" hreflang> tags
Codes match your languages
JSON-LD
<script type="application/ld+json"> blocks
Structured data matches what you added
H1
The first <h1> heading and any more
Usually one
X-Robots-Tag header
The X-Robots-Tag response header, if one was sent
Whether it says noindex
A dashed chip with a 0 means none was in the source we received.
Noindex can arrive in a header too: in our run, this site's /login page answered with an X-Robots-Tag of "noindex, nofollow". Google's robots meta tag and X-Robots-Tag rules let the stricter one win, so check both.
Search before you scroll: our home page had 2,947 lines on November 2, 2026.
Search the source. Matches appear as you type. On that page, "canonical" found 2 matches, and "Canonical" with Match case on found "No matches."
Regex. A regular expression in JavaScript syntax, 300 characters at most; one still running after about two seconds is stopped. <h[1-3][ >] finds the h1 to h3 tags: 15 matches on that page.
Wrap lines. Minified code is one long line; line wrap folds it.
Copy and Download .txt. Both give you the text as shown: UTF-8 with LF line breaks, and common invisible characters as markers such as [U+202E]. Our home page arrived as 146,370 bytes and downloaded as 145,499, because its 871 CRLF line breaks each lose a byte.
View Page Source on iPhone, Android and Other Phones
To view page source on mobile, type the address into the tool above and press View source. It is an ordinary web page with no app, extension or bookmarklet, and phone browsers often hide the source option.
We checked the layout at 360 and 390 px wide in Chromium, not on an iPhone or Android device. The page does not scroll sideways; only the code box does, until you press Wrap lines. Buttons, chips and the search box are 44 px high. Copy is untested there; if it is refused, the tool says so, and Download .txt is the other route.
Why the Source Differs From What Your Browser Shows
Scripts are the usual reason. We show the raw server response, the HTML that arrived before any script ran. Your browser goes on to build the Document Object Model (DOM), visible as the live DOM in Chrome DevTools, so a page built by client-side JavaScript may arrive as a bare shell. Google renders pages after crawling too, so its rendered HTML can differ from the raw response (see how Google processes JavaScript).
A site can also answer our server differently. Our request announces itself as SEOSiteCheckerBot, asks for English (US) and keeps no cookies, so language, location or login state can change the answer. We chose an honest user agent over a disguise, and sometimes that costs us the real page.
Some sites answer bots with a challenge page or a block page. A fixed list of known ones gets an amber banner naming the provider; in our run, a page behind a Cloudflare challenge came back as HTTP 403 with that banner. We never try to get past one, and an unrecognized page is shown as received. For more on what bots fetch, read how search engines crawl pages.
Limits to Know Before You Look
Small limits stop one site from hogging this online source code viewer.
One public address per run. The tool refuses http://localhost/, private addresses, ports other than 80, 443, 8080 and 8443, and addresses with a user name and password: "That address is not allowed."
Redirects. More than 10 are refused with "The address redirects more than 10 times." A page that reloads itself with a meta refresh tag is noted, never followed.
Size. A very large specification page we tried was cut: Received read "1.91 MB (cut at 2,000,000 bytes)". When a page is drawn in part, only Copy and Download hold the tail.
Time. A read stops at 12 seconds, and a silent site ends with "The website took too long to answer."
Not offered. Formatting, a user agent or cookie choice, page comparison, saved history and separate CSS or JavaScript views.
A per-minute limit. A free account gets a higher one, and all visitors share a per-website limit that a busy site can hit.
What Happens to the Page You Look At
The fetched page is shown as text only. Nothing in it runs, and we never serve it back as a web page.
The site you look at sees a request from our server that names itself SEOSiteCheckerBot, not one from your browser or your IP address. We do not save the page text, and the lookup is not recorded in our tool usage history. Short-lived limit counters use the host you typed and your IP address. Our web server keeps access logs, so this is not a promise of anonymity.
Frequently Asked Questions (FAQs) is a list of common questions and answers provided to quickly address common concerns or inquiries.
How do I view the page source of a website?
In most desktop browsers, right-click the page and choose View Page Source. Chrome and Edge also take Ctrl+U on Windows, Option+Command+U on a Mac, or view-source: before the address. For a phone, use our view page source tool.
What is the difference between View Page Source and Inspect Element?
View Page Source shows the HTML the server sent first. Inspect Element opens developer tools on the live DOM, the page after JavaScript has changed it. This tool shows only the first kind, so use developer tools for the live page.
Why does the source look different from the page I see?
Scripts add content after the HTML arrives, which the source never contains. A site can also answer our server differently because it sees SEOSiteCheckerBot, English (US) and no cookies. To see what scripts added, use Inspect Element in your own browser.
Can I view page source on an iPhone or Android phone?
Yes. To view page source online from a phone, type the address into the tool above and press View source. We checked the layout in browser windows 360 and 390 px wide, not on a real device. If Copy fails, use Download .txt.
Can I view the source of any website?
Only public pages, one address at a time. A page behind a login returns what a signed-out visitor gets, because we send no cookies. A recognized protection page is shown and labeled, never bypassed, and local or private addresses are refused.
Is there a size limit for the page source?
Yes. We read the first 2,000,000 bytes, and the result says when a page was cut. The end of a cut page is not shown, so open that page in your own browser's source view to read the tail.
Is it legal to view the source code of a website?
Reading the HTML of a public page is what every browser does when it loads one. Reusing someone else's code depends on copyright and the site's terms. This is general information, not legal advice, so ask a lawyer about a specific case.
Do you store the pages I look at?
We do not save the page text, and the lookup is not recorded in our tool usage history. The address feeds counters that last about a minute. Copy and Download use text your browser already holds, so nothing goes to us.
How do I find a specific tag or word in the page source?
Use the Jump to chips for the title, robots meta, canonical, hreflang, JSON-LD and H1. For any other tag, such as the meta description, type part of it into Search the source: plain text matches as you type; Regex takes patterns.
We use cookies to personalize content and ads, to provide social media features and to analyze our traffic. You consent to our cookies if you continue to use our website.
Install SEO Site CheckerFree SEO tools - always in your pocket.
