Google Search archive

Google Search update history

Browse confirmed Google Search updates and Search Central documentation changes, organized for historical reference.

Use this archive to compare traffic changes against past Google updates and documentation changes.
Stored historical records Records remain available after they leave the main Google Search updates tracker.
Official-source context Each entry keeps its source link, status, dates, and captured summary where available.
Commentary follows the record Approved interpretation stays attached as updates move from the main page into the archive.

Past Google Search updates

Confirmed ranking updates, spam updates, and Search incidents from the Google Search Status Dashboard. Records are grouped by year, newest first.

11 archived records found.

2026

  1. Sep 24, 2026

    September 2026 spam update

    The rollout was complete as of October 8, 2026.

    Complete Ranking Official source
    Tech Help Canada interpretation

    Google's September 2026 spam update is complete. The official Search Status record says the rollout finished on October 8, 2026, after starting on September 24, 2026.

    What this may mean

    If your organic traffic or rankings shifted during this window, the update is a possible timing match, but the source does not confirm impact on any specific site, industry, query type, or tactic. Treat the completion date as the point where post-rollout analysis can begin with more confidence.

    What to check next

    • Compare organic traffic and ranking changes before, during, and after September 24 to October 8.
    • Check whether changes are isolated to specific pages, templates, locations, or query groups.
    • Review pages that lost visibility for spam-risk signals, thin content, aggressive automation, or low-value pages.
    • Avoid major SEO overhauls until you separate update-related movement from normal ranking volatility.
    • Document affected URLs and queries so any fixes are tied to evidence, not guesswork.

    Uncertainty noted: Google did not provide site-level impact details in the supplied record.; The source does not describe the specific spam systems or signals involved.; No affected industries, regions, or content types are identified.

  2. Aug 18, 2026

    August 2026 spam update

    The rollout was complete as of August 21, 2026.

    Complete Ranking Official source
    Tech Help Canada interpretation

    Google's August 2026 spam update for Search ranking is complete. The rollout started on August 18, 2026 at 16:27 and ended on August 21, 2026 at 08:49, with Google stating: "The rollout was complete as of August 21, 2026."

    What this may mean

    If your site saw ranking or traffic changes during this window, the update may be a possible factor, but the supplied source does not confirm affected site types, spam signals, industries, or causes. Small businesses should avoid quick, panic-driven changes and instead compare performance before, during, and after the rollout. Focus on whether losses are isolated to specific pages, queries, or content patterns rather than assuming the whole site was affected.

    What to check next

    • Check organic traffic from August 18-21.
    • Compare rankings before and after August 21.
    • Look for page-level drops, not just sitewide movement.
    • Review thin, duplicated, or low-quality content.
    • Document changes before making fixes.

    Uncertainty noted: Google did not specify affected industries or site categories in the supplied data.; The source does not identify which spam systems or signals were involved.; The supplied data does not explain why any individual site may have gained or lost rankings.

  3. Jun 24, 2026

    June 2026 spam update

    The rollout was complete as of June 26, 2026.

    Complete Ranking Official source
    Tech Help Canada interpretation

    Google's June 2026 spam update for Search ranking is complete. The official status record says the rollout finished on June 26, 2026, after starting on June 24, 2026.

    What this may mean

    If your organic visibility changed around this window, the update may be one factor to review. Because this is identified as a spam update, sites should focus on whether their content, links, or SEO practices could be interpreted as manipulative or low-value. The source does not provide details on specific systems, industries, or types of spam affected.

    What to check next

    • Check organic traffic and ranking changes from June 24-26, 2026.
    • Compare affected pages against pages that stayed stable.
    • Review thin, duplicated, automatically generated, or overly SEO-driven content.
    • Audit backlink patterns and remove any risky link-building tactics.
    • Document changes before making fixes so you can track recovery signals.

    Uncertainty noted: No specific spam tactics or ranking signals are named in the source.; No affected industries, regions, or site types are listed.; No recovery guidance is included in the status record.

  4. May 21, 2026

    May 2026 core update

    The rollout was complete as of June 2, 2026.

    Complete Ranking Official source
    Tech Help Canada interpretation

    Google's May 2026 core update for Search ranking is marked complete. The rollout started on May 21, 2026 and was complete as of June 2, 2026, according to the official Google Search Status record.

    What this may mean

    If your organic traffic or rankings changed during this window, the update may be one factor to review. The record confirms timing only; it does not explain what changed, which sites were affected, or why any specific ranking movement happened.

    What to check next

    • Compare organic traffic and keyword rankings before, during, and after the rollout window.
    • Check whether changes affected specific pages, queries, locations, or devices.
    • Review pages with ranking drops for usefulness, clarity, search intent match, and outdated content.
    • Avoid making major SEO changes based on one data point; look for consistent patterns first.

    Uncertainty noted: Google did not provide details on ranking factors changed in this status record.; No affected industries, site types, or query categories are identified.; Any site-specific impact needs confirmation from analytics and Search Console data.

  5. Mar 27, 2026

    March 2026 core update

    The rollout was complete as of April 8, 2026.

    Complete Ranking Official source
    Tech Help Canada interpretation

    Google's March 2026 core update is marked complete. The official status record says the rollout started on March 27, 2026 at 09:00 and was complete as of April 8, 2026 at 13:00.

    What this may mean

    If your organic traffic or rankings changed during this window, the update may be one factor to review. The record confirms timing and completion only; it does not explain what changed, which sites were affected, or why specific rankings moved.

    What to check next

    • Compare organic traffic before, during, and after the rollout window.
    • Check ranking changes for priority pages and commercial keywords.
    • Review affected pages for content quality, usefulness, and search intent match.
    • Separate update-related patterns from site changes, tracking issues, or seasonality.
    • Monitor performance for a few more days before making major SEO changes.

    Uncertainty noted: No details were provided about ranking systems changed.; No affected site types, industries, or query categories were named.; No recovery guidance was included in the supplied status record.

  6. Mar 24, 2026

    March 2026 spam update

    The rollout was complete as of March 25, 2026.

    Complete Ranking Official source
    Tech Help Canada interpretation

    Google's March 2026 spam update for Search ranking is complete. The rollout started on March 24, 2026 at 19:00 and ended on March 25, 2026 at 14:30, with Google's latest official note stating: "The rollout was complete as of March 25, 2026."

    What this may mean

    If your organic traffic, rankings, or visibility changed around this window, the update may be one factor to review. The supplied record confirms completion only; it does not explain what specific spam systems changed, which sites were affected, or what types of tactics were targeted. Avoid making immediate assumptions from a single ranking swing. Compare performance before and after the rollout, then look for patterns across pages, queries, and content types.

    What to check next

    • Check organic traffic and ranking changes from March 24-25, 2026 onward.
    • Compare affected pages against stable pages to spot quality or compliance patterns.
    • Review pages for spam risks such as thin content, doorway pages, scaled low-value content, or manipulative links.
    • Annotate the update in SEO reports so future performance reviews have context.

    Uncertainty noted: Google did not provide details in this record about specific spam systems or targets.; The record does not identify affected industries, query types, or site categories.; Ranking changes during the same period may have other causes.

  7. Feb 24, 2026

    Serving was experiencing an issue

    We fixed the issue with serving search results. There will be no more updates.

    Resolved Serving Official source
    Tech Help Canada interpretation

    Google reported a Serving issue affecting search results on 2026-02-25 from 03:55 to 04:10. The incident is marked resolved, and Google's latest update says the issue was fixed with no further updates planned.

    What this may mean

    This was a short Google Search serving incident. If you saw unusual ranking visibility, traffic, impressions, or click changes during that window, the issue may have contributed. The official record does not state the cause, scope, affected regions, or query types, so avoid treating any related analytics movement as confirmed without checking your own data.

    What to check next

    • Check Search Console performance around 03:55-04:10 on 2026-02-25.
    • Compare organic sessions and conversions before, during, and after the incident window.
    • Look for short-lived drops or spikes rather than long-term ranking changes.
    • Annotate the incident in SEO reporting if your data shows movement during that period.

    Uncertainty noted: Google did not specify the cause of the serving issue.; Google did not specify regions, query types, or sites affected.; No impact level or affected percentage was provided.

  8. Feb 5, 2026

    February 2026 Discover update

    The rollout was complete as of February 27, 2026.

    Complete Ranking Official source
    Tech Help Canada interpretation

    Google's February 2026 Discover update is complete. The rollout started on February 5, 2026 at 17:00 and was marked complete on February 27, 2026 at 10:00. Google's latest official note says: "The rollout was complete as of February 27, 2026."

    What this may mean

    If your site receives traffic from Google Discover, performance changes during or shortly after this rollout may be related to the update, but the source does not explain what changed, which sites were affected, or why rankings shifted. Treat any Discover traffic movement as something to review carefully rather than proof of a specific issue.

    What to check next

    • Check Google Search Console for Discover traffic changes between February 5 and February 27, 2026.
    • Compare Discover clicks, impressions, CTR, and top-performing pages before, during, and after the rollout.
    • Look for page-level patterns instead of judging the whole site from one traffic spike or drop.
    • Review affected content for quality, freshness, headline accuracy, and alignment with user interest.
    • Avoid rushed sitewide changes unless you see a clear, repeated pattern.

    Uncertainty noted: Google did not provide details about what changed in this Discover update.; The source does not identify affected industries, content types, or ranking factors.; The source does not confirm whether any specific traffic change was caused by this update.

