🤔 Content SEO vs Technical SEO


Sponsored:

Explore the Wix Studio SEO resource center

Ramp up productivity with a growing library of expert-crafted templates, toolkits, and checklists, designed to speed up SEO implementation on any project. From a GA4 event cheat sheet to a customizable podcast planning template and a yearly client goal planner, these resources are created by the industry’s most trusted experts for SEOs, marketers, designers and developers.

Customize and use them on your next project to streamline SEO processes and set your clients up for lasting search success.

​Download Resources>​

Content SEO vs Technical SEO.

They serve the same purpose but use different tools.

But which of them is more important? 🤔

Content (or on-page) SEO and technical SEO are both parts of website optimization.

On-page SEO is written content.

It helps a page to be relevant and meet user intent so it’s competitive enough to rank.

Technical SEO is everything that lies outside of written content.

It helps this page to be crawled and indexed so that it can be ranked on Google and users can find it.

Plus, technical SEO plays a role in user experience through page speed, accessibility, etc.

Let's use the Title tag as an example.

With the title tag, on-Page SEO is responsible for:

  • Using the right keywords in the title tag
  • Its length
  • Its user intent

While technical SEO is responsible for:

  • Having the title tag in the right place in the HTML layout of the page - the section
  • Making sure that the section is configured properly and doesn’t have any
  • Correct JavaScript handling so that the title tag is not accidentally re-written after the page is rendered

I love this chart that shows how the importance of Technical vs Content SEO changes as a website is growing:

Credit: Mark Williams-Cook, SEO tips​

​

As you can see, to be a successful SEO, you need to know both parts, as one doesn’t go without the other.

(It’s like shoes - you need both of them)

But let me guess:

Most likely, you already know content SEO pretty well.

But lack of technical SEO understanding keeps you second-guessing yourself and your abilities making you feel like an imposter.

If that’s the case, I have something for you... Tech SEO Pro!

​

Tech SEO Pro is the only online course created for experienced SEO who want to master technical SEO skills and ditch imposter syndrome for good. Get more info here >

​

Content SEO vs Technical SEO

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

​

Smart SEO Newsletter

I'll help you trade an imposter syndrome for a technical SEO superpower. My mission is to break down and simplify complex technical SEO things so that you can understand and use them to advance your SEO career.

Read more from Smart SEO Newsletter

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...

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...

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...