🤖 Don't let AI kill your technical SEO expertise

Published 4 months ago • 1 min read

This is not your typical "AI tools and secrets for tech SEOs" post.

Because the tools and secrets are secondary.

The first thing is your expertise.

I know, it can be an unpopular opinion. But hear me out.

Every day, there's a new post on LinkedIn about "that great new AI tool for technical SEOs". It gets overwhelming as you already have a list of AI tools to try, and you never have time to get to it. So you add that another tool to your list, hoping one day you'll have time to explore it.

(you most likely won't).

That's why I wanted to share with you a few thoughts that might help you.

Video gif. A gray tabby cat quickly puts on a pair of round sunglasses and looks up. Text, "I'm ready." — Im Ready Lets Go GIF by Leroy Patterson

Here are 2 different approaches that one can take:

Tools first

❌ Overwhelmed by the amount of available tools

❌ Trying to find "the right scenario" to test a tool

❌ Using tools to replace you or a portion of your work without building a solid process first

😭

Knowledge first

✅ You rely on your technical SEO expertise first

✅ You build solid processes for different aspects of your work

✅ You integrate specific AI tools that help you streamline your processes

😎

Integration is the main point here

1️⃣ First, you need to have deep technical SEO knowledge and processes (I teach ALL of it in my Tech SEO Pro course).

2️⃣ You look for the processes (or parts of them) that can be automated without losing the quality.

3️⃣ Only then do you choose the best tool (sometimes through trial and error) to automate these processes or parts of them.

That's why knowledge comes first and tools are secondary.

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

about 1 month ago • 1 min read

5+1 tools to check rendered HTML of any page

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

about 2 months 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...