Send the click to the exact product, not the nearest page
Send shoppers to the exact product they clicked, with a page that shows the right photo, live price, description and add-to-cart action. If the product is missing, out of stock, or only sold in some locations, the destination needs a rule, not a guess, or you end up paying for clicks that cannot convert.
A lot of ad accounts fail on a small but expensive detail: the ad promise and the landing page drift apart. Google Shopping, Facebook catalogue ads and Instagram catalogue ads can all point at the wrong place if the product feed, URL structure and site rules are not tied together.
What was wrong before the product pages were fixed
The story here was a small online shop that wanted Google Shopping and its Facebook and Instagram catalogue to send shoppers straight to what they clicked. That sounds simple until the catalogue changes, products get renamed, stock moves, and old links keep circulating.
If the click lands on a category page, a generic collection, or a dead product, the shopper has to hunt. That is where conversion leaks out. It is also where tracking gets messy, because a click that should have gone to one SKU now bounces around the site before it can be attributed properly.
For businesses in Australia running paid traffic, the pain is usually not the ad platform. It is the handoff between feed, site and analytics. If that handoff is loose, you can keep spending on Google Shopping product pages, Instagram catalogue product pages and Facebook catalogue product pages without actually improving the path to purchase.
What the build needed to do
The fix was not a fancier homepage. It was a product page with live price and add-to-cart, one that could stand on its own as the destination for each click.
That meant each product had its own page with:
- a product photo
- live price
- description
- add-to-cart button
That sounds basic, but the details matter. The page needs to be the source of truth for the item the ad showed, not a cached version that disagrees with the feed, and not a page that only exists until the next catalogue update.
This is where custom software earns its keep. Off-the-shelf catalogue tools will often get you most of the way there, then leave you stuck when you need URL control, redirect rules, stock-aware routing, or a way to keep old shop links still work after a range change or site migration. That is the point where Custom Development stops being a nice-to-have and becomes the thing protecting revenue.
The practical rule is simple: one click, one product, one live page. If the ad shows a specific item, the destination should already know that item’s current URL, current price and current availability.
How the routing should behave when stock or location changes
Not every product should always land on the same page shape. If the product is out of stock, only available in some locations, or temporarily unavailable, you need to decide what the shopper should see before the click goes live.
A useful rule set looks like this:
-
In stock and available everywhere
Send the click to the exact product page. -
Out of stock, but returning soon
Keep the product page live, show the current status clearly, and if you have it, offer back-in-stock capture on that page. Do not send the shopper to a random substitute just to salvage the click. -
Only available in some locations
Route to the exact product page if the site can explain availability by location. If not, a category page usually creates more confusion than it solves. -
Discontinued or permanently removed
Use a redirect to the closest relevant replacement only if the replacement is genuinely the same intent. Otherwise, a category page or a curated alternative page is safer than a dead end.
That judgement call matters because ads are not all the same. Google Shopping is usually intent-heavy, so the shopper expects the exact item. Instagram and Facebook catalogue clicks are often more browse-led, but they still need to land on the item they saw, not a vague collection page that forces a second search.
Key takeaway: If the product is still sellable, keep the product page alive. If it is not, decide the fallback rule once, then apply it consistently across feeds, redirects and analytics.
How to keep old links working after a rename or migration
Old shop links still work was not a throwaway detail in this build. It is the part that keeps the whole thing from breaking every time the catalogue changes.
If you rename a product, change a range, or move to a new site structure, you need redirects that preserve intent. That usually means mapping the old product URL to the new one at the server or application layer, not relying on a manual spreadsheet of links that someone has to remember to update.
The safest pattern is:
- keep a stable product identifier behind the scenes
- generate the public URL from that identifier or a redirect map
- preserve old URLs with 301 redirects where the content has moved
- log 404s so you can catch stale ad destinations early
- test old campaign links after every catalogue or site change
That last point gets missed more often than it should. A campaign can keep spending for weeks against a broken destination if nobody checks the actual click path. The ad platform will still report clicks. The customer will just disappear.
If you have already lived through a migration, this is the bit that saves you from rebuilding campaigns every month. It is also why the URL strategy belongs in the software design, not as an afterthought in the marketing team’s notes.
One setup for Google, Facebook and Instagram, if the feed and site agree
You do not need a separate landing-page philosophy for each channel. You need one product source of truth, then channel-specific feed formatting on top of it.
The destination logic can be shared across Google Shopping, Facebook catalogue ads and Instagram catalogue ads if the underlying system knows:
- which product is current
- which URL is canonical
- whether the item is in stock
- whether the item is location-restricted
- which redirects apply after a rename or migration
That is the difference between a catalogue that scales and one that becomes a maintenance job. The channel feeds can differ in syntax, but the landing rule should not change just because the click came from Meta instead of Google.
For a business selling through multiple systems, this is the same kind of problem as keeping stock and orders aligned across channels. Our sell on Etsy and my website with one stock count piece covers the same principle from a stock angle, and the payoff is the same, fewer mismatches between what was advertised and what can actually be bought.
What to check before you change the destination rules
Before you change where ads land, check the things that usually get damaged in the shuffle.
- SEO: make sure canonical tags still point to the live product page, and that redirects are 301s, not temporary hops.
- Analytics: confirm your events still fire on the new destination, especially view item, add to cart and purchase.
- Conversion tracking: test the full path from click to checkout in GA4, Google Ads and Meta Pixel, not just the page load.
- Feed matching: confirm the product ID in the feed still matches the product on the site.
- Old links: click a sample of historical ad URLs after the change, not just the newest ones.
- Price consistency: check that the ad feed and the product page show the same current price, including GST where relevant.
If your site uses dynamic pricing or daily catalogue updates, this is where a custom build helps. You can keep the routing logic close to the catalogue data instead of bolting on patches every time the merchandising team changes a range.
For a broader systems view, Custom Development is the right lane when the ad destinations are only one part of a bigger commerce stack.
What this means for a live catalogue
The hard part is not sending a click to a page. It is keeping that page right when the catalogue changes daily and the product URLs do not stay still.
That is why the build in this story matters. Each product had its own page with live price and add-to-cart, and old shop links still worked. Those two things together mean you can keep campaigns running while the catalogue evolves, instead of pausing ads every time something is renamed or moved.
It also means you can answer a simple question with confidence: if a shopper clicks a specific item in Google Shopping, Facebook or Instagram, they land on that exact product, or on the fallback you chose for that product state. No guessing. No dead ends.
Common questions
How do I send ad clicks to the right product page?
Use a stable product source of truth, then route each ad click to the current canonical URL for that item. If the product is out of stock or restricted, apply a pre-decided fallback rule rather than sending people to a random substitute.
If my product changes name or URL, will old ad links still work?
They should, if you keep redirect rules in place. Use 301 redirects from the old product URL to the new one, and test historical campaign links after every rename, range update or site migration.
Do Google Shopping, Facebook and Instagram need different landing-page rules?
Usually no. One setup can handle all three if the feed, product IDs, canonical URLs and stock rules are aligned. The feed format changes by channel, but the destination logic should stay consistent.
What should happen if the product is out of stock?
Keep the product page live if the item is returning or can be back-ordered, and show the status clearly. If it is permanently gone, use a deliberate redirect or category page, not a dead link.
Keep the click path tied to the catalogue, then build the rules once
If your paid traffic is already sending people to the wrong page, fix the routing before you spend another dollar on scaling the campaign. Check the feed, the canonical URL, the redirect map and the tracking events together, because those four things usually fail together.
If the product page has become core commerce infrastructure rather than a simple web page, that is the point to have it designed and built as part of the system, not patched around it.




