Advanced SEO

The Short Answer

Make sure those three things are always in sync: what the shopper sees on the page, what your product schema. What your feed says. Use one URL per product, with a canonical that doesn't change when the price or stock level changes. Keep your tags evergreen, avoiding sale text that can become stale. Then, of course, test it with a price change before a big sale.

Key takeaways

• The schema price and availability should be the same as what the end user sees and must update when that changes.

• A sale or a change in stock should never create a URL or affect the canonical.

• Use timeless language that does not change over time in your titles and descriptions. Do not use phrases like '50% off' or 'only 3 left'.

• On Magento, the usual offender is cached pages, which will have the old price and old markup.

On Magento, the problem is usually cached pages, which will show the old price and markup.

• Test one product completely before the sale starts or during the sale.

Picture a shopper who searches for a jacket. They see one price in Google. Then they land on your page and see a different one. They leave, and Google notices that kind of mismatch too. Google’s merchant listing guidance asks for prices. The currency and availability that reflect the page. During a sale, those values change often, and that is when the gaps appear.

This guide details how to keep schema, canonical tags and meta tags correct as prices and stock change. It uses MageDelight’s Advanced SEO Suite as an example and includes a pre‑sale checklist at the end.

What Goes Wrong When Prices and Stock Move

Stale prices show up in markup. Price drops are visible on sale pages. Price schema still displays the old price (usually because the page is cached).

Stale availability. It sells out quickly. The markup just says it's in stock. One developer guide says it clearly: if you can't generate availability in time, it's probably safer not to have it at all.

Expired sale dates. A sale has ended, but the markup can still have an end date in the past. Google's docs to that effect are quoted in one developer write-up as stating that a listing may not be displayed if the priceValidUntil property indicates a past date.

Feed and page are at odds. Your Merchant Centre feed states one price, and the page states a different price. An SEO article on Google's new rules refers to the outcome as lower-visibility listings, warnings, or a sale price that continues to display after the sale has ended.

Product Schema: Keep It Truthful

Product schema is the markup that tells Google what a page sells. The rule is simple: the schema must describe what a visitor can actually see.

Field

Rule

Common mistake

price and priceCurrency

Send the current selling price as a number, with its currency. Merchant listings need a price above zero

A zero or placeholder price while stock loads

Offer

Use an Offer. Google says merchant listings require one, and a price range as an AggregateOffer can rule a page out

A range on a configurable product

Was-price

Show the old price as a StrikethroughPrice inside a priceSpecification, with the active price as the main price

Using the old price as the main price

Sale dates

Use validFrom and validThrough on the price specification, or priceValidUntil on the Offer, and remove them when the sale ends

Leaving an old end date in the template

availability

InStock, OutOfStock, BackOrder or PreOrder, matching the page

InStock hard-coded into the theme

Ratings

Match the ratings and review count that shoppers can see

Markup for reviews the page does not show

Don't insert any implied claims. If the page doesn't say "only 3 left", then don't do the markup.

Canonical Tags: One Product, One URL

A sale should never create a new URL. Your canonical should remain unchanged through all price and stock variations and should always point to the clean product URL.

• Don't add sale or stock parameters such as ?sale=1 or ?instock=1 to indexable URLs. If you absolutely have to, canonicalise them back to the clean URL.

• Pick one category path. Magento can generate the same product URL in several different ways. The extension lets you select the shortest path, the longest path, or a URL without any categories for the canonical, and optionally a 301 redirect to it. Pick one and stick with it.

• Configurable products: have one canonical product, not one for each option.

• Out of stock for now: keep the page live with an OutOfStock status and a mechanism for us to be notified. A temporary stock out is not a reason to noindex or redirect.

• Gone for good: redirect via a 301 to the nearest real alternative, or return a 410 if no such alternative exists.

If your filtered category pages spawn many URLs, our navigation best practices guide explains the filter side of canonicals.

Advanced Layered Navigation also has its own canonical and robots settings for filtered pages.

Meta Tags: Keep Them Evergreen

Search results can show the old title/description for days. If your meta text says "Black Friday: 50% off" and the sale has actually finished, then the snippet is incorrect, and no one ever notices until someone complains.

• Describe the product, not the deal: name, key attributes, brand and a simple benefit.

• Leave out sale percentages, countdowns and stock counts.

• Use a template to generate titles and descriptions for your products and categories, so you're not manually editing thousands of pages. The extension will create them for you based on category patterns.

• Be careful with "Replace Existing Meta." The manual has this switch for category meta. If it is on, your carefully written text can be overwritten.

• Add the page number to the titles and descriptions on paginated pages so they remain unique.

A quick note on sitemaps: the extension lets you set change frequency and priority for products in the XML sitemap. Google has said it ignores those two fields, so don’t expect them to speed anything up.

