Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
An immediate and long-term plan for expired Events?
-
Hello all, I've spent the past day scouring guides and walkthroughs and advice and Q&As regarding this (including on here), and while I'm pretty confident in my approach to this query, I wanted to crowd source some advice in case I might be way off base. I'll start by saying that Technical SEO is arguably my weakest area, so please bear with me. Anyhoozles, onto the question (and advance apologies for being vague):
PROBLEM
I'm working on a website that, in part, works with providers of a service to open their own programs/centers. Most programs tend to run their own events, which leads to an influx of Event pages, almost all of which are indexed. At my last count, there were approximately 800 indexed Event pages.
The problem? Almost all of these have expired, leading to a little bit of index bloat.
THINGS TO CONSIDER
-
A spot check revealed that traffic for each Event occurs for about a two-to-four week period then disappears completely once the Event expires.
-
About half of these indexed Event pages redirect to a new page. So the indexed URL will be /events/name-of-event but will redirect to /state/city/events/name-of-event.
QUESTIONS I'M ASKING
-
How do we address all these old events that provide no real value to the user?
-
What should a future process look like to prevent this from happening?
MY SOLUTION
Step 1: Add a noindex to each of the currently-expired Event pages. Since some of these pages have link equity (one event had 8 unique links pointing to it), I don't want to just 404 all of them, and redirecting them doesn't seem like a good idea since one of the goals is to reduce the number of indexed pages that provide no value to users.
Step 2: Remove all of the expired Event pages from the Sitemap and resubmit. This is an ongoing process due to a variety of factors, so we'd wrap this up into a complete sitemap overhaul for the client. We would also be removing the Events from the website so there are not internal links pointing to them.
Step 3: Write a rule (well, have their developers write a rule) that automatically adds noindex to each Event page once it's expired.
Step 4: Wait for Google to re-crawl the site and hopefully remove the expired Events from its index.
Thoughts? I feel like this is the simplest way to get things done quickly while preventing future expired events from being indexed. All of this is part of a bigger project involving the overhaul of the way Events are linked to on the website (since we wouldn't be 404ing them, I would simply suggest that they be removed entirely from all navigation), but ultimately, automating the process once we get this concern cleaned up is the direction I want to go.
Thanks. Eager to hear all your thoughts.
-
-
Great! Happy to help
-
Hi Robin, thanks for taking the time to write out such detailed and helpful responses. I think I've decided to go with the approach you're outlining above:
For those that are already indexed:
- Change the 302s to 301s (all of the expired events that are indexed are 302s for some reason)
- 404/410 those that don't have any equity
- Create a custom 404 page
- Wait for them to drop out of index
For future Expired Events
- Wait about one month, then apply a 404 with custom page
- Redirect any that have backlinks
It'll require a little more work, but it is, I think, the right thing to do in this very bizarre situation.
-
To be honest it sounds like you already have your plan.
One thing I'd bear in mind is a crawl you run of your site won't line up with the pages that Google is visiting. For one thing, the tools we use try to approximate Google but won't be exactly the same. More importantly, once Google knows of a page it'll come back and check on it to see if the content changed, the only way you'll see that is by looking at your log files.
Yea there's no point making it "noindex, follow", it's not that Google doesn't know what to do with the page, it's just that it's attitude to the page will change over time.
In terms of the large number of redirects, there is some risk that Google could see the large number of 301s as spammy but, to be honest, I've never directly seen evidence of that being a problem. The way I see it, the choice is fairly similar you could
-
404/410 that's the way the internet is meant to work when something no longer exists but you'll lose link equity.
-
301 to preserve link equity but you're essentially misusing the status code.
-
Do a monthly check, 301 any expired pages with discovered backlinks, 410 the rest. This is best of both worlds but is much more time consuming.
I think you can probably get away with the 301s but it all comes down to your appetite for risk.
Good luck!
-
-
Thanks for the detailed response and the suggestion. The problem is, I think, a little more complicated than that. So there are two main concerns:
**1. What do we do with the current expired pages? **
So one thing that happens is that the event pages are effectively orphaned once the event has passed. All trace of them is removed from the website, and if my previous crawl is to be believed, they don't get crawled. Right now, the majority of these expired and indexed event pages are actually 302 redirects. So we're getting a temporary redirect to a page that is expired. Hardly a good user experience.
I do know that since it's a 302, Google is thinking "Hey, the page is coming back, so we're going to index that but send visitors to the new pages." This would be why the 302 URL is indexed. Am I correct in assuming that updating all of these to a 301 would result in the URL ultimately being removed? If so, then I think the best course of action would simply be to 301 redirect all of the current 302 URLs, as well as the actual expired event pages to the relevant event host / program pages.
Also, I did not know that _noindex _was treated as noindex, nofollow after awhile. Would it be beneficial to make them _noindex, follow, _or would that still be a redundancy that Google will ultimately ignore? I also do not think a pop-up is the way to go. These are very short-term events, so the issue is _less _a user experience and more a means of preventing them from clogging up the index. Also it would just be more work for the client and I'm trying to keep things as simple as possible.
**2. What do we do with the future expired pages so they don't end up getting indexed? **
This is probably a more pressing question. So the main concern is we want the Event pages to be indexed while they're live then ultimately removed after they've expired. I'm okay with this process: write a script that auto-redirects and remove all internal links from the website and just simply be patient. My main concern is just having way too many 301 redirects in place.
I'm hoping that the 301 in place combined with the complete orphaning of the page will mean they simply won't be crawled and eventually dropped from the index and thus not accessible to Google or users, but I'm still a little wary. Thoughts? Is there any room for adding anything to robots.txt?
Thanks again for your help. It is much appreciated.
-
Hi there, thanks for posting!
I think my main question here is around the decision to note 404 or 301 these pages. I totally understand that you want to reduce the number of indexed pages which aren't providing value but also don't want to lose equity. I know you mention you're not super technical so I'm going to break down how I expect link equity to be passed around a site and therefore how I expect each of these techniques to impact the page.
Equity is passed from page to page via links so these events pages will pass equity to other pages on yo by Google having a record of the page and the equity of that page, then distributing that equity through links it can follow. Google representatives have said recently that, after a period of time, noindex pages are treated as noindex nofollow at which point we can't rely on equity being passed along any of the outbound links from these pages.
-
noindex: removes the page from the index, after a period of time no equity will be passed from the noindexed page. Initially Google will continue to crawl the page but that will reduce over time.
-
404: the page doesn't exist so will be removed from the index after a period of time. No equity will be passed from the page. Google should stop crawling the page fairly quickly.
-
410: more definitive than 404. Page should drop out of the index more quickly. No equity will be passed from the page. Google should should stop crawling the page fairly quickly.
-
301: we're telling Google that this address is no good any more and it should instead look at a different address. Again, the redirected page should drop out of the index and some proportion of the redirected page's equity should be transferred to the target page. Google should stop crawling the page more quickly than noindexed version but probably not as quickly as the 404/410.
Based on all that I don't think noindex is necessarily your best option. You'll still have a bunch of defunct pages, which Google may still spend time crawling, and you can't rely on them passing equity.
A custom 404/410 page explaining to users that the event has passed is probably a pretty good user experience and would be the most expected behaviour for a situation where content isn't there any more, but won't help you with equity.
I think what you could do is automatically 301 redirect to a relevant category page with a pop-up message that explains to users what's happened. Doesn't sound like you expect the event pages to pop in and out of existence so the logic should be fairly simple.
Hope that helps!
-
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Two websites, one company, one physical address - how to make the best of it in terms of local visibility?
Hello! I have one company which will be operating in two markets, printing and website design / development. I’m planning on building two websites, each for every market. But I’m a bit confused about how to optimize these websites locally. My thought is to use my physical address for one website (build citations, get listed in directories, etc. ) and PO Box for another. Do you think there is a better idea?
Technical SEO | | VELV1 -
How long does it take to rank easy keywords?
I have an established site with low keyword ranking and the keyword I am wanting to rank for it rated below 10 on Moz. It has been a few days since I published the article.
Technical SEO | | Begbie20060 -
Clients domain expired - rankings lost - repurchased domain - what next?
Its only been 10 days and i have repurchased the domain name/ renewed. The who is info, website and contact information is all still the same. However we have lost all rankings and i am hoping that our top rankings come back. Does anyone have experience with such a crappy situation?
Technical SEO | | waqid0 -
What is the best way to deal with an event calendar
I have an event calendar that has multiple repeating items into the future. They are classes that typically all have the same titles but will occasionally have different information. I don't know what is the best way to deal with them and am open to suggestions. Currently Moz anayltics is showing multiple errors (duplicate page titles, descriptions and overly dynamic urls). I'm assuming that it's showing duplicate elements way into the future. I thought of having the calendar no followed at all but the content for the classes seems valuable. Thanks,
Technical SEO | | categorycode0 -
How long does it take for Google for deindexing pages?
Hi mozzers, We just launched a mobile website(parallel) and realized that it created many duplicate content with desktop URLs. I decided to add name="robots" content="No index, No follow" /> to the entire mobile site. My only concern is that I am still seeing the mobile site indexed when it's been almost a week I added these tags. Does anyone know how long it takes google to deindex your content? Thanks
Technical SEO | | Ideas-Money-Art0 -
How long should I keep 301 redirects?
I have modified a the URL structure of a whole section of a website and used mod_rewrite 301 redirect to match the new structure. Now that was around 3 months ago and I was wondering how long should I keep this redirect for? As it is a new website I am quite sure that there are no links around with the old URL structure but still I can see the google bot trying from time to time to access the old URL structure. Shouldn't the google bot learn from this 301 redirect and not go anymore for the old URL?
Technical SEO | | socialtowards0 -
How long does it take for rank to return after 301?
Hello all -- just looking for those who have implemented site-wide 301 redirects due to a domain change. I am about 2 weeks into mine and am seeing minimum 5, maximum 21 spot drops in many of my targeted terms. My pages have strong GPR, with most being 3 or higher. Anyone out there been able to track a ballpark of when rank will return? The 301 redirects were implemented correctly, with 1 to 1 setups in most cases. Google has updated the listings with the new domain name, but I'm taking a huge rank hit. Any experience on how long I can expect (I know it's different for every situation) would be great! Thanks.
Technical SEO | | Bandicoot0 -
Using Schema.org: Product or Event as the schema type?
Hello, Most of you heard from the launch of the new format for microdata: Schema.org and my question is about the different types of Schema they provide. Our websites provide an overview of courses, visitors can search/filter training courses and most important: read peer reviews. Until now we formatted (the source) of those courses with the schema type "Product" because it allows us to provide search engines with metadata about reviews via the "Aggregrated Rating". Recently we updated the information about courses, to also provide start dates and locations to users, just like the schema type for: "Events". Because we would like to provide search engines also with both types of data I would like to know your opinion. Schema.org looks like not to support the Aggregated Rating for Events and vice versa for Startdates/Locations for the Product type. And combining the two Schema types also does not looks like an option because we can't put them on the same level like it should be. So what would you recommend to use for kind of schema type(s), are we able to use the 'Product' type next to the 'Event' type and so to combine them? Thanks a lot!
Technical SEO | | Martijn_Scheijbeler0