Setting Up MODX SEO Tools: A Step-by-Step Guide
Imagine: you've launched a site on MODX, but in Google Search Console you see hundreds of errors like "Duplicate without canonical" and "Missing meta description." This is typical for a "raw" MODX installation. Without properly configured SEO packages, your site loses rankings and traffic. We solve this problem in 2–4 hours—over 50 projects confirm the result.
Why MODX Doesn't Play Well with SEO by Default?
MODX's architecture relies on customization via snippets and TV parameters, but there are no built-in solutions for sitemap, redirects, or hreflang. The developer must either write code manually or install specialized extensions. The second option is faster and more reliable—fewer chances for errors like incorrect canonical URLs or duplicate pages. Moreover, modern performance requirements (Core Web Vitals: LCP, CLS, INP) require fine-tuning of meta tags and data structure, which is hard to implement without packages. Core Web Vitals are a key ranking factor, and incorrect setup can cost you up to 30% of traffic.
Which SEO Package to Choose: SEO Tab or Seosuite?
The choice depends on the project scale. If you only need basic meta tags and Open Graph—SEO Tab will suffice. If you need to manage sitemap, redirects, 404s, and multilingual support—Seosuite is more functional. Our clients save on SEO optimization by choosing the right package. And proper setup pays off within a few months.
| Criterion |
SEO Tab |
Seosuite |
| Meta tags (title, description, keywords) |
✅ |
✅ |
| Open Graph / Twitter Cards |
✅ |
✅ |
| Sitemap.xml |
❌ |
✅ (with priorities) |
| robots.txt management |
❌ |
✅ |
| 301/302 redirects |
❌ |
✅ |
| 404 statistics |
❌ |
✅ |
| Hreflang |
❌ |
✅ |
| Auto-canonical URL |
✅ (manual) |
✅ (auto) |
| Installation complexity |
15 minutes |
30 minutes |
What Problems Does Each Package Solve?
| Problem |
Solution |
Tool |
| Duplicate pages without canonical |
SEO Tab or Seosuite |
Any package |
| Missing sitemap.xml |
Seosuite or pdoSitemap |
Seosuite |
| 404 errors without redirects |
Seosuite with auto-redirects |
Seosuite |
| No hreflang for multilingual |
Only Seosuite |
Seosuite |
Step-by-Step Guide to Setting Up SEO Packages
Step 1. Analytics. Check current meta tags, indexing, duplicates. Often we find missing canonical URLs and incorrect hreflang.
Step 2. Choose the package. If the site is multilingual—Seosuite, otherwise SEO Tab. Consider budget: Seosuite requires more resources for maintenance.
Step 3. Install via Package Manager. Go to admin → System → Package Management → Search "Seosuite" / "SEO Tab" → Install. After installation, configure system settings:
seosuite.sitemap_always_generate: 1
seosuite.use_default_canonical: 1
seosuite.redirect_404: 1
seosuite.redirect_to: ID of 404 resource
For SEO Tab, minimal settings are enough.
Step 4. Integrate into template. Output meta tags via chunks:
<head>
[[seoTab.meta]]
[[seoTab.og]]
</head>
For Seosuite, the package automatically includes output, but you can customize.
Step 5. Generate sitemap. For Seosuite, it's automatic. For SEO Tab, use the pdoSitemap snippet. Create a resource with alias sitemap, template with Content Type XML, and output:
[[!pdoSitemap?
&contexts=`web`
&excludeResources=`10,11,12`
&excludeTemplates=`6`
&cache=`1`
&cacheTime=`86400`
]]
Step 6. Configure redirects and 404. Seosuite tracks 404 statistics and allows setting 301 redirects to the desired page. For SEO Tab, redirects must be written manually via .htaccess.
What to Do When Seosuite Conflicts with Other Packages?
Sometimes Seosuite may conflict with caching snippets (pdoTools, pdoCache). Solution: disable caching for Seosuite output or use a newer version. In our practice, we encountered this twice—the issue is resolved by updating the package or changing the order of snippet calls.
What's Included in Our SEO Package Setup Service
- Installation and configuration of SEO Tab or Seosuite
- Output of meta tags, Open Graph (see Open Graph), canonical URLs
- Sitemap.xml generation with priority settings
- Setup of redirects (301/302) and 404 page
- Hreflang support for multilingual versions
- Documentation on using the SEO panel
- Training editors on new fields
- Guarantee of correct indexing within 30 days
Timelines and Cost
Installation and basic setup—from 2 to 4 hours. If customization is required (additional TVs, complex redirects, hreflang)—from 1 to 2 days. Cost is calculated individually after a free project assessment. Request a diagnosis—we'll choose the optimal solution for your budget.
Why Choose Us?
We have been working with MODX for many years and know all the pitfalls. Our clients note a reduction in SEO optimization costs and an increase in organic traffic. Contact us—get a consultation and assessment within 1 day.
Why are Core Web Vitals critical for technical SEO?
PageSpeed 34/100 on mobile. Search Console shows red on all category pages. A competitor with an older site outranks you despite weaker content. Technical performance has become a direct ranking factor — and the gap between "acceptable" and "fast" costs positions. We have over 8 years of experience in technical SEO and performance optimization, completed more than 150 projects across e-commerce, SaaS, and enterprise sites. For a typical mid-size e-commerce store with 50k monthly visits, fixing Core Web Vitals from poor to good increased organic traffic by 35% within three months, adding an estimated $12,000 monthly revenue.
Core Web Vitals: what really affects rankings
Google uses three metrics as ranking signals (Page Experience): Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Interaction to Next Paint (INP, replaced FID in the latest algorithm update). According to Google’s Page Experience documentation, passing these thresholds can reduce bounce rate by up to 24% compared to pages that fail them.
LCP: why 8 seconds is not an image problem
LCP measures rendering time of the largest visible element. Good <2.5s, poor >4s.
Real case: online clothing store, LCP 7.8s on mobile. Hero image 4.2MB JPEG without srcset, loaded via CSS background-image (not <img>). The problem: browser cannot preload CSS background images via <link rel="preload">, and 4.2MB on mobile connection is slow.
Solution:
- Move to
<img> with fetchpriority="high" and loading="eager"
- Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
-
<link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
- Remove render-blocking scripts above hero with
defer
Result: LCP 7.8s → 1.9s without changing hosting or CDN. That's 4x faster — a competitive advantage in search ranking.
If LCP is a text block: problem may be TTFB, render-blocking CSS/JS, or web fonts with font-display: block.
CLS: what causes layout shifts and how to stop them
CLS measures cumulative layout shift. Good <0.1, poor >0.25. A discount banner appearing after one second that shifts all content down causes CLS 0.35.
Sources:
- Images without dimensions.
<img src="photo.jpg"> without width/height — browser doesn't reserve space. Fix: explicit width/height or aspect-ratio in CSS.
- Ad blocks and widgets — Google Ads, chat, cookie consent. Reserve space via
min-height or load before main content.
- Web fonts.
font-display: swap with size-adjust minimizes CLS.
- Dynamic content — add skeleton placeholder with dimensions.
| Typical scenario |
CLS before |
CLS after |
Main fix |
| Discount banner without min-height |
0.42 |
0.02 |
min-height: 300px |
| Article images without attributes |
0.18 |
0.01 |
width/height + aspect-ratio |
| Chat widget loaded after 3s |
0.35 |
0.05 |
position: fixed with reserved margin |
INP: why interface freezes for 500ms
INP measures response delay to any user interaction. Good <200ms, poor >500ms. INP 680ms means user presses filter button and waits half a second.
Main cause: blocked main thread. A 2.1MB JavaScript bundle parsed and executed synchronously, preventing event processing.
Diagnosis: Chrome DevTools → Performance → interact → find Long Tasks (>50ms). Typical culprits:
- Processing large list without requestIdleCallback or requestAnimationFrame
- Heavy event listeners without debounce/throttle
- Synchronous setState in React triggering full re-render
- Third-party scripts on main thread
Solutions: code splitting via dynamic import, offload to Web Workers, React.memo + useMemo, Scheduler API.
How do structured data and Schema.org improve search visibility?
Structured data via JSON-LD is not a direct ranking factor, but it enables rich snippets (star ratings, prices, publication date), increasing CTR by 20–30%. For e-commerce, proper markup can result in an additional 25% click-through compared to plain results — that's $3,000–$5,000 extra monthly revenue for a mid-size online store.
Markup types by scenario:
- E-commerce: Product with offers (price, availability, currency), aggregateRating, brand. BreadcrumbList, ItemList.
- Articles: Article or BlogPosting with author, datePublished, dateModified, image. Organization and WebSite.
- Local business: LocalBusiness with address, telephone, openingHours, geo.
- FAQ: FAQPage with mainEntity — questions appear as expandable block.
Validation: Google Rich Results Test, Schema Markup Validator. Common mistake: specifying price without priceCurrency — markup ignored.
How to conduct a technical SEO audit
Crawlability. robots.txt blocks necessary pages or doesn't block service pages. Canonical URLs incorrectly set — duplicates with UTM parameters. Sitemap contains noindex pages. Tools like Screaming Frog or Sitebulb show this in an hour.
Core Web Vitals at scale. Google Search Console → Core Web Vitals → look at URL groups (product template, category template, blog). Problem is usually systemic.
JavaScript SEO. Google renders JS with delay. For critical content, SSR or SSG are mandatory. Check via Search Console → Inspect URL → View Crawled Page.
Internal linking. Orphan pages lose PageRank. Broken links (404) are a quality signal.
Common mistakes when implementing Schema.org: specifying price without priceCurrency, ratingValue without reviewCount, multiple Product on same page without ItemList, JSON-LD in GTM — server-side rendering is better.
What does the optimization process look like?
| Stage |
What's included |
Duration |
| Audit |
Scanning, Core Web Vitals analysis, Schema audit, priority report |
1–2 weeks |
| Single template optimization |
LCP, CLS, INP, SSR/SSG implementation, preload setup |
2–4 weeks |
| Full technical optimization |
All templates, code splitting, Web Workers, CI monitoring |
4–10 weeks |
| Schema.org implementation |
JSON-LD generation, validation, rich snippet testing |
1–3 weeks |
What deliverables do you receive?
- Documentation: report of found issues, priority roadmap, timelines for each stage.
- Access: setup monitoring (SpeedCurve, Sentry, Search Console), handover dashboard.
- Training: one or two calls reviewing typical mistakes for your team.
- Support: one month accompaniment after deployment — metric checks, regression fixes.
How many positions can you regain through technical SEO?
We have 5+ years on the market and 150+ projects completed. For a case study: a SaaS platform with 200k monthly visits had LCP 6.2s, CLS 0.45, INP 600ms. After optimization, LCP dropped to 1.8s, CLS to 0.02, INP to 180ms. Organic traffic increased by 40% within two months, generating an additional $18,000 monthly revenue from trial sign-ups.
Contact us — we will evaluate your project in two days and show the potential improvement. Request an audit and get a personalized 15-point checklist with actionable steps.
