Search-engine discovery

XML Sitemap

The XML Sitemap gives search engines a clean machine-readable list of important public store URLs. It helps discovery; it does not force ranking.

Try it on your storeThree steps to check this feature
  1. 1Choose the correct store and review which catalog URL groups should be included.
  2. 2Copy its public sitemap URL from the component; open it in a browser.
  3. 3Confirm XML is displayed, test a few product/category URLs and submit the sitemap URL to Search Console.
What confirms it works

The sitemap responds successfully with real public URLs for the correct store. Submission does not guarantee indexing.

Remember: A sitemap must use the correct domain and should not publish disabled/private URLs. Frontend verification guide →

RecommendedStore-specific output

Recommended setup

  • Keep XML Sitemap enabled.
  • Use the selected store's sitemap_index.xml URL.
  • Keep caching enabled/default unless you have a specific freshness requirement.
  • Include normal active products, categories, manufacturers and public information/CMS content.
  • Add Custom URLs only for real public pages not already covered.

Why is the Store selector needed?

Each OpenCart store can have a different domain, assigned products and language setup. The sitemap must therefore be generated for the selected store. Moving the selector to the panel heading is only a UI change; its store scope is important.

Which URL should I submit?

Submit the store's sitemap index, normally:

https://your-store.example/sitemap_index.xml

The index points to the smaller child sitemaps HuntBee creates for languages/content types/pages. This scales better than putting a very large catalog into one XML file.

Clean sitemap URLs and .htaccess

OpenCart's default Apache rules can send unknown .xml paths to the wrong place unless a rewrite exists. HuntBee installs a small managed sitemap block so clean public paths work, including the sitemap index and child sitemap patterns.

Before the first managed modification, HuntBee creates a backup of the existing .htaccess.

If you updated the component and clean sitemap URLs still return 404/Forbidden: run SEO Suite Update/Repair once so the current routing event and rewrite block are installed.

What do Purge Cache and Rebuild do?

Purge CacheDeletes generated sitemap cache files so the next request/build uses fresh data.
RebuildRegenerates the sitemap output immediately.

Use these after large catalog/URL changes when you want an immediate refresh. Routine catalog changes can normally rely on the component's cache/invalidation behaviour.

Custom URLs

Use Add URL only for a public page that search engines should discover and that is not already represented by a normal OpenCart entity.

Good custom URLDo not add
A public custom landing page created by another extension and not included automatically.Admin URLs, account pages, login, cart or checkout.
A useful public editorial page outside the standard entity types.Search result URLs, sort/filter variants or duplicate tracking URLs.

Recommended settings

AreaRecommendedWhy
StatusEnabledProvides a stable discovery source.
CacheEnabled/default lifetimePrevents expensive regeneration on every crawler request.
Active products/categoriesIncludeCore public catalog content.
ImagesInclude where supported/usefulHelps search engines associate product images with product pages.
Custom URLsOnly genuine additional public pagesA sitemap should be a clean list, not every URL the site can produce.

Sitemap vs Indexing Manager

The sitemap should contain URLs you want discovered/indexed. If a route is intentionally noindexed, it generally should not be added to the sitemap. Keep Indexing Manager and sitemap intent consistent.

Sitemap vs IndexNow

  • XML Sitemap = complete discovery map of existing important URLs.
  • IndexNow = fast notification that selected URLs changed.

They complement each other; one does not replace the other.

Troubleshooting

  • sitemap_index.xml does not open: run Update/Repair, then check the managed Apache rewrite/routing setup.
  • Store switch sends you to login: use a current build; admin URLs should retain a valid user token.
  • Add URL does nothing: current builds use AJAX and standard OpenCart alerts; check the top alert area for validation/error text.
  • Old URLs remain after changes: Purge Cache and Rebuild.
  • Sitemap contains the wrong domain: check the selected store's OpenCart URL configuration.