Catalogue URL and canonical audit
Identify which URLs represent distinct products and where filters repeat the same catalogue view.
Make the intended product pages discoverable and easier to use on mobile. GreyBath audits the route from a category link to the product specification, and tests how the site handles similar variants.
Explore what we build
01 / What we build
Identify which URLs represent distinct products and where filters repeat the same catalogue view.
Align category links and sitemap URLs with the pages intended to appear in search.
Measure representative product pages and identify heavy images, scripts and document links worth reviewing.
City context, honestly stated
For projects in Navi Mumbai, a supplier around Mahape may give a product several entry points by size, material and application. Review the generated URLs and the pages buyers can reach through a catalogue link. GreyBath delivers through remote workshops, reviews and handover.
A valve supplier exposes 18 filter combinations for one product family. Several URLs return the same product list, while the two variants buyers actually specify have their own technical pages. A crawl compares internal links, canonicals and sitemap entries. The pilot gives the distinct variants consistent links and leaves filter views usable for buyers. An old datasheet URL still has incoming links. The team checks that it resolves to the appropriate replacement, then compares mobile loading on the product page before and after changes. Search Console is used to observe indexing over time.
Where it fits
Bring the people who use, review and maintain the first release into the scope discussion.
Help buyers reach the current product page and datasheet with fewer hops.
Coordinate crawl evidence, development changes and follow-up observations on the same set of URLs.
How we work
Record response codes, canonicals, internal links and sitemap membership.
Verify the intended product pages still open, filter interactions work and retired URLs resolve correctly.
Measure mobile loading again and record Google’s observed indexing status separately.
The proposal sets the first workflow, delivery responsibilities and the evidence needed before rollout.
Discuss your projectChoose a category with duplicates and at least one genuinely distinct technical variant.
Provide public URLs and, if available, read access to Search Console or an exported report.
Give a separate page to a variant when it serves a distinct buyer need and the specifications justify its own URL.
A public crawl and performance baseline are possible. Search Console adds Google’s own indexing and query observations.
The site checks are available immediately after release. Search Console follow-ups record changes as Google recrawls and processes the URLs.
Start with one workflow