First of all, yes, Google no longer notes rel prev / next and he hasn't done it (officially) for almost a year. Google officially deprecated rel prev / next as a tracking / indexing factor in March 21, 2019:
Unofficially, Google stopped taking note of rel prev / next Several years before that.
But, as with any web document metainformation, just because Google is not using rel prev / next, does not mean that it is not useful information from the library, independently.
In fact, Google itself even highlights this:
rel prev / next can, not least, help accessibility and represent a valuable resource pre-fetching Suggestion for browsers.
So, here I am, one year after the official announcement, I still use rel prev / next perfectly happy to create a chain of product pages that show and discuss one of a set of associated products.
To date, I have use rel prev / next To indicate a straight line of product pages from the first page of the product to the last page of the product:
As the PageSpeed information tool report stated that my page could be improved by preloading 2 of the sources on my page, I added rel="preload" to the Tags in question. However, PageSpeed Insights still complains that these sources are not being preloaded, but only for the mobile version. The desktop version is fine.
That said, here is the exact code for one of the sources:
Also, I checked to make sure that JS is not adding that after loading the page, and it is not. That is what I get in the first request in the response body.
I am using a custom font on my WP site. It is now included with @font-face css attribute. But I wonder if there is any way to wp_enqueue this file with the attribute rel="preload" and may be some other attributes. Then you see something like this in the browser:
I am working on the site maps of a multilingual website and I have doubts about the best practices to refer to each language version of a page.
For a little background, the website refers to around 20,000 places with community comments and descriptions. The website is available in 5 languages (website.com/fr; website.com/it …)
At the moment, my site map only refers to pages in English and on the site map for each page that I specify for each language (as well as English) as recommended by Google.
In Google Search Console, I see that approximately 75% of pages with valid coverage are described as "indexed, not submitted on Sitemap", which makes me think that the alternative link with the hreflang attribute is not enough to "send" the Google page to index it.
Should I list the pages in the 5 languages on my site map and use them too?
When nofollow was introduced, Google would not count any links marked in this way as a signal to use within our search algorithms. This has now changed. All link attributes [sponsored, UGC and nofollow] are treated as clues about which links to consider or exclude within the Search.
I have always been a big fan of the expiration headings of distant futures. The first visit on the home page of my site results in 40 HTTP requests, but a subsequent visit comes to 1, with a response as agile as you would expect. This is great, very happy.
However, I just learned about dns-prefetch and preconnect. I can see that they would help (marginally) with a load for the first time, but I suppose that the additional overhead is a bad thing in subsequent uploads, since I would be starting some DNS searches / SSL link protocols for domains that I don't & # 39; I don't even get used to it.
What is the best practice, or how have you approached this?