We just fixed a Meta refresh, unified our link profile and now our rankings are going crazy

[Dr-Pete]

I tend to agree that it could just be a short-term re-evaluation period, but I do understand that patience is hard to come by in these situations. I have one concern - I assume the META refresh was acting as some kind of redirect to a different URL? When you removed it, did you canonical the other URL somehow? Just removing the refresh wouldn't consolidate the link "juice" of the various URLs, so it could be that you went from one form of fragmentation to another, different form.

That's just speculation, since I don't fully understand the old/new setups. If you can provides some details with fictional URLs, we might be able to dig in deeper.

[danatanseo]

Thanks Dr. Pete. Here's the scoop, and I'm happy to provide the actual URLs so you can have a real view of the source code, etc.

The meta refresh was on this URL:

http://www.ccisolutions.com

it redirected to this URL:

http://www.ccisolutions.com/StoreFront/IAFDispatcher?iafAction=showMain

We removed the meta refresh, and put "<rel="canonical" href="<a class=" external"="" rel="nofollow" target="_blank">http://www.ccisolutions.com/" /> to the head of both URLs</rel="canonical">

Our IT Manager couldn't get a 301 redirect to work from http://www.ccisolutions.com/StoreFront/IAFDispatcher?iafAction=showMain  to http://www.ccisolutions.com, but in another Q&A thread Streamline Metrics mentioned that this really shouldn't matter as long as the canonical tag is properly set up, which I think it is.

What do you think? (and thanks very much!)

[Dr-Pete]

Yeah, the canonical should be ok - I just wanted to make sure you had something in place. One minor thing - I'd get that up on the page - with all the JS, the canonical is down on line 436 of the source code. You'd really be better off getting all that script into external files. It shouldn't make a big ranking difference, but it won't hurt.

You do have have a dozen pages that share your home-page TITLE and META description. Some seem to be odd, near-duplicates, where others probably just have duplicate meta data. Either way, I'd clean that up. Run this query in Google to see them:

site:ccisolutions.com intitle:"Acoustics, Sound, Lighting"

...or check Webmaster Tools (or your SEOmoz campaigns). Again, it probably isn't the culprit, but it's not helping.

I'd really dig to see if anything else is going on. The timing could just be coincidence. I find it really hard to believe that the META refresh change alone harmed you, unless this is just a temporary bounce while Google sorts it out. I definitely would NOT put it back - you risk compounding the problem. People rush to reverse things, assuming that will take them back to where they were, and it rarely does. More than 70% of the time, it just makes a bigger mess.

[danatanseo]

Thanks Dr. Pete. The marketing team has been complaining about how far the meta tags, etc. are pushed down in our code for years. Unfortunately, there hasn't been enough evidence that this is doing us any harm so it's never been a priority to fix. I believe moving those lines of JS to an external file would, if nothing else, improve our page speed wouldn't it? If our pages load faster it could impact our SEO in a positive way

Thanks again very much for your suggestions

[Dr-Pete]

I can't prove it would cause substantial improvement, but right now it's just in your way, and you'll never know. To me, that kind of clean-up is a no-brainer, because it's no risk. At worst, it cleans up the code, improves caching (and load times as you said), and makes updating easier. At best, you see measurable gains.

As a former developer and dev-team manager, I have to say, too, that it's not a tough fix to split out that JS. It would probably make the dev teams life easier down the road. If they're acting like it's a Herculean task, then either (1) they just don't want to do it, or (2) you need a better dev team.

[danatanseo]

Agreed. I worked at another company that had a 19-year-old kid split out the JS. I submitted the request. I'll let you know what happens. Thanks again!

[Dr-Pete]

It's just one of those things where you're always going to be wondering if the bloated code is causing problems, and it's going to drive you nuts. Fix it, and worst case, you'll rule out a cause. Some days, that's the best we can do.

[danatanseo]

Dr. Pete, Our IT manager responded to my request. Can you point me in the right direction to research these things (I am copying and poasting directly from his message): "A few items that I noticed just skimming the forums that we will
need to look at a little closer are:

1. Java script that is self referencing, as both tab control and the slide show are self referencing
2. Alias domains which we have a number of
3. HTTPS pages, which for us, is all pages depending on
        when a person logs in."

I found info in the GW forum about the mod_pagespeed rewrite module and sent that to him.

He responded "We are currently using mod_rewrite to handle a number of things including 301 redirection. My experience with mod_rewrite does have me very cautious, because it is very easy to “blow up” the site. I would want to run this on the dev site for some time with a concerted testing effort to make sure we do not have issues."

Any references you can recommend would be great. Thank you so much!

[Dr-Pete]

Sorry, I'm not really clear on what the question is - these seem like general IT items unrelated to the SEO problem. The JS rewrites definitely can be tricky and depend completely on the code in question - I can't really provide a general resource.

Not sure how the alias domains tie in, but they definitely need to be part of any redirection scheme. I've used mod_rewrite for pretty large-scale stuff (as do many large sites), but it's possible to write bad/slow rules. It really depends on the scope. I'm not sure if you're talking about 100s or 1000s (10000s, etc.) of pages. Writing the rules for a big site is beyond the scope of any general Q&A. That's something your team is going to have to really dig deep into.

I feel like they might be over-thinking this one issue and trying to fix everything all at once, but I can't say that confidently without understanding the situation. I think it might be better to tackle these things one at a time.

[danatanseo]

Thanks Dr. Pete. I know this is pushing the boundaries of normal Q&A. I appreciate your answer. Yes, one thing at a time I think is a good way to go. I suggested that we try the mod_pagespeed rewrite on the dev site as a first step. I think it would probably be more efficient for us to hire a developer proficient in SEO to handle some of the more technical items. Thanks again!

[PrizeWize]

Totally agree,

Have seen this a few times in the past.

Major SEO changes, big drop in rankings for 2/3 weeks. Then rankings gradually return.

@Dana: Keep us posted, im curious to see if in a few weeks time things have improved