I noticed that Google updated its canonicalization troubleshooting guide to clarify how long it may take for fixes to appear in Google Search results. According to the revised guidance, Google might keep pages in a duplicate cluster for up to two weeks after content issues have been fixed.
What changed. I found a new section at the top of the guide that explains the expected timeline for canonicalization fixes. Google now makes it clear that the process can take up to two weeks.
I also saw additional technical details about clustering. Google explains that pages need to be sufficiently similar before its systems can group them into a duplicate cluster and select one version as the canonical page.
Google’s updated canonicalization guidance sets expectations for SEOs: fixed pages may remain in a duplicate cluster for up to two weeks, while clearer content differences can speed reevaluation.
Here is the section Google added:
Why I care. This clarification gives me a more realistic timeline when monitoring canonicalization fixes. Once Google has processed an update, I know I may need to wait the full two weeks before deciding whether the change worked.
As AI reshapes search, every glowing path to discovery carries commercial value—turning SEO investment into a conversation about pipeline, risk, and customer acquisition costs.
That waiting period can help me avoid making unnecessary page changes while Google is still consolidating duplicate URLs and evaluating the appropriate canonical version.
I’m seeing Google Search Console get a useful new reporting layer for social and video content through what Google calls platform properties. This gives me a way to understand how my content on Instagram, TikTok, X, and YouTube is performing in Google Search.
The big change is that I can now connect supported social or video accounts to Search Console and see how people find that content through Google. Instead of only analyzing websites I own or manage directly, I can begin looking at search visibility for content hosted on third-party platforms.
Google said this update makes it possible to track which search terms lead people to Instagram, TikTok, X, and YouTube content in Search, along with how audiences interact with those posts. I’ll be able to review this data inside the performance report, insights report, and achievements sections of Google Search Console.
A Google Search Console dropdown highlights the new platform property flow, with the rustybrick X profile appearing as a selectable property for reporting.
In the performance report, I can review total clicks, impressions, and other key metrics. I can also filter and sort the data to see which posts and queries are driving the most traffic, and if I want to analyze it somewhere else, I can export the data.
In the insights report, I can get a higher-level view of recent traffic trends, top-performing posts, and the ways people are discovering my account through Google Search.
A Google Search Console platform property view shows how an X profile appears in Search, pairing 28-day click and impression trends with the queries driving visibility.
The achievements section adds another useful angle by helping me track growth milestones, such as reaching a new threshold for total clicks from Google Search over the last 28 days.
This feels similar to the social channel details that previously appeared in Search Console insights, but platform properties look like a more direct way to verify and analyze these accounts.
A Google Search Console Insights view highlights how YouTube posts are gaining visibility in Search, with 17.8K clicks and traffic broken down by web, video, Discover, and image search.
To set this up, I need to verify a platform property inside my Google Search Console account. I can start by opening Search Console, going to the Search Console verification page, or using the property selector dropdown anywhere in Search Console and choosing “Add property.”
From there, I select one of the currently supported platforms: Instagram, TikTok, X, or YouTube. Then I follow the onscreen verification steps to securely authorize the connection.
A glowing Google search bar cuts through streams of digital data, capturing the fast-moving world of search, shopping visibility, and SEO innovation.
Google said platform properties will roll out gradually over the coming weeks, so I may not see the option in my account right away. For setup details, Google points users to its help center documentation. The help document had briefly appeared a few weeks earlier before being removed, so this release makes the feature official.
What stands out to me is the access this gives marketers, creators, and SEOs. Google has not traditionally given us a clear way to see how our content performs on domains or properties we do not own. With platform properties, I can finally start seeing how my social and video content performs in Google Search, even when I do not have developer access to those platforms. That opens up a much better view of search-driven visibility beyond my own website.
I’m seeing Google expand merchant listing structured data with support for sale duration and the Product.category property. The update brings Google Search’s merchant listing structured data closer to the capabilities already available in Google Merchant Center feeds.
Sale duration. Google added a new Sale duration section to its Merchant listing structured data documentation. In that update, Google said the guidance explains how to use the validFrom, validThrough, and priceValidUntil schema.org properties to define the effective date range for sale prices.
I find this useful because Google’s guidance also covers best practices and examples for placing those properties on either Offer or PriceSpecification nodes. Google said the change aligns schema.org usage with the Merchant Center feed attribute sale_price_effective_date, giving merchants clearer instructions for handling sale price timing in structured data.
Google's sale duration guidance shows merchants how to define when a sale price starts and ends in structured data, including Offer and UnitPriceSpecification JSON-LD examples.
Here is the new sale duration section Google added:
Product category. Google also updated the same Merchant listing structured data documentation to include support for the Product.category property.
Google’s merchant listing guidance now shows how product categories can mix custom text labels with Google Product Category codes in structured data.
Google wrote that the documentation now explains how Product.category can be used with both Text and CategoryCode types. According to Google, this aligns with Google Merchant Center feed specifications for the product_type and google_product_category attributes.
From my perspective, this makes the structured data more practical for merchants because it lets them provide both merchant-defined and Google-defined category details directly in schema.org markup. Google said this can enhance product information for Google Search and Shopping.
A glowing Google search bar cuts through streams of digital data, capturing the fast-moving world of search, shopping visibility, and SEO innovation.
Here is what Google added for product category support:
Why I care. If I maintain merchant listing structured data for Google, these additions are worth reviewing. Product category support can help Google better understand the products being provided, which may improve how those products match relevant queries.
I also see sale duration support as a practical improvement for planning promotions. When I update merchant listing structured data, I can now define sale price timing more clearly and align that markup more closely with Google Merchant Center feed behavior.
I can finally say the page indexing report inside Google Search Console has been updated after a frustrating three-week delay. Instead of showing data stuck on June 11, 2026, the report is now displaying data through June 29, 2026.
The delay. I previously noted that the page indexing report had been frozen at June 11, which made it much harder to understand what Google was seeing across a site.
Now, as of Friday, July 3, the report is showing much fresher data, with updates running through June 29.
Page indexing report. I use this report to see which pages Google can find and index on a website. It also helps surface indexing issues Google may have run into while crawling the site.
I can access the report directly in Search Console over here, or by opening the Indexing section and selecting Pages.
The report shows indexed pages in green and not indexed pages in gray. I can also overlay impressions on the chart, then review the listed reasons explaining why certain pages on a website are not being indexed.
For more details on how the page indexing report works, I would refer to Google’s help document.
Why I care. If I was trying to diagnose why Google had not indexed specific pages over the past couple of weeks, the delayed report left me with limited visibility.
Now that the data has finally been refreshed through June 29, I can dig back into the indexing report, review the latest issues, and decide what needs attention next.
I’m tracking a growing Google Business Profile issue after several days of complaints from businesses that say reviews have disappeared from their local listings. Google has now confirmed that it is investigating the reports, and in some cases, review submissions on affected profiles appear to be paused.
What Google said. Google told us that when its systems detect suspicious review activity, it may take several actions, including removing reviews and temporarily pausing reviews on a profile to prevent further abuse. Google also said it is investigating the issue and will restore any reviews that were incorrectly removed.
What I’m seeing. As I documented on the Search Engine Roundtable, there are dozens of complaints in the Google Business Profile Forums from business owners and local SEOs who say their reviews have mysteriously vanished. In some cases, businesses are also unable to receive new reviews on their local listings.
From what I can tell, Google’s review spam detection systems may be identifying certain patterns and aggressively removing or blocking reviews on suspected Google Business Profiles. What remains unclear is whether this is tied to spammers abusing some profiles, a recent algorithmic adjustment, or Google’s systems becoming overly sensitive.
More details. Amy Toman, a volunteer Google Product Expert for Google Business Profiles, shared on LinkedIn that businesses or clients affected by this issue can post in the forum if they want to, but Google is already aware of the problem and working on it. She also noted that no timeline for a resolution has been provided yet.
She said she is seeing a new pattern where, after fake or spam reviews are reported, some Google listings receive a review block and all reviews are hidden. In at least one case, she said the rating was reduced to 0.
Why I care. If I noticed a sudden drop in reviews or stopped receiving new reviews this week, I would consider this issue a likely explanation. For local businesses, reviews can directly affect trust, visibility, and customer decisions, so even a temporary review disruption can be frustrating.
Google is investigating, and I’m watching to see whether missing reviews are restored and whether affected Google Business Profiles can begin receiving new reviews again.
I’m tracking an important AMP update from Google Search: users who tap AMP results will now be sent directly to publisher-hosted AMP pages instead of cached AMP pages shown inside Google’s AMP viewer.
A Google spokesperson told Search Engine Land, “Starting today, we are updating how we connect users to AMP pages from Search, taking them directly to the AMP host pages.”
Google also made it clear that this is not a ranking change. AMP content will continue to rank like any other webpage, and Google said the serving and ranking of AMP content in Google Search and Google Discover will remain the same.
From my perspective, the practical value here is mostly on the publisher side. By sending searchers straight to the AMP host page, Google says publishers should have simpler analytics management and tracking, along with less maintenance work when creating and supporting AMP content.
Google told us it will continue to support the open-source AMPhtml format, and it also posted the update in its Search documentation.
I also think it’s worth noting how much AMP’s role has changed over time. AMP has not received preferential treatment in Google’s Top Stories for a while, and AMP pages are much less common to encounter than they once were. Search Engine Land even turned off AMP in 2021.
It has been a long time since I’ve had much reason to cover AMP closely, but this change matters because it shifts the user journey back to publisher-hosted pages while keeping AMP’s ranking treatment unchanged.
I can now use Google Trends to quickly add previous time period data to a chart, making it easier to see how search interest compares with the same length of time immediately before it.
Google announced the update on LinkedIn, saying that I can now compare how a trend has changed against preceding periods directly inside Google Trends.
What it looks like. Google shared a GIF showing the feature in action, with a comparison line added directly to the Trends chart for faster context.
How it works. I can go to Google Trends, enter a search term or topic, and then use the new chips that appear above the timeline. Those chips surface percentage changes across different periods, including month-over-month, week-over-week, and specific year-over-year comparisons.
With one click, I can overlay the historical comparison line onto the graph and immediately see whether interest is rising, falling, or following a familiar seasonal pattern.
Why I care. Google Trends is already a helpful source for spotting topics, keywords, and audience interest patterns. When I am planning content, SEO priorities, or marketing campaigns, being able to compare current demand against a previous period gives me a clearer read on timing and momentum.
This update gives me more historical perspective inside Google Trends, which can make trend analysis faster and more useful for content strategy and marketing planning.
I am seeing Google Search Console’s page indexing report running more than two weeks behind, with the latest visible timestamp still showing June 11, 2026. That means I cannot get a fresh view of page indexing data for the pages on my site right now.
When I check the Google Search Console page indexing report, I would expect to see that June 11 date instead of a more recent update. The delay is inconvenient, especially when I am trying to understand whether Google has recently found, crawled, or indexed important pages.
This report matters because it shows me which pages Google can find and index on a website. It also helps me spot indexing problems Google may have encountered while crawling the site.
I can access the report in Search Console over here, or I can open Search Console, go to the Indexing section, and then select Pages.
Inside the report, I usually see a chart with indexed pages in green and not indexed pages in gray. I can also overlay impressions on the chart, which makes it easier to connect indexing patterns with search visibility.
Below that chart, Google lists the reasons pages on the website are not being indexed. That section is often where I look first when I need to understand whether the issue is related to crawling, duplication, redirects, noindex signals, canonical choices, or another indexing reason.
For more details about how the page indexing report works, I can refer to Google’s help document.
Why I care: if I am trying to debug why Google has not indexed specific pages over the past couple of weeks, this delay leaves me with limited visibility. Until Google updates the report again, I would need to rely on my own SEO analysis or use the URL inspection tool to investigate indexing issues one page at a time.
The delay is frustrating, but I do not see it as especially uncommon. Search Console reports can lag from time to time, so for now I would treat the page indexing report as stale and avoid making major conclusions from that delayed data alone.
I’m noting that Google has confirmed its June 2026 spam update is now fully rolled out. The update started on Wednesday, June 24, around noon ET, and finished on June 26 at 2 p.m. ET.
Google’s official status update was brief and direct: “The rollout was complete as of June 26, 2026.”
What stands out to me is that this was the second Google spam update announced in 2026. It appeared to feel somewhat bigger than the March 2026 spam update, but as with most updates, if my site was not affected, I would treat that as a good sign for now.
That said, I always keep in mind that spam updates can sometimes affect sites that are not intentionally trying to spam Google. Hopefully, that is not the case for your site, but it is still worth watching traffic, rankings, and Search Console data closely after a rollout like this.
As for the type of update, Google originally described it as a normal spam update that would roll out across all languages and locations, with completion expected to take a few days.
If I wanted more context on how these updates work, I would review Google’s official documentation on spam updates in this Google help document.
What Google said. Google wrote, “Released the June 2026 spam update, which applies globally and to all languages. The rollout may take a few days to complete.”
Timing. I expect this update to move fairly quickly, since Google said the rollout may take only a few days to finish.
Why I care. Google releases search ranking updates several times each year, and spam updates are meant to target sites that use manipulative tactics to abuse the ranking system. If a site is not relying on those kinds of practices, I would not expect it to be the main target of this update.
More on spam updates. Google’s documentation explains that its automated systems are always working to detect search spam, but the company occasionally makes notable improvements to those systems and labels them as spam updates.
Google also points to SpamBrain, its AI-based spam-prevention system, as one example of how it improves its ability to identify spam and catch new types of abuse.
If I saw a ranking change after a spam update, my first step would be to review Google’s spam policies and make sure the site is complying with them. Sites that violate those policies may rank lower or disappear from results, while improvements can help over time if Google’s automated systems recognize that the site is now compliant.
For link spam updates specifically, Google says recovery can work differently. If Google removes the value of spammy links, any ranking benefit those links once created is lost, and that benefit cannot be regained simply by cleaning up the links later.
