Skip to content

Raw Source. Rendered DOM. The Difference.

See what the server sent, what the browser built, and what changed in between. Quickly debug SEO and dev issues.

Join 38,004 other SEOs and devs

Trail Runner - Shop https://shop.example.com/products/trail-runner
Raw Source
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Trail Runner - Shop</title> <script src="/app.js" defer></script> </head> <body>
Rendered DOM
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Trail Runner - Shop</title> <link rel="canonical" href="https://shop.example.com/products/trail-runner"> <script src="/app.js" defer></script> </head> <body>
Difference
Added Removed SEO
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Trail Runner - Shop</title> <link rel="canonical" href="https://shop.example.com/products/trail-runner"> <script src="/app.js" defer></script> </head> <body>

38,004 installs

on the Chrome Web Store

Nick LeRoy
“Ever found a tool you didn't want to share with others? View Rendered Source is that tool.”
Nick LeRoy, Author of #SEOForLunch Newsletter

Featured in

  • Search Engine Journal
  • Moz
  • Ahrefs
  • Search Engine Land
  • Core Updates
  • Sitebulb
  • BuzzSumo

View Source is useless in 2026

After the HTML arrives, JavaScript runs. It changes some tags, adds new ones and removes others. The page you're looking at is not the page in View Source. View Rendered Source shows the raw source, the rendered DOM, and the difference between them.

Debug tricky on-page SEO issues and hydration problems. Check your pages are visible to AI tools like ChatGPT.

Would you spot these changes manually?

Raw Source
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Trail Runner Shoes | Northpeak</title> <meta name="theme-color" content="#fff"> <link rel="canonical" href="https://northpeak.com/trail-runner"> <link rel="stylesheet" href="/app.css"> <script src="/app.js" defer></script> </head> <body> <div id="root"> <header class="site-header"> <a href="/">Northpeak</a> <a href="/shoes">Shoes</a> <a href="/sale">Sale</a> </header> <main> <h1>Trail Runner</h1> <p>Free delivery on all shoes.</p>
Rendered DOM
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Northpeak | Home</title> <meta name="theme-color" content="#fff"> <link rel="canonical" href="https://staging.northpeak.com/"> <link rel="stylesheet" href="/app.css"> <script src="/app.js" defer></script> </head> <body> <div id="root"> <header class="site-header"> <a href="/">Northpeak</a> <span data-href="/shoes">Shoes</span> <span data-href="/sale">Sale</span> </header> <main> <h1>Trail Runner</h1> <p>Free delivery on all shoes.</p>
Difference
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Trail Runner Shoes | Northpeak</title> <title>Northpeak | Home</title> <meta name="theme-color" content="#fff"> <link rel="canonical" href="https://northpeak.com/trail-runner"> <link rel="canonical" href="https://staging.northpeak.com/"> <link rel="stylesheet" href="/app.css"> <script src="/app.js" defer></script> </head> <body> <div id="root"> <header class="site-header"> <a href="/">Northpeak</a> <a href="/shoes">Shoes</a> <a href="/sale">Sale</a> <span data-href="/shoes">Shoes</span> <span data-href="/sale">Sale</span> </header> <main> <h1>Trail Runner</h1>
  1. 1Title tag rewritten by JavaScript
  2. 2Canonical now points to the staging site
  3. 3Internal links are no longer links

How it works

Install from the Chrome Web Store

Add to Chrome
  1. 1Launch it on any page

    On the page you want to audit, launch with the toolbar, right-click, or Alt+U

  2. 2See three panels

    Raw Source, Rendered DOM, and Difference open side by side.

  3. 3See what changed

    In the Difference panel, see what was added, removed or changed. Filter by important SEO elements.

    Difference All Changes Added Removed SEO
    <meta name="robots" content="noindex"> <meta name="robots" content="index">

Inventory

Review key page elements together in one table and see where Raw and Rendered disagree.

Inventory: Raw Source shows noindex, a shorter title and a different H1 than the Rendered DOM

Does your SEO survive JavaScript?

JavaScript can hide, delay or break your titles, canonicals, headings and structured data. Turn on the SEO filter in the Difference panel to see only the tags search engines care about, and exactly how they changed.

See only what matters for SEO

Quickly filter in the Difference panel to show only changes that matter for SEO. See if JavaScript changes, removes, or breaks them.

Or filter by All, Changes, Added or Removed. Click a filter to try it.

Difference
<head> <title>Trail Runner Shoes | Northpeak</title> <title>Northpeak | Home</title> <link rel="canonical" href="https://northpeak.com/trail-runner"> <link rel="canonical" href="https://northpeak.com/"> <link rel="stylesheet" href="/app.css"> <script src="https://chat.example/widget.js"></script> </head> <h1>Trail Runner</h1> <div class="loading"></div>
Difference panel for Compare the Market: JavaScript added scripts, A/B test attributes and other markup that is not in the Raw Source

<link rel="canonical">

Injected canonicals

JavaScript changed or added your canonical. Catch it before Google does.

<title>Blue Widgets</title> <link rel="canonical" href="/widgets?page=2"> </head>

<title> <meta>

Title and meta changes

The title in the raw HTML isn't the one users and crawlers end up with. Descriptions and robots tags can change the same way.

<title>Blue Widgets | Acme</title> <title>Acme | Home</title> <meta name="robots" content="index"> <meta name="robots" content="noindex">

</head>

The head closes early

An <iframe> pixel closed the head early. Title, canonical and robots fell into the body.

<iframe src="/pixel.html"></iframe> </head><body> <link rel="canonical" href="/blue"> </head><body>

