Hello,
My crawled pages/articles show a non-www url as canonical while in the SEO settings tab i have set a www url as canonical. Does this need a specific setting inside joomla config to work?
In my .htaccess i have set that i always use www and non-www wil redirect to www.
Kind regards
Tim
#1415
Posted in ‘Route 66’
canonical URL shows non-www
Latest post by Tim Alegria on Wednesday, 01 October 2025 14:31 EEST
Sunday, 28 September 2025 18:14 EEST
Tim Alegria
Sunday, 28 September 2025 18:56 EEST
Tim Alegria
An addition, i only recently changed from non-www to www URLs
Monday, 29 September 2025 10:37 EEST
Lefteris Kavadas
Hi Tim,
Crawled pages are refreshed gradually as long as you have the scheduled task set up according to the documentation:
https://www.firecoders.com/documentation/route-66#crawl-refresh
Since you recently switched from non-www to www, it’s recommended to run a full site crawl from the beginning. This will ensure that all canonical URLs are updated consistently to reflect the new www domain.
Kind regards,
Lefteris
Monday, 29 September 2025 16:50 EEST
Tim Alegria
Hi Lefteris,
That was my idea too but it didn't help.
I tried to purge and crawl again multiple times but the canonical url stays without www.
I see this warning message when i want to see the crawl details from Route 66->pages:
"Could not fetch page contents. Make sure the page is published in order to have SEO and Readability analysis in this form."
https://photos.app.goo.gl/srLxSTJEKE8Hza4x6
I also see this 500 error in my console
https://photos.app.goo.gl/wdHuQNFBkS1j4uDw6
Kind regards
Tim
Monday, 29 September 2025 22:09 EEST
Tim Alegria
Hi Lefteris,
I've found the problem why my canonical URLs still were without www.
I needed to change the System - SEF Site Domain also into the www variant
Plugins -> System - SEF -> Site Domain
But the other problems still are there about the warning and 500 error.
"Could not fetch page contents. Make sure the page is published in order to have SEO and Readability analysis in this form."
https://photos.app.goo.gl/srLxSTJEKE8Hza4x6
500 error in my console
https://photos.app.goo.gl/wdHuQNFBkS1j4uDw6
Do i need to create a seperate ticket for it?
Kind regards,
Tim
Monday, 29 September 2025 22:19 EEST
Lefteris Kavadas
Hi Tim,
You’re right — besides the System - SEF setting, there’s also an option in Route 66 called “Site URL” under the Advanced tab. This value is set automatically during installation, but if you change your domain (like moving from non-www to www), you’ll need to update it manually.
Apologies for not mentioning this earlier. Please update it and let me know if it resolves the issue. If the warning message and 500 error still persist afterward, we can troubleshoot those separately.
Kind regards,
Lefteris
Tuesday, 30 September 2025 00:20 EEST
Tim Alegria
Hi Lefteris,
No problem. The setting in the advanced tab of Route 66 i was aware of and i changed right away but the one in joomla itself i didn't remember.
The issue concerning the 500 error still persists
https://photos.app.goo.gl/UEPJtyKoApqYDBs37
I've been looking in the dev tools but i couldn't get any wiser from it.
Kind regards,
Tim
Tuesday, 30 September 2025 10:39 EEST
Lefteris Kavadas
Hi Tim,
Thanks for checking that. Since the 500 error still persists, we’ll need to look deeper into it. Could you please create a new private ticket and provide temporary administrator credentials so we can troubleshoot the issue directly on your site?
Kind regards,
Lefteris
Tuesday, 30 September 2025 15:24 EEST
Tim Alegria
Hi Lefteris,
I've created a private ticket for this.
Kind regards
Tim
Wednesday, 01 October 2025 00:42 EEST
Lefteris Kavadas
Hi Tim,
I had a look and noticed that when logging in with the language set to en-GB, everything works fine. However, if I log in with en-US, the 500 error appears. This points to a language file issue.
If you need the en-US language, I recommend removing it and reinstalling it through the backend. Alternatively, you can manually download the package from https://downloads.joomla.org/language-packs and install it again.
Kind regards,
Lefteris
Wednesday, 01 October 2025 02:15 EEST
Tim Alegria
Hi Lefteris,
I removed the en-US language and now only have en-GB as default.
Though i'm still seeing the warning message when i go to Route66-pages
"Could not fetch page contents. Make sure the page is published in order to have SEO and Readability analysis in this form."
Kind regards
Tim
Wednesday, 01 October 2025 10:37 EEST
Lefteris Kavadas
Hi Tim,
I updated the Site URL setting and added the trailing slash — it now works correctly. We’ll adjust Route 66 so that this works regardless of whether the trailing slash is present or not.
Thanks a lot for reporting this issue!
Kind regards,
Lefteris
Wednesday, 01 October 2025 14:31 EEST
Tim Alegria
Hi Lefteris,
Thanks for the great support.
Kind regards
Tim
Note: An active subscription is required in order to get support for our paid extensions. For our free extensions, if you don't have an account, register and then submit your support request. In case you just want to ask a question, you can also use the contact form .
