Understand QCMM Frontend SEO, Headings, Canonical URLs, and noindex Routes

Understand QCMM 2.0.21 SEO: public Plans and valid Plan Detail pages receive canonical URLs while transaction, account, and utility views are noindex.

SEO Directives Apply to Frontend GET HTML

QCMM applies its SEO directives only to frontend GET requests that render HTML. It intentionally distinguishes public catalog landing pages from account, transaction, and utility views.

Public Plans Is Canonical

The plans view is indexable and receives a canonical URL based on the current URL. QCMM removes an existing canonical link from Joomla head data before adding its own deterministic canonical.

Valid Plan Detail Is Canonical

A plandetail request with a positive Plan ID receives a canonical containing only ?view=plandetail&plan_id=ID. Unrelated query-string state is not copied into the canonical. A malformed Plan Detail request without a valid positive Plan ID falls through to noindex.

Private and Transactional Views Are noindex

Checkout, dashboard/Member Area, schedule, Meeting Room, fulfillment, malformed Plan Detail, and future utility views default to noindex, follow. Account-activation requests and PayPal return/cancel requests are also explicitly noindex so one-time or transaction state cannot become an indexed landing page.

Heading Structure Still Matters

Keep one meaningful page-level heading and a logical section hierarchy in content surrounding QCMM. Canonical and robots directives solve URL/indexing concerns; they do not replace accessible heading structure or useful page copy.

Community Discussion

Want to compare QCMM workflows or share practical tips? Visit the QC Memberships & Meetings Community. For private support, bug reports, account-specific entitlement or billing problems, or feature requests, use the QuantaCade support system.