Official statement
For JavaScript pagination, there is no difference for Google between using absolute URLs (\/topic?page=2) or relative ones (?page=2). Crawling issues related to parameters, such as infinite crawl spaces, apply in both scenarios.
Other statements from this video 10 ▾
- □ Should you standardize meta descriptions for users and Googlebot?
- □ Why does the lack of content after rendering lead to incorrect canonicalization?
- □ Why is it essential to inspect rendered HTML and unloaded resources?
- □ Should you prefer dynamic rendering to avoid indexing troubles?
- □ Could blocked resources by robots.txt be a nightmare for your SEO?
- □ Why is it crucial to test mobile compatibility before launching your website?
- □ Why are generic button texts a concern for SEO?
- □ What are the key differences between live testing and Google indexing?
- □ Why is the 2.5-second LCP threshold still critical for SEO?
- □ Does hidden code in React really affect SEO?
Official statement from
(5 years ago)
⚠ A more recent statement exists on this topic
Does it really matter whether you use absolute or relative URLs for SEO?
View statement →
TL;DR
Google states that there is no difference between using absolute or relative URLs in JavaScript pagination. However, crawling issues related to parameters persist in both cases.
❓ Frequently Asked Questions
Absolues ou relatives, pourquoi choisir l'une ou l'autre ?
Aucune différence pour Google, faites votre choix selon ce qui simplifie votre architecture.
Quels sont les risques des espaços de crawl infinis ?
Ils peuvent surconsommer votre budget de crawl et empêcher l'indexation de pages importantes.
La déclaration s'applique-t-elle aux sites non-JavaScript ?
Oui, la différenciation d'URL ne s'applique pas uniquement aux sites JavaScript.
🎥 From the same video 10
Other SEO insights extracted from this same Google Search Central video · published on 18/05/2021
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.