Canonical Manager
A canonical URL tells search engines which URL is the preferred version when the same or very similar content can be reached through more than one URL.
- 1Keep the automatic canonical rule unless you have an intentional preferred URL.
- 2Open a product from a category or a filtered path and view its page source.
- 3Find
rel="canonical"; verify the URL returns the intended public page.
A single sensible canonical points to the preferred URL. It is a hint to search engines, not a forced redirect.
Remember: Check store domain and language before adding overrides. Frontend verification guide →
Recommended starting point
Let HuntBee generate normal canonicals automatically. Do not create custom canonical overrides unless you have a specific duplicate-content case and know which public URL should be treated as the primary version.
Simple example
A category might be reachable with extra sort/order parameters:
/catalog/laptops?sort=p.price&order=ASC
The preferred canonical may remain the clean category URL:
/catalog/laptops
This helps search engines understand that the sorted variant is not a separate important page.
What a canonical does — and does not do
| Canonical can | Canonical does not |
|---|---|
| Suggest a preferred URL among duplicates/near-duplicates. | Redirect the visitor. |
| Help consolidate duplicate URL signals. | Guarantee that search engines choose it. |
| Point variants back to a clean entity URL. | Replace a proper noindex rule for utility/search pages. |
Recommended setup
- Keep automatic self-canonicals for normal public pages.
- Let clean product/category/manufacturer/information URLs be their own canonical.
- Keep parameter/sort/filter handling consistent with Indexing Manager.
- Use custom override only when there is a deliberate preferred URL.
- Test a real storefront page source after changing canonical settings.
When is a custom override reasonable?
- A known duplicate page should explicitly point to another live primary page.
- A custom extension creates duplicate routes for the same content and you have chosen one public version.
- A migration temporarily leaves multiple accessible URLs and you need a controlled preferred signal.
Canonical and language/store URLs
The canonical must be built as a real public URL for the current store/language context. It should not mix domains or accidentally point a French page to an unrelated English URL merely because the entity ID is the same.
Canonical and pagination
Pagination strategy can depend on the page type and current search-engine guidance. HuntBee's built-in handling is designed to avoid blindly collapsing every useful paginated page into page 1. Keep the default behaviour unless you have a deliberate reason to change it.
Common mistakes
- Canonical every product to the category.
- Canonical every category page to the homepage.
- Point canonicals to URLs that redirect or return errors.
- Use a canonical to hide thin/private/utility pages instead of noindex.
- Mix store domains or language versions unintentionally.
Troubleshooting
- Canonical points to the wrong store: check store URL configuration and shared SEO URL/public resolver output.
- Canonical has query parameters unexpectedly: inspect the page type and current canonical policy.
- Search engine ignores the canonical: make sure internal links, sitemap, redirects and page content do not strongly contradict it.