Skip to main content
Learn how Maestra’s on-site JavaScript interacts with search engine crawlers, what Google sees on pages with Maestra installed, and how to keep your Core Web Vitals healthy. Maestra does not modify or replace the content that search engines index on your pages.

​
Before you begin

This article assumes Maestra’s SDK is already installed on your site. If you’re also looking for information on page speed impact, see How Maestra affects website loading speed?. For details on integration modes (injector, manual div, API), see Site Integration Modes.

​
How Maestra interacts with search crawlers

Maestra’s SDK loads asynchronously and does not alter your page’s HTML, headings, product descriptions, structured data, or internal links. Crawlers see your original page content exactly as your platform (Shopify, your CMS, etc.) serves it. Pop-ups and overlays. These are rendered client-side and triggered by visitor behavior (scroll depth, time on page, exit intent). Crawlers don’t replicate these behaviors, so pop-ups don’t appear during crawling. Your underlying content remains fully visible. Inline widgets and recommendations. These render client-side into designated containers. Google renders JavaScript and can see this content, but it is purely additive — Maestra adds content to your page, it does not replace or hide existing content.
Key distinction: Client-side rendering of individual widgets (a recommendation carousel, a promo banner, an embedded form) is not an SEO concern. What would be an SEO problem is rendering your entire product catalog or core page content client-side — because that makes your content dependent on JavaScript for crawlers to see it. Maestra does not do this. It adds localized personalization widgets to pages whose core content is served as HTML by your platform.
For sites where long-tail SEO is critical, Maestra’s API-only (headless) mode lets your team include personalization data in the initial HTML response — making it visible to crawlers without relying on client-side rendering. This requires more dev effort and is less common. For details, see Site Integration Modes.

​
Core Web Vitals and Maestra

Maestra’s impact on page speed can indirectly affect your Core Web Vitals scores, which Google uses as a ranking signal. Here’s how each metric is affected: For detailed best practices on minimizing speed impact, see How Maestra affects website loading speed?

​
Monitor your SEO-relevant metrics

Google Search Console → Core Web Vitals report. Shows which pages pass or fail based on real user experience data (CrUX). This is the same data Google uses for ranking decisions. PageSpeed Insights (pagespeed.web.dev). Enter your domain and check the “Discover what your real users are experiencing” section for 28-day field data. Google Search Console → URL Inspection Tool. Enter any URL to see how Google rendered it. Confirm your content is visible and Maestra’s widgets haven’t interfered with crawlable elements. Track trends over time. If Core Web Vitals scores change after modifying your Maestra configuration, investigate.

​
Quick reference