2025

  1. Dec 11, 2025

    December 2025 core update

    The rollout was complete as of December 29, 2025.

    Complete Ranking Official source
    Tech Help Canada interpretation

    Google's December 2025 core update for Search ranking is marked complete. The official record says the rollout started on December 11, 2025, and was complete as of December 29, 2025.

    What this may mean

    If your organic traffic, rankings, or lead volume shifted during this window, the update may be one factor to review. The source does not explain what changed, which sites were affected, or why specific rankings moved, so avoid jumping to conclusions from ranking changes alone.

    What to check next

    • Compare organic traffic before, during, and after the rollout window.
    • Check ranking changes for your most important service, product, and local pages.
    • Review Search Console for drops in clicks, impressions, or query visibility.
    • Look for page-level patterns before making sitewide SEO changes.
    • Prioritize improving helpful, clear, trustworthy content over quick fixes.

    Uncertainty noted: No details are provided on ranking factors adjusted.; No industries, regions, or query types are identified as affected.; No guidance is included beyond the completion notice.

  2. Oct 3, 2025

    Serving is experiencing an ongoing issue

    The issue with serving has resolved itself. There will be no more updates.

    Resolved Serving Official source
    Tech Help Canada interpretation

    Google Search reported a Serving issue that began on 2025-10-03 at 20:00:00 and ended on 2025-10-06 at 20:40:00. The latest official update says the issue resolved itself and there will be no more updates.

    What this may mean

    This was a serving-related Search incident, so sites may have seen unusual search visibility, traffic, or reporting patterns during the affected window. The official record does not explain the cause, scope, or types of queries/sites affected, so any business impact should be confirmed against your own analytics rather than assumed.

    What to check next

    • Check organic traffic from 2025-10-03 to 2025-10-06 against nearby normal days.
    • Review Google Search Console clicks, impressions, and average position for unusual dips or spikes.
    • Avoid making SEO changes based only on movement during the incident window.
    • Annotate the incident in analytics reports so future comparisons have context.
    • Monitor post-incident performance to confirm metrics returned to normal.

    Uncertainty noted: Google did not provide a cause.; Google did not state the scale or affected regions.; Google did not specify which result types or queries were impacted.

  3. Aug 26, 2025

    August 2025 spam update

    The rollout was complete as of September 22, 2025.

    Complete Ranking Official source
    Tech Help Canada interpretation

    Google's August 2025 spam update for Search ranking is complete. The rollout started on August 26, 2025, and Google's official status record says it was complete as of September 22, 2025.

    What this may mean

    If your organic traffic or rankings changed during this window, the update may be part of the context, but the supplied Google record does not identify specific sites, industries, spam systems, or ranking factors affected. Treat the completion date as a point to start reviewing performance trends, not as proof of cause.

    What to check next

    • Compare organic traffic and ranking changes before, during, and after the rollout window.
    • Check whether drops are isolated to specific pages, queries, countries, or device types.
    • Review affected pages for spam-risk issues such as thin content, doorway-style pages, keyword stuffing, or manipulative linking.
    • Separate Google Search changes from other causes like site edits, tracking changes, seasonality, or technical errors.
    • Document findings before making large SEO changes.

    Uncertainty noted: Google's record does not explain what specific spam signals were targeted.; No affected industries, regions, or site types are listed in the supplied source.; The source does not confirm whether any individual ranking change was caused by this update.

