Google Caches Different URL

[bhavita]

This post is deleted!

[AlanMosley]

As you can see here Bing does the same http://www.bing.com/search?q=site%3Akeesen.co.in+nfl&src=IE-TopResult&FORM=IETR02&conversationid=

so it looks like you have a problem on your site, or rather had a problem.

I did a crawl of your site and I could not find any reference to the NFL site. but I think some time in the past there was a problem when your sites got crawled by both Google and Bing. See if it goes away over the next few weeks.

[RyanPurkey]

Hello Bhavita. I'm seeing a couple of errors in your DNS settings.

1. No CNAME setup for 'www'  See: https://www.whatsmydns.net/#CNAME/www.keesen.co.in
2. Nameserver not being recognized yet in Mountain View, CA (Home of Google) See: https://www.whatsmydns.net/#NS/keesen.co.in

The CNAME setup is easy to take care of, the Nameserver recognition is just a matter of time in most cases, but get with your DNS/Hosting provider to make sure things are accurate.

Beyond the DNS is making sure your GWT is correctly attributed to the right domain. If you have a group, you might have accidentally associated it with the other business.

[Dr-Pete]

Hmmm... usually when we see this, it's some kind of implicit canonicalization, but clearly these sites have nothing at all in common and aren't remotely duplicates of each other. I'm not seeing any issues in the headers, either as a browser or as Googlebot, and the cache is very recent, so the problem isn't some legacy of weeks or months ago - it seems to be still happening.

The cached page seems to reflect this one:

http://www.sidelinemvp.com/nfl_personalized_jerseys.htm

...and I'm not seeing any bad headers or tags on that side either (?) The NFL site uses a content delivery network, and there's an off-chance something is seriously screwed up on that, but that's speculation at best.

Looking at your indexed pages, via the site: operator, I'm seeing multiple indexed URLs that seem to redirect to another NFL site. For example:

http://keesen.co.in/poolfelt.html

This seems to set off a chain of 301-redirects and goes back to the home-page, but something very weird is happening here. Was your site hacked at some point? If you added the 301s to fix the hack, I'd suggest you actually let these bad URLs die (404 them). You may be mis-attributing some old/bad URLs to your home-page somehow.