Any ideas how to remove it?
Thank you!
]]>My website has always used non www format for its URLs, however, a recent SEMrush site audit has ran and detected that 18 (interestingly not all) URLs www format have been crawled.
I optimised the features within free Yoast SEO last week, and also migrated my site hosting from Greengeeks to Hostinger – so I’m not sure if either of these variables are the cause of this.
For example: https://novellusproperties.co.uk has always been crawled/indexed, but https://www.novellusproperties.co.uk has also just been crawled according to SEMrush (though not indexed, and to note the crawl doesn’t show in Google Search Console yet either).
Is this anything to worry about in terms of search engines thinking it’s duplicate content (that’s what SEMrush suggests), and do I need to do anything?
I found this Yoast article https://yoast.com/how-to-remove-www-from-your-url/, however when I made the change to my htaccess file it broke the site as said there were too many redirects, so undid the changes.
Thanks,
Daniel Mullane
]]>I’m using ACF for a job listing. I have activated the archive setting and entered the Archive Slug “jobs”. But the URL of the specific job doesn’t have “jobs” in their URL. Instead it shows the generic page archive slug “news”. Any idea what’s wrong?
]]>/event/title-of-event
Which is pretty, but not unique, when an event happens multiple times with the same name/title, it will be confusing. Could the date/year or maybe event ID be inserted?
/event/2025/title-of-event
Where would the url be modified?
]]>we use automated systems to sync a site to another server. When using your plugin we discovered that syncing the generated CSS file isn’t possible as it contains absolute urls that point to the “old” server. This then breaks loading of the fonts.
Therefore it would be awesome if your plugin could only use “path-absolute” URLs like “/wp-content/uploads/fonts/123456/my-font.woff2” which omit the host.
Otherwise we must recreate the CSS file by hand (which breaks automation) oder patch the CSS file afterwards which is not ideal.
Best