Hi Federico,
Sorry for the delayed response.
Yes. The extension should do the trick.
Thank you!
Dino
Welcome to the Q&A Forum
Browse the forum for helpful insights and fresh discussions about all things SEO.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Hi Federico,
Sorry for the delayed response.
Yes. The extension should do the trick.
Thank you!
Dino
Hi folks,
I have run into a situation were a new client has 3 TLDs (e.g. mycompany.com, mycompany.org and mycompany.biz), all with the same content. They are on a Windows IIS environment, which I am not familiar with. Until now, all of my clients have been Linux/Apache environment, so I always dealt with these issues utilizing htaccess. Currently all resolve to the same IP, but the URL remains the same in the browser address field (e.g. if you type-in mycompany.org - it remains as such).
We want the .org and .biz version to 301 Redirect to the .com TLD.
I am wondering what the best practice might be in this situation? Could we simply redirect at the registrar level or would implementation at the server level be best? If so, I would really appreciate an example from someone with experience implementing redirects on IIS.
Thank you!
While I am not familiar with Magento specifically; principal concepts of on-page optimization should hold true.
I wouldn't worry about an exact match (and whether or not someone is going to query that exact term) in your H1 tags, rather, keep your keywords toward the front and even include variants of the page title tag. Similar to the meta description, the H1 no longer contributes a strong search ranking signal, but should definitely be utilized in structuring taxonomies of information on the site.
For example, if those tabs fall below an H2 or H3 on your page, I wouldn't place the H1 in that position. As a matter fact, I wouldn't place the H1 there, period. As you know, the H1 is meant to be used as a heading tag and to provide a weighted emphasis to content that is to follow. Stick to using the H1 as it was intended to be used and produce copy for your audience.
Perhaps you could have your developer remove the H1 from wrapping your category or product, and instead, parse a configurable H1 attribute as the first line when viewing the information contained "Product Details" tab.
Just an idea...