How to best evaluate issues with your Accelerated Mobile Pages

As you #AMPlify your site with Accelerated Mobile Pages, it’s important to keep an eye periodically on the validation status of your pages, as only valid AMP pages are eligible to show on Google Search.

When implementing AMP, sometimes pages will contain errors causing them to not be indexed by Google Search. Pages may also contain warnings that are elements that are not best practice or are going to become errors in the future.

Google Search Console is a free service that lets you check which of your AMP pages Google has identified as having errors. Once you know which URLs are running into issues, there are a few handy tools that can make checking the validation error details easier.

1. Browser Developer Tools

To use Developer Tools for validation:

  1. Open your AMP page in your browser
  2. Append “#development=1” to the URL, for example, http://localhost:8000/released.amp.html#development=1.
  3. Open the Chrome DevTools console and check for validation errors.

Developer Console errors will look similar to this:

2. AMP Browser Extensions

With the AMP Browser Extensions (available for Chrome and Opera), you can quickly identify and debug invalid AMP pages. As you browse your site, the extension will evaluate each AMP page visited and give an indication of the validity of the page.

Red AMP icon indicating invalid AMP document.

When there are errors within an AMP page, the extension’s icon shows in a red color and displays the number of errors encountered.

Green AMP icon indicating valid AMP document.

When there are no errors within an AMP page, the icon shows in a green color and displays the number of warnings, if any exist.

Blue AMP icon indicating AMP HTML variant if clicked.

When the page isn’t AMP but the page indicates that an AMP version is available, the icon shows in a blue color with a link icon, and clicking on the extension will redirect the browser to the AMP version.

Using the extensions means you can see what errors or warnings the page has by clicking on the extension icon. Every issue will list the source line, source column, and a message indicating what is wrong. When a more detailed description of the issue exists, a “Learn more” link will take you to the relevant page on ampproject.org.

3. AMP Web Validator

The AMP Web Validator, available at validator.ampproject.org, provides a simple web UI to test the validity of your AMP pages.

To use the tool, you enter an AMP URL, or copy/paste your source code, and the web validator displays error messages between the lines. You can make edits directly in the web validator which will trigger revalidation, letting you know if your proposed tweaks will fix the problem.

What’s your favourite way to check the status of your AMP Pages? Share your feedback in the comments below or on our Google Webmasters Google+ page. Or as usual, if you have any questions or need help, feel free to post in our Webmasters Help Forum.

Posted by Tomo Taylor, AMP Community Manager

How to best evaluate issues with your Accelerated Mobile Pages

As you #AMPlify your site with Accelerated Mobile Pages, it’s important to keep an eye periodically on the validation status of your pages, as only valid AMP pages are eligible to show on Google Search.

When implementing AMP, sometimes pages will contain errors causing them to not be indexed by Google Search. Pages may also contain warnings that are elements that are not best practice or are going to become errors in the future.

Google Search Console is a free service that lets you check which of your AMP pages Google has identified as having errors. Once you know which URLs are running into issues, there are a few handy tools that can make checking the validation error details easier.

1. Browser Developer Tools

To use Developer Tools for validation:

  1. Open your AMP page in your browser
  2. Append “#development=1” to the URL, for example, http://localhost:8000/released.amp.html#development=1.
  3. Open the Chrome DevTools console and check for validation errors.

Developer Console errors will look similar to this:

2. AMP Browser Extensions

With the AMP Browser Extensions (available for Chrome and Opera), you can quickly identify and debug invalid AMP pages. As you browse your site, the extension will evaluate each AMP page visited and give an indication of the validity of the page.

Red AMP icon indicating invalid AMP document.

When there are errors within an AMP page, the extension’s icon shows in a red color and displays the number of errors encountered.

Green AMP icon indicating valid AMP document.

When there are no errors within an AMP page, the icon shows in a green color and displays the number of warnings, if any exist.

Blue AMP icon indicating AMP HTML variant if clicked.

When the page isn’t AMP but the page indicates that an AMP version is available, the icon shows in a blue color with a link icon, and clicking on the extension will redirect the browser to the AMP version.

