Google Analytics 4 and Search Console

2026-08-31User Manual

The Google Analytics 4 and Search Console module connects a Superlite website to Google Analytics 4 and allows you to verify the site in Google Search Console.

The module handles the required code automatically. You only need to enter the identifiers provided by Google.

You do not need to edit the theme or manually add tracking code to the generated HTML.

Installing the module

Open Modules in the Superlite administration interface.

Install the Google Analytics 4 and Search Console module and activate it.

Once activated, the module adds its configuration options to Superlite.

You can use Google Analytics 4, Google Search Console or both.

The two integrations are independent, so you do not need to configure both services.

Google Analytics 4

Google Analytics 4 can be used to measure traffic and visitor activity on the website.

To connect a Superlite website to Google Analytics 4, you need the Measurement ID from your Google Analytics property.

The Measurement ID normally looks like this:

G-XXXXXXXXXX

Do not enter the numeric property ID or another Google Analytics identifier.

Superlite needs the Measurement ID beginning with `G-`.

Finding your GA4 Measurement ID

Open Google Analytics and select the property you want to use.

Open the administration area and find the Data Streams section.

Select the Web data stream for your website.

The Measurement ID is shown in the stream information.

It begins with:

G-

Copy the complete Measurement ID.

For example:

G-ABC1234567

Return to Superlite and paste it into the Google Analytics 4 field in the module settings.

Save the settings.

Adding Google Analytics to the site

Once a valid Measurement ID has been saved, the module adds the required Google Analytics code when Superlite generates the public website.

You do not need to paste the full Google tracking script into the CMS.

Only enter the Measurement ID.

After saving the configuration, rebuild the site if Superlite does not do this automatically.

The generated public pages should then contain the Google Analytics integration.

Checking whether GA4 works

After configuring Google Analytics, open the public website in your browser.

Then open Google Analytics and go to the Realtime report.

Visit several pages on your website.

If the integration is working and tracking is permitted, your visit should normally appear in the realtime data.

There can be a short delay before data appears.

If nothing appears, first verify that the Measurement ID entered in Superlite is correct.

A common mistake is to copy another Google Analytics identifier instead of the Measurement ID beginning with `G-`.

Testing with Google Tag Assistant

Google Tag Assistant can be used to check whether the Google tag is loading on the website.

Open Tag Assistant and connect it to the public website.

Visit the site through the Tag Assistant debugging session.

If the integration is working, Tag Assistant should detect the Google tag associated with your Measurement ID.

This is useful when Google Analytics realtime data does not immediately show your visit.

Tag Assistant can confirm whether the tag itself is present and loading before you investigate the Analytics configuration further.

GA4 is not showing realtime traffic

If Google Analytics does not show your visit, check the configuration in this order.

First, confirm that the Measurement ID in Superlite begins with `G-` and matches the Web data stream for the correct website.

Then make sure the module is activated and the settings have been saved.

Rebuild the public site if necessary.

Open the public page source or use Tag Assistant to confirm that the Google tag is present.

If the site uses the Cookie Consent module, Analytics may also be blocked until consent has been given.

Browser extensions, tracking protection and ad blockers can also prevent your own visit from being recorded.

Google Analytics and Cookie Consent

If the Cookie Consent module is installed, it can control whether Google Analytics is allowed to collect data.

This means GA4 may be correctly installed without immediately sending analytics data when a visitor first opens the site.

The Cookie Consent module is designed to handle the relationship between visitor consent and Analytics.

Do not work around consent controls by adding the Google Analytics script manually to the theme.

Configure Analytics through this module so that the other Superlite modules can manage it correctly.

Removing Google Analytics

To stop using Google Analytics, remove the Measurement ID from the module settings or disable the Analytics integration where the module provides that option.

Save the settings and rebuild the site.

The Google Analytics code should then no longer be included in newly generated public pages.

You do not need to edit the theme manually.

Google Search Console

Google Search Console helps you verify ownership of a website and access information about how Google Search sees it.

The Superlite module supports verification using the HTML tag method.

Google provides a verification tag containing a unique value.

You enter that value in Superlite and the module places the required verification metadata in the generated website.

Adding a site to Search Console

Open Google Search Console and add your website as a property if it is not already present.

Choose a verification method that uses an HTML tag.

Google displays a meta tag similar to:

You do not need to paste the entire meta tag into Superlite unless the module interface specifically asks for it.

The important part is the verification value contained in the `content` attribute.

For example:

your-verification-code

Copy that value.

Adding the Search Console verification code

Open the Google Analytics 4 and Search Console module settings in Superlite.

Find the Search Console verification field.

Paste the verification value provided by Google.

Save the settings.

Superlite adds the required verification metadata when it generates the public website.

Rebuild the site if necessary so that the verification tag appears in the public HTML.

Verifying the site

Return to Google Search Console after saving the verification code in Superlite.

Choose Verify.

Google checks the public website for the verification tag.

If the value has been added correctly and the rebuilt page is publicly accessible, verification should succeed.

Keep the verification code in Superlite after the site has been verified.

Removing the verification tag later can cause Google to lose the ability to confirm ownership.

Search Console verification fails

If Google cannot verify the website, first check that the verification value was copied correctly.

Make sure you have not accidentally copied a value from another property.

Save the module settings and rebuild the site.

Then open the public homepage and confirm that you are checking the same domain or URL property that was added to Search Console.

If a cache is serving an older version of the page, clear it or wait until the rebuilt page is being served.

Try the verification again after confirming that the new public HTML is active.

Using GA4 and Search Console together

Google Analytics and Google Search Console serve different purposes.

Google Analytics measures activity on the website.

Google Search Console provides information about the site's presence in Google Search and verifies that you control the website.

You can configure either service independently or use both at the same time.

Each service uses its own identifier in the Superlite module.

Do not enter the Search Console verification value in the Analytics field or the GA4 Measurement ID in the Search Console field.

Updating the configuration

You can change the Measurement ID or Search Console verification value at any time.

Open the module settings, replace the existing value and save.

Rebuild the site if required.

The next generated version of the public website will use the new configuration.

After changing a GA4 Measurement ID, test the site again using Realtime or Google Tag Assistant to make sure traffic is being sent to the intended Analytics property.