How to use this archive

Use the dates in this archive as context for traffic changes, but avoid assuming every movement came from one update. Compare your own data before, during, and after the record you are reviewing.

  • Find the closest confirmed update before or during the traffic change you are investigating.
  • Compare landing pages, query groups, and conversions across the update window and the prior period.
  • Look for patterns across groups of pages instead of reacting to one keyword or one unusual day.
  • Review Search Central documentation changes near the same date for guidance Google may have clarified.
  • Run a Website Health Report if the drop could be connected to crawl, indexing, speed, or technical SEO issues.
Does this archive include every Google ranking change?

No. Google Search changes constantly, and many changes are not announced individually. This archive stores records we have captured from official Google sources.

Why keep documentation changes beside ranking updates?

Search Central documentation changes can clarify how Google wants site owners to handle content, structured data, crawling, indexing, or policy issues. They are useful context even when they are not ranking updates.

Can old updates still matter?

Yes. Older updates help explain long-term patterns, recurring ranking themes, and past volatility. They are especially useful when reviewing older analytics data or major traffic shifts.

Why might commentary be missing on some older records?

Commentary appears only when it is available for a record. Older records can still be useful without commentary because the official date, status, and source context remain preserved.

Should I make changes based only on an archived update?

No. Use archived updates as context, then confirm the impact in your own analytics, Search Console data, affected pages, query groups, and technical health checks.

Where should I check current status?

Use the main Google Search updates tracker for the current status and latest visible records. Use this page when you want the historical record.

Past Google Search Central changes

Past Search Central documentation changes, including updates to guidelines, best practices, and structured data references. Records are grouped by year, newest first.

44 archived records found.

