Connect with us

SEO

How Google’s Hreflang x-default Enhances Website Navigation

Published

on

How Google's Hreflang x-default Enhances Website Navigation

Google is reminding website owners and SEO professionals about the benefits of using the hreflang x-default value, an underused feature that can improve user experience.

The hreflang x-default value helps direct users to the appropriate language and region-neutral URL when the site doesn’t support their preferred language and region.

This feature can enhance URL discovery, increase conversions, and better serve your audience.

The Role of Hreflang x-default In User Experience

Hreflang x-default is used in conjunction with other hreflang values that specify the URL version for content targeted to a specific language and region.

For instance, if a page has hreflang annotations for English and Spanish versions, along with an x-default value pointing to the English version, French-speaking users would be directed to the English page due to the x-default annotation.

This can result in a more seamless experience for website users, regardless of language or location.

Advantages Of Using Hreflang x-default

There are two main benefits to implementing the hreflang x-default value on your site:

  • URL Discovery: The URLs specified in hreflang annotations, including x-default, may be used for URL discovery. This can be helpful for large sites with complex structures, ensuring every localized URL is well-linked and accessible.
  • Conversions: The goal for site owners is to convert users. Using the hreflang x-default value, you can direct users to a page where they are more likely to convert if your content is unavailable in their preferred language.

Implementing Hreflang x-default

To implement the hreflang x-default value, you need to add a series of link elements in the head section of your HTML page, specifying the different language and region URLs along with the x-default value.

The process involves the following steps:

  • Identify the different language and region versions of your page.
  • Create a unique link element for each version, including the x-default value.
  • Add the link elements to the head section of your HTML page.

Here’s an example of how to add hreflang annotations, including the x-default value, to a webpage:

<head>

<link rel=”alternate” href=”https://example.com/en” hreflang=”en” />
<link rel=”alternate” href=”https://example.com/es” hreflang=”es” />
<link rel=”alternate” href=”https://example.com/language-selector” hreflang=”x-default” />

</head>

In this instance, three link elements are present: an English version, a Spanish version, and an x-default value directing to a language selector page.

Users with unsupported language preferences are guided to the language-selector page through the x-default value.

For comprehensive guidance on incorporating hreflang values, including x-default, consult Google’s official documentation.

Best Practices & Common Mistakes

Here are some best practices to consider when using the hreflang x-default value:

  • Consistency across pages: Ensure that hreflang annotations are consistently implemented across all page versions. Each language and region version of the page should include the same set of hreflang annotations, including the x-default value.
  • Use of absolute URLs: Always use absolute rather than relative URLs when specifying href attributes in hreflang annotations. This helps avoid potential issues with URL resolution.
  • Canonical tags: Make sure to include a canonical tag for each language and region version of the page, pointing to the self-referencing URL. This helps search engines understand the preferred version of the page.
  • Language and region codes: Use ISO 639-1 language codes and ISO 3166-1 Alpha 2 country codes when specifying language and region values in the hreflang attribute. This ensures consistency and adherence to the standard.
  • Sitemap implementation (optional): If you have a large site with many language and region versions, consider implementing hreflang annotations in your XML sitemap instead of in the head section of your HTML pages. This can help with site management and organization.

Avoid the following common mistakes:

  • Missing or incorrect x-default value: Ensure that the x-default value is correctly implemented and points to the appropriate language-neutral or language selector page.
  • Incomplete hreflang annotations: Ensure that all relevant language and region versions of a page are included in the hreflang annotations. This helps search engines index and serve the correct content to users.
  • Inconsistent hreflang annotations: Avoid using different hreflang annotations on different versions of the same page. This can confuse search engines and may result in indexing and ranking issues.
  • Incorrect language or region codes: Double-check your language and region codes to ensure they are correct and adhere to the ISO standards mentioned previously.
  • Duplicate content issues: Be mindful of potential duplicate content issues when implementing hreflang annotations. Ensure each language and region version of a page has unique content to avoid potential SEO issues related to duplicate content.

In Summary

The hreflang x-default value is a valuable yet underutilized tool that can enhance user experience and boost conversions.

By directing users to an appropriate language-neutral or region-neutral URL when their preferred language is unsupported, this feature can provide a more seamless browsing experience.

Implementing the hreflang x-default value involves consistent annotations, correct language and region codes, and adherence to best practices to avoid common mistakes.

Leveraging this feature helps ensure that your content is accessible and well-linked for users worldwide.


Featured image generated by author using Midjourney. 



Source link

Keep an eye on what we are doing
Be the first to get latest updates and exclusive content straight to your email inbox.
We promise not to spam you. You can unsubscribe at any time.
Invalid email address

SEO

8% Of Automattic Employees Choose To Resign

Published

on

By

8% Of Automattic Employees Choose To Resign

