Datapipe
Start free

Ecommerce · USE CASE

Find search opportunities you can actually support.

Combine Search Console demand, GA4 engagement and Shopify stock before deciding which product pages to promote or improve.

Search ConsoleGoogle AnalyticsShopify
Try it with your data Free with up to 3 data sources · No credit card
A WORKED EXAMPLE

Which product pages deserve more search attention?

Product pageSearch clicksProduct stock
Desk organizer1803
Everyday tote9080

Search/GA4 Oct 5–Nov 1 · Current Shopify stock Nov 8

Check organizer availability before sending it more traffic. The tote is the stronger candidate for a page review with stock on hand.

EXAMPLE WORKFLOW

Ask. Follow up.
Take the next step.

✦ AI assistantSample workflow
Search ConsoleGoogle AnalyticsShopify
YOU

  1. 01
    /products/desk-organizer · 3 sourcesStock check first

    Next

  2. 02
    /products/everyday-tote · 3 sourcesContent review

    Next

Search/GA4 Oct 5–Nov 1 · Current Shopify stock Nov 81 / 3

01 · CONNECT YOUR DATA

Your tools. One place to ask.

3 of 3 Free data sources
No credit card · Daily refresh

Search ConsoleGoogle AnalyticsShopify
DatapipeYour project
Your AI assistantor a report in Sheets / Data Studio
  1. Create your free workspace

    Sign up with your company email. Your first project opens on Data sources.

  2. Add the data sources

    Choose the accounts for this workflow. Authorize access and select the property or site.

  3. Bring your question

    Connect your project to a supported AI assistant, or build your source reports.

Create a free account →
Setup steps & what you need

Email/password signups confirm their email first. Use Google signup with a company account if you prefer.

  • Search Console: Authorize Search Console with Google and select the property you can access. Setup guide ↗
  • Google Analytics: Authorize Google Analytics and select the GA4 property for the same website. Setup guide ↗
  • Shopify: Enter your shop, authorize it, and add that store to the project. Setup guide ↗

Free includes 3 data sources across the workspace. One account/property added to one project counts as one. Extra properties or the same account in another project use another slot.

02 · ASK A USEFUL QUESTION

Start with a prompt.
Follow the evidence.

Copy these in order into your connected assistant.
Each builds on the answer before it.

01

Find product pages with search visibility

Read the full prompt
Use only this Datapipe project’s authorized data. Discover the connected accounts, datasets and compatible fields first. Confirm dates, timezones, currencies and data coverage. Keep missing or unmatched rows visible; never substitute sample data. Compare the sources explicitly and explain every match. Do not change source records or send messages.

Read Search Console page clicks/impressions and GA4 organic landing-page sessions/engaged sessions for matching complete dates. Shortlist product pages with meaningful search visibility. Keep the page grain and report timezones explicit; do not duplicate page sessions across query rows.
02

Follow up across your data sources

Read the full prompt
Use only this Datapipe project’s authorized data sources. Discover the connected accounts, datasets, and fields first. If the right account or required data is missing, ask me rather than substituting sample data. Show the actual dates, filters, coverage, and any partial results.

Check the tote page and its search queries. Suggest a better product title. Read the actual current records behind the shortlist. Show which source supports each observation, distinguish causes from hypotheses, and propose one specific next step.
03

Put the change into practice

Read the full prompt
Update the tote’s SEO title. Use real returned records and verified current values, not the example identifiers or wording. Show the exact proposed change. Prepare the supported action for review in Datapipe; after approval there, apply only the approved change and re-read the source record to verify it. If configured write access or a field is missing, explain what is needed instead of claiming success.
Need to connect your assistant?Claude guide ↗ChatGPT guide ↗

03 · USE WHAT YOU FIND

Separate the stock check from the content brief.

  1. 01

    Read search and engagement at page grain.

  2. 02

    Map the pages to Shopify products.

  3. 03

    Separate the stock check from the content brief.

Check the result at your next review.

At the next review, check current stock again and compare the same page-level search and engagement measures. Track page changes separately from stock movements.

Implementation tips for this use case

Use current stock as operational context, then verify variants and locations. Decide which available product page deserves a query and content review. Do not turn historical clicks into a demand forecast.

WHEN YOU NEED MORE CONTEXT

Go a little deeper.

The method and reporting checks
behind this example.

How to prioritize product pages with search and stock context

  1. Read search and engagement at page grain.

    Use page-level Search Console clicks/impressions and GA4 organic landing-page sessions/engaged sessions for the same complete window. Keep query details in a separate investigation.

  2. Map the pages to Shopify products.

    Read current Shopify product handles, titles and total inventory. Confirm the storefront URL mapping to each handle; custom routes, redirects and markets can change it. Keep unmatched products separate.

  3. Separate the stock check from the content brief.

    Use current stock as operational context, then verify variants and locations. Decide which available product page deserves a query and content review. Do not turn historical clicks into a demand forecast.

See the complete example report
EXAMPLE REPORTFictional sample data

Which product pages deserve more search attention?

Search/GA4 Oct 5–Nov 1 · Current Shopify stock Nov 8

Which product pages deserve more search attention? · fictional sample data
Product pageSearch clicksProduct stock
Desk organizer1803
Everyday tote9080
WHAT TO LOOK ATCheck organizer availability before sending it more traffic. The tote is the stronger candidate for a page review with stock on hand.

Separate the stock check from the content brief.

Illustrative report output · no live query or source change

Search Console shows 12,000 impressions and 180 clicks. GA4 shows 168 organic landing sessions, 96 engaged. Shopify currently reports only 3 units at product level. The page has 9,000 search impressions, 90 clicks and 86 organic landing sessions, 40 engaged. Current Shopify product inventory is 80.

Try the example with sample CSVs

Fictional rows matching the example above. Attach these files to your assistant for a sample analysis.

Data method, reporting checks & sources

Use page-level Search Console clicks/impressions and GA4 organic landing-page sessions/engaged sessions for the same complete window. Keep query details in a separate investigation. Read current Shopify product handles, titles and total inventory. Confirm the storefront URL mapping to each handle; custom routes, redirects and markets can change it. Keep unmatched products separate. Use current stock as operational context, then verify variants and locations. Decide which available product page deserves a query and content review. Do not turn historical clicks into a demand forecast.

Storefront URLs are deliberately matched to Shopify handles. Page sessions are not repeated across query rows. Product totals are verified at variant/location level before promotion.

  • Storefront URLs are deliberately matched to Shopify handles.
  • Page sessions are not repeated across query rows.
  • Product totals are verified at variant/location level before promotion.
  • Access to the intended Search Console account or property.
  • Access to the intended Google Analytics account or property.
  • Access to the intended Shopify account or property.
  • Storefront URLs are deliberately matched to Shopify handles.

For blended reports, align dates, normalized URLs, and reporting grain. Query-level search rows must not duplicate page-level sessions. This is an illustrative workflow; live accounts and destinations need their own setup.

Search Console performance metrics ↗Shopify inventory states ↗Report starting points ↗

A FEW USEFUL ANSWERS

Before you start.

Does product inventory tell me how long stock will last?

No. It is current availability context. A forecast needs sales velocity, lead times, location/variant detail and an explicit forecasting method.

Are Search Console clicks the same as GA4 sessions?

No. They measure different activity. Use them side by side with aligned dates and page matching rather than expecting identical totals.

YOUR NEXT STEP

Try it with your own data.

Start free with up to 3 data sources. No credit card.

Start free →