Don't block Google from crawling your new HTTPS site

[sharminakter]

Some recommend using only relative URLs for your resources. If you know how to handle the common needs of your website, you don't need to do this step. You just need to make sure that all the content on the site is covered by the right protocol. And don't forget your XML sitemap !

You'd be surprised how many audits I've done on sites that haven't done this step: making sure all of their content is secure.

It doesn't matter whether you use relative or absolute URLs, as long as you keep them up to date on the site. You can switch to relative URLs if you prefer, but if your site is built on absolute URLs, use a search uae telegram data and replace option with your database, if your site allows it. This will help eliminate any cases of mixed content.

Make sure your URLs are properly prefixed with after the transition, and you shouldn't encounter any significant issues.

You need to make sure that everything in your robot.txt is crawlable. Unless you have a specific issue, like a folder that shouldn’t be indexed, it makes sense to allow Google to crawl everything on the site, even CSS and JS files. If your site doesn’t allow CSS and JS files to be rendered, you could run into problems.

For example, if you disallow rendering of an essential CSS or JS element on the page, you may prevent Google from understanding the full context of the page, which is important for better rankings. Also, in about 99% of cases, there is no reason to disallow CSS or JSS files in this way.

Semrush's Site Audit tool will give you a lot of useful information regarding your HTTPS implementation. It shows you the issues you may encounter and offers recommendations on how to fix them.