Official statement
Other statements from this video 22 ▾
- 3:03 Les erreurs 404 temporaires lors d'une migration tuent-elles vraiment votre référencement ?
- 4:56 Googlebot crawle depuis les USA : comment éviter le piège du cloaking géo-IP ?
- 8:42 Peut-on vraiment bloquer Googlebot état par état aux USA sans tout casser ?
- 11:31 Pourquoi Google n'indexe-t-il pas toutes vos pages malgré un crawl actif ?
- 12:17 Les liens nofollow de Reddit sont-ils vraiment inutiles pour le SEO ?
- 14:14 Faut-il systématiquement activer loading='lazy' sur toutes vos images pour booster le SEO ?
- 15:25 Faut-il vraiment réduire le nombre de versions linguistiques pour hreflang ?
- 18:27 Faut-il vraiment corriger toutes les erreurs 404 remontées dans Search Console ?
- 20:47 Les jump links sont-ils vraiment inutiles pour le crawl de Google ?
- 21:55 Faut-il désavouer les backlinks fantômes visibles uniquement dans Search Console ?
- 23:20 Pourquoi le fichier Disavow ne masque-t-il pas les mauvais liens dans Search Console ?
- 29:18 Faut-il vraiment contextualiser l'attribut alt au-delà de la description visuelle ?
- 32:47 Faut-il vraiment s'inquiéter des redirections 301 et pages 404 multiples ?
- 33:02 Google déclasse-t-il algorithmiquement certains secteurs en période de crise sanitaire ?
- 34:06 Faut-il vraiment utiliser plusieurs noms de domaine pour un site multilingue ?
- 36:28 Faut-il vraiment rendre toutes les images de recettes indexables pour performer en SEO ?
- 37:49 Faut-il encoder les caractères non-ASCII dans les URLs de sitemap XML ?
- 38:15 Hreflang garantit-il vraiment le bon ciblage géographique de votre trafic international ?
- 41:05 Pourquoi Google indexe-t-il une seule version quand vos pages pays sont quasi-identiques ?
- 45:51 Faut-il créer du contenu différent pour indexer plusieurs variantes d'un même service ?
- 49:01 Faut-il vraiment éviter les balises title et meta description multiples sur une même page ?
- 52:13 Les erreurs 500/503 de quelques heures sont-elles vraiment invisibles pour votre indexation ?
Google prefers adding temporary information to an existing page rather than creating a new URL. Already indexed pages benefit from historical context and understanding acquired by the engine, unlike a new page that has to build its authority from scratch. This approach is particularly applicable to contextual modifications like temporarily moving online services that are usually physical.
What you need to understand
Why does Google recommend not creating new pages for temporary content?
The engine already has a crawl and indexing history for your existing pages. Creating a dedicated URL for temporary information forces Google to discover, crawl, index, and evaluate this page — a process that takes time, even on high crawl budget sites.
Established pages possess accumulated trust signals: backlinks, age, historical user behavior, thematic association with the rest of the site. A new page starts with trust capital close to zero, which delays its ranking.
Does this recommendation apply only to COVID or to all temporary changes?
Mueller used COVID as a context — closures, restrictions, forced online transitions — but the principle remains valid for any temporary service adjustment. A closure for renovations, exceptional hours, a limited-time promotion: adding to the relevant page remains the most effective strategy.
Creating a separate page is only justified if the volume of temporary content is massive or if the information requires a distinct structure that cannot be properly integrated into the existing content. In 90% of cases, enriching the current page is sufficient.
How does Google differentiate temporary information from permanent information?
The engine does not have an automatic mechanism to detect that added content is likely to disappear soon. It treats the updated page as a natural evolution of the content, without automatically distinguishing the temporary from the permanent.
Your responsibility: remove or properly archive these additions once the period has passed. Google will eventually recrawl and update its index, but without an active signal from you (like changing the last updated date), the delay can stretch.
- Existing pages have a trust history that Google exploits to speed up the ranking of new added content
- A new URL starts without capital: no backlinks, no age, no established behavioral signals
- The indexing and ranking time for a fresh page can greatly exceed the lifespan of the temporary information
- Google does not automatically detect the temporary nature of an addition — it's up to the webmaster to clean up afterwards
- Enriching the existing content prevents dilution of the crawl budget on low-duration URLs
SEO Expert opinion
Is this recommendation consistent with what we observe in the field?
Yes, and tests have confirmed it for years. Pages with a strong indexing history see their updates taken into account more quickly than new URLs. The time between publication and ranking is often measured in hours for an established page, compared to several days or even weeks for a new page on a site with a limited crawl budget.
The notable exception: news sites or those with very high authority, where Google indexes and ranks new content in just a few minutes. But for the average site — SMEs, medium-sized e-commerce, institutional sites — Mueller's recommendation holds perfectly. [To be verified] remains the exact impact on the Quality Rater Guidelines, which do not explicitly detail the treatment of temporary content.
In what cases should a separate page still be created?
When the volume of temporary information exceeds 40-50% of the existing page's content. At this stage, you risk drowning the main message of your page under contextual details that will lose their relevance. User readability always takes precedence.
Another case: if the temporary information targets a distinct search intent with its own keywords. A concrete example: a gym temporarily moving online should not pollute its "group classes" page with entire paragraphs about streaming. It's better to have a dedicated "online classes" page that it can 301 redirect to the main page once it returns to physical classes.
What should be done with temporary content once the period is over?
Properly delete the added sections and force a recrawl via Search Console. Allowing obsolete content to linger — mentions of lifted restrictions, past exceptional hours — diminishes the perceived freshness of your page and can mislead users.
If you ended up creating a dedicated page anyway, there are two options: a 301 redirect to the parent page (recommended) or removal with a 410 Gone status. The 301 preserves some link juice if the temporary page had gained backlinks, which often happens on highly topical subjects.
Practical impact and recommendations
What should be done concretely when adding temporary information?
Identify the most relevant existing page already positioned for the concerned query. If your restaurant needs to communicate about an exceptional closure, it is the "Practical Information" or "Contact" page that should receive the addition, not the homepage or a URL created for the occasion.
Integrate the temporary information at the top of the page in a visually distinct block (banner, colored box) to maximize user visibility. Properly mark it with semantic tags — an <aside> or a <div class="temporary-notice"> makes cleaning up later easier and helps Google contextualize.
What mistakes should absolutely be avoided?
Do not create a temporary page without an exit plan. Too many sites leave "COVID" or "Confinement" URLs lingering three years after the fact, with obsolete content that dilutes their crawl budget and pollutes their site structure. If you create a dedicated page despite the recommendations, document in a spreadsheet the planned deletion date.
Avoid burying temporary information at the bottom of the page in a drowned paragraph. Google prioritizes visible content at the top of the DOM — an addition in the footer will be crawled but with less weight than a block at the top of the main content. The user should come across it without scrolling.
How can you check that the update has been successfully acknowledged?
Request a reindexing through Search Console as soon as the modification is published. Monitor Google’s cache date (query cache:your-url.com) to confirm the recrawl. If your page is strategic, daily monitoring of its snippet in the SERPs allows you to verify that the temporary information is displayed.
Also test the search with your keyword + temporary term ("restaurant Paris temporary delivery") to check if Google correctly associates your updated page with this intent. If after 48-72 hours nothing changes, either the crawl did not happen, or the added content lacks semantic weight.
- Identify the most relevant existing page to receive the temporary information
- Add content at the top of the page in a visually distinct and semantically marked block
- Request immediate reindexing through Search Console to expedite acknowledgment
- Document the planned removal date in an editorial calendar to avoid leaving obsolete content lingering
- Properly clean up after the period and force a new crawl to update the index
- Monitor the snippet in the SERPs to ensure Google displays the updated version correctly
❓ Frequently Asked Questions
Dois-je créer une nouvelle page si l'information temporaire concerne un service totalement différent de mon activité habituelle ?
Combien de temps Google met-il à recrawler une page existante après modification ?
L'ajout d'un bandeau temporaire en haut de page peut-il diluer la pertinence SEO de mon contenu principal ?
Faut-il modifier le title et la meta description pour refléter l'information temporaire ?
Que faire si j'ai déjà créé plusieurs pages temporaires qui traînent depuis des mois ?
🎥 From the same video 22
Other SEO insights extracted from this same Google Search Central video · duration 54 min · published on 15/05/2020
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.