- Home
- Page analysis
- Page Source Viewer
Page Source Viewer
See the code your server actually sends, before any JavaScript runs.
A direct HTTP request, with no JavaScript executed and no cookie. The document displayed is exactly the one a crawler receives on its first pass. No usage limit.
What this tool is for
What you see in your browser is not what a crawler receives. Your browser executes the JavaScript, applies your cookies, takes your session and your language into account. The initial document sent by the server is often far poorer.
The gap can be considerable. On a site built entirely on the client, the initial document sometimes comes down to an empty tag and a script. The content appears afterwards, in the browser — but a crawler that does not wait sees nothing.
This tool fetches that raw document. It lets you check that your meta tags are present, that your main content exists without JavaScript, and that your structured data is emitted. It also reveals what you did not mean to expose: internal paths, development comments, email addresses.
The decisive test: look for a sentence from your main content in the code fetched. If it is not there, your page depends on JavaScript to exist in the engines’ eyes — and that dependence is a risk.
How to read the results
The response code opens the analysis. 200 is normal. A 301 or 302 means the address requested is not the address served, and the redirect checker will set out the journey. A 404 or a 500 needs no comment.
The response headers reveal the server configuration: content type, encoding, cache directives, security headers. It is also where any X-Robots-Tag shows up, which can forbid indexing with no tag appearing in the page at all — a case particularly hard to diagnose any other way.
The head section concentrates most of the SEO signal. Check for the title, the description, the canonical, and the absence of an unwanted noindex.
The body of the document answers the question that counts: is your content there? Look for a specific sentence from your text. Its presence guarantees that engines see it on the first pass.
The JSON-LD blocks hold your structured data. Their absence means you are eligible for no rich result.
Common mistakes
Trusting the code shown by the browser inspector. The inspector shows the state of the document after JavaScript has run, not the document received. The two can have almost nothing in common.
Leaving development comments in production. They regularly hold server paths, environment names, sometimes credentials. All of that is public.
Ignoring the X-Robots-Tag header. A page can be deindexed by an HTTP header while no noindex tag appears in the HTML. That is invisible to anyone looking only at the page.
Believing Google always executes JavaScript. It does, but with a variable delay and no guarantee. Essential content has to be in the initial HTML, without exception.
Testing only with the browser agent. Comparing the response as Googlebot sometimes reveals that a firewall blocks crawlers. That is a cause of complete deindexing, and it is undetectable while browsing normally.
Going further
- Googlebot SimulatorSee a page exactly as a search engine crawler sees it
- Meta Tags AnalyzerTitle, description, Open Graph and indexing directives of a page
- Exposed Email FinderEmail addresses visible in the code
Frequently asked questions
How does this differ from right-click “view source”?
Your browser shows the code after executing the JavaScript and applying your context: cookies, session, language, device. This tool fetches the raw document the server returns to an anonymous visitor. That is what a crawler sees on the first pass, and it is often very different.
Why does my content not appear in the code fetched?
Because it is generated by JavaScript in the browser. Google executes JavaScript, but on a second pass that can be days late, and with no guarantee. Content absent from the initial HTML is content whose indexing is uncertain — the main flaw of sites built entirely on the client.
Can I see the code of a password-protected page?
No. The tool arrives as an anonymous visitor and only reaches public pages. A page behind authentication will return the login page, which is useful information in itself: it confirms the protection works.
What is the point of changing the user agent?
To find out whether the server serves different content depending on the visitor. Some sites return a stripped-down version to crawlers, others block automated requests outright. Comparing the response as a browser and as Googlebot reveals that differential treatment immediately.
Does this tool respect robots.txt?
This is a one-off look at a public page at your request, not automated crawling. It is the equivalent of a visit with right-click. For large-scale crawling, on the other hand, respecting robots.txt is indispensable — which is what the crawler simulator does.
What should I look at first in the code fetched?
Three things, in order. The head section, which holds the meta tags and the canonical. The actual presence of your main content, which confirms it is readable without JavaScript. And the JSON-LD structured data, which determines your eligibility for rich results.