Official statement
Other statements from this video 28 ▾
- 1:05 Do Google’s style guides really influence your site’s SEO ranking?
- 1:05 Do Google's developer style guides really influence your SEO?
- 2:19 Cache vs. Similar on Google: How does this distinction impact your SEO strategy?
- 4:55 Why does it take months for content improvements to affect ranking?
- 4:58 How long does it really take for Google to reassess the quality of content?
- 6:24 Does brand popularity really affect Google ranking?
- 6:25 Does brand popularity really influence Google rankings?
- 9:44 Should you delete or noindex duplicate content flagged by Panda?
- 10:46 Does precise anchor text really boost your SEO more than a generic anchor?
- 11:20 Is loading speed really a ranking factor or just an SEO myth?
- 13:20 Is loading speed truly a decisive SEO ranking factor?
- 15:02 Is it true that Google indexes tabbed content in a mobile-first world?
- 15:28 Is hidden content in tabs truly indexed in mobile-first?
- 17:35 How does Google really index identical products across multiple URLs?
- 19:33 Do you really need to contact webmasters before disavowing toxic backlinks?
- 20:32 Should you really use the disavow tool to handle toxic backlinks?
- 24:17 How does Google really rank a brand's social media pages in its search results?
- 26:56 Does mobile indexing really work with separate m-dot and dynamic sites?
- 27:41 Does mobile-first indexing really treat all types of mobile sites the same way?
- 29:02 How does Google actually adjust your rankings in real time?
- 29:09 Do Google's algorithms really work in real-time?
- 30:18 Why does the Search Console only show a fraction of your actual backlinks?
- 38:51 Can bad backlinks really harm your website?
- 39:53 Are PBNs truly detectable by Google or just a risky gamble?
- 48:31 Should you really ignore page numbers in your URLs for pagination?
- 50:34 Should you really prioritize NO-NO over NO-NB for Norwegian hreflang?
- 52:37 Should you still worry about URL escaping for Google’s JavaScript crawl?
- 57:17 Is it true that Google indexes all website JavaScript?
Google offers two distinct features: the 'Cached' option displays a page's archived version by its servers, while 'Similar' reveals other pages deemed algorithmically close. The noarchive meta tag allows for disabling caching. These tools give SEOs direct control over the visibility of archived versions and an insight into the thematic clustering perceived by Google.
What you need to understand
What sets 'Cached' apart from 'Similar'?
The 'Cached' option provides access to a copy of the page stored by Google's servers during the last crawl. This frozen version serves as a reference when the site is down or when a page has been modified. It's a technical snapshot, not a semantic analysis.
The 'Similar' option relies on Google's clustering algorithms. It identifies other web pages sharing thematic, structural, or semantic characteristics. It reveals how Google categorizes content within its index.
How does the noarchive meta tag work?
The noarchive meta tag is inserted into the of the HTML page: <meta name="robots" content="noarchive">. It instructs Google not to provide the 'Cached' link in search results. The page remains indexed, crawled normally, but its history is no longer publicly accessible.
This directive applies to all bots that respect the robots meta tag standard. Google consistently adheres to it, unlike some optional directives. It's a binary control: either the cache is visible, or it isn't.
When should you use this feature?
Websites with dynamically changing content (prices, availability, news) should block the cache. Displaying outdated information can create confusion and degrade user experience. E-commerce platforms often hide their product listings to prevent outdated pricing from circulating.
Sensitive pages containing personal or confidential data also justify this directive. Even if the content is removed or modified, the cached version remains accessible for several days. This is a frequently overlooked information leakage vector.
- Direct control over the display of archived versions via noarchive
- Algorithmic clustering revealed by the 'Similar' option without the possibility of disabling it
- Unchanged indexing: blocking the cache does not affect SEO
- Immediate compliance with the directive after the next crawl
- Free thematic diagnostics through analysis of suggested similar pages
SEO Expert opinion
Is this feature still relevant?
The removal of the 'Cached' link from Google’s public interfaces in 2024 makes this statement partially obsolete. The cache technically still exists, but public access has disappeared. The cache: operators still work for those in the know, but for how long?
The noarchive directive remains active and respected, even as its practical utility diminishes. For sites already using it, there’s no reason to remove it. For new projects, the decision becomes less clear. [To be verified]: Will Google officially communicate about the obsolescence of this tag?
Does the 'Similar' option truly reveal Google's clustering?
Yes, but with significant limitations. The suggestions reflect a simplified calculation, not the full clustering used for ranking. It's an indicator of thematic proximity, not an exhaustive mapping of competition.
Results can vary based on geographic context and the language of the interface. The same page may display different suggestions based on these parameters. Therefore, using this tool for competitive analysis demands stringent methodological precautions.
Can the 'Similar' option be disabled?
No. Unlike the cache, there is no directive in robots.txt or meta tag to block this feature. Google unilaterally decides which pages are similar, without an opt-out option.
This aligns with Google's logic: the cache is a replica of your content (thus controllable), while 'Similar' is an external analysis (therefore beyond your authority). This frustrating asymmetry reflects the engine's philosophy: you control your data, not its interpretation.
cache:yoururl.com in the search bar. If Google ignores the directive, a crawl bug or HTML syntax error is likely.Practical impact and recommendations
Should you always implement noarchive?
No. The majority of sites have no reason to block the cache. It can even be counterproductive: in the event of a server outage, users lose access to your content through the archived version. It's a safety net that you destroy without benefit.
Reserve this directive for time-sensitive content (news, pricing, events) or requiring enhanced confidentiality. For everything else, let Google do its job. Cache visibility does not influence ranking or traffic.
How to audit suggested similar pages by Google?
Manually inspect your strategic pages by searching for their exact URL on Google, then clicking on 'Similar'. Note the patterns: direct competitors, affiliate sites, content aggregators. If low-quality pages appear, it's a signal that your thematic positioning lacks clarity.
Compile this data into a monthly tracking file. A sudden change in suggestions may indicate an algorithmic shift or editorial drift on your part. It's a free KPI, underutilized, to measure the semantic consistency perceived by Google.
What mistakes to avoid with noarchive?
Do not confuse noarchive with noindex. The former hides the cache, while the latter removes the page from the index. Mixing the two inadvertently disindexes entire content. Always check the syntax: content="noarchive" and not content="noarchive, noindex" if you only want to block the cache.
Avoid applying noarchive via robots.txt. This file controls crawling, not cache display. The directive must be in the HTML or HTTP headers (X-Robots-Tag: noarchive). This is a common mistake on multilingual sites where tags are duplicated without adaptation.
- Check the HTML syntax of the noarchive meta tag in the <head>
- Test with the
cache:operator after sufficient crawl delay - Document affected pages in an SEO specifications file
- Monitor 'Similar' suggestions on a sample of key pages monthly
- Never apply noarchive by default across the site without justification
- Ensure that HTTP headers do not conflict with meta tags
❓ Frequently Asked Questions
La balise noarchive impacte-t-elle le référencement naturel ?
Peut-on appliquer noarchive uniquement à certaines sections d'une page ?
Les pages similaires suggérées changent-elles fréquemment ?
Comment forcer Google à mettre à jour le cache d'une page ?
L'option Similaire peut-elle révéler des contenus dupliqués ?
🎥 From the same video 28
Other SEO insights extracted from this same Google Search Central video · duration 1h05 · published on 20/10/2017
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.