2026

  1. Oct 22, 2026

    Updated guidance on crawlable URL structures

    What: Updated the URL structure best practices to clarify word separation guidelines using hyphens versus underscores. Why: To synchronize the documentation with the episodes of "The Non-Canonical Cabinet" video series.

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its URL structure best practices to clarify guidance on word separation, specifically hyphens versus underscores. The stated reason is to align the documentation with episodes of "The Non-Canonical Cabinet" video series.

    What this may mean

    This appears to be a documentation clarification rather than a new ranking system update. For small business sites, the practical takeaway is to make sure URLs follow Google's preferred readability guidance, especially when creating new pages, blog posts, product URLs, or location pages.

    What to check next

    • Check whether new URLs use clear word separation.
    • Review templates for blog, service, product, and location page URLs.
    • Avoid changing existing URLs unless there is a clear SEO or usability reason.
    • If URLs are changed, confirm redirects, canonicals, and internal links are updated.

    Uncertainty noted: The supplied update does not include the full revised best-practice text.; No ranking impact, rollout period, or enforcement change is stated.

  2. Oct 20, 2026

    Updated the control what you share with Google Search documentation

    What: Updated the control what you share with Google Search documentation to include existing options such as the robots meta tag, data-nosnippet, X-Robots-Tag, and the Search generative AI control, along with minor clarifications that the page applies to Goog...

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its Search Central documentation on controlling what site owners share with Google Search. The page now references existing controls including robots meta tags, data-nosnippet, X-Robots-Tag, and Search generative AI controls, with minor clarifications that the page applies to Google Search.

    What this may mean

    This appears to be a documentation refresh, not a ranking update or new policy announcement. For small businesses and marketing teams, the practical takeaway is to review how your site controls indexing, snippets, and AI-related Search display options. If you already use robots directives or snippet controls, this update is a reminder to confirm they still match what you want Google to show.

    What to check next

    • Review key pages for robots meta tags and X-Robots-Tag headers.
    • Check whether data-nosnippet is used where you want to limit displayed text.
    • Confirm your Search generative AI controls match your content-sharing preferences.
    • Make sure blocked or restricted content still supports your SEO goals.

    Uncertainty noted: The source does not mention any new control or ranking impact.; No rollout period or enforcement change is stated.; The exact wording changes on the documentation page are not provided.

  3. Oct 15, 2026

    Updating the Indexing API quota page

    What: Updated the Indexing API quota page to reflect the current quota limits and process. Why: To document the current quota limits for the Indexing API and remove an outdated form.

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its Indexing API quota documentation to reflect current quota limits and the current process. The update also removes an outdated form from the page.

    What this may mean

    If you use the Indexing API, your workflow may need to match the revised quota guidance. This does not confirm a ranking change, indexing change, or new API capability. It only confirms that Google's quota documentation has been brought up to date.

    What to check next

    • Review the updated Indexing API quota page.
    • Check whether your current API usage fits the documented limits.
    • Remove any internal references to the outdated form.
    • Confirm your team's request process matches Google's current documentation.

    Uncertainty noted: The source does not list the specific quota limits.; The source does not explain how the process changed.; The source does not state whether existing users are affected differently from new users.

  4. Oct 7, 2026

    Added documentation on the UGC Fresh Data Program

    What: Added a new page about the UGC Fresh Data Program. Why: To explain the purpose of the program and help prospective applicants understand the eligibility criteria and how to participate.

    Published Search Central Official source
    Tech Help Canada interpretation

    Google Search Central published documentation for the UGC Fresh Data Program on 2026-10-08. The new page explains the program's purpose, eligibility criteria, and how prospective applicants can participate.

    What this may mean

    If your business relies on user-generated content, this may be worth reviewing to see whether the program is relevant to your site. The update is informational documentation, not a confirmed ranking change or broad Search feature rollout based on the supplied source.

    What to check next

    • Review the new UGC Fresh Data Program documentation on Search Central.
    • Check whether your site has qualifying user-generated content.
    • Compare your current content and data practices against Google's stated eligibility criteria.
    • If eligible, document the participation steps and assign an owner to evaluate next steps.

    Uncertainty noted: The source does not include the full eligibility criteria.; The source does not state whether participation affects visibility in Search.; The source does not identify which types of UGC sites are most likely to qualify.

  5. Sep 30, 2026

    Updated guidance on using generative AI content

    What: Updated the using generative AI content guide with information from the Search Quality Raters guidelines. Why: To get our documentation in sync with our presentations we use at our developer events.

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its Search Central guide on using generative AI content on October 1, 2026. The update adds information from the Search Quality Raters Guidelines and aligns the documentation with material used in Google developer event presentations.

    What this may mean

    This suggests Google is clarifying how its existing quality concepts apply to generative AI content, rather than announcing a new ranking system or penalty in the supplied record. For small businesses and marketing teams, the practical takeaway is to review AI-assisted content against Google's quality expectations, especially where usefulness, originality, trust, and reader value may be evaluated.

    What to check next

    • Review Google's updated generative AI content guide directly.
    • Audit AI-assisted pages for usefulness, accuracy, and originality.
    • Check whether important claims are supported by real expertise or sources.
    • Avoid publishing AI content that adds little beyond existing search results.
    • Update internal content guidelines to reflect the revised Google documentation.

    Uncertainty noted: The supplied update does not state whether any ranking systems changed.; No specific added passages from the guide were provided.; No rollout timeline or enforcement details were included.

  6. Sep 23, 2026

    Added creator property and updated interactionStatistic in VideoObject structured data

    What: Added the creator property (noting support for author) and updated interactionStatistic to document supported interaction types in the VideoObject structured data documentation. Why: To document support for the creator and author properties, and clarify...

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its VideoObject structured data documentation to add the creator property, note support for author, and clarify which interaction types are supported for interactionStatistic.

    What this may mean

    If your site uses VideoObject markup, this update may affect how you describe who created or authored a video and how you mark up engagement signals. The change appears to be documentation-focused, so it should be treated as guidance clarification unless Google provides more detail elsewhere.

    What to check next

    • Check any VideoObject markup on key video pages.
    • Review whether creator or author should be added where relevant.
    • Compare current interactionStatistic markup against Google's supported interaction types.
    • Validate updated pages with Google's structured data testing tools.
    • Document any schema changes before rolling them across the site.

    Uncertainty noted: The source does not state whether this changes eligibility for search features.; No rollout timeline or ranking impact is provided.; The exact supported interaction types must be confirmed in the linked documentation.

  7. Sep 17, 2026

    Added local business query support to the aggregator and supplier units

    What: Updated the aggregator unit and supplier unit documentation to include support for local business queries. Why: The aggregator unit and supplier unit now support local business queries.

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its Search Central documentation for aggregator units and supplier units to state that both now support local business queries.

    What this may mean

    If you use or manage structured documentation tied to aggregator or supplier units, local business query support may now be relevant to how those units are configured or reviewed. The update confirms support in the documentation, but it does not explain implementation details, ranking impact, eligibility requirements, or whether any existing setup needs changes.

    What to check next

    • Review the updated aggregator unit and supplier unit documentation.
    • Check whether your local business data is accurate and consistently formatted.
    • Confirm any aggregator or supplier integrations reflect current business details.
    • Monitor Search Console and search visibility for relevant local queries after any changes.

    Uncertainty noted: No implementation examples were included in the supplied update.; No ranking or visibility impact was stated.; No rollout timeline beyond the documentation update date was provided.

  8. Sep 15, 2026

    Added documentation on adding a Search profile badge to your website

    What: Added a new guide on how to add a Search profile badge to your website. Why: To help site owners point their audience to their Search profile.

    Published Search Central Official source
    Tech Help Canada interpretation

    Google Search Central published documentation for adding a Search profile badge to a website. The stated purpose is to help site owners point visitors to their Search profile.

    What this may mean

    This appears to be a visibility and trust-related website enhancement rather than an algorithm change. For small businesses and marketing teams, the badge may offer a simple way to connect website visitors with a Google Search profile, but the supplied update does not say it affects rankings, eligibility, traffic, or Search appearance.

    What to check next

    • Review the new Google guide before adding the badge.
    • Confirm your Search profile is accurate and worth sending visitors to.
    • Place the badge only where it supports user trust or navigation.
    • Avoid treating the badge as an SEO ranking tactic unless Google states that directly.

    Uncertainty noted: The source does not explain eligibility requirements for the badge.; The source does not state whether the badge affects Search performance.; The source does not include implementation details beyond the existence of the guide.

  9. Sep 7, 2026

    Added documentation about regional differences in Search experience

    What: Added documentation about regional differences in Search experience, which includes information about search experiences available in certain countries, such as aggregator units, supplier units, and carousels. Why: To help publishers, businesses, and agg...

    Published Search Central Official source
    Tech Help Canada interpretation

    Google Search Central published a documentation update on September 8, 2026 about regional differences in Search experiences. The new documentation covers search features available in certain countries, including aggregator units, supplier units, and carousels, plus eligibility criteria and participation guidance.

    What this may mean

    This may matter if your business, publishing site, or aggregation platform operates in markets where Google shows region-specific Search features. The update does not announce a ranking change or new rollout; it points to documentation meant to help businesses understand which regional features exist, who may be eligible, and how participation works.

    What to check next

    • Check whether your target countries are covered in the new regional Search experience documentation.
    • Review eligibility criteria for any relevant aggregator units, supplier units, or carousels.
    • Compare the guidance against your current structured data, feed, or listing setup.
    • Document any participation requirements that apply to your business or clients.

    Uncertainty noted: The supplied update does not list the specific countries covered.; No impact on rankings, traffic, or visibility is stated.; No rollout timeline or feature expansion details are provided.

  10. Aug 30, 2026

    Updated the European Search Dataset Licensing Program page

    What: Updated the Google European Search Dataset Licensing Program page. Why: Refreshed the program overview, eligibility criteria, and application details.

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its European Search Dataset Licensing Program page on August 31, 2026. The documented change refreshed the program overview, eligibility criteria, and application details.

    What this may mean

    This appears to be a documentation update, not a confirmed ranking, crawling, indexing, or search visibility change. For most small businesses and marketing teams, there may be no direct action unless your organization uses, applies for, or evaluates access to Google's European Search Dataset Licensing Program. If your work depends on search data access in Europe, the updated eligibility and application details could affect whether and how you apply.

    What to check next

    • Review the updated program page if your team uses or seeks European search dataset access.
    • Check whether the refreshed eligibility criteria change your organization's fit.
    • Confirm any application requirements before submitting or resubmitting materials.
    • Monitor Google Search Central updates for related documentation changes.

    Uncertainty noted: The source does not specify what eligibility criteria changed.; No ranking or SEO impact is stated.; No rollout timeline beyond the update date is provided.

  11. Aug 27, 2026

    Updated the favicon documentation

    What: Updated the favicon documentation to specifically list out the supported favicon file formats. Why: To be clearer about which favicon file formats are supported by Google Search. Previously, the documentation linked to an external reference that evolved...

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its Search Central favicon documentation to explicitly list the favicon file formats supported by Google Search. The supported formats have not changed; the update clarifies documentation that previously relied on an external reference.

    What this may mean

    This appears to be a documentation clarity update, not a ranking or feature change. For small business sites, the main takeaway is to confirm your favicon uses a Google-supported format and is implemented cleanly, since favicons can affect how your brand appears in Search results.

    What to check next

    • Check your current favicon file format against Google's updated documentation.
    • Confirm the favicon is accessible to Googlebot and not blocked by robots.txt.
    • Review your site's favicon markup for accuracy.
    • Test how your favicon appears in Google Search when possible.

    Uncertainty noted: The supplied update does not list the supported file formats.; No implementation changes or rollout effects are described.

  12. Aug 27, 2026

    Updated the site reputation policy

    What: Updated the site reputation policy. Why: We've adjusted our enforcement approach within the European Economic Area (EEA). For more information, see our blog post.

    Published Search Central Official source
    Tech Help Canada interpretation

    Google Search Central published an update to its site reputation policy on August 28, 2026. The official note says Google has adjusted its enforcement approach within the European Economic Area (EEA) and points readers to a blog post for more detail.

    What this may mean

    If your business operates in or targets the EEA, this may affect how Google evaluates content connected to site reputation policy enforcement. The source does not explain the exact enforcement changes, which sites are most exposed, or whether non-EEA activity is affected. Treat this as a prompt to review compliance rather than assume a ranking impact.

    What to check next

    • Review Google's site reputation policy and the linked blog post.
    • Check whether your site publishes third-party, sponsored, partner, or hosted content.
    • Identify any pages targeting EEA users or markets.
    • Document ownership, editorial control, and purpose for reputation-sensitive content.
    • Monitor Search Console for unusual visibility or indexing changes.

    Uncertainty noted: The official note does not describe the specific enforcement adjustment.; The supplied source does not include the linked blog post content.; No rollout duration or affected site examples are provided.

  13. Aug 19, 2026

    New custom button for preferred sources

    What: Updated the preferred sources documentation to include instructions on how to add the new custom, interactive button to your site. Why: Site owners can now implement a custom, interactive button to guide their audience to set them as a preferred source,...

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its preferred sources documentation with instructions for adding a new custom, interactive button to a website. The button is intended to help site owners guide visitors to set the site as a preferred source, then return users to where they left off.

    What this may mean

    For publishers, content-heavy businesses, and brands with loyal audiences, this may create a cleaner path to encourage repeat visibility through Google's preferred sources feature. The update appears implementation-focused rather than a ranking change. Small businesses should treat it as an audience-retention and engagement opportunity, not a guaranteed traffic lift.

    What to check next

    • Review Google's preferred sources documentation.
    • Check whether your site audience would benefit from the button.
    • Ask your developer to assess implementation effort.
    • Test the user flow before adding it sitewide.
    • Track engagement after launch.

    Uncertainty noted: No performance impact or traffic benefit is stated.; No rollout duration or eligibility limits are provided.; No industry-specific guidance is included.; No implementation details beyond the documentation update are supplied here.

  14. Jul 28, 2026

    Added guide on analyzing social and video platform content

    What: Added a new guide on how to analyze your social and video platform content performance in Search Console. Why: To help content creators, social media managers, and SEO professionals understand how their social and video platform content performs on Googl...

    Published Search Central Official source
    Tech Help Canada interpretation

    Google Search Central published a documentation update adding a new guide on analyzing social and video platform content performance in Search Console.

    What this may mean

    This may give content creators, social media managers, and SEO professionals clearer guidance on understanding how social and video platform content appears and performs on Google Search. For small businesses and marketing teams, the practical value is likely in connecting off-site content efforts with Search visibility, instead of judging social and video performance only inside each platform's own analytics.

    What to check next

    • Review the new Google guide and note which Search Console reports it recommends.
    • Check whether your social and video content is eligible to appear in Google Search.
    • Compare Search Console performance data with platform analytics where possible.
    • Look for content types or pages gaining impressions from social or video-related search results.
    • Update reporting templates if Search Console adds useful context for these channels.

    Uncertainty noted: The supplied update does not specify which Search Console reports or metrics the guide focuses on.; No rollout details, feature changes, or ranking impact are stated.; The source does not say whether this applies differently by platform or content format.

  15. Jul 23, 2026

    Added a new review snippet guideline

    What: Added a new guideline to the review snippet documentation about fake and undisclosed incentivized reviews. Why: To improve user review transparency.

    Published Search Central Official source
    Tech Help Canada interpretation

    Google added a new guideline to its review snippet documentation on July 24, 2026. The guideline addresses fake reviews and undisclosed incentivized reviews, with the stated goal of improving transparency around user reviews.

    What this may mean

    If your site uses review markup or relies on review snippets in Google Search, this update signals closer attention to whether reviews are authentic and whether incentives are clearly disclosed. The official note does not describe penalties, enforcement timing, or technical markup changes, so the safest takeaway is to review your current review collection and display practices for transparency.

    What to check next

    • Check that reviews displayed on your site are genuine and not fabricated.
    • Confirm any incentivized reviews are clearly disclosed where they appear.
    • Review pages using review snippet markup for compliance with Google's review documentation.
    • Audit third-party review widgets or feeds to understand how reviews are collected and labeled.
    • Update internal review-request processes so incentives, if used, are documented and disclosed.

    Uncertainty noted: The source does not include the exact new guideline text.; No enforcement date or rollout details were provided.; No specific markup changes were mentioned.

  16. Jul 13, 2026

    Updated the package tracking documentation

    What: Updated the feature availability and eligibility requirements sections package tracking early adopters program documentation. Why: The package tracking early adopters program is no longer accepting new partners.

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its package tracking early adopters program documentation. The key change: the program is no longer accepting new partners, and Google revised the feature availability and eligibility requirements sections.

    What this may mean

    If your business was planning to join Google's package tracking early adopters program, that path appears closed for now. Existing partners may still need to review the updated documentation to confirm whether availability or eligibility language affects their current setup, but the source does not state any change to existing participation.

    What to check next

    • Check whether your business is already enrolled in the program.
    • Review the updated feature availability and eligibility sections.
    • Avoid planning new implementation work around joining the early adopters program.
    • If package tracking matters to your search presence, monitor Google's Search Central updates for future options.

    Uncertainty noted: Google does not state whether existing partners are affected.; No replacement program or reopening date is mentioned.; The exact documentation wording changes are not included in the update summary.

  17. Jul 9, 2026

    Updated the canonicalization troubleshooting guide

    What: Updated the canonicalization troubleshooting guide with clarifications on re-evaluation time. Why: To provide better expectations about how long it takes for canonicalization changes to take effect.

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its canonicalization troubleshooting guide on July 10, 2026. The change clarifies expectations around how long it can take for canonicalization changes to be re-evaluated and reflected in Search.

    What this may mean

    If you recently changed canonical tags, redirects, duplicate-page handling, or preferred URLs, the impact may not show immediately. This update does not announce a ranking change or new canonicalization rule; it appears to improve guidance on timing and expectations. For site owners, the main takeaway is to avoid assuming a canonical fix failed too quickly.

    What to check next

    • Review recent canonical tag and redirect changes before making more edits.
    • Check Google Search Console for selected canonical versus user-declared canonical.
    • Document the date each canonicalization fix was implemented.
    • Avoid repeated changes while Google is still re-evaluating the URLs.
    • Read the updated troubleshooting guide if canonical issues are active.

    Uncertainty noted: The source does not state a specific re-evaluation timeframe.; The source does not mention any algorithm or ranking system change.; The exact wording added to the guide is not included in the update record.

  18. Jul 6, 2026

    Added category to merchant listing structured data

    What: Updated the Merchant listing documentation to detail how the Product.category property can be used with both Text and CategoryCode types. This aligns with the Google Merchant Center feed specifications for the product_type and google_product_category att...

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its Merchant listing structured data documentation to clarify that Product.category can use both Text and CategoryCode values. The update aligns schema.org markup guidance with Google Merchant Center feed attributes: product_type and google_product_category.

    What this may mean

    Merchants can now document both their own product categories and Google-defined category information more clearly in structured data. For small businesses, this may help keep product markup consistent with Merchant Center feeds and give Google more complete product context for Search and Shopping surfaces. The update explains supported usage; it does not state any ranking change or new eligibility requirement.

    What to check next

    • Check whether your product pages already use Product.category.
    • Compare on-page structured data with Merchant Center product_type and google_product_category fields.
    • Confirm category values use the right format: Text or CategoryCode.
    • Update product schema templates if category markup is missing or inconsistent.

    Uncertainty noted: No rollout duration or enforcement timeline is provided.; No performance impact or ranking effect is stated.; No examples are included in the supplied update text.

  19. Jul 6, 2026

    Clarified how to specify sale price effective dates in Product structured data

    What: Added a new section on "Sale duration" to the Merchant listing guide. This explains how to use the validFrom, validThrough, and priceValidUntil schema.org properties to set the effective range for sale prices, including best practices and examples for pl...

    Published Search Central Official source
    Tech Help Canada interpretation

    Google clarified how merchants should specify sale price effective dates in Product structured data. The Merchant listing guide now includes a "Sale duration" section explaining how to use validFrom, validThrough, and priceValidUntil with sale prices, including placement on either Offer or PriceSpecification nodes.

    What this may mean

    If your site uses Product structured data for merchant listings, sale pricing markup should now be checked against Google's clarified guidance. This update appears aimed at aligning structured data usage with the Merchant Center sale_price_effective_date feed attribute, which may help reduce inconsistencies between on-page markup and feed data.

    What to check next

    • Review Product structured data on sale items.
    • Check whether sale start and end dates use validFrom, validThrough, or priceValidUntil correctly.
    • Compare on-page structured data with Merchant Center sale_price_effective_date values.
    • Confirm whether sale date properties are placed on Offer or PriceSpecification nodes as intended.
    • Update examples or templates used by your ecommerce platform or SEO team.

    Uncertainty noted: The source does not say whether this changes eligibility, ranking, or display behavior.; The source does not mention enforcement timing or whether existing markup will trigger warnings.; The supplied record does not include the full guide text or examples.

  20. Jun 30, 2026

    Updating our AMP documentation

    What: Simplified our AMP documentation by removing outdated references to the AMP viewer, AMP Cache, and signed exchange. Why: Starting today, Google Search is updating how it connects users to AMP pages, and will now take users directly to the publisher's AMP...

    Published Search Central Official source
    Tech Help Canada interpretation

    Google updated its AMP documentation on July 1, 2026. The docs now remove outdated references to the AMP viewer, AMP Cache, and signed exchange. Google says Search will take users directly to publishers' AMP host pages, and AMP content will continue to rank like any other web page.

    What this may mean

    For publishers still using AMP, this may reduce technical maintenance because Google says there is no longer a need to update the AMP cache or configure signed exchanges. The ranking message is also important: AMP is not described as receiving separate ranking treatment here. For small businesses, this update is mainly a technical cleanup signal unless your site actively serves AMP pages.

    What to check next

    • Check whether your site still uses AMP pages.
    • Review AMP setup for references to AMP Cache or signed exchanges.
    • Confirm AMP pages resolve correctly on your own host.
    • Monitor Search Console for AMP-related errors after the change.
    • Update internal documentation if your team still follows old AMP workflows.

    Uncertainty noted: No rollout duration is provided.; No details are given about edge cases for existing AMP implementations.; No specific Search Console reporting changes are mentioned.

  21. Jun 16, 2026

    Site move guidance now includes information on domain variants

    What: The site move guide now includes information on using the Change of Address tool for all subdomain variants (including www and non-www) during domain migrations. Why: The domain migrations work best when all variants of a site are migrated properly.

    Published Search Central Official source
  22. Jun 14, 2026

    Clarifying guidance on llms.txt files

    What: Added a note to the AI optimization guide clarifying Google Search's usage of llms.txt files. Why: To address questions from the community and clarify that while these files aren't needed for Google Search (and won't negatively or positively impact your...

    Published Search Central Official source
  23. Jun 14, 2026

    Removing documentation for the FAQ rich result feature

    What: Removed documentation for the FAQ rich result feature. Why: The FAQ rich result feature is no longer shown in Google Search results, as announced in the changelog entry in May 2026.

    Published Search Central Official source
  24. Jun 11, 2026

    New article for small business owners in Tennessee

    What: Created a new article explaining how small business owners in Tennessee can receive notifications from Google Search. Why: To help small businesses in Tennessee learn how they can get notified if their web content is removed or restricted on Google Searc...

    Published Search Central Official source
  25. Jun 4, 2026

    Guidance on third-party SEO tools, services, and advice

    What: Added Google Search's guidance on using third-party SEO tools, services, and advice. Also added guidance to the Do you need an SEO? page on evaluating your SEO's recommendations and tools, along with other minor updates to the page to simplify and modern...

    Published Search Central Official source

How this archive works

The archive uses the same stored records as the main tracker, then keeps older entries available for historical research.

1

We check official sources

The archive tracks records from the Google Search Status Dashboard and Google Search Central documentation feed.

2

Every record gets logged

Each update, incident, or documentation change is stored with dates, status, source link, and captured text.

3

Context stays attached

When Tech Help Canada interpretation is available, it stays with the record as it moves into the archive.

Reviewing an old traffic change?

Use the archive to find the closest confirmed Google record, then compare it against your own technical SEO, page speed, web vitals, and Search Console data.

Run a free Website Health Report