XML Sitemap Best Practice for Multilingual Websites – Should I list my URLs in any language or is it sufficient to use rel = "alternate" + hreflang?

I am working on the sitemaps of a multilingual website and have doubts about the best way to refer to each language version of a page.

For a bit of background, the site points to around 20,000 places with community commentary and descriptions. The website is available in 5 languages ​​(website.com/fr; website.com/it …)

Currently, my sitemap only refers to English pages and in the sitemap on every page I have specified for any language (as well as English) as recommended by Google.

In the Google search console, about 75% of the pages with valid coverage are described as "indexed, not submitted to the sitemap", so I think the alternative link with the "hreflang" attribute is not enough to display the page for " to "Google" to index it.

Do I have to list and use the pages in all 5 languages ​​in my sitemap? at every link?

cache – rel = "dns-prefetch" / rel = "preconnect" against remote expiration headers …?

I've always been a big fan of far-futures expiry headers. The first visit to my website's home page will result in 40 HTTP requests, but a subsequent visit will be 1, and the answer is as snappy as you would expect. That's great, very happy.

I just learned about DNS Prefetch and Preconnect. I can see that they would (slightly) help with loading for the first time, but I suppose the extra overhead on subsequent loads is a bad thing, as I would initiate some DNS lookups / SSL handshakes for domains that will not function. do not even get used to it.

What is the best course of action or how did you tackle this?

htaccess – rel canonical for http and https

Simply set the Canonical to the (preferred) HTTPS version. Both HTTP and HTTPS are still available. Google will probably prefer the HTTPS version over HTTP anyway, no matter what protocol you set in rel = "canonical" Day (because it will probably know that both HTTPS and HTTP are available).

Setting the Canonical condition based on the protocol does not make sense – both HTTP and HTTPS probably serve the same content? You can not have two different "canonical URLs" for the same content.

seo – Google custom search shows redirect URLs to external links, even though rel = "do not follow noopener" for those links

I have a website that contains a list of all businesses in my area. They all have a profile page that can contain a Facebook or website URL.

I added rel = "nofollow noopener" to all external links, but it seems that this does not work and Google continues to index the redirector. If I search this in Google: Website: www.mijngistel.be I still see Facebook links, etc.

I did not set this at the top of the site, but I made that change a few months ago.

What is wrong?

html – rel = "norferrer noopener" in target = "_ blank" external links

Many websites I read say that you must use rel = "norferrer noopener" when using target = "_ blank" within external links.

I can understand why you should use Noopener as a precaution against reverse tabnapping and also for performance benefits. I understand too noreferrer For older browsers like Firefox version 51 and lower, as they are not supported Noopenerbut as suggested in GitHub:

Attempting to serve legacy browsers is in vain, as there are numerous other vulnerabilities that make these browsers vulnerable. If the user wants to be sure, he should use the latest browser.
– Comment by mojavelinux (May 1, 2017)

Use noreferrer Also affects Google Analytics data.

What is the current attitude regarding the use of noreferrer within target = "_ blank" External links?

html – rel = "norferrer noopener" in target = "_ blank" links

Many websites I read say that you must use rel = "norferrer noopener" when using target = "_ blank" within left.

I can understand why you should use Noopener as a precaution against reverse tabnapping and also for performance benefits. I understand too noreferrer For older browsers like Firefox version 51 and lower, as they are not supported Noopenerbut as suggested in GitHub:

Attempting to serve legacy browsers is in vain, as there are numerous other vulnerabilities that make these browsers vulnerable. If the user wants to be sure, he should use the latest browser.
– Comment by mojavelinux (May 1, 2017)

Use noreferrer Also affects Google Analytics data.

What is the current attitude regarding the use of noreferrer within target = "_ blank" Left?

schema.org – Combination of RDFa Lite authoring scheme and rel = "author" HTML markup

The rel Attribute has two different purposes that might conflict:

  • Simple HTML code: provide a connection type
  • RDFa: provide a property (just like that property Attribute, but with some technical differences)

In both sections, it is interpreted as a Schema.org property¹ author, not the link type author,

The best way to avoid such confusion in general is not to use it vocabulary, Use prefix Instead (or rely on the RDFa core initial context):




  
Contact



  
Contact

Note that Google is now reporting an error:

The property http://www.w3.org/TR/html5/links.html#link-type-author is not recognized by Google for an object of the type person,

This is not a problem, you can ignore it because the generated URI shows that Google's SDTT correctly recognizes that rel value is a link type (which can also be used as an RDF property) and is no longer interpreted as a Schema.org property. This error is also output when properties from vocabularies other than Schema.org are used. This is a very good and useful measure.


¹ Side Note: If I understand Listen Point 7 correctly, an RDFa parser should ignore that rel Attribute in your particular case because you have the property Attribute for the same element and yours rel does not contain a CURIE / URI value.

Google Search Console – rel = "next" in Anchor Tag is not working

I have hundreds of duplicate meta descriptions in Google Webmaster Tool because of the pagination. Page pages appear as duplicates in the tool. So I added that rel = "next" and rel = "prev" to the pagination link anchor tags. But it seems like it will not work.

I've read the Google Office webmaster's blog post. I never mentioned that to add an anchor tag to the rel attributes. So just add the rel attribute with the link or it will work with the anchor tag as well.

Example:

 

I've posted a couple of unofficial blogs mentioning it will work with Anker. Can someone please tell me what I'm doing wrong here!