The Magento Cache Gotcha

Here's the problem that most stores run into. Magento can, of course, schedule a special price with a start and end date. The pages are then cached for speed, and the cached HTML will contain the schema. If the page cache isn't refreshed when the price changes, both the customer and Google will see the old price and markup even though the database is correct. The same applies to stock changes.

Check three things: that your price and stock indexers run on schedule, that changing a price or stock status clears the cache for that page, and that your cache setup treats product pages correctly. A performance audit can review caching without impacting speed, and our Technical SEO audit can compare what Google sees with what the end user sees.

What the Advanced SEO Suite Covers

As per the user manual the extension provides canonical URL settings (enable, category path selection, 301 redirect to canonical), pagination settings, a 404 redirect to search, meta tag rules by category (title, description, keywords and H1 patterns), Google XML and HTML sitemaps and an SEO toolbar which will show page-level SEO details on the storefront for approved IP addresses.

For product rich data, we have manual listing, options to turn it on, the choice of short or long description, the option to show availability, the option to show ratings, and the choice of brand. There's also organisation, breadcrumb and category markup, an HTML sitemap (with the option to show out-of-stock items) and cross-linking rules.

It's compatible with Magento 2.4.7 to 2.4.9 on Open Source, Adobe Commerce and Adobe Commerce Cloud and is Hyvä-ready. First-year prices are $199 for Open Source, $399 for Adobe Commerce and $499 for Cloud, with $129 per year thereafter for updates and support. You can have a look at the storefront demo first.

Then open the admin demo to see where the settings live.

What the manual does not say, so ask or test

• Can the Product markup include a was-price (StrikethroughPrice) and sale dates?

• How availability maps to Back Order and Pre Order.

• Whether the markup uses an Offer or an AggregateOffer for configurable products.

• How the markup behaves when the full page cache is in use and when a special price begins or ends.

The manual covers the older settings so you'll want to check what your version actually has. MageDelight can be customised if you need sale dates or more detail in the markup.

A Seven-Step Pre-Sale Checklist

1. Pick three test products: one which has a scheduled sale, one which is low stock and one which is configurable.

2. View the page source and check the schema price and availability against what's displayed on the page.

3. Change the sale price and the stock for each test product. Reload and check that both the page and the schema have updated.

4. Test the page in Google's Rich Results Test and have a look at the Merchant listings report in Search Console for any warnings.

5. Compare the same products in your Merchant Centre feed. The price and availability should match the page.

6. Check that the canonicals are unchanged and that no sale or stock parameter creates a new indexable URL.

7. Review the meta templates for sale words and remove them.

If you use a product feed, MageDelight’s Product Feeds can help keep it in step with the page.

Quick Checks You Can Repeat

Check

You want to see

Where

Sale price on page vs schema

Same number and currency

Page source

Sell out a test item

OutOfStock in schema and a clear page message

Page source

End a test sale

Old price and dates disappear from markup

Page source

Open the product by two paths

Same canonical URL

Page source

Add a sale parameter to the URL

Canonical points to the clean URL

Page source

Search for the page title

No sale words that have expired

Search results

Merchant listings report

No new price or availability warnings

Search Console

Which Setup Fits Your Store?

Stores with heavy sales and thousands of products should automate: templates for meta, schema from live data and a daily check on a sample. For smaller stores, a weekly look at three products is enough. If you run frequent promotions, set your offers up carefully with Advanced Promotions, and plan bundles with our Black Friday bundle margin guide.

Price changes also affect your emails. Our guide to cart recovery emails for Black Friday looks at showing the live price.

Need hands-on help? MageDelight’s support team can review your markup and cache setup.

FAQ

Should I use a canonical tag for sale pages?

Yes, but not a new one. A sale doesn't create a new URL so the canonical remains pointing at the normal product URL before, during and after the sale.

How do I mark up a sale price?

Set the active price as the main price, and show the old price as a StrikethroughPrice inside a priceSpecification. Add sale dates only if you can keep them accurate and remove them when the sale ends.

What should schema say when a product is out of stock?

Use the OutOfStock availability value and keep the page live as long as the product is coming back. If it's gone for good, then redirect to a close replacement or return a 410.

Why does Google show the old price?

Common reasons are cached pages, an out-of-date feed or markup that simply never updates. Check the page against the schema and the feed for the same product.

Should I put sale offers in my meta title?

It's safer not to. Titles and descriptions can remain in search results after the sale ends, so it's worth keeping them evergreen.

Does the extension handle sale dates in schema?

The manual lists availability, rating, brand and description options for product markup, but it does not describe sale dates or a was-price. Ask MageDelight or test your version.