Sitelink Trouble - CMS Migration
-
Hi Mozzers,
My company recently took over a website for a client and moved them onto our CMS. We are having some issues right now with sitelinks.
A few things have happened to cause this:
1. Our IT department didn't put in the proper 301 redirects from their old subdirectory pages to the new corresponding subdirectory pages. (Insert head smack here.)
2. In addition to taking over the client's desktop domain, we've also taken over the client's mobile site. The mobile site has changed from m.domain.com to www.domain.mobi. Again, there was a missing 301 between the two (head smacking ensues).
As a result, Google has selected the following pesky sitelink for one of the sitelinks returned during a brand search for the client. The brand search is returning a sitelink under www.domain.com as:
IIS7 IIS7When you click on the sitelink for IIS7, it's a link to m.domain.com which NOW redirects to www.domain.mobi.
My question is how long until the IIS7 sitelink goes away and is there anything we can do to speed it up?
What we've been doing to fix this:
1. Demoting sitelinks in GWT for www.domain.com that have the old subdirectory structure while the 301 redirects are being implemented. I can't demote this m.domain.com as a sitelink for www.domain.com because it's a different subdomain, and GWT will only allow me to demote subfolder pages or the www.domain.com itself
2. We've verified m.domain.com and demoted its homepage as a sitelink. Still not sure how this could stop it from showing up for a brand search that returns www.domain.com
Thanks in advance!
-
Tom,
Would there be any benefit to use GWT's url removal tool for the old mobile website? m.domain.com?
Thanks,
Ellen
-
Thanks Tom!
-
Sorry I can't offer any more help here, but you've done exactly all I could recommend to speed up the process - demoting the pesky sitelinks.
Only thing really to add is to ensure that the links that you would want to appear in the sitelinks are recognised by Google as the most important landing pages - so link to them internally wherever you can and of course externally (though of course the 301s will help with this)
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
-
Sudden drop in organic traffic after migration from Django to Wordpress.
I have seen a sudden drop organic reach in a particular page of our website www.hackerearth.com/innovation earlier this was www.hackerearth.com/sprint. I although understand that it happens while migration but it has been a while we did the migration. The migration happened around May month. Something similar has happened to our blog. Earlier it was a blog.hackerearth.com now hackerearth.com/blog _Could anyone suggest me what could be the possible issue for the drop in traffic? _
Intermediate & Advanced SEO | | Rajnish_HE0 -
Site Migration Question
Hi Guys, I am preparing for a pretty standard site migration. Small business website moving to a new domain, new branding and new cms. Pretty much a perfect storm. Right now the new website is being designed and will need another month, however the client is pretty antsy to get her new brand out over the web. We cannot change the current site, which has the old branding. She wants to start passing out business cards and hang banners with the new domain and brand. However, I don't want to be messing with any redirects and potentially screw up a clean migration from the old site to the new. To be specific, she wants to redirect the new domain to the current domain and then when the new site, flip the redirect. However, I'm a little apprehensive with that because a site migration from the current to the new is already so intricate, I don't want to leave any possibility of error. I'm trying to figure out the best solution, these are 2 options I am thinking of: DO NOT market new domain. Reprint all Marketing material and wait until new domain is up and then start marketing it. (At cost to client) Create a one pager on new domain saying the site is being built & have a No Follow link to the current site. No redirects added. Just the no follow link. I'd like option 2 so that the client could start passing out material, but my number one concern is messing with any part of the migration. We are about to submit a sitemap index to Google Search Console for the current site, so we are just starting the site migration. What do you guys think?
Intermediate & Advanced SEO | | Khoo0 -
Scary bug in search console: All our pages reported as being blocked by robots.txt after https migration
We just migrated to https and created 2 days ago a new property in search console for the https domain. Webmaster Tools account for the https domain now shows for every page in our sitemap the warning: "Sitemap contains urls which are blocked by robots.txt."Also in the dashboard of the search console it shows a red triangle with warning that our root domain would be blocked by robots.txt. 1) When I test the URLs in search console robots.txt test tool all looks fine.2) When I fetch as google and render the page it renders and indexes without problem (would not if it was really blocked in robots.txt)3) We temporarily completely emptied the robots.txt, submitted it in search console and uploaded sitemap again and same warnings even though no robots.txt was online4) We run screaming frog crawl on whole website and it indicates that there is no page blocked by robots.txt5) We carefully revised the whole robots.txt and it does not contain any row that blocks relevant content on our site or our root domain. (same robots.txt was online for last decade in http version without problem)6) In big webmaster tools I could upload the sitemap and so far no error reported.7) we resubmitted sitemaps and same issue8) I see our root domain already with https in google SERPThe site is https://www.languagecourse.netSince the site has significant traffic, if google would really interpret for any reason that our site is blocked by robots we will be in serious trouble.
Intermediate & Advanced SEO | | lcourse
This is really scary, so even if it is just a bug in search console and does not affect crawling of the site, it would be great if someone from google could have a look into the reason for this since for a site owner this really can increase cortisol to unhealthy levels.Anybody ever experienced the same problem?Anybody has an idea where we could report/post this issue?0 -
Migrating From Parameter-Driven URL's to 'SEO Friendly URL's (Slugs)
Hi all, hope you're all good and having a wonderful Friday morning. At the moment we have over 20,000+ live products on our ecomms site, however, all of the products are using non-seo friendly URL's (/product?p=1738 etc) and we're looking at deploying SEO friendly url's such as (/product/this-is-product-one) etc. As you could imagine, making such a change on a big ecomms site will be a difficult task and we will have to take on A LOT of content changes, href-lang changes, affiliate link tests and a big 301 task. I'm trying to get some analysis together to pitch the Tech guys, but it's difficult, I do understand that this change has it's benefits for SEO, usability and CTR - but I need some more info. Keywords in the slugs - what is it's actual SEO weight? Has anyone here recently converted from using parameter based URL's to keyword-based slugs and seen results? Also, what are the best ways of deploying this? Add a canonical and 301? All comments greatly appreciated! Brett
Intermediate & Advanced SEO | | Brett-S0 -
Rel=canonical on pre-migration website
I have an e-commerce client that is migrating platforms. The current structure of their existing website has led to what I would believe to be mass duplicate content. They have something north of 150,000 indexed URLs. However, 143,000+ of these have query strings and the content is identical to pages without any query string. Even so, the site does pretty well from an organic stand point compared to many of its direct competitors. Here is my question: (1) I am assuming that I should go into WMT (Google/Bing) and tell both search engines to ignore query strings. (2) In a review of back links, it does appear that there is a mish mash of good incoming links both to the clean and the dirty URLs. Should I add a rel=canonical via a script to all the pages with query strings before we make our migration and allow the search engines some time to process? (3) I'm assuming I can continue to watch the indexation of the URLs, but should I also tell search engines to remove the URLs of the dirty URLs? (4) Should I do Fetch in WMT? And if so, what sequence should I do for 1-4. How long should I wait between doing the above and undertaking the migration?
Intermediate & Advanced SEO | | ExploreConsulting0 -
301's, Mixed-Case URLs, and Site Migration Disaster
Hello Moz Community, After placing trust in a developer to build & migrate our site, the site launched 9 weeks ago and has been one disaster after another. Sadly, after 16 months of development, we are building again, this time we are leveled-up and doing it in-house with our people. I have 1 topic I need advice on, and that is 301s. Here's the deal. The newbie developer used a mixed-case version for our URL structure. So what should have been /example-url became /Example-Url on all URLs. Awesome right? It was a duplicate content nightmare upon launch (among other things). We are re-building now. My question is this, do we bite the bullet for all URLs and 301 them to a proper lower-case URL structure? We've already lost a lot of link equity from 301ing the site the first time around. We were a PR 4 for the last 5 years on our homepage, now we are a PR 3. That is a substantial loss. For our primary keywords, we were on the first page for the big ones, for the last decade. Now, we are just barely cleaving to the second page, and many are 3rd page. I am afraid if we 301 all the URLs again, a 15% reduction in link equity per page is really going to hurt us, again. However, keeping the mixed-case URL structure is also a whammy. Building a brand new site, again, it seems like we should do it correctly and right all the previous wrongs. But on the other hand, another PR demotion and we'll be in line at the soup kitchen. What would you do?
Intermediate & Advanced SEO | | yogitrout10 -
We will be switching our shopping cart platform from volusion to magento and really cautious / nervous about our rankings / seo stuff. any advice for anyone that has migrated stores, etc. these urls are years old, etc.
shopping cart platform switch and SEO. What do you suggest? What's the best way to ensure we keep rankings.
Intermediate & Advanced SEO | | PaulDylan0 -
How can we minimize the SEO impact during a major platform migration?
We are preparing for a major platform migration with an ecommerce client. The website is in the range of 7000 pages. During this migration, all URLs will change due to differences in the platform and improvements to the site structure. Unfortunately, they run on a Microsoft server, so doing 301 redirects also tends to be a painful process. What can we do to minimize the initial dent this puts in the website traffic? We are prepared to submit XML sitemaps to Google and Bing as soon as the new site is live. writing 301 redirects for all pages which have inbound links (this is tough to automate due to the URL structures). In the long run, we expect the new platform, URL structure, and site architecture to be a huge improvement for our organic rankings. The client and we are worried about the transition period though! Any tips or advice to help us through it? Thanks!
Intermediate & Advanced SEO | | outofboundsdigital0