Joomla SEO

TL;DR — Joomla can rank perfectly well, but its defaults work against you. The single most important step is making your URLs readable — turn on Search Engine Friendly URLs and rename the htaccess.txt file to .htaccess, or the setting does nothing. After that, deal with duplicate content (Joomla keeps the old ugly URLs alive), add a sitemap extension, and you’re most of the way there.

What Joomla SEO is

Joomla is a free, open-source content management system — the same job WordPress does, just less common (it runs roughly 2% of the web). I’ve worked with it for a long time; back in 2012 I gave a technical SEO talk at Joomla Day Chicago, so a lot of this comes from getting my hands dirty in the admin.

Joomla SEO is just regular SEO applied to Joomla’s quirks. The good news: Joomla 5 has strong SEO features built in. The catch: the important settings are scattered and a little hidden, and a few defaults create problems you have to clean up.

The one step everyone misses

Joomla turns ugly URLs like index.php?option=com_content&view=article&id=2 into clean ones — but only if you do two things, not one:

1. Go to System → Global Configuration → Site tab → SEO Settings and set Search Engine Friendly URLs to Yes and Use URL Rewriting to Yes.
2. In your site’s root folder (on the server), find the file named htaccess.txt and rename it to .htaccess.

That second step is the one people forget. Without it, “Use URL Rewriting” has no effect and your clean URLs silently break. (This is on Apache hosting, which most Joomla sites use; Nginx needs the rewrite rules added to its config instead.)

The duplicate content trap

Here’s the thing nobody warns you about: even after you turn on clean URLs, the old ugly ID-based URL still works. So you can end up with the same article living at two (or more) addresses, which is exactly the duplicate content situation search engines don’t love. You fix it with canonical tags (Joomla has a field for this per article) or by redirecting the old URLs — usually easiest with an SEO extension.

A short starter checklist

• Turn on SEF URLs and rename htaccess.txt → .htaccess.
• Set Force HTTPS to “Entire Site” (Global Configuration → Server). Evidence for this claim Joomla global server configuration includes a Force HTTPS setting with an Entire Site option. Scope: Joomla global configuration; HTTPS also requires a valid certificate and working server HTTPS. Confidence: high · Verified: 2026-07-14 Joomla: Global configuration help
• Give each article a page title and a meta description (note: they live in different tabs — more on that in Advanced).
• Install a sitemap extension — Joomla doesn’t make one on its own — and submit it to Google Search Console and Bing. Evidence for this claim Joomla sites commonly add sitemap generation through an extension and then submit the resulting sitemap to search engines. Scope: Joomla Extensions Directory sitemap category; no specific third-party extension is endorsed. Confidence: medium · Verified: 2026-07-14 Joomla Extensions Directory: Site map Google: Build and submit a sitemap
• Don’t reach for sh404SEF; it doesn’t work on modern Joomla (use Route66 instead).

Want the full version — the multiple-canonical bug, schema, hreflang, and what changed across Joomla 3, 4, and 5? Switch to the Advanced tab.

TL;DR — Joomla 5 is genuinely capable: SEF URLs, per-article metadata, a native Schema plugin, and a strong Core Web Vitals baseline. But the defaults need work. SEF URLs only function after you rename htaccess.txt to .htaccess (Apache) — the #1 missed step. Even then the non-SEF ID URLs stay reachable and Joomla can output up to 3 competing rel=canonical tags for one article, so duplicate content is real out of the box — fix it with canonicals, redirects, or an extension. No native XML sitemap (OSMap / Aimy Sitemap / Route66 / 4SEO). sh404SEF was never ported to Joomla 4/5 — use Route66 (free) or 4SEO (paid). Joomla 5 adds native schema and hreflang (the 5.2 self-referencing hreflang bug was fixed in 5.3). Joomla 6 shipped in October 2025 and is the current major, with Joomla 5.x still getting security/bugfix updates alongside it — check which major a site is on before trusting any settings path.

Where I’m coming from

I’ve described my background as working with “Drupal, Joomla, WordPress, and tons of different e-commerce systems,” and Joomla goes back a while for me — I gave a talk, Technical SEO, at Joomla Day Chicago in 2012. So this isn’t a tour of a CMS I read about; it’s the platform I’ve actually configured. The short version of my opinion: the myth that “Joomla is bad for SEO” is wrong. Joomla 5 is comparable to WordPress technically. The real issues are UX (settings are scattered) and a few harmful defaults.

