I have a question. When content is finished with, i.e. jobs available or a specific event, how do I handle it in Umbraco. At the moment, the content gets unpublished. This, however, causes a 404 error with Google, so how do I overcome this?
What do you want to happen? There are various strategies for dealing with this - it depends if you want to keep the SEO juice and attempt to redirect this?
I would probably add a flag for "job has expired" or date time for expiration and show a slightly revised page template that tries to direct the user to the search / current jobs list. Perhaps even auto redirecting after 10 seconds.
Or you could use 301 redirects. If you have similar jobs then you might want the facility to add an alternative URL to the doc type if this is set add code to redirect it to this or just use a 301 redirect package or just redirect up to the default job list / event list? Here you'd have to consider what you want to happen to the old nodes. Are they in any kind of month / year folder structure or would leaving old job nodes start to annoy?
If you've got regularly changing content I'd probably make amends to add a date structure e.g. /jobs/2017/01/currentjob/ so that they file themselves away.
Most of this should be possible with a small amount of razor code - basically ... what do you want it to do?
Thanks for the quick response. I am just drafting an email to ask exactly that question from the team.
I think possibly the way to go is to have a 'past events' link, so that when an event is passed and the user clicks 'unpublish', what it actually does is move the event to a 'previous events' folder and create a 301 re-direct. This is also more to keep the event as some are annual and a lot of PR and marketing is focused around the success of previous events.
In terms of the jobs, I think that maybe when the job has run its course, it gets archived and a no-follow command is put on the page. Good housekeeping with then remove the job after x months to prevent a huge build up.
One thing you could do is create a hijack controller for /events/ /jobs/ and catch were there isn't a node (e.g. it has been deleted or it doesn't exist) and redirect accordingly to the lister / homepage / whatever.
By the sounds of it - keeping some events and not others might be better to have a date time expired bit of logic and then display it differently. If you're creating a lot of these (and I mean a lot) 301 redirects can become an admin nightmare and an overhead on page loads.
Hard to recommend exactly but I'd definitely recommend looking at a year / month structure - this is good for SEO too.
Unpublish content
Hi
I have a question. When content is finished with, i.e. jobs available or a specific event, how do I handle it in Umbraco. At the moment, the content gets unpublished. This, however, causes a 404 error with Google, so how do I overcome this?
Thanks in advance
Hi Jocelyn,
What do you want to happen? There are various strategies for dealing with this - it depends if you want to keep the SEO juice and attempt to redirect this?
I would probably add a flag for "job has expired" or date time for expiration and show a slightly revised page template that tries to direct the user to the search / current jobs list. Perhaps even auto redirecting after 10 seconds.
Or you could use 301 redirects. If you have similar jobs then you might want the facility to add an alternative URL to the doc type if this is set add code to redirect it to this or just use a 301 redirect package or just redirect up to the default job list / event list? Here you'd have to consider what you want to happen to the old nodes. Are they in any kind of month / year folder structure or would leaving old job nodes start to annoy?
If you've got regularly changing content I'd probably make amends to add a date structure e.g. /jobs/2017/01/currentjob/ so that they file themselves away.
Most of this should be possible with a small amount of razor code - basically ... what do you want it to do?
Steve
Hi Steve
Thanks for the quick response. I am just drafting an email to ask exactly that question from the team.
I think possibly the way to go is to have a 'past events' link, so that when an event is passed and the user clicks 'unpublish', what it actually does is move the event to a 'previous events' folder and create a 301 re-direct. This is also more to keep the event as some are annual and a lot of PR and marketing is focused around the success of previous events.
In terms of the jobs, I think that maybe when the job has run its course, it gets archived and a no-follow command is put on the page. Good housekeeping with then remove the job after x months to prevent a huge build up.
Does that make sense?
Sure - that work,
One thing you could do is create a hijack controller for /events/ /jobs/ and catch were there isn't a node (e.g. it has been deleted or it doesn't exist) and redirect accordingly to the lister / homepage / whatever.
By the sounds of it - keeping some events and not others might be better to have a date time expired bit of logic and then display it differently. If you're creating a lot of these (and I mean a lot) 301 redirects can become an admin nightmare and an overhead on page loads.
Hard to recommend exactly but I'd definitely recommend looking at a year / month structure - this is good for SEO too.
Steve
Cool - will have the conversation.
Thanks for replying :)
is working on a reply...