Use the root HTML template for simple public React sites

For many React websites, the root HTML template is the simplest place to add a site-wide snippet.

This is often a good option when:

• The site is public and mostly marketing-oriented.
• You want Conscriba to load across the whole website.
• Your setup has a stable HTML template.
• You do not need route-specific logic.

Use the app shell or root layout for framework-managed apps

Some React setups use a root layout, app shell, or framework-specific document file.

This is common in frameworks such as Next.js, Remix, Gatsby, and similar React-based architectures.

Use this path when your framework provides a clear global script-loading area or layout-level integration point.

Use a dedicated script-loading component for more control

A dedicated component can be useful when you need more control over when Conscriba loads.

This can help if you need to account for:

• Consent state
• Production-only loading
• Route groups
• Feature flags
• User authentication state
• Script lifecycle behavior

React’s own documentation describes escape hatches as ways to connect to systems outside React, and recommends using these patterns carefully.

Use Google Tag Manager if your team already manages scripts there

If your React website already uses GTM, it may be the best installation path.

Use GTM when:

• Marketing or analytics teams own script deployment.
• You want GTM preview and publishing workflows.
• You already manage analytics, pixels, and conversion scripts in GTM.
• You want trigger-based control without a frontend deployment.

Use a framework-specific integration page when relevant

If your website uses Next.js, a dedicated Next.js implementation guide may be more precise than a general React guide.

React is the UI library. Frameworks such as Next.js or Remix can add their own routing, rendering, layouts, and script-loading conventions.

Ask a developer for route-specific or consent-aware loading

A developer-led setup is best when the app has complex routing, authenticated areas, payment flows, private dashboards, or strict security requirements.

Prioritize high-intent routes

AI agents are most useful when they can help users complete meaningful actions.

Good routes and page types for WebMCP discovery include:

• Homepage
• Product pages
• Pricing pages
• Search pages
• Catalog or listing pages
• Contact pages
• Demo booking pages
• Signup and onboarding pages
• Support or FAQ pages
• Documentation pages
• Account or dashboard flows, if relevant and safe
• Quote request or booking flows
• Checkout or ecommerce flows, if relevant and technically safe

The goal is not only to make routes visible. The goal is to expose useful actions that AI agents can understand and perform.

The snippet does not appear to load

Confirm that the snippet was added to the right template, layout, component, or tag manager container.

Then check the live production site, not only local development.

The snippet only loads in local development

Make sure the code path that loads Conscriba is included in your production build.

Also check environment variables, build flags, feature flags, and deployment configuration.

The snippet is added multiple times during route changes

In a React SPA, route changes may happen without a full page reload.

If the snippet is added from a component that remounts on navigation, it may be injected more than once. Move it to a stable app shell, root layout, or guarded script-loading component.

The snippet is placed in a component that unmounts

If the component responsible for loading the script unmounts too early, the snippet may not work reliably.

Use a stable global area or a component designed specifically for external script loading.

The intended route was not tested

Client-side routing can hide issues if you only test the initial landing route.

Test the route groups that matter for WebMCP discovery, such as pricing, search, catalog, contact, demo, support, and onboarding routes.

Lazy-loaded content or modals need testing

React apps often load content after user interaction.

If important actions live inside modals, tabs, lazy-loaded sections, or dynamic components, test those flows directly.

The snippet was added to the wrong environment or domain

Check whether the snippet was added to staging, preview, development, or production.

Conscriba should be active on the domain you want to scan and connect.

The app uses Google Tag Manager

If your React app already uses GTM, check whether the Conscriba snippet was added directly in React or inside GTM.

Avoid loading the same snippet twice unless there is a specific reason to do so.

Consent tools or privacy settings delay execution

Some consent tools block or delay scripts until the user gives permission.

Review your consent setup and make sure Conscriba loads according to your privacy and compliance requirements.

A Content Security Policy blocks the script

Strict CSP rules can block external scripts.

If this happens, your technical team may need to allow the relevant Conscriba script source.

Build optimization affects execution

Bundler settings, script loading strategies, minification, deferring, and lazy loading can affect third-party scripts.

If the snippet does not behave as expected, test with a simpler loading path and then reintroduce optimizations carefully.

Authenticated or private routes need careful review

Account areas, payment flows, personal data, admin dashboards, and private workflows should not be treated like public pages.

Review what should and should not be exposed to AI agents before enabling tool candidates in those areas.

The snippet is installed, but no AI scan has been run

Installing the snippet is only the first step.

Return to Conscriba and run or schedule an AI scan to discover WebMCP tool opportunities.