Global Configuration: the SEO settings that matter

Everything starts at System → Global Configuration → Site tab → SEO Settings:

• Search Engine Friendly URLs → Yes. Converts index.php?option=com_content&view=article&id=2 into a readable slug. Google has long recommended readable, word-based URLs over ID strings, so this is the baseline.
• Use URL Rewriting → Yes — but only after the .htaccess rename below. Removes index.php from the path.
• Adds Suffix to URL → No (usually). Appends .html; leave off for clean URLs unless a legacy site already relies on it.
• Unicode Aliases → No in most cases. Transliterated slugs are cleaner than raw non-Latin characters; only enable for genuine international need.
• Include Site Name in Page Titles — choose Before/After to control how your site name appears in the <title>.

Then two more, elsewhere in Global Configuration:

• Server → Force HTTPS → Entire Site to enforce HTTPS sitewide. Evidence for this claim Joomla provides an Entire Site Force HTTPS configuration option. Scope: Joomla global configuration after HTTPS is functional on the server. Confidence: high · Verified: 2026-07-14 Joomla: Global configuration help
• Metadata Settings — set a global meta description and confirm the default Robots value is “Index, Follow.”

The .htaccess rename — the single most-missed step

Joomla ships a file named htaccess.txt (not .htaccess) in the root directory. Until you rename it to .htaccess, the “Use URL Rewriting” toggle does nothing — this is the #1 cause of SEF URL failures on Apache. Do the rename before (or at least at the same time as) enabling URL rewriting in Global Configuration, or you’ll flip the switch and watch your clean URLs break. On Nginx there’s no .htaccess; you add the equivalent rewrite rules to the server config instead.

Joomla’s duplicate content problem

This is Joomla’s biggest out-of-the-box SEO issue, and it’s worth understanding precisely. Joomla manufactures multiple URLs for the same content:

• The non-SEF URL (/index.php?option=com_content&view=article&id=2) — always reachable, even with SEF on.
• SEF URL via menu vs. SEF URL via category — different paths to the same article if it appears in multiple places.
• www vs. non-www, HTTP vs. HTTPS, trailing-slash variants, and ?layout=print appended to any URL.

The JoomlaSEO.com checklist puts the core of it well: “Even when you have SEF links turned on in your Joomla global configuration, the non-SEF URL still exists, meaning 2 URLs with the same content, and often there are more,” and notes that “Non-SEF URLs are still reachable, despite SEF-URLs being activated, like this: /index.php?option=com_content&view=article&id=2.” As JoomUnited frames the stakes, “Any duplicate content could have harmful effects on your SEO because search bots cannot determine which version deserves indexing priority.”

It gets worse than just two URLs. In some configurations — opening the same article by category ID, article ID, or query parameters — Joomla outputs three different rel="canonical" links by default. Multiple canonicals is a self-defeating signal: as Google’s canonicalization guidance makes clear, declare more than one and they tend to get ignored. So before launch, run a single-page audit (URL Inspection, or a crawler) and confirm each page emits exactly one canonical.

How to fix it:

• Use the per-article Canonical URL field (Publishing tab → Metadata).
• 301-redirect non-SEF URLs to SEF via .htaccess.
• Use the System – SEF plugin’s strict routing / “strict handling of index.php” (Joomla 4/5) to strip index.php and redirect older URLs.
• Or let an extension (4SEO, Route66) add canonicals and redirect non-SEF URLs automatically.

For the underlying concepts, see canonicalization and the canonical tag.

Per-article and per-category metadata (and the UX trap)

Joomla lets you set metadata at the article level — but the fields are split across tabs, which is the single most annoying thing about Joomla content SEO:

• SEO title (Browser Page Title): Edit Article → Options tab.
• Meta description: Edit Article → Publishing tab → Metadata.
• Robots (Index/Follow, NoIndex/NoFollow): Edit Article → Publishing tab → Metadata.
• Canonical URL: Edit Article → Publishing tab → Metadata.

So the page title is in one tab and the description is in another. Seobility’s review captures the broader pattern — “Basic SEO settings are buried” in Joomla’s standard interface, making them “easy to miss.” Categories have their own metadata under Edit Category → Options. And ignore the meta keywords field Joomla still exposes — Google has ignored meta keywords since 2009; it’s harmless but worthless.

XML sitemaps — no native solution

