Google respects JS canonicals -
Posted: Thu Feb 13, 2025 10:49 am
The obvious source for this is the resources or offerings provided by Google itself. Of the various resources that have come up, I have found these two to be somewhat more useful for providing insight into first principles:
This excellent talk, How Google Works - Paul Hahr , is a must-listen.
At their recent IO conference, John Mueller and Tom Greenway gave a useful presentation on how Google renders JavaScript .
But there’s often a difference between what canada number data says and what the SEO community sees in practice. All the SEO experiments that people in our industry tirelessly perform can also help shed some insight. There are many lists, but here are two good examples:
For example, Eoghan Henn does some good digging here , showing that Google respects JS canonicals.
How does Google index different JS frameworks? - Another great example of Bartosz Góralewicz's widely read experiment last year to investigate how Google treated different frameworks.
7. Can Google aggregate your website over others?
If we've reached this point, we're very happy that our website is running smoothly. But not all problems can be solved on your website alone. Sometimes you have to look at the broader landscape and the surrounding SERPs.
In general, what I'm looking for here is:
Similar/duplicate content to pages with issues.
This can be intentional duplicate content (e.g. syndicating content) or unintentional (scraping of competitors or mistakenly indexed sites).
Either way, they are almost always found by doing a very precise search in Google. That is, taking a relatively specific piece of content from your page and searching for it in quotes.
This excellent talk, How Google Works - Paul Hahr , is a must-listen.
At their recent IO conference, John Mueller and Tom Greenway gave a useful presentation on how Google renders JavaScript .
But there’s often a difference between what canada number data says and what the SEO community sees in practice. All the SEO experiments that people in our industry tirelessly perform can also help shed some insight. There are many lists, but here are two good examples:
For example, Eoghan Henn does some good digging here , showing that Google respects JS canonicals.
How does Google index different JS frameworks? - Another great example of Bartosz Góralewicz's widely read experiment last year to investigate how Google treated different frameworks.
7. Can Google aggregate your website over others?
If we've reached this point, we're very happy that our website is running smoothly. But not all problems can be solved on your website alone. Sometimes you have to look at the broader landscape and the surrounding SERPs.
In general, what I'm looking for here is:
Similar/duplicate content to pages with issues.
This can be intentional duplicate content (e.g. syndicating content) or unintentional (scraping of competitors or mistakenly indexed sites).
Either way, they are almost always found by doing a very precise search in Google. That is, taking a relatively specific piece of content from your page and searching for it in quotes.