SEO FranciscoFrancisco Leon de ViveroToronto · Montréal
⌕ESBook a 30-min consultationBook a 30-min call
SEO news and events News Archived

SEO News: June and July 2020

Read this as a historical 2020 recap published in 2022. Confirmed announcements are separated from unverified volatility claims, and old feature descriptions do not establish current availability.

Updated November 16, 2026 Francisco Leon de Vivero
SEO News: June and July 2020

Archived article

This post was originally published in December 15, 2022 and has not been updated.

It is preserved here for historical reference. Some tools, recommendations, algorithm details, and links may be outdated or no longer accurate. For current guidance, see Francisco's up-to-date service pages or book a focused consultation.

This historical recap preserves the June and July 2020 topic and the original 2022 publication date. It should be read as a record of the period, with corrected event labels and a distinction between historical announcements and current product availability.

Search Console Insights in historical context

The original coverage discussed the beta of Search Console Insights and the attempt to connect search discovery with content engagement. Google's August 2020 beta announcement supplies a dated primary reference. It should not be presented as a confirmed June or July launch.

The useful distinction in that reporting was between how readers discover content and what happens after arrival. Search Console and Analytics measure different events. Combining their data can provide context, but a dashboard integration does not prove that engagement metrics became ranking factors.

Products and reports have changed since that beta. Preserve the historical feature discussion without instructing a present-day reader to enable controls from an old interface. Check current documentation before applying a procedure today.

Algorithm movement and confirmed update names

The prior recap called June 23, 2020 a confirmed core update and described a correction on June 27 and 28. That precise claim lacks a verified primary announcement in the record used here. It should not become an official update name or a causal explanation for smaller publishers gaining traffic.

Google's May 2020 core update announcement provides a confirmed historical event. Observed ranking volatility in another week needs its own dataset, dates and qualification. Keep an observation distinct from a provider-confirmed rollout.

Comments and indexable page content

The older report also described more consistent Disqus indexing around June 20. Without a reproducible observation or primary announcement for that date, treat it as unverified historical coverage. Do not infer a universal change to how Google handled every comment system.

The durable operational question is whether useful discussion is accessible as part of the page. Moderate spam and abusive material, inspect rendering, and avoid relying on comments to supply missing article evidence. A provider name cannot establish that the discussion was indexed or improved the page's ranking.

Structured data and image fact checks

Adding Person or Article markup cannot make an unsupported claim true or establish an author's expertise. The general structured-data policies require accurate representation of visible content. Use that distinction when evaluating the historical authority claims.

Google's June 2020 image fact-check announcement described labels for qualifying fact-check content in Images. The ClaimReview vocabulary describes a review of a claim. It was not a general instruction to mark every chart, case study or brand image as a fact check.

Preserve the historical announcement without promising current eligibility. A genuine editorial review needs a specific claim, evidence and verdict. Present availability and search requirements require a current documentation check before implementation.

Googlebot geography and internal links

The earlier recap mentioned crawler requests outside the US. Verify crawler identity with Google's published verification guidance, rather than trusting a user agent or treating an unfamiliar country as proof of an attack. The historical note does not supply a current geographic traffic distribution.

Internal links remain a practical architectural review. The SEO Starter Guide explains discovery and descriptive links. Audit orphan pages, redirects, generic anchors and priority pages buried in navigation. Check rendered links, including language equivalents, rather than accepting a crawl total as proof that users can navigate the site.

Using the archive responsibly

Keep the event date, original publication date and later substantive review separate. Verify a dated primary announcement before reusing a historical feature claim. If the product changed, describe the old state as historical rather than silently relabeling it as current advice.

This archive is useful for measurement boundaries, accurate markup and internal architecture. It cannot establish a new 2026 update or a strategy from an unverified 2020 volatility report.

Historical measurement and implementation lessons

The Insights beta discussion was about connecting discovery and engagement records. A page could attract search visits while failing to keep readers interested, or attract useful readers from another channel. Keeping those questions separate was more informative than calling every increase in traffic a content-quality result. The dated beta announcement belongs to August 2020, even when discussed alongside the June and July archive.

The structured-data lesson was equally bounded. Markup described a person, article or genuine claim review. It did not supply the missing evidence for expertise or a verdict. A fact-check label concerned qualifying fact-check material, not a general badge for every image. Keep the claim, supporting evidence and verdict connected when interpreting that historical feature.

Crawler geography required identity verification before interpretation. An unfamiliar request location or recognizable user-agent string alone did not prove either legitimate Googlebot or hostile activity. Preserve the request evidence and verification result rather than deriving a search strategy from an unverified count.

Internal-link work was a concrete architectural task: identify orphaned useful pages, repair relevant broken links and replace vague anchors with descriptions that explain the destination. A larger crawl total did not prove that readers could reach the right page. The lasting value of this archive is those measurement and implementation distinctions, with the event chronology kept accurate.

Frequently Asked Questions

Did Search Console Insights make engagement a ranking factor?

The historical beta connected discovery and engagement data. That integration did not establish that the engagement measures became ranking factors.

Was ClaimReview intended for every editorial image?

No. The historical announcement concerned qualifying fact-check content. A genuine claim review needs the claim, evidence and verdict. Ordinary charts or brand images do not establish that context.

Was June 23 established here as an official core update?

No. The precise claim lacks a verified primary announcement in this review and is not retained as an official event.

Does the review change the original publication date?

No. The original 2022 publication date remains, alongside the date of the substantive correction.

Related Articles

About the Author

Francisco Leon de Vivero at an industry conference

About the author

Francisco Leon de Vivero

Francisco Leon de Vivero is a senior SEO strategist and VP of Growth at Growing Search, with 15+ years of enterprise search experience. He previously served as Global SEO Lead (Corporate SEO) at Shopify from 2015 to 2022 and focuses on technical SEO, international search strategy, and platform optimization.

Next step

Check the original announcement before reusing the archive

Preserve the historical date and verify present availability separately before applying an old procedure.

Current service page

Technical SEO Advisory

The goal is not audit sprawl. It is translating complex technical issues into prioritized actions that development and marketing teams can actually execute.

Explore this service

Search SEO Francisco

Use the arrow keys to move through results. Press Enter to open a result and Escape to close search.

Your resource list 0

Collect useful pages while you browse. Enable saving to keep this list in this browser between visits.

    This list contains page titles and links. Clearing it removes the saved copy for this feature.