Is it true that the Classic Search Console is about to vanish?

Why is Google shutting down the old Search Console?

The Classic Search Console was never more than a transitional solution. Since the gradual launch of the new version starting in 2018, Google has been sending multiple signals that the old interface was nearing its last months.

This announcement by John Mueller confirms what many anticipated: the coexistence of both versions is coming to an end. Google wants to focus its development efforts on a single, more modern platform that is designed to offer a better user experience.

What will actually change for users?

Most features have already been transferred. The search performance reports, indexing data, URL inspections — all of this already exists in the new version, often with more granularity.

Let's be honest: some reports are still missing or are less detailed. Internal links, for example, are not as well represented in the new interface. And that's where the issue lies — Mueller mentions features that could be "reconsidered," a euphemism for saying that not everything will necessarily be transferred.

What is the exact timeline for this closure?

Mueller speaks of "the end of the year" without providing further details. In Google jargon, this generally means between September and December, with a notice of a few weeks at most before the final cut-off.

History shows that Google doesn't linger on this type of transition. Remember the closure of Google+ or certain APIs: once the announcement is made, the timeline is often shorter than anticipated. It's better to anticipate now than to find yourself caught off guard.

• Mandatory incremental migration: adopt the new Search Console now to identify gaps
• Some reports might disappear: export your critical historical data before the closure
• Team training is necessary: the usability of the new version is different enough to require an adaptation period
• Check APIs and integrations: if you use the Search Console API, ensure your scripts point to the correct version
• Vague but imminent timeline: prepare for a closure within 6-9 months at most

Was this closure predictable?

Absolutely. Google has been announcing this transition for years. What surprises is mainly the relatively short timeline between this announcement and the actual closure. Generally, Google prefers to allow several years of transition for such critical tools.

The timing suggests that Google considers the new Search Console sufficiently mature. However, field feedback shows that some professionals remain attached to the old version for specific — and legitimate — reasons.

Which features might really disappear?

When Mueller says that some aspects "could be reconsidered," it deserves attention. [To be checked] — Google has never published a comprehensive list of features that will NOT be migrated.

According to observations, detailed internal link reports, certain long historical views, and some advanced filters from the old interface still do not have a strict equivalent in the new version. If you rely on this data for regular audits, now is the time to export massively.

Is the new Search Console really up to par?

Yes and no. The new interface offers fresher data (16 months versus 90 days for certain metrics), better granularity on performance, and features like the significantly improved index coverage report.

However — and this is an important but — some workflows are heavier. Bulk exports are sometimes less convenient, and some visualizations lack flexibility. For automated monitoring via API, the transition is smooth. For daily manual work, there is a real learning curve.

What immediate actions should be taken?

First, switch to the new Search Console now for all your sites. Even if you keep the old one open in a tab, force yourself to work primarily with the new interface for at least two weeks.

Second, identify the critical reports that you still rely solely on in the old version. List them, check if they have an equivalent in the new interface, and if not, export your historical data in bulk. Some exports will no longer be possible after the closure.

How to ensure nothing will be lost in the transition?

Create a mapping table between your current workflows and the features of the new Search Console. For each report you generate monthly, note where to find it in the new interface and test the data quality.

If you use scripts or API integrations, check that they point to the correct endpoints. The API of the new Search Console uses slightly different data structures — it's better to discover incompatibilities now rather than after the cut-off.

What mistakes should be avoided during this migration?

Don't assume that "everything will be transferred automatically." Google has already abandoned features in the past during tool migrations — remember Google Analytics Universal to GA4. Some reports simply disappeared.

Another classic pitfall: neglecting team training. If your clients or collaborators are accustomed to the old interface, a sudden transition can cause confusion and loss of productivity. Prepare short orientation sessions in advance.

Finally, beware of automated alerts and reports. If you have set up notifications or dashboards connected to the old Search Console, they will stop working overnight. Test alternatives now.

• Switch all sites to the new Search Console and test daily workflows
• Export critical historical data still available only in the old version
• Check the compatibility of all scripts and API integrations with the new interface
• Train teams and clients on the new usability before the mandatory closure
• Document missing reports and prepare alternatives (manual exports, third-party tools, etc.)
• Test alerts and notifications to ensure they work in the new version