WordPress co-founder and Automattic CEO announced today that he offered Automattic employees the chance to resign with a severance pay and a total of 8.4 percent. Mullenweg offered $30,000 or six months of salary, whichever one is higher, with a total of 159 people taking his offer.

Reactions Of Automattic Employees

Given the recent controversies created by Mullenweg, one might be tempted to view the walkout as a vote of no-confidence in Mullenweg. But that would be a mistake because some of the employees announcing their resignations either praised Mullenweg or simply announced their resignation while many others tweeted how happy they are to stay at Automattic.

One former employee tweeted that he was sad about recent developments but also praised Mullenweg and Automattic as an employer.

He shared:

“Today was my last day at Automattic. I spent the last 2 years building large scale ML and generative AI infra and products, and a lot of time on robotics at night and on weekends.

I’m going to spend the next month taking a break, getting married, and visiting family in Australia.

I have some really fun ideas of things to build that I’ve been storing up for a while. Now I get to build them. Get in touch if you’d like to build AI products together.”

Another former employee, Naoko Takano, is a 14 year employee, an organizer of WordCamp conferences in Asia, a full-time WordPress contributor and Open Source Project Manager at Automattic announced on X (formerly Twitter) that today was her last day at Automattic with no additional comment.

She tweeted:

“Today was my last day at Automattic.

I’m actively exploring new career opportunities. If you know of any positions that align with my skills and experience!”

Naoko’s role at at WordPress was working with the global WordPress community to improve contributor experiences through the Five for the Future and Mentorship programs. Five for the Future is an important WordPress program that encourages organizations to donate 5% of their resources back into WordPress. Five for the Future is one of the issues Mullenweg had against WP Engine, asserting that they didn’t donate enough back into the community.

Mullenweg himself was bittersweet to see those employees go, writing in a blog post:

“It was an emotional roller coaster of a week. The day you hire someone you aren’t expecting them to resign or be fired, you’re hoping for a long and mutually beneficial relationship. Every resignation stings a bit.

However now, I feel much lighter. I’m grateful and thankful for all the people who took the offer, and even more excited to work with those who turned down $126M to stay. As the kids say, LFG!”

Read the entire announcement on Mullenweg’s blog:

Automattic Alignment

Featured Image by Shutterstock/sdx15

Source link

Keep an eye on what we are doing
Be the first to get latest updates and exclusive content straight to your email inbox.
We promise not to spam you. You can unsubscribe at any time.
Invalid email address
Continue Reading

SEO

YouTube Extends Shorts To 3 Minutes, Adds New Features

Published

on

By

YouTube Extends Shorts To 3 Minutes, Adds New Features

YouTube expands Shorts to 3 minutes, adds templates, AI tools, and the option to show fewer Shorts on the homepage.

  • YouTube Shorts will allow 3-minute videos.
  • New features include templates, enhanced remixing, and AI-generated video backgrounds.
  • YouTube is adding a Shorts trends page and comment previews.

Source link

Keep an eye on what we are doing
Be the first to get latest updates and exclusive content straight to your email inbox.
We promise not to spam you. You can unsubscribe at any time.
Invalid email address
Continue Reading

SEO

How To Stop Filter Results From Eating Crawl Budget

Published

on

By

How To Find The Right Long-tail Keywords For Articles

Today’s Ask An SEO question comes from Michal in Bratislava, who asks:

“I have a client who has a website with filters based on a map locations. When the visitor makes a move on the map, a new URL with filters is created. They are not in the sitemap. However, there are over 700,000 URLs in the Search Console (not indexed) and eating crawl budget.

What would be the best way to get rid of these URLs? My idea is keep the base location ‘index, follow’ and newly created URLs of surrounded area with filters switch to ‘noindex, no follow’. Also mark surrounded areas with canonicals to the base location + disavow the unwanted links.”

Great question, Michal, and good news! The answer is an easy one to implement.

First, let’s look at what you’re trying and apply it to other situations like ecommerce and publishers. This way, more people can benefit. Then, go into your strategies above and end with the solution.

What Crawl Budget Is And How Parameters Are Created That Waste It

If you’re not sure what Michal is referring to with crawl budget, this is a term some SEO pros use to explain that Google and other search engines will only crawl so many pages on your website before it stops.

If your crawl budget is used on low-value, thin, or non-indexable pages, your good pages and new pages may not be found in a crawl.

If they’re not found, they may not get indexed or refreshed. If they’re not indexed, they cannot bring you SEO traffic.

This is why optimizing a crawl budget for efficiency is important.

Michal shared an example of how “thin” URLs from an SEO point of view are created as customers use filters.

The experience for the user is value-adding, but from an SEO standpoint, a location-based page would be better. This applies to ecommerce and publishers, too.

Ecommerce stores will have searches for colors like red or green and products like t-shirts and potato chips.