Joomla does not generate an XML sitemap on its own. You install an extension: Evidence for this claim Sitemap generation for Joomla is supplied by extensions rather than the cited core global configuration features. Scope: Joomla Extensions Directory ecosystem; extension compatibility must be checked against the installed Joomla version. Confidence: medium · Verified: 2026-07-14 Joomla Extensions Directory: Site map

• OSMap (Weeblr/JoomlaShack) — the most widely used; free and pro.
• Aimy Sitemap — supports Joomla 3/4/5/6, highly configurable.
• JSitemap — XML, HTML, image, and video sitemaps.
• Route66 and 4SEO — both bundle sitemap generation into a broader SEO suite.

After generating it, add Sitemap: https://example.com/sitemap.xml to your robots.txt and submit it in Google Search Console and Bing Webmaster Tools.

robots.txt — full manual control

Joomla places a real robots.txt in the site root (same level as index.php), fully editable via FTP or your host’s file manager. The default sensibly blocks /administrator/, /api/, /cache/, and /components/ — admin and system directories you don’t want crawled. Just remember the universal rule: robots.txt controls crawling, not indexing — don’t use it to try to deindex pages.

Extensions: what to use (and what to avoid)

• Route66 (Firecoders, free) — Seobility calls it “as close as you’ll get to a WordPress SEO plugin like YOAST for Joomla.” SERP previews, sitemap, canonical management, SEO scoring.
• 4SEO (Weeblr, premium) — Weeblr describes it as software that “works exactly like a search engine, crawling your site to understand it then adds metadata, structured data, builds a sitemap, replace content, helps your social networks sharing or finds broken links.” Pair with 4SEF for URL management.
• sh404SEF — do not use on Joomla 4/5. This is the critical migration gotcha. After 15+ years as the dominant Joomla SEO extension, Weeblr chose not to port it: “After more than 15 years of duty, sh404SEF won’t be ported to Joomla 4. It will not run on Joomla 4.x. To move to Joomla 4, consider newer extensions, including 4SEF to maintain your site SEF URLs and 4SEO for metadata.” And be careful even on older sites — Joomlashack warns that “If you have an existing site that is already using the built in SEF, activating this extension may change all of your URLs.” Switching URL-management extensions on a live site can rewrite URLs and break inbound links; always test on staging and prepare redirect maps first.
• JCH Optimize (performance) — combines and minifies CSS/JS.

Structured data

Structured data handling depends on your Joomla version:

• Joomla 5 ships a native Schema plugin supporting BlogPosting, Event, Product, and Organization (plus Book, Vacancy, Person, Recipe) — configured via Edit Article → Schema tab. No extension needed.
• Joomla 4 and older require an extension (Google Structured Data, 4SEO, or tassos.gr’s) — or manual JSON-LD in the template <head>.
• Manual JSON-LD always works regardless of version, and Joomla’s built-in Breadcrumbs module pairs naturally with BreadcrumbList markup.

Multilingual SEO and hreflang

Joomla has a strong built-in multilingual system. Install languages via System → Extensions → Languages, then enable the Language Filter plugin and turn on “Add alternate meta tags” to generate hreflang tags automatically; the Language Code plugin keeps the BCP47 codes correct. Each language gets a URL prefix (/en/, /fr/, /de/).

