Connect with us

SEO

Google Search Console Updates Structured Data Report

Published

on

Google Search Console Updates Structured Data Report


Google is updating the structured data report in Search Console to provide more context about errors, helping you fix invalid markup with less guesswork.

The update is rolling out to Search Console reports starting today and impacts all rich result status reports, the URL inspection tool, and the rich results test.

How Is The Structured Data Report Changing?

As an example of what’s changing — let’s say you’re using review snippet markup but you omit the name of the author.

That would result in an error. Prior to today, the structured data report would display a messaging stating: Missing field “name”.

If there’s multiple fields in the markup for a person’s name, the previous way of reporting errors wasn’t as helpful as it could have been.

Going forward, the same error will now read: Missing field “name” (in “author”).

The added detail in parenthesis makes it possible to immediately pinpoint what’s missing from the markup so you can go in and fix it.

Advertisement

Here’s a visual comparison of the old versus new method of reporting errors in Search Console’s structured data report:

Screenshot from developers.google.com/search/blog, March 2022.

How Will This Impact My Use Of Google Search Console?

As mentioned, this update will affect:

  • All Search Console rich result status reports
  • URL Inspection tool
  • Rich Results test

As a result of these changes, all open issues that refer to nested properties will be automatically closed. New issues will be opened with more context about what’s missing.

To avoid inbox overload, Search Console will not be sending email notifications about the new issues.

Google clarifies there are no changes to how errors are detected. This only changes how errors are reported.


Source: Google

Featured Image: GaudiLab/Shutterstock

fbq('init', '1321385257908563');

fbq('track', 'PageView');

fbq('trackSingle', '1321385257908563', 'ViewContent', { content_name: 'google-search-console-updates-structured-data-report', content_category: 'news digital-marketing-tools ' });





Source link

SEO

Google On How To Simplify Hreflang Implementation

Published

on

Google On How To Simplify Hreflang Implementation

Google’s Search Advocate John Mueller says hreflang implementation doesn’t have to be as complicated as people think.

Hreflang is one of the more confusing aspects of technical SEO and among the most important for international businesses and publishers.

In reply to a thread on Reddit, Mueller outlines a simplified approach for publishers to follow.

Hreflang: The Problem

Hreflang is a link attribute that informs Google of the language used on a page. With that information, Google can show the page version corresponding to the language a person is searching in.

Without the hreflang attribute, Google may serve pages in a language the searcher doesn’t speak or pages specific to a country the searcher doesn’t reside.

In the r/TechSEO forum on Reddit, a user is seeking advice regarding the use of hreflang for websites in multiple countries.

They ask if they can get by with a partial implementation of hreflang. For example, they are setting up hreflang for versions of the website in the same language, such as Germany and Switzerland.

Advertisement

The alternative is linking all versions of all pages with hreflang, which is a considerable amount of work.

Mueller says that’s the best solution, but not exactly practical:

“In an idea [sic] world, you’d link all versions of all pages with hreflang. It would be the clean approach, however, sometimes it’s just a ton of work, and maintaining it if the sites are run individually is … good luck with that.”

Although linking every page with hreflang is the ideal solution, Mueller says it doesn’t have to be so complicated.

Hreflang: The Solution

First, Mueller suggests figuring out what needs fixing.

Identify whether a problem exists with searchers landing on the wrong site version.

If that isn’t happening, you may not need to implement hreflang.

Mueller states:

“In practice, you can simplify the problem. Where do you actually see issues with regards to people coming to the wrong country / language site? That’s where you should minimally implement hreflang (and, of course, a JS country/language recognizer / popupper to catch any direct visits). Probably a lot of that will be limited to same-language / different-country situations, so Switzerland / Germany in German may be the right place to start. Nothing breaks if you set up hreflang for 2 versions and have 4 unrelated versions.

If you already have these sites running, I’d check your analytics setup for traffic from Search, and compare the country where they come from vs the country that they end up on (pick one country, filter for the traffic from search, and compare the domains they end up on). If you don’t find a big mismatch there, most likely you don’t need to do a lot (or anything) for hreflang. There is no bonus for hreflang, it’s only about showing the most-fitting page in search for users in a specific country / language.”

Advertisement

Next, look at which pages searchers are landing on. One of the most likely mistakes Google can make is serving the wrong version of a website’s homepage.

Since brand names aren’t localized, Google doesn’t always know which version of a homepage to serve if that’s all a user types into the search box.

If you find searchers are landing on the wrong homepage, but there are no issues with other pages, you can get by with a partial implementation of hreflang.

Mueller states:

“When checking, focus on the most likely mistakes first: same-language / different-country sites is one, but there’s also homepage traffic. Often times a brand name is not localized, so when people search for it, it’s unclear to search engines what the expectation is. If you find a lot of mismatches on the homepage but not elsewhere in the site, you can also just do hreflang across the homepages (that’s often easier than all pages in a site). Or you could do a combination, of course, all homepages + all German-language pages. Hreflang is on a per-page basis, so the beauty (and curse) is that you can pick & choose.”

Lastly, Mueller reiterates that it’s possible to save a lot of time with hreflang by checking to see if there’s a genuine problem.

Google may serve the correct versions of pages all on its own, in which case you don’t gain anything by adding hreflang.

“In any case, before you rush off and work on this for a year, double-check that it’s an actual problem first, and if so, check where the problem is. Maybe there are super-simple solutions (maybe you just need a country/language popup and don’t even need the rest?), and you can spend your time more wisely elsewhere.”

Think of hreflang as a tool to utilize when needed. You can prioritize other tasks if there’s no need for it.


Source: Reddit

Advertisement

Featured Image: patpitchaya/Shutterstock

fbq('track', 'PageView');

fbq('trackSingle', '1321385257908563', 'ViewContent', { content_name: 'google-on-how-to-simplify-hreflang-implementation', content_category: 'news seo' }); } });



Source link

Continue Reading

DON'T MISS ANY IMPORTANT NEWS!
Subscribe To our Newsletter
We promise not to spam you. Unsubscribe at any time.
Invalid email address

Trending

en_USEnglish