Link Search Console to GA4, and write a one-page measurement plan before you build anything

Linking Search Console to a web stream

The link connects a Search Console website property to a GA4 web data stream. Google says you need the Editor role on the property and verified ownership of the Search Console property, which can be completed during linking. In Admin, open Product links, then Search Console Links, choose Link, pick the account and then the web stream, and confirm.

Check three limits first. A stream links to one Search Console property and vice versa. You cannot edit a link; to change it you delete it and create another. And Google advises making sure both properties collect data for the same set of pages, so check that the Search Console property and the stream describe the same site.

• Confirm the Search Console property matches the stream's site exactly.
• Note who holds verified ownership; the link fails without it.

What you get, and when

The linked data appears in Analytics 48 hours after Search Console collects it, and reports cover at most 16 months, matching Search Console. Google describes two reports: Google Organic Search Queries, with Search Console metrics, and Google Organic Search Traffic, which shows landing pages with both Search Console and Analytics metrics. The Search Console report collection is unpublished by default, so publish it in the Library.

Do not judge the link on the day you create it. Check that the collection is published, then check the report after the delay Google states.

• Publish the collection from Library, not only the link.
• Search Console metrics work only with Search Console dimensions plus landing page, device and country.

A one-page measurement plan

Before adding events, write one row per business question. Each row has the question, the event that answers it, whether it is a key event, the test action that produces it, the parameters it carries, and the person who uses the answer. A standard property can hold up to 30 key events, and marking applies only from the time of marking, so plan the short list before you start.

The plan is also the test book. If a row has no test action you can perform on the site, the event cannot be proved and should not be built yet. Keep names lowercase and consistent, and keep personal data out of every parameter.

• Start with the five actions that matter most to the business.
• Rows with no test action stay on a "later" list.

What does not fit, and how the paid outcome is accepted

A plan does not guarantee rankings, traffic or sales, and linking does not change search performance. If one event is simply broken, a single repair is cheaper than a rebuild.

The project Rebuild a site's measurement starts from £4,500 as an untested proposal, quoted after the site and event list are seen, with payment as the proposal sets it. It includes the plan, a data layer specification, a cleaned container, the agreed events with named tests, and the Search Console link. Acceptance: every plan event passes its test in DebugView, the link exists with the collection published, and the report loads after the stated delay. Send the site address and your five key actions; no logins.