Last post 1 hour 50 min ago

Posts last week 128

Average response time last week 28 min

All time posts 70381

All time tickets 10863

All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#8767 – What is the best approach to switch from other tools to 4SEO

Posted in ‘4SEO’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Tuesday, 17 May 2022 22:30 UTC

mavendesignstudio

Hello Yannick,

I've added 4SEO to a site (for the first time) that has already been set for SEO. I plan to replace the following with 4SEO:

-- JSitemap Pro for the sitemap and meta data
-- Scripts for Google Analytics, local schema, and Google tag manager
-- Redirects that are in the htaccess file
-- Google Structured Data (Tassos component)

I started doing this in a Stageit environment. To do so, I changed the main URL the stageit directory, i.e. https://[redacted].com/stageit/

After it's set up in the Stageit environment, I plan to disable JSitemap Pro and Google Structure data, and remove the Google scripts and redirects from the htaccess file, presuming that leaving them would cause conflicts.

A few questions about my approach:

-- Is this approach appropriate?
-- What do you recommend for this type of effort where there are already tools in place that duplicate some of the functions within 4SEO?
-- Can the metadata in JSitemap Pro be imported to 4SEO?

Thank you in advance,

Karen

Wednesday, 18 May 2022 07:09 UTC

wb_weeblr

-- Is this approach appropriate?

Yes. Leave everything in place, just disable the other extensions until you're happy with the results. Once the site is live and working, then you can think of uninstalling.

-- What do you recommend for this type of effort where there are already tools in place that duplicate some of the functions within 4SEO?

Sitemap: 4SEO needs to analyze the site in full so that it can produce the sitemap, any update later on is automated. So you can have the first analysis happens on your staging site. The data collected is relative to the root of the site (ie the domain is not part of the data) meaning when you move it to the live site, you'll only have to change the site address but the collected data will still be valid.

Structured data (tassos): depends on your current setup. If talking about Joomla articles, 4SEO has built-in rules so there should be nothing to do (aside from disabling GSD), unless you use specific features in GSD to build custom-made structured data records. If other extensions are involved, a review is needed to see if 4SEO supports them, what GSD rules are in place.

.htacces redirect: You can create redirect rules in 4SEO to match those in your .htaccess. But in that case, I'd argue if your .htaccess rules are there and working, I see no point in re-creating them inside of Joomla. .htaccess will always be faster to execute the redirects, while 4SEO will always be easier, to create and to manage. So it depends a lot on who you want/can manage redirects, whether you have a dozen or a 400 (you probably should not have 400!).

One thing I'd avise is to make a decision and use one or the other. Likely not best to split between 2 tools to manage redirects.

-- Can the metadata in JSitemap Pro be imported to 4SEO?

Sorry no. We're currently extremely busy completing 4SEF, our successor to sh404SEF for SEF URLs management, and extending 4SEO to add the ability to import meta data and redirects from sh404SEF.

JSitemap was never really an SEO extension, most people use it for sitemaps only so we have not had any prior request for that actually but importing meta from JSitemap will happen, I agree it's important to facilitate the transition. I have added this to our internal tracker but unfortunately cannot provide any timeline.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

Saturday, 18 June 2022 05:34 UTC

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.