Recommended setup
Recommended HuntBee SEO Suite Setup
This page tells you what each area is for, what is normally safe to enable, and which controls should be left alone unless you have a specific reason.
New in SEO Suite 4.6.1: product gallery images can have individual multilingual Alt Text and Image Title. Follow the step-by-step image guide. To confirm the actual storefront output, follow the frontend verification checklist.
RecommendedSEO Suite 4.5.xRecommended setup
Best rule: start with safe defaults, generate only missing data, preview before bulk changes, and enable automation only after a manual test looks correct.
If you only have 15 minutes: run SEO Health, generate missing SEO URLs, check Structured Data business information, enable XML Sitemap, verify IndexNow, configure the one Cron Manager scheduler, and leave advanced robots/canonical overrides alone.
On this page
1. Safe setup order
1. Run SEO Health
2. Fix titles, descriptions and basic content
3. Generate only missing SEO URLs
4. Check Canonical, Structured Data, Sitemap and Indexing
5. Enable IndexNow and background queues you actually use
6. Test optional AI, image and automation tools on a small sample
This order reduces risk. Search engines care more about a stable, crawlable site with useful pages than about switching on every possible SEO feature.
2. Recommended settings by component
| Component | What it is for | Recommended setup | Use extra care when… |
|---|---|---|---|
| SEO Health | Your SEO check-up. It finds content, technical, image and link issues. | Run it first, then again after major changes. Fix high-value issues gradually. | Do not chase a perfect score by making changes you do not understand. |
| Quick Editor | A fast way to edit SEO/content fields without opening every OpenCart edit page. | Use it for titles, descriptions, H1/H2, tags and image text. The SEO URL Store selector changes only the store-specific SEO URL. | Do not assume changing the SEO URL store changes product content; normal catalog content remains centrally managed. |
| Meta Tags | Controls page titles and descriptions shown to search engines. | Use unique, readable titles and descriptions that describe the real page. Prioritize products and categories that matter commercially. | Meta Keywords are not a ranking requirement. Do not keyword-stuff. |
| SEO URLs | Creates clean readable URLs. | Use Generate Missing URLs. Generate for All Stores unless you intentionally want one store only. Keep the default-language prefix hidden if that matches your URL strategy. | Use Regenerate Existing URLs only when you deliberately want URL changes and understand redirects. The homepage should resolve to the store root, not ?route=common/home. |
| Canonical Manager | Tells search engines which URL is the main version of a page. | Keep automatic/default canonical behaviour. Let HuntBee handle normal product/category pages and common duplicate variants. | Only add an exact override when you know the preferred URL must be different. |
| Structured Data | Gives search engines machine-readable product and business information. | Enable the relevant standard schemas and enter only real business facts. Check store name, logo, contact/business details, shipping and returns before publishing them. | Never invent ratings, reviews, prices, shipping promises or business facts. |
| XML Sitemap | Lists crawlable store pages so search engines can discover them efficiently. | Keep it enabled, use caching, and include normal active content. Submit sitemap_index.xml to search engines. Use Custom URLs only for real public pages that are not already covered. | Do not add admin, account, checkout, filter/sort URLs or duplicate URLs to the sitemap. |
| Indexing Manager | Controls pages that search engines should not index. | Keep the built-in global policies: normal home/product/category/manufacturer/information pages are Index, Follow by default; search, account, checkout, compare and duplicate sort/filter variants are noindexed. | You usually do not need an explicit index,follow tag. Use Custom Rules only for exceptions. |
| Robots.txt | Controls crawler access to URL areas. | Keep the safe default rules unless you have a known crawl problem. | robots.txt is not the same as noindex. Do not block a page if a search engine must crawl it to see its noindex/canonical instructions. |
| IndexNow | Notifies participating search engines when important URLs change. | Configure each store, generate a verification key, open/verify the public key file, enable automatic notifications, and keep the IndexNow Queue job enabled in Cron Manager. | The store selector is required because domains, verification and queues are store-specific. IndexNow does not guarantee indexing. |
| Broken Links | Records genuine 404 URLs and helps redirect visitors to a useful destination. | Keep the recommended ignored query parameters, review important 404s, use relevant redirects, and monitor Storage Health. Let automatic cleanup remove low-value old records. | Do not redirect every 404 to the homepage. Smart Redirects should resolve real entities and real final URLs, not just similar keywords. |
| Disabled Content Redirects | Redirects old disabled content to a relevant replacement. | Use a permanent 301 when a product/category/information page has been permanently replaced. Pick the closest useful destination. | A bad redirect can confuse users and search engines. Do not send unrelated products to random categories. |
| WebP Optimizer | Serves smaller modern image files where compatible. | Global setting. Enable after a conversion test succeeds. A quality around 82 is a practical starting point for most stores. | HuntBee checks the active theme per store. If another theme such as Journal3 already controls the image pipeline, avoid double-processing. |
| Image Organizer | Improves poor filenames and can organize image folders. | Preview first, back up images/database, then process small batches. Rename poor filenames before considering large folder reorganizations. | Image paths are referenced by products/categories. Never bulk move/rename files outside the tool without updating references. |
| Product Tags | Creates useful OpenCart product-search tags. These are not Meta Keywords. | Good sources: Categories, Manufacturer, Attributes, Filters and Product Name Terms. Keep Product Codes/Model off unless customers genuinely search those values. Maximum generated tags around 10–15; minimum useful word length 3. | Preview first. Avoid stuffing dozens of weak or repeated words. |
| Related Products | Builds relevant product relationships automatically. | Keep the queue enabled if you use automatic generation. Preserve manual relationships and start with small batches such as 10. | Periodic refresh is optional; use it only when you want generated relationships re-scored/cleaned automatically. |
| AI Content | Generates SEO/catalog text using your configured AI provider. | Configure AI Settings first. Generate a few products manually, inspect the result, keep overwrite rules conservative, then enable a small queue only after you trust the prompts. | AI can make factual mistakes and consumes API credits. Do not publish large batches without review. |
| AI Product Feed | Creates machine-readable product feeds and checks merchant-feed readiness. | Select the correct Store + Language. Use Product Readiness to find missing brand/identifier/feed data. Generate the Merchant Feed only when you intend to use it. Public AI Catalog and Merchant Feed are different exports. | Generating a file does not automatically submit it to OpenAI or guarantee inclusion/ranking. Automatic refresh is optional and useful only after a feed snapshot exists. |
| Cron Manager | Runs background jobs without making the admin wait. | Configure one server cron to call HuntBee every minute. Leave recommended queue jobs enabled and optional/advanced jobs disabled until you use their feature. | AI automation can use API credits; Image Organizer can rename files; maintenance refresh jobs are not required for every store. |
3. Multi-store and languages
Not every setting should be store-specific. HuntBee deliberately keeps some configuration global and keeps only the data that truly depends on a store separate.
Usually global
- SEO URL language/route policy
- Indexing built-in policies
- WebP quality/status
- Cron Manager scheduler
- Shared catalog content fields
Store-specific where required
- Actual SEO URL rows
- XML Sitemap output/domain
- IndexNow domain, verification and queue
- Broken Link records and redirects
- AI Product Feed output
- Store default language/domain
Language rule: the store's own default language can use a clean URL without a language prefix, while another language can use a prefix such as
/fr/. Do not create blank language-prefix records as a workaround.4. Automation and Cron Manager
Queues let HuntBee do larger jobs safely in small pieces. The server only needs to call the central Cron Manager once per minute; HuntBee decides which enabled task is due.
| Task | Recommended starting point |
|---|---|
| IndexNow Queue | Recommended Keep enabled when IndexNow is enabled. |
| Product Tags Queue | Recommended Keep enabled when automatic Product Tags are used. |
| Related Products Queue | Recommended Keep enabled when automatic Related Products are used. |
| AI Product Feed Refresh | Optional Enable only after you have generated a merchant-feed snapshot and want it refreshed automatically. |
| AI SEO Content Generation | Advanced Enable only after manual AI results are approved. It may consume API credits. |
| Image Organizer Queue | Optional Enable when you intentionally want queued rename/organization work processed. |
| Image Audit | Maintenance Daily is enough for most stores if you choose to automate it. |
| Related Products Refresh / Product Tags Refresh | Maintenance Optional periodic maintenance; not needed just because the Suite is installed. |
Use the Scheduler Health panel in Cron Manager. A healthy recent heartbeat confirms that automatic calls are actually reaching the store. Clicking Run Now tests a task, but it does not pretend that your server scheduler is configured.
5. Changes to avoid
- Do not regenerate all established SEO URLs just to make them look different.
- Do not redirect every 404 to the homepage. Use the closest relevant live page.
- Do not add random noindex, robots or canonical rules. Built-in defaults cover common cases.
- Do not enable every cron job. Enable the jobs for features you actually use.
- Do not publish large AI batches without review.
- Do not bulk rename/move images without a backup and preview.
- Do not treat SEO Health as a game score. A useful store is more important than forcing every warning to zero.
6. A simple ongoing SEO routine
Weekly
Check SEO Health, Broken Links and failed background jobs. Fix important issues first.
When adding content
Use good titles/descriptions, generate missing URLs, add useful images, and let queues handle tags/related products if enabled.
Monthly
Review Search Console/search performance, sitemap health, important redirects and whether automation is producing useful results.
Recommended profile: keep the technical defaults, concentrate on real product/category content, clean URLs, crawlable pages, valid structured data, a working sitemap, sensible redirects and a healthy scheduler. Add advanced automation only when it solves a real problem.
Tracking Suite quick note
If you also use HuntBee Tracking Suite, start with Consent & Privacy, configure only the advertising platforms you actually use, test purchase tracking, keep debug logging temporary, and configure the Tracking scheduler when server-side delivery is enabled.