🚨 6 must-dos while editing an .htaccess file

Published 6 months ago • 1 min read

🚀 Psst... Here's the truth:

It's not enough to send your recommendations to developers and call it a day. They won't implement any of your smart ideas (sad, right?)

What you need to do instead is to start speaking the same language with developers (and it does not = becoming one 😉).

This is the only way to get your SEO recommendations implemented.

I created the BRIDGE framework to help you with that. And I teach it inside my short but impactful GSI course:

Get SEO implemented Bridge Framework by Kristina Azarenko, MarketingSyrup SEO Academy.

Check out the Get SEO Implemented course>>

Let’s talk about the almighty .htaccess (most SEOs avoid).

The .htaccess file configures how your Apache-based web server operates.

You can set up site-wide (like www to non-www) and individual (like Page A to Page B) redirects there.

Note:

Never EVER edit .htaccess directly in your CMS (even if plugins give you this option). Especially if you don't have FTP access to revert the changes in case any error occurs.

The .htaccess file rules to NEVER break:

Make a backup of the website installation before accessing .htaccess
Always download the initial .htaccess file before editing it. Save its unedited copy if you need to revert your changes quickly.
Make sure that the .htaccess file is saved in the right format and that no invisible characters are added to it.
Before uploading your edited .htaccess to the server, run it through a validator (this will help to identify if there are any special characters which are not directly seen in the file)
If everything is OK, upload the updated file to the root folder, replacing the old one
Check the website in different browsers to make sure it works (and not just cached).

Have you ever edited an .htaccess file? Any stories to share? Let me know.

Grab this free resource 👇

6 must-dos while editing an .htaccess file

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

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