These create URLs with parameters just like a filter search for locations. They could also be created by using filters for size, gender, color, price, variation, compatibility, etc. in the shopping process.

The filtered results help the end user but compete directly with the collection page, and the collection would be the “non-thin” version.

Publishers have the same. Someone might be on SEJ looking for SEO or PPC in the search box and get a filtered result. The filtered result will have articles, but the category of the publication is likely the best result for a search engine.

These filtered results can be indexed because they get shared on social media or someone adds them as a comment on a blog or forum, creating a crawlable backlink. It might also be an employee in customer service responded to a question on the company blog or any other number of ways.

The goal now is to make sure search engines don’t spend time crawling the “thin” versions so you can get the most from your crawl budget.

The Difference Between Indexing And Crawling

There’s one more thing to learn before we go into the proposed ideas and solutions – the difference between indexing and crawling.

  • Crawling is the discovery of new pages within a website.
  • Indexing is adding the pages that are worthy of showing to a person using the search engine to the database of pages.

Pages can get crawled but not indexed. Indexed pages have likely been crawled and will likely get crawled again to look for updates and server responses.

But not all indexed pages will bring in traffic or hit the first page because they may not be the best possible answer for queries being searched.

Now, let’s go into making efficient use of crawl budgets for these types of solutions.

Using Meta Robots Or X Robots

The first solution Michal pointed out was an “index,follow” directive. This tells a search engine to index the page and follow the links on it. This is a good idea, but only if the filtered result is the ideal experience.

From what I can see, this would not be the case, so I would recommend making it “noindex,follow.”

Noindex would say, “This is not an official page, but hey, keep crawling my site, you’ll find good pages in here.”

And if you have your main menu and navigational internal links done correctly, the spider will hopefully keep crawling them.

Canonicals To Solve Wasted Crawl Budget

Canonical links are used to help search engines know what the official page to index is.

If a product exists in three categories on three separate URLs, only one should be “the official” version, so the two duplicates should have a canonical pointing to the official version. The official one should have a canonical link that points to itself. This applies to the filtered locations.

If the location search would result in multiple city or neighborhood pages, the result would likely be a duplicate of the official one you have in your sitemap.

Have the filtered results point a canonical back to the main page of filtering instead of being self-referencing if the content on the page stays the same as the original category.

If the content pulls in your localized page with the same locations, point the canonical to that page instead.

In most cases, the filtered version inherits the page you searched or filtered from, so that is where the canonical should point to.

If you do both noindex and have a self-referencing canonical, which is overkill, it becomes a conflicting signal.

The same applies to when someone searches for a product by name on your website. The search result may compete with the actual product or service page.

With this solution, you’re telling the spider not to index this page because it isn’t worth indexing, but it is also the official version. It doesn’t make sense to do this.

Instead, use a canonical link, as I mentioned above, or noindex the result and point the canonical to the official version.

Disavow To Increase Crawl Efficiency

Disavowing doesn’t have anything to do with crawl efficiency unless the search engine spiders are finding your “thin” pages through spammy backlinks.

The disavow tool from Google is a way to say, “Hey, these backlinks are spammy, and we don’t want them to hurt us. Please don’t count them towards our site’s authority.”

In most cases, it doesn’t matter, as Google is good at detecting spammy links and ignoring them.

You do not want to add your own site and your own URLs to the disavow tool. You’re telling Google your own site is spammy and not worth anything.

Plus, submitting backlinks to disavow won’t prevent a spider from seeing what you want and do not want to be crawled, as it is only for saying a link from another site is spammy.

Disavowing won’t help with crawl efficiency or saving crawl budget.

How To Make Crawl Budgets More Efficient

The answer is robots.txt. This is how you tell specific search engines and spiders what to crawl.

You can include the folders you want them to crawl by marketing them as “allow,” and you can say “disallow” on filtered results by disallowing the “?” or “&” symbol or whichever you use.

If some of those parameters should be crawled, add the main word like “?filter=location” or a specific parameter.

Robots.txt is how you define crawl paths and work on crawl efficiency. Once you’ve optimized that, look at your internal links. A link from one page on your site to another.

These help spiders find your most important pages while learning what each is about.

Internal links include:

  • Breadcrumbs.
  • Menu navigation.
  • Links within content to other pages.
  • Sub-category menus.
  • Footer links.

You can also use a sitemap if you have a large site, and the spiders are not finding the pages you want with priority.

I hope this helps answer your question. It is one I get a lot – you’re not the only one stuck in that situation.

More resources: 


Featured Image: Paulo Bobita/Search Engine Journal

Source link

Keep an eye on what we are doing
Be the first to get latest updates and exclusive content straight to your email inbox.
We promise not to spam you. You can unsubscribe at any time.
Invalid email address
Continue Reading

Trending