Should you abandon onclick to avoid being penalized for cloaking?

What does Google really mean by 'consistent content'?

Martin Splitt's statement sets a clear framework: a link with href and onclick that prevents traditional navigation is not cloaking if the displayed content meets user expectations. The determining criterion is not the technical method used, but the consistency between what the link promises and what is then displayed.

Specifically, if your link says 'See customer reviews' and the onclick displays a modal with reviews, that's acceptable. If the same link displays an ad or unrelated content, you cross the red line into cloaking. Google still considers the element a valid link for crawling, even if the JavaScript interaction alters the browser's default behavior.

Why this clarification now?

Modern JavaScript frameworks — React, Vue, Angular — heavily rely on client-side routers that intercept link clicks to avoid a full page reload. This approach enhances user experience and performance, but has long caused doubts among SEOs: Will Google consider these links valid?

Splitt's response clears up this ambiguity. Google does not penalize the use of onclick to enhance user experience, as long as the href remains present and the displayed content stays relevant. This represents an official validation of widely used practices in modern web development.

What distinguishes this approach from traditional cloaking?

Traditional cloaking involves serving different content to bots and users, often to manipulate rankings. Here, the content remains the same for Googlebot and the user — only the display method changes. The href remains accessible for crawling, and onclick only alters the navigation mechanics.

The nuance is critical: Google crawls the href, not the onclick event. If your link points to /page-a in the href, but onclick displays content from /page-b, you create an inconsistency. In this case, you risk being perceived as misleading, even without malicious intent.

• A link with href + onclick remains a valid link for Googlebot, provided the displayed content matches expectations.
• The consistency criterion outweighs the technical method: what matters is that the user receives what the link promises.
• Google crawls the href, not the onclick — any divergence between the two creates a risk of confusion.
• This clarification validates the practices of modern JavaScript frameworks that rely on client-side routers.
• The absence of href or an onclick that displays irrelevant content remains problematic and may be interpreted as cloaking.

Is this statement consistent with observed practices on the ground?

Yes, overall. Sites using modern JavaScript frameworks with client-side routing generally do not suffer cloaking penalties, as long as the content remains accessible and consistent. Field tests show that Googlebot correctly indexes these pages, even with complex JavaScript interactions.

The nuance lies in the quality of the implementation. Sites that only render content accessible via JavaScript, without serving a basic HTML version, are taking a risk. Googlebot can execute JavaScript, but it doesn't always do so exhaustively — especially if the crawl budget is limited or if the JavaScript is poorly structured.

What gray areas remain in this statement?

Splitt refers to 'content that meets expectations', but Google does not precisely define this criterion. What constitutes a legitimate 'expectation'? If a link says 'Learn more' and opens a modal with 50% relevant content and 50% ads, is that acceptable? [To be verified] — this gray area leaves room for interpretation.

Another vague point: how does Google assess the consistency between the href and the content displayed via onclick? If the href points to a complete page and onclick only displays a snippet of that page in a modal, does Google consider that coherent? The statement does not provide a precise technical answer, leaving practitioners in the dark.

In what cases might this rule not apply?

If your onclick loads dynamic content that does not exist in the href, you create a dissonance that Googlebot may interpret as misleading. For example, a link to /product-a that, via onclick, displays the features of /product-b in a modal: technically, the displayed content does not match the crawled href.

Sites that abuse modals to conceal strategic content behind onclick without a valid href remain exposed. Google can crawl the link, but if the displayed content is not accessible via the href, it may not be indexed — or worse, be viewed as an attempt to manipulate. Let's be honest: just because Splitt says it's not cloaking doesn't mean Google will index everything you display via JavaScript.

What should you do concretely to stay compliant?

Keep a valid and relevant href on all your links, even those that trigger JavaScript interactions. The href should point to a real URL that displays the promised content. If your onclick prevents default navigation, ensure the displayed content on the current page corresponds to what the user would have received by following the href.

Test your pages with Googlebot Fetch and Render or tools like Screaming Frog in JavaScript mode to verify that the content is accessible and consistent. If Googlebot crawls the href and onclick displays something else, you risk being perceived as inconsistent — even without malicious intent.

What mistakes should be absolutely avoided?

Never create a link with a blank href, anchored (#), or javascript:void(0) if you are relying solely on onclick to display content. Without a valid href, Google cannot crawl the destination, and you lose any SEO benefit from that link. The 'ghost link' is a classic mistake among JavaScript developers.

Avoid also loading different content via onclick compared to what the href promises. If your link says 'See technical specifications' and onclick displays a promotional video, you create an inconsistency. Google may not penalize you for cloaking, but you risk losing relevance and user trust.

How to check if your site is compliant?

Audit your links with onclick to ensure that each href points to a real and indexable URL. Use Search Console to identify crawl errors or pages indexed with unexpected content. If Googlebot encounters inconsistencies, you will see signals in coverage or indexing reports.

Also test the user experience: disable JavaScript in your browser and check that links remain functional. If your site becomes unusable without JavaScript, you create a risky dependency — and make it more difficult for Googlebot, which may not always execute your code correctly.

• Every link with onclick must have a valid href pointing to a real URL.
• The content displayed via onclick must match the expectations created by the href.
• Test your pages with Googlebot Fetch and Render to check the consistency of crawled and displayed content.
• Avoid empty hrefs, anchored (#), or javascript:void(0) — Google cannot crawl these destinations.
• Regularly audit your links with onclick to detect inconsistencies between href and displayed content.
• Ensure your site remains functional with JavaScript disabled to guarantee accessibility for Googlebot.