application/ld+json

Structured data

See schema that only exists after rendering, or disappears.

<script type="application/ld+json"> {"@type":"Product","name":"Blue Widget"} </script>

<a href> <h1>

Links and headings from JavaScript

Links that exist only in the rendered DOM. A second H1 that appears after hydration.

<h1>Acme</h1> <h1>Blue Widgets</h1> <a href="/widgets/blue">Blue Widget</a>

<script src>

Third-party scripts

Tag managers, chat widgets and A/B tests inject their own markup. See exactly what they added to your page.

</main> <script src="https://chat.example/widget.js"></script> <div id="chat-launcher"></div>

Catch hydration mismatches in plain sight

React, Vue, Next and Nuxt can render different HTML on the server and in the browser. The Difference panel shows you that mismatch, line by line. No console archaeology.

DevTools Elements shows the live DOM. It does not show the raw HTML the server sent, and it has no diff.

Server HTML says signed out. The browser says signed in.

<nav class="account"> <a href="/login">Sign in</a> <a href="/account">Hi, Sam</a> </nav>

Essential for SEOs and developers

“An essential bit of tech. I've been using it for years. Great stuff!”
Crystal CarterHead of AI Search & SEO Communications at Wix
“This has been super useful on a lot of occasions. Thanks for making it!”
Glen AllsoppHead of Marketing Strategy & Research at Ahrefs / Detailed.com founder
“Not sure how I did SEO or QA without this. I literally use it almost every time I look at the source code of a page now.”
Rob WoodsSenior Director, SEO at EssilorLuxottica

Upgrade to Pro to save and compare Snapshots.

Migrating, redesigning or shipping to production? Snapshot the page before, compare after, and share a link with your team or client.

Pro

Take a Snapshot

Save the raw, rendered and diffed source to your account, with capture date and an optional private note.

Pro

Snapshots library

Browse, filter by date, title, URL or note, and reopen any Snapshot whenever you need it.

Pro

Compare any two

Diff two Snapshots across time, before and after a migration, or across environments like staging and production.

Pro

Share a public link

Anyone can open it, no extension needed. Send it to a client or your team.

Snapshots library: a table of saved Snapshots with capture date, title, URL and comment filters
Compare Snapshots: pick a Snapshot and Raw or Rendered for the left and right panels

Free forever. Or try Pro free for 7 days.

Free

$0

Free forever. No account needed.

Add to Chrome, it's free  
  • Raw Source, Rendered DOM and Difference panels
  • SEO filter for titles, canonicals, headings, hreflang, JSON-LD and more
  • One-click inventory summary of key page elements
  • Find, filter, copy and download in every panel
  • Auto-formatted source with syntax highlighting
  • Light and dark theme
Pro

$10 per license per month, billed annually ($120/year)

Same extension. Activate with a license key in Settings.

7 days free, then $120/year. Cancel anytime. Each license covers one browser.

Everything in Free, plus:

  • Snapshots save the date-stamped raw, rendered and diff to your account for later
  • Compare any two Snapshots, from different dates or even domains
  • Share links anyone can open, no extension needed
  • Email support
Buying for a team? Save up to 10%
120

4 or more licenses save 5%. 11 or more save 10%.

FAQ

Still have questions? Email [email protected]

What does the View Rendered Source extension do?

It shows you two versions of a page side by side: the Raw Source, which is the HTML the server sends, and the Rendered DOM, which is the page after JavaScript has run. It then highlights the differences between them, so you can see what JavaScript added, removed or changed. SEOs use it to check what search engines and AI crawlers can see. Developers use it to debug hydration mismatches, check what a framework renders on the server, or find what a third-party script injected.

What is the difference between Raw Source and the browser's View Page Source?

They show the same HTML, but Raw Source is formatted and syntax highlighted, so it's easier to read.

How do I open it?

Click the toolbar button, use the right-click menu, or press Alt+U.

How do I check if Google sees my content?

As a general rule, if it's in the Raw Source, all crawlers see it. If it's only in the Rendered DOM, only Google sees it, and only after it renders the page. Rendering lags behind crawling, sometimes significantly.

How do I check what AI crawlers see?

Use Raw Source. Most AI crawlers don't run JavaScript because it's slow and expensive to render, so they only see the HTML the server sends.

Can I compare a staging site against production?

Yes, with Pro. Take a Snapshot of the page on each site, then compare the two Snapshots later to see what's different.

Do people who get my share link need the extension or an account?

No. Anyone with the link can open it in their browser. They don't need the extension or an account.

Can I change the Alt+U keyboard shortcut?

Yes. If it conflicts with another extension, change it at chrome://extensions/shortcuts.

Does any data leave my browser?

In the free version everything stays in your browser. With Pro, if you Take a Snapshot the raw and rendered sources are saved to your account. Share links you create are public but unguessable URLs, not indexable by search engines and revocable at any time.

How is it different from DevTools Elements?

Elements shows the live DOM. It does not show the raw HTML the server sent, and it has no diff. To compare the two in DevTools you copy both into a diff tool and spot what's important yourself.

How do Pro and licensing work?

One license covers one browser. Activate with your code in the extension Settings. Pro lets you take Snapshots, compare them later and create share links. Buy 4+ licenses for your team and get 5% off, and buy 11+ for 10% off. First 7 days are free.

Can I get a refund?

Email [email protected] within 14 days of your first payment and we'll refund you in full. After that, if you cancel, Pro stays active until the end of the period you paid for and doesn't renew. We don't refund the unused part of a period.

See what JavaScript changed.

Join 38,004 SEOs and developers.

Add to Chrome, it's free