One historical caution, now resolved: Joomla 5.2 shipped with the self-referencing hreflang tag missing — the tag pointing to the current page itself was omitted (GitHub issue #44297). That was fixed in the 5.3 release, and the issue is closed. If you’re on 5.3 or later (including Joomla 6), you shouldn’t hit it — but if you’re auditing an old, unpatched 5.2 install, verify hreflang output directly before assuming it’s correct.

Performance: Joomla’s quiet strength

Joomla’s Core Web Vitals baseline is better than many expect. Seobility found the default Cassiopeia template “scored 93/100 on PageSpeed Insights with ‘absolutely nothing’ done for optimization,” and concluded “Joomla 5 is even better, with great performance and many SEO features built in.” Enable Gzip Page Compression and Cache in Global Configuration → Server; add JCH Optimize, image compression, and a CDN for more. Because Joomla doesn’t carry WordPress’s typical plugin stack (separate SEO + cache + security plugins), bare Joomla often beats bare WordPress on performance — which matters for Core Web Vitals.

Joomla 3 vs. 4 vs. 5 vs. 6 for SEO

• Joomla 3 (end of life Dec 2023): basic SEF URLs; nearly everything else needed an extension; sh404SEF was the dominant solution.
• Joomla 4 (Aug 2021): cleaner admin, improved SEF routing — but sh404SEF was abandoned, and Route66 / 4SEO emerged as the alternatives.
• Joomla 5 (Oct 2023): native Schema plugin, extended meta descriptions (~300 chars), trailing-slash control and strict index.php handling in the System – SEF plugin, AVIF support, Organization/Website schema, and a better performance baseline.
• Joomla 6 (Oct 2025, currently on the 6.1.x line): the current major version. It carries forward Joomla 5’s SEO feature set — I haven’t found first-party documentation of SEO-specific settings changes between 5 and 6, so treat the Global Configuration paths above as still accurate on 6 until you’ve confirmed otherwise on the actual install you’re auditing. Joomla 5.x remains on active security/bugfix support in parallel, so plenty of live sites are still on 5, not 6.

If you’re auditing a Joomla site, the first three questions are: which major version (check Joomla’s own version number in the admin footer or System Information, don’t assume from the theme), are SEF URLs actually working (check the .htaccess rename), and is the non-SEF duplicate URL handled? Get those right and Joomla behaves.

AI summary

A condensed take on the Advanced version:

• Joomla 5 is genuinely good for SEO — SEF URLs, per-article metadata, a native Schema plugin, and a strong Core Web Vitals baseline. The “Joomla is bad for SEO” idea is a myth; the real problems are scattered settings and a few harmful defaults.
• Enabling SEF URLs takes two steps: set Search Engine Friendly URLs + Use URL Rewriting to Yes and rename htaccess.txt → .htaccess (Apache). The rename is the #1 missed step; without it, URL rewriting does nothing. Nginx needs server-config rewrites instead.
• Duplicate content is real out of the box: the non-SEF ID URL stays reachable even with SEF on, and Joomla can emit up to 3 competing rel=canonical tags for one article. Fix with the per-article canonical field, .htaccess 301s, the System – SEF plugin’s strict routing, or an extension. Audit a single page pre-launch to confirm one canonical.
• No native XML sitemap — use OSMap, Aimy Sitemap, JSitemap, Route66, or 4SEO, then submit in GSC and Bing.
• sh404SEF was never ported to Joomla 4/5. Use Route66 (free, the closest thing to Yoast) or 4SEO/4SEF (Weeblr, premium). Switching URL extensions on a live site can change URLs — stage first.
• Schema: native in Joomla 5 and 6; extension or manual JSON-LD for Joomla 4 and older.
• Hreflang: Language Filter plugin generates it. A Joomla 5.2 bug omitted the self-referencing hreflang tag (GitHub #44297) — fixed in 5.3, so current installs shouldn’t hit it; verify output on an unpatched 5.2 site.
• Metadata UX trap: page title is in the Options tab, meta description in the Publishing tab. Ignore the meta keywords field.
• Version check first: Joomla 6 shipped October 2025 and is the current major (on the 6.1.x line as of mid-2026), with Joomla 5.x still receiving security updates. Confirm which major a site runs before trusting a settings path.

Official documentation

Joomla’s own docs (docs.joomla.org) sometimes return errors or 403s; when they do, joomla.org/download and forum.joomla.org are reliable fallbacks. Google and Bing have no Joomla-specific guidance — their general, platform-agnostic docs apply directly. As of mid-2026, Joomla 6 (released October 2025) is the current major version, on the 6.1.x line, with Joomla 5.x still receiving active security and bugfix updates — check a site’s actual version before assuming which release this guide’s settings paths match.

Joomla

• Joomla downloads & version info — current Joomla 5.x/6.x releases (use this when docs.joomla.org is unavailable).
• Joomla release news — official changelog for each Joomla 5.x and 6.x release.
• Joomla Forum — the community reference, a dependable fallback for SEF, routing, and extension questions.
• Search Engine Friendly URLs (docs.joomla.org) — the official SEF reference (occasionally 403s; retry or use the forum).
• Enabling SEF URLs on Apache (docs.joomla.org) — covers the htaccess.txt → .htaccess step.
• Joomla 5.2 / 4.4.9 release announcement — the version where the hreflang issue (#44297) was reported.

Google (platform-agnostic, applies to Joomla)

• URL structure best practices — why readable URLs beat Joomla’s default ID strings.
• URL canonicalization — directly relevant to Joomla’s multi-URL / multi-canonical problem.
• Build and submit a sitemap — for the sitemap you’ll generate via extension.
• Localized versions / hreflang — applies to Joomla’s Language Filter setup.

Bing

• Bing Webmaster Tools — sitemap submission and IndexNow (which Joomla can implement via extensions); platform-agnostic.

Quotes from the source

Statements from Joomla SEO authorities and extension developers. (Google and Bing publish no Joomla-specific guidance, so these come from the Joomla ecosystem.)

On Joomla 5’s overall SEO quality

• “Joomla 5 is even better, with great performance and many SEO features built in.” — Seobility. Source
• “It [the default Cassiopeia template] scored 93/100 on PageSpeed Insights with ‘absolutely nothing’ done for optimization.” — Seobility. Source

On the settings being hidden

• Basic SEO settings are “buried” in Joomla’s standard interface, making them “easy to miss.” — Seobility. Source

On duplicate content (the core Joomla problem)

• “Even when you have SEF links turned on in your Joomla global configuration, the non-SEF URL still exists, meaning 2 URLs with the same content, and often there are more.” — JoomlaSEO.com. Source
• “Non-SEF URLs are still reachable, despite SEF-URLs being activated, like this: /index.php?option=com_content&view=article&id=2.” — JoomlaSEO.com. Source
• “Any duplicate content could have harmful effects on your SEO because search bots cannot determine which version deserves indexing priority.” — JoomUnited. Source

On extensions

• Route66 is “as close as you’ll get to a WordPress SEO plugin like YOAST for Joomla.” — Seobility. Source
• 4SEO “works exactly like a search engine, crawling your site to understand it then adds metadata, structured data, builds a sitemap, replace content, helps your social networks sharing or finds broken links.” — Weeblr. Source

On sh404SEF and modern Joomla (the migration warning)

• “After more than 15 years of duty, sh404SEF won’t be ported to Joomla 4. It will not run on Joomla 4.x. To move to Joomla 4, consider newer extensions, including 4SEF to maintain your site SEF URLs and 4SEO for metadata.” — Weeblr, via the Joomla Extensions Directory. Source
• “If you have an existing site that is already using the built in SEF, activating this extension may change all of your URLs.” — Joomlashack. Source

Joomla SEO checklist

A pass to get a Joomla site search-ready and clear of its default traps:

• SEF URLs on: Global Configuration → Site → SEO Settings → Search Engine Friendly URLs = Yes, Use URL Rewriting = Yes.
• htaccess.txt renamed to .htaccess in the site root (Apache) before relying on URL rewriting — the #1 missed step. (Nginx: add rewrite rules to the server config.)
• Force HTTPS = Entire Site (Global Configuration → Server).
• Single canonical per page — audit one page (URL Inspection or a crawler); Joomla can emit up to 3 canonicals by default.
• Non-SEF URLs handled — 301-redirected, or covered by the System – SEF strict routing / an extension (4SEO, Route66).
• Per-article metadata set — Browser Page Title (Options tab), Meta Description
  • Robots + Canonical (Publishing tab). Confirm no stray NoIndex.
• XML sitemap installed (OSMap / Aimy Sitemap / Route66 / 4SEO), listed in robots.txt, and submitted to GSC + Bing.
• robots.txt reviewed — default admin/system disallows kept; nothing important blocked.
• Schema in place — Joomla 5 native Schema plugin (Schema tab), or an extension / manual JSON-LD on Joomla 4 and older.
• Hreflang verified if multilingual — Language Filter “Add alternate meta tags” on; verify output directly if the site is still running an unpatched Joomla 5.2 (the self-referencing hreflang bug, #44297, was fixed in 5.3).
• Confirm the Joomla major version (admin footer or System Information) before trusting any settings path — Joomla 6 is current (Oct 2025+), 5.x is still maintained in parallel.
• Performance: Gzip + Cache enabled; consider JCH Optimize, image compression, CDN.
• Not running sh404SEF on Joomla 4/5 — migrated to Route66 or 4SEF/4SEO.

Joomla SEO cheat sheet

Where the settings actually live

The traps, at a glance

Extensions, fast

• Route66 — free; closest thing to Yoast (SERP preview, sitemap, canonicals).
• 4SEO + 4SEF — Weeblr premium suite (metadata/schema/sitemap + URL management).
• OSMap / Aimy Sitemap / JSitemap — dedicated sitemaps.
• JCH Optimize — CSS/JS combine + minify.
• sh404SEF — legacy only; not for Joomla 4/5.

Version quick reference

• Joomla 3: basic SEF, extension-heavy, EOL Dec 2023.
• Joomla 4: better routing, sh404SEF abandoned.
• Joomla 5: native schema, extended meta, strict index.php handling, best for SEO.

Tools for Joomla SEO

Built into Joomla

• Global Configuration → SEO Settings — SEF URLs, URL rewriting, title handling.
• System – SEF plugin — strict routing, trailing-slash control, strict index.php handling (Joomla 4/5) to tame duplicate URLs.
• Native Schema plugin (Joomla 5) — BlogPosting/Event/Product/Organization, no extension.
• Language Filter + Language Code plugins — multilingual URLs and hreflang.

SEO extensions

• Route66 (free) — SERP preview, sitemap, canonical management, SEO scoring.
• 4SEO / 4SEF (Weeblr, paid) — full SEO suite + sh404SEF-replacement URL management.
• OSMap, Aimy Sitemap, JSitemap — XML/HTML/image/video sitemaps.
• JCH Optimize — performance (CSS/JS).

Search-engine and audit tools (platform-agnostic)

• Google Search Console — URL Inspection (verify the canonical Joomla chose), sitemap submission, indexing reports.
• Bing Webmaster Tools — sitemaps, IndexNow.
• Ahrefs Site Audit / Screaming Frog — crawl the site to catch the duplicate non-SEF URLs, multiple canonicals, and redirect chains Joomla creates by default.
• PageSpeed Insights — check the Cassiopeia/Core Web Vitals baseline.

Prove the fixes actually took

These are pass/fail checks for the specific changes above — run them right after you make the change, not weeks later.

SEF URLs are actually rewriting

Test to run: curl -I https://example.com/index.php?option=com_content&view=article&id=2 alongside curl -I on the clean SEF equivalent. Or just click a menu link on the live site and watch the address bar.

Expected result: the clean SEF URL loads with a 200, and the site’s internal links point to it (not the index.php?... form).

Failure interpretation: if the SEF URL 404s or the address bar still shows index.php?option=com_content... after you flip “Use URL Rewriting” to Yes, the htaccess.txt → .htaccess rename didn’t happen (or didn’t take on Apache).

Monitoring window: immediate — this is a live status check, not something that needs time to propagate.

Rollback trigger: if renaming .htaccess breaks the site entirely (500 errors), rename it back to htaccess.txt while you check for a syntax conflict with your host’s existing rewrite rules, then retry.

Only one canonical tag per article

Test to run: Patrick’s Canonicalization Checker — paste the article URL or its HTML and it flags HTML/HTTP canonical conflicts. (Google’s URL Inspection in Search Console works too, but only shows you Google’s already-chosen canonical, not the raw conflict.)

Expected result: the checker reports exactly one rel="canonical" link, pointing at the SEF URL you want indexed.

Failure interpretation: more than one canonical (or a canonical pointing at a different variant — category path vs. menu path vs. the non-SEF ID URL) means the per-article Canonical URL field, the System – SEF plugin, or your extension isn’t resolving Joomla’s multi-URL problem the way you set it up to.

Monitoring window: immediate for the check itself; give Google a few days to a couple of weeks to reflect the corrected canonical in Search Console’s “Google-selected canonical” field for that URL.

Rollback trigger: if Search Console keeps showing a different Google-selected canonical than your declared one for 2+ weeks after the fix, that’s a sign the duplicate-URL sources (query params, print layout, trailing slash) are still live somewhere and need redirecting, not just canonicalizing.

Sitemap extension is producing a valid, submittable file

Test to run: Patrick’s XML Sitemap Validator — fetch your generated sitemap by URL (e.g. https://example.com/sitemap.xml) after installing OSMap, Aimy Sitemap, Route66, or 4SEO.

Expected result: no errors, a health score reflecting a clean file, and the URL count roughly matching your published article/category count.

Failure interpretation: malformed XML, URLs pointing at the non-SEF ID form instead of SEF URLs, or a URL count far off from your real content usually means the extension’s sitemap settings need reconfiguring (some default to including unpublished or index.php URLs).

Monitoring window: immediate for the file check; check Google Search Console’s Sitemaps report a few days after submitting to confirm it was fetched successfully.

Rollback trigger: if GSC reports “Couldn’t fetch” repeatedly, or the “Discovered URLs” count stays flat for weeks, re-check the sitemap URL is reachable and listed correctly in robots.txt.

Joomla 5 native schema validates

Test to run: Patrick’s Schema Markup Validator — paste the article’s live URL or fetch its HTML after filling in the article’s Schema tab (Joomla 5) or your structured-data extension’s fields (Joomla 4 and older).

Expected result: the schema type you set (BlogPosting, Product, Event, etc.) validates with required fields present; no severity-tier errors.

Failure interpretation: missing-required-field errors usually trace back to an empty article field the schema type depends on (author, publish date, featured image) rather than a plugin bug — check the article’s own metadata first.

Monitoring window: immediate for validation; rich-result eligibility in Search Console’s Enhancements reports can take days to weeks to update after Google recrawls.

Rollback trigger: if the same schema type keeps failing validation after you’ve filled the fields it flags, disable the native Schema plugin (or extension output) for that content type rather than shipping broken JSON-LD.

Test yourself: Joomla SEO

Five quick questions on Joomla’s SEO settings and its default traps. Pick an answer for each, then check.

Resources worth your time

My related writing

• The Beginner’s Guide to Technical SEO — where platform settings like Joomla’s fit in the bigger technical picture.
• Duplicate Content: Why It Happens and How to Fix It — the concept behind Joomla’s biggest out-of-the-box problem.
• Canonical Tags: A Simple Guide for Beginners — the tag you’ll use in Joomla’s per-article canonical field.

My speaking

• Technical SEO — my talk at Joomla Day Chicago, 2012, where I worked through technical SEO on the Joomla platform directly. (My standing disclaimer applies: “This is my understanding of systems… not going to be 100% complete or accurate.”)

From around the industry

• Tested: Is Joomla Good For SEO? (Seobility) — the source for the Cassiopeia 93/100 PageSpeed finding and the Route66 ≈ Yoast framing.
• Avoid Duplicate URLs (JoomlaSEO.com) — the clearest explanation of why non-SEF URLs persist.
• How to Solve Duplicate Content in Joomla (JoomUnited) — practical fixes for Joomla’s multi-URL problem.
• Joomla SEO (Weeblr) — from the 4SEO/4SEF (and former sh404SEF) developer; the authoritative source on the sh404SEF → Joomla 4/5 migration.
• sh404SEF listing (Joomla Extensions Directory) — the official “won’t be ported to Joomla 4” notice.
• Joomla 5.2 hreflang issue #44297 (Joomla GitHub) — the missing self-referencing hreflang bug, closed as fixed in Joomla 5.3.
• Joomla! Downloads (official) — current release lines; Joomla 6 (current major, since Oct 2025) and Joomla 5.x (still maintained) are both actively updated as of mid-2026.

Joomla SEO

Joomla SEO is the practice of optimizing sites built on the Joomla CMS — enabling SEF URLs (which requires renaming htaccess.txt to .htaccess), fixing the duplicate content Joomla creates by default, and adding sitemaps and schema, mostly via extensions like Route66 or 4SEO.

Related: Duplicate Content, Canonical Tag

Joomla SEO

Joomla SEO is the practice of optimizing websites built on the Joomla content management system — a free, open-source PHP/MySQL CMS first released in 2005 that powers roughly 2% of the web and sits, in complexity, between WordPress and Drupal.

Joomla has solid built-in SEO capabilities: search engine friendly (SEF) URLs, per-article metadata, robots meta directives, canonical fields, and (in Joomla 5) a native Schema plugin. But several things still need manual configuration or extensions — XML sitemaps, advanced redirect/duplicate management, and hreflang control.

Three Joomla-specific points trip people up:

• The .htaccess rename. Joomla ships an htaccess.txt file. Until you rename it to .htaccess, “Use URL Rewriting” in Global Configuration does nothing — this is the single most-missed step that breaks SEF URLs on Apache.
• Default duplicate content. Even with SEF URLs on, the legacy ID-based URLs (index.php?option=com_content&view=article&id=123) stay reachable, and Joomla can emit multiple competing canonical tags — so canonical tags or a redirect extension are usually needed.
• sh404SEF is abandoned for Joomla 4/5. The long-dominant SEO extension was never ported; Route66 (free) and 4SEO (premium) are the modern replacements.

Related: Duplicate Content, Canonical Tag

Changelog