5+1 tools to check rendered HTML of any page

Published 9 days ago • 1 min read

This shouldn’t come as a surprise to you:

Google uses rendered HTML of your page to evaluate the page’s optimization.

First, let’s make sure we’re on the same page here.

What is rendered HTML?

Rendered HTML is displayed after CSS and JavaScript are processed.

It means that if you’re only relying on the source code for your SEO efforts, it’s easy to miss many important things that can be altered by JavaScript, such as:

Rewritten title tag
A sneaked noindex tag
A removed canonical
Added/removed links

That’s why it’s critical to look into the rendered HTML vs source code when evaluating SEO of any page.

Use these 5+1 tools to check the rendered HTML of any page 👇👇👇

1. Inspect URL in the Google Search Console

2. Google Rich Results test tool

It shows the same info as the URL Inspection tool in the Google Search Console but comes in handy when you’re looking at a website you don’t have GSC access for (like your competitor’s)

3. Chrome Dev tools

You can see rendered HTML in the Elements tab:

4. SEO Pro browser extension (Chrome & Mozilla)

All the SEO info you see in the SEO Pro extension is based on the rendered HTML:

5. View Rendered Source Chrome extension

It shows you a comparison between the page source code and rendered HTML so that you can spot any changes

+1 Rendering Difference Engine

This is a new extension launched by my friends The Gray Dot Co. It highlights discrepancies between response HTML and rendered HTML. the extension makes it easy to use the findings to facilitate a JavaScript audit and clearly document JS SEO issues for decision makers and developers.

Grab this free resource 👇

5 tools to check rendered HTML of any page

Download a free PDF with a copy of this email, so it's easy for you to get back to it when you need (no signup required) 👇👇👇

Download a free PDF

Optimize critical rendering path

Do you know what the Critical rendering path is? It’s what your browser goes through in order to build a beautiful usable page from your source code. It requires communication between the server and browser: Steps to render a page in a browser (Critical rendering path) Begin constructing the DOM by parsing HTML incrementally Request CSS and JS files Parse CSS and construct CSSOM Execute JS, build a render tree Merge Document and CSS Object Models Run layout and paint Optimizing critical...

3 days ago • 1 min read

🚨 Source code vs rendered HTML: Critical Differences you must know

Critical knowledge alert 🚨🚨🚨 As a technical SEO, it’s crucial you know the difference between source code and rendered HTML them. Source code It is the initial code of the page before any JavaScript files are executed and CSS files are parsed. It’s the code you see when viewing the source code of a page in your browser. Rendered HTML It is displayed after CSS and JavaScript are processed. When you inspect an element on a page using Chrome dev tools, you’re looking at the rendered HTML. Why is...

17 days ago • 1 min read

3️⃣ steps to debug JavaScript SEO issues

JavaScript is a great option to make website pages more interactive and less boring. But it’s also a good way to kill a website’s SEO if implemented incorrectly. Tired Oh No GIF by Law & Order That’s why, as a technical SEO, you need to be comfortable debugging JavaScript issues. Here’s how you do it in 3 steps 👇👇👇 Step 1: Disable JavaScript in the browser using Web Developer Chrome extension The easiest way to do it is to disable JavaScript in your browser. I use the Web Developer Chrome...

24 days ago • 1 min read