Using the extensions means you can see what errors or warnings the page has by clicking on the extension icon. Every issue will list the source line, source column, and a message indicating what is wrong. When a more detailed description of the issue exists, a “Learn more” link will take you to the relevant page on ampproject.org.

3. AMP Web Validator

The AMP Web Validator, available at validator.ampproject.org, provides a simple web UI to test the validity of your AMP pages.

To use the tool, you enter an AMP URL, or copy/paste your source code, and the web validator displays error messages between the lines. You can make edits directly in the web validator which will trigger revalidation, letting you know if your proposed tweaks will fix the problem.

What’s your favourite way to check the status of your AMP Pages? Share your feedback in the comments below or on our Google Webmasters Google+ page. Or as usual, if you have any questions or need help, feel free to post in our Webmasters Help Forum.

Posted by Tomo Taylor, AMP Community Manager

Google Is Grouping Keyword Volumes – What Does This Mean for SEO?

Posted by sam.nemzer

As of June this year, Google is now grouping keyword volumes for similar keywords in Keyword Planner. I wanted to investigate whether or not this is having an impact on the pages that rank for these similar, grouped keywords. My hypothesis is that, given that Google is associating keywords closely enough to group their volumes, we should expect that the search results would be very similar too.

What has Google changed and why does it matter?

The grouping of keyword volumes is a problem for anyone working in search because Keyword Planner is the primary source for volume data that we use in keyword research, whether that be from Keyword Planner directly, or through a third party tool that takes Keyword Planner data as its input—such as SEMRush, BrightEdge or SearchMetrics.

By “grouping keyword volumes,” we mean that different keywords that are slightly different (but generally convey the same meaning) are given the same volume, which represents the combined volume of every variation. For example, if (hypothetically) [SEO] is searched 21,000 times per month in the UK, and [Search Engine Optimisation] is searched 12,100 times per month, once these keywords are combined, each will be reported as receiving the total of the two—33,100 searches per month.

On top of this, in the last few weeks Google have also been reducing access to keyword planner data for some accounts. Earlier this month, it was announced that Keyword Planner data will be given only in very broad buckets for advertisers with “lower monthly spend” (although some ways around this have been found). This is a separate change from the volume grouping, which is the main focus of this article.

The fact that Google is grouping keyword volumes in this way implies that they see these keywords as equivalent, at least to some extent. The questions that this raised for me were:

  • Does this mean that we should see keywords with grouped volumes as identical?
  • From an SEO point of view, should we focus our targeting efforts on any one of the grouped keywords, given that Google is seeing them as the same?

There is further reason to think this way given the simple fact that Google is always getting smarter. As well as Parsey McParseface, the English language parser that Google released to the public, much of the research output that we see in patents and journal articles from Google relates to natural language processing, so it is clear that this is an area that Google see as a priority for their research.

One way to test whether or not Google does indeed consider grouped keywords to be identical is to look at search results. The theory is that if keywords are viewed identically, we should see exactly the same pages ranking for the keywords.

What’s going on in the SERPs?

I did a similar analysis a few months ago, which was focused more on general distinctions between keywords within a topic. This analysis is much more focused on the types of variations of keywords that we are seeing being grouped. These types of variations were categorised by, among others, Jennifer Slegg at The SEM Post.

The five types of variations that I’ve looked into for this analysis are the following:

  1. Initialisms/Abbreviations. For example, comparing SERPs for [BBC] and [British Broadcasting Corporation]
  2. Plurals. For example, [waffle maker] and [waffle makers].
  3. Verb stems with and without suffixes. For example, [calculate], [calculated] and [calculating].
  4. Keywords with and without punctuation. For example, [midnight’s children] and [midnights children]
  5. Keywords with and without typos. For example, [heart rate monitor] and [heart rat monitor].

For each of these five categories, I put together a list of 50-100 keywords, along with a variation for each. Within these keyword pairs I investigated whether or not Keyword Planner reported the same volume, and also used the rank tracking tool STAT to see what pages are ranking for each keyword.

