SEO Suite Component
Indexing Manager
Use safe indexing policies for search, utility, checkout, compare and duplicate page types.
RecommendedComponent 1.0.2Difficulty: Easy
Control whether common low-value or duplicate page types should normally be indexable.
Indexing vs crawling
Indexing Manager controls page-level indexing directives such as noindex. Robots.txt controls crawler access. They are different tools.
Do not confuse noindex with robots.txtIf you block a page in robots.txt, a crawler may be unable to see a noindex directive on that page. Use the correct tool for the goal.
Safe default policies
| Setting | What it means | Recommended for beginners | Change it when… |
|---|---|---|---|
| Master Status | Enables HuntBee indexing policy output. | Enabled. | Temporary conflict diagnosis. |
| Search Pages Policy | Handles internal search-result pages. | Keep the default protection enabled. | You have a deliberate, tested SEO strategy for public search pages. |
| Utility Pages Policy | Handles low-value utility/system page types. | Keep enabled. | A specific public route should be treated differently. |
| Checkout Policy | Protects checkout-related pages from normal search indexing. | Keep enabled. | Almost never change for a normal store. |
| Compare Policy | Handles compare pages. | Keep enabled. | You intentionally created index-worthy compare landing pages. |
| Variant / Duplicate Policy | Helps with URL variants that should not become separate search results. | Keep enabled. | Your custom routing requires a different exact rule. |
| Custom Rules | Exact OpenCart route + directive, optional query name/value, status and sort order. | Use only after identifying a real route that needs a special policy. | A custom/public route is not covered by normal policies. |
| Rule Tester | Tests how current rules would treat a route. | Use before saving an advanced rule. | Any time you add/change a custom rule. |
What does noindex mean?
It asks supported search engines not to keep/show that page in their search index after they can crawl and process the directive. It is not a security feature. Private information should be protected with authentication/access controls, not SEO directives.
Beginner workflow
- Keep the built-in policies enabled.
- Do not add custom rules unless you can name the exact page type/problem.
- Use Rule Tester before publishing a custom rule.
- After changes, inspect a sample public page source/header and verify the intended robots directive.
Explore HuntBee Suites