Use cases / Traffic and performance
Traffic and performance
When traffic declines, Paz identifies the likely cause with Google Analytics and Search Console, checks whether the lost traffic was converting, and suggests changes to recover it.
Example: your landing page loses organic clicks
Organic clicks to your page fell 38% over two weeks but impressions held. The page still ranks; fewer shoppers choose it. Paz analyzes how your product appears against competitors, identifies what’s missing, and recommends changes to improve your chances of winning the click.
- Signal
- Search Console: clicks down 38% in two weeks, impressions flat, average position unchanged.
- Worth fixing?
- Orders from the page fell with the clicks, so the loss is converting traffic, not noise.
- Likely cause
- Competing results now show price, fabric and “with pockets” in the snippet. Your title and description don't mention these.
- Suggested changes
- Rewrite the page title and meta description to include linen, pockets and the price range, from information already in your catalog. Add the missing “material” attribute to the product record so Shopping results can show it too.
- Approval
- Both changes are drafted and waiting in your queue. Approve one or both, or edit before publishing.
- Next check
- Clicks and click-through rate on the same page, next run, against the two-week baseline.
When the cause is outside your control, such as seasonality or a change in how the search engine shows results, Paz says so and suggests where the traffic could be recovered instead.
Common questions
What data does the traffic use case use?
Google Analytics for sessions, channels and landing pages; Search Console for queries, impressions, clicks and position. Both are read only. If you connect a data warehouse such as BigQuery or Snowflake, Paz also reads orders and margin, so a drop in non-converting traffic is deprioritized.
What does Paz suggest when traffic drops?
Changes that address the likely cause: PDP titles and descriptions, missing attributes that affect Shopping results, or a product-data issue that removed a page from a channel. Where the cause is seasonality or a market change, Paz says so.
Can it run when something moves, not just weekly?
Yes. Routines run on a schedule or on a trigger, such as a change in a tracked signal or a catalog sync.
Test Paz on your store
See how Paz finds an issue, prepares a change and carries it through approval and publishing.
Other workflows: Product data and GMC · AI visibility