From that analysis, I was able to measure the prevalence of grouping keyword volumes within each category (i.e. the percentage of keyword pairs that have grouped volumes), and the similarity of the SERPs (the number of top ten results that were shared between the two keywords) for grouped and ungrouped keyword pairs.

Results

The results for those metrics are the following:

I also looked at how common it is that SERPs are exactly identical, that is that the top ten results are the same pages, in the same order. This showed an interesting pattern. There are only two categories with significant numbers of identical SERPs—Punctuation and Typos. In the case of keywords with and without punctuation, you are more likely to see identical SERPs (implying that Google sees the pair of keywords as identical) if keyword volumes are grouped than if they are not. This is not a hard-and-fast rule though – there are still some ungrouped keywords which have identical SERPs.

In the case of Typos, there are no grouped keyword pairs at all that have identical SERPs. Given also the low prevalence of grouped keywords in this category, it appears that the identical SERPs are coming from “showing results for” SERPs, where Google replaces results for the mistyped keywords with the correct one.

What conclusions can we draw?

  1. The prevalence of keyword grouping is highest for plurals, and very low for typos

    This may be a result of the sample of keywords used in this study, but overall, around 50% of keywords in the sample are grouped. This indicates that, although this volume grouping is a growing phenomenon in Keyword Planner data, it is not yet consistent across all SERPs.

  2. There is not a lot of difference between keywords that are grouped by Keyword Planner, and those that aren’t.

    This is a surprising result. The motivation for conducting this study was to confirm the suspicion that Google associating keyword volumes means that it also associates the search intent. This is comprehensively disproven by this data. There is no significant difference between grouped and ungrouped keyword pairs when it comes to SERP similarity.

    The one group where there is a larger difference is the verb stems category. This is likely because there are many verbs where the present and past tense mean very different things, indicating different search intent. For example, the keywords [march] and [marched] have completely different intents due to the multiple meanings of the word ‘march.’ This means that there’s no chance that these SERPs will be similar. On the other hand, some verbs have little intent difference between past and present forms (for example [admire] and [admired]). These types of keyword pairs generally have grouped volume, and also have more similar SERPs.

  3. Overall, there is not a very high rate of similarity of SERPs for similar keywords

    When starting this analysis, I expected to see much higher rates of similarity between very similar keywords. This is not the case, and to me that is surprising for two reasons. The first is that, as mentioned above, I saw the grouping of keyword volumes to be a clear signal that the keywords were seen as identical intents. This appears not to be the case.

    The other reason is that I have a lot of faith in how smart Google is. Its developments in natural language processing and intent assessment give me the impression that it is able to associate similar keywords in the results it shows.

    It may be that things are heading in this direction, but it’s too early for it to have been fully implemented. The alternative explanation would be Google is that smart, and can interpret the subtle difference between keywords with incredibly similar content.

What should we take away from this?

What does this mean for SEOs doing keyword research? Rank tracking companies such as STAT are looking into ways of splitting keyword volumes between the constituent keywords, so there is hope for at least semi-accurate volume data. What it does mean is that we should ignore the grouped volumes when targeting keywords—just because keywords are given the same volume, it doesn’t mean you shouldn’t target them individually on your site.

On a wider scale, this tells us something about how the anthropomorphised “Google” thinks and works. There are two very separate factors at work here—what Google tells us, and what we actually see. This is something Rand picked up on in his recent Whiteboard Friday, and it applies across all of search—Google tells us one thing, but search rankings don’t necessarily behave the same way. This backs up my belief to never take anything at face value, and always do your own research.

Do these results surprise you as much as they do me? Let me know in the comments.

Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don’t have time to hunt down but want to read!

Why is Yelp Failing at the iMessage App Game? Because They are Choosing To

As a consumer I like and use Yelp. I don’t like their business practices but as a consumer it’s my goto restaurant resource these days when traveling. I also like messaging, particularly iMessage, as my way of communicating with the 15 or so people I love and work with and often travel to see. So I was baffled … Continue reading Why is Yelp Failing at the iMessage App Game? Because They are Choosing To