sitemap – Is there an SEO or pagerank advantage in grouping (rel = "alternative") multilingual websites (using multiple domains) together?

I am building this website which will be multi-region / multi-language.

And for that, Google suggests the following:

https://support.google.com/webmasters/answer/182192?hl=en

enter description of image here

Since, my domain will have to change according to the language of the country, I will have to go there with Option 1.

A country-specific area.

Example:

  • www.name-in-english.net
  • www.name-in-deutsch.net
  • www.name-in-spanish.net
  • www.name-in-french.net

Since they all have different domains, if I don't let Google know that this is the same website, they will all be treated as unique and unique websites.

Google suggests "grouping" them using one of these 3 options:

https://support.google.com/webmasters/answer/189077

enter description of image here

If I do, I will use the Sitemap option.

But my question is:

What do I gain by letting Google know that all of these websites are identical, but in different languages? What will be different if I let Google think that these are unique and separate websites?

Do I need to gain SEO or pagerank by doing this?

I mean, what if I get a lot of traffic to my website in English Does it benefit my other languages ​​in other areas?

meta tags – Is it legitimate that rel prev / next links indicate a circular sequence of pages?

First of all, Yes, Google no longer takes note of rel prev / next and has not (officially) done so for almost a year. Google is officially discouraged rel prev / next as an exploration / indexing factor on March 21, 2019:

Unofficially, Google has stopped taking note of rel prev / next several years before that.

But, as with any web document meta-information, simply because Google doesn’t use rel prev / next, does not mean that it no longer represents useful information about the library.

In fact, Google itself even points this out:

rel prev / next may in particular:

  • help accessibility
  • represent a resource pre-fetching advice to mariners.

So here I am, a year after the official announcement still using rel prev / next perfectly happy to create a chain of product pages that each show and discuss one of a set of related products.

To date, I have used rel prev / next to indicate a straight line of product pages from the first product page to the last product page:

Product Page 1 ==> Product Page 2 ==> Product Page 3

This is it.

Therefore:

  • Product Page 1 has no ; and
  • Product Page 3 has no

But would there be something absurd and / or illegitimate to give Product Page 3 a pointing to Product Page 1 and vice versa?

for example. Product 3 ==> Product 1 ==> Product 2 ==> Product 3 ==> Product 1

I would love to implement it, but first I want to verify that creating a circular sequence of pages is not, in principle, an abuse of pagination, in some way so.

Do these monads on Rel compose?

$ Rel $ is the category of sets and relationships.

The cyclical list monad, $ mathcal {Cy} = (Cy, mu_c, eta_c) $ is defined as follows:

$ Cy: Rel $ Rel $ rightarrow,
such as, $ Cy (X) $ All cyclic lists in the set X. A cyclic list is similar to a list, except that each element points to the next element, and that each element has exactly one predecessor pointed in the list. The list thus forms a cycle or a circle.
$ mu_c: Cy cdot Cy rightarrow Cy $
so that a cyclic list of cyclic lists maps all the cyclic lists found by decomposing the internal lists in all possible ways and concatenating the resulting flat lists.

We know that multiset is a monad, $ mathcal {Mu} $ sure $ Rel $.

I would like to know if the following composition is also a monad $ Rel $.

$ mathcal {Cy} cdot mathcal {Mu} $

These are cyclic lists of multisets.

Best practices for multilingual websites – Should I list my URLs in each language or use of rel = "substitute" + is hreflang sufficient?

I'm working on the sitemaps of a multilingual website and I have a doubt about the best practice for referencing each language version of a page.

For a bit of background, the website references about 20,000 places with comments and descriptions of the community. The website is available in 5 languages ​​(website.com/fr; website.com/it …)

For the moment, my site map only refers to English pages and the site map for each page I specify. for each language (as well as English) recommended by Google.

In the Google Search Console, I find that about 75% of the pages with valid coverage are described as "indexed, not submitted in Sitemap", which makes me think that the alternative link with the hreflang attribute not enough to "submit" the page. google to index it.

Do I have to list the pages in the 5 languages ​​of my sitemap and use them as well? on each link?

Google adds new options to rel = NOFOLLOW attribute

When introducing nofollow, Google would ignore links marked this way as a signal to use in our search algorithms. This has now changed. All link attributes [sponsored, UGC, and nofollow] are treated as indications of which links to consider or exclude in the search.

htaccess – canonical rel for http and https

Battery Exchange Network

The Stack Exchange network includes 176 question and answer communities, including Stack Overflow, the largest and most reliable online community on which developers can learn, share knowledge and build their careers.

Visit Stack Exchange

seo – Google Custom Search showing redirection URLs to external links despite rel = "nofollow noopener" on these links

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

I've added rel = "nofollow noopener" to all the external links, but it seems that it does not work and that Google always indexes the redirector. When I search this in Google: website: www.mijngistel.be I still see Facebook links, etc.

I did not define this at the beginning of the website, but I made this change a few months ago.

What's wrong?

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

In many sites that I've read, they say you have to use rel = "noreferrer noopener" using target = "_ blank" in the external links.

I can understand why you should use noopener as a precaution against reverse tabnapping and to improve performance. I also understand using noreferrer for older browsers such as Firefox versions 51 and lower, because they do not support noopenerbut as suggested in GitHub:

Trying to support older browsers is futile because there are many other security exploits that these browsers are exposed to. If the user wants to be secure, he must use the latest browser.
– Comment by mojavelinux (May 1, 2017)

Using noreferrer also affects Google Analytics data.

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

html – rel = "noreferrer noopener" in the links target = "_ blank"

In many sites that I've read, they say you have to use rel = "noreferrer noopener" using target = "_ blank" in the links.

I can understand why you should use noopener as a precaution against reverse tabnapping and to improve performance. I also understand using noreferrer for older browsers such as Firefox versions 51 and lower, because they do not support noopenerbut as suggested in GitHub:

Trying to support older browsers is futile because there are many other security exploits that these browsers are exposed to. If the user wants to be secure, he must use the latest browser.
– Comment by mojavelinux (May 1, 2017)

Using noreferrer also affects Google Analytics data.

What is the current position regarding the use of noreferrer in target = "_ blank" connections?

tried to put this <link rel = "canonical" href = "https://www.example.com"> as a canonical beacon

This message appears in the dashboard "The URL of your website has recently been changed." Automatic payments and customer emails have been disabled to prevent live transactions from development or storage servers intermediate." As I am new to this field, I have no idea what I should do to solve this problem.