Your price changed at nine this morning. Your markup didn't.
Almost every other ecommerce category sets a price and leaves it there for a season. Jewellery doesn't. The rate moves daily, sometimes sharply, and the displayed price of every gold product on your site is a calculation, not a stored value: metal weight times the day's rate, plus making charges, plus wastage where you charge it, plus stone value, plus GST.
Three of those four inputs move. When the front end recalculates and the structured data doesn't, you end up publishing two different prices on the same page — one for the shopper and an older one for the crawler. Google notices. A price mismatch between your markup and your page is a routine reason for product rich results to be dropped, and if you feed a shopping surface, it's a routine reason for items to be disapproved.
This is fixable, and it's usually a deployment problem rather than an SEO problem. But it has to be fixed first, because a rich result showing yesterday's price on today's page costs you the click and the trust in one go.
Product schema when the price is a formula
You have three honest options, and the right one depends on how fast your build pipeline can move. Pick deliberately — the failure mode is picking none and letting the platform default decide.
- Publish making charges as text, per gram or as a percentage. It's the single most searched-for thing about a jeweller and the thing most sites hide until checkout.
- `aggregateRating` only from reviews you actually collected. Borrowed or invented ratings are covered by Google's structured data spam policies, and a manual action strips rich results across the whole domain.
- Don't mark up a discount that isn't real. Inflated strike-through pricing on gold is easy to disprove — the metal rate is public.
| Approach | When it fits | The trade |
|---|---|---|
| Exact price, regenerated with the rate | Server-rendered pricing, rate updates that redeploy or revalidate markup in the same step | Best result. Requires the rate feed and the page cache to be genuinely coupled. |
priceSpecification with a short priceValidUntil | Rates that update once daily at a known time | Honest and durable. Set the validity to the end of the rate day, not a year out. |
| Price range on the product, exact price only in the cart | Made-to-order, custom weight, high-value bridal sets | You lose the price rich result. You keep your credibility, which is worth more than the snippet. |
The gold rate page: a real asset, or a daily liability
gold rate today in Chennai, 22 carat gold price Hyderabad, silver rate today — this is enormous, repeating, daily demand, and it's one of the few genuinely evergreen traffic sources in the category. It's also the fastest way to look unreliable in public.
Rates differ by city, which is why the city-level pages exist at all. Build them only where you actually have a rate you can stand behind, and only where you have a reason to be found — the cities you sell in, not all 200 you could generate. A rate page for a city where you have no showroom and no feed is scaled content with no upside.
Structure them as one permanent URL per city and purity combination, updated automatically from your feed, with a visible timestamp. Add the seven-day and thirty-day movement, the current making-charge range, and a clear line explaining what the rate does and doesn't include. That last part is what stops it being a commodity page indistinguishable from forty others.
- One URL per city, refreshed daily. Never a dated URL.
/gold-rate-chennaiforever, not/gold-rate-chennai-26-july-2026. - Show the timestamp and the source. A page that says 'updated 09:30 today' outperforms one that just asserts a number.
- Link the rate page to the products it prices. Traffic that lands on a rate page and leaves is a vanity metric; traffic that lands and clicks into a collection is a channel.
- Automate it or don't publish it. If updating means someone editing a CMS field each morning, it will be wrong by the second week of the second month.
Two demand cycles, and the lead time nobody plans for
Jewellery demand in India isn't a smooth line. It's festive — Akshaya Tritiya, Dhanteras and Diwali, plus regional peaks around Onam, Pongal and Durga Puja — and it's bridal, following wedding muhurat seasons that shift each year and differ by region.
The mistake is treating these as campaigns. A page published two weeks before Dhanteras is competing against pages that have held that URL for four years. Ranking for a seasonal peak takes lead time; six to ten weeks is a reasonable planning assumption for a page that already has some authority behind it, and considerably longer for a new one.
So keep one permanent URL per occasion and refresh it annually. The page accumulates links and history instead of resetting every year, and you spend the six weeks before the festival improving it rather than getting it indexed.
Bridal is the higher-value cluster and the more forgiving one, because the research window is months long. Bridal buyers search sets, budgets and specifics — bridal necklace set under 2 lakh, temple jewellery for South Indian wedding, light weight bridal set — which is a content problem more than a rate problem, and one where a jeweller who explains the trade-offs honestly beats a marketplace grid.
Hallmarking, HUID and the trust content that actually converts
Buying gold from a website you don't recognise is an act of faith, and the objections are always the same: is it genuinely the purity claimed, what happens when I want to exchange it, and who do I go to if something is wrong. Answering those in public is both trust content and search content — people search these questions directly.
Hallmarking gives you concrete material to work with. BIS hallmarking of gold jewellery is mandatory across notified districts in India, and hallmarked pieces carry a six-digit alphanumeric HUID that a buyer can check themselves. Explaining what the mark contains, how to verify it, and what your own buy-back and exchange terms are does more for conversion than another product carousel.
This is also the E-E-A-T argument in a category where it genuinely matters. Put your BIS registration details, showroom addresses, certification partners and exchange policy where both a buyer and a crawler can find them, and write the purity explainers under a named person rather than 'admin'.
Multi-store jewellers: one profile per showroom, not one per brand
Jewellery is still overwhelmingly bought in person for anything above a certain ticket size, which makes the map pack the highest-value surface most jewellers under-work. jewellery shop near me, gold showroom in <locality>, bridal jewellery <city> are all local-pack queries first and organic queries second.
Each showroom needs its own Google Business Profile and its own store page — address, hours, the collections carried there, photographs of that showroom, the staff who run it, and a reviews stream of its own. A single store locator listing eleven branches ranks in none of their neighbourhoods.
That store page is also where the online and offline halves of the business connect. Show the stock or collection available at that branch, offer an appointment for bridal consultations, and give a phone number that reaches that showroom rather than a central call centre. The local SEO mechanics are the same as any multi-location retailer; the ticket size just makes them worth more.