Welcome to the Q&A Forum

Yups I agree with the answer that is given here, if you're using any way of event tracking currently on your site it might be a good idea to look into changing that to the dataLayer and making the switch to a Tag Manager as well. By doing this you can make sure that with future changes for your site you can depend on a protocol that isn't depending on a specific tool or changes that a tool like Google Analytics will make in the future.

Hey Anirban - internal linking is definitely a good tactic for the right sized site. There's a pretty good overview of internal linking over on this Quicksprout video, one highlight: "But, to find out how to get the most bang for your buck, you want to find the pages that have the most authority. Those are the ones that you want to link from to the pages you’re trying to rank. Let me show you what I mean. We’re at Open Site Explorer. What I did is, I put in the home page of my site and pressed the search button. When you’re here, it’ll automatically rank inbound links coming from other sites, but that’s not what we want. We want pages from within our site. So, click on the “Top Pages” tab. When you do that, you’ll see the page authority of all the pages on your site. Starting from highest to lowest, these are the pages that you want to build internal links on, pointing to the pages that you actually want to rank." Brian notes that you can automate some of it if you have thousands of pages, but you shouldn't rely on it too much since there's not enough anchor text diversity: "I’m not a huge fan of doing the automated, because if you do it like this, you’re not going to have a lot of anchor text diversity which may get you dings for over-optimization. If you have a site with thousands of pages, you will need to maybe do some automation and at least have some of your internal links done by a plugin or some piece of software." This Moz Academy lesson also has some good tips on internal linking: Make links relevant, and useful Don't stuff keyword into anchor text too much, and don't overuse footer links For huge sites, you can use sitemaps well and include them in the footer (see 5:00 into the video) I recently wrote up a summary of ecommerce internal links best practices, but the ideas apply to non-ecomm sites: Link product pages together via the description if they're related Tell a story in blog posts of your products and link to those product pages Link blog post content to relevant category pages (underutilized) Make category pages more user-friendly with content, and link liberally to relevant internal pages Use user-generated content/curation pages to help you naturally build internal links at scale Hopefully these ideas point you in the right direction, let me know if you have any followup or more specific questions! If you haven't used Screaming Frog's SEO Spider to scan your site and show internal linking pages, that can be another great tool to help you out.

Hi Anirban, Can you tell me a bit more about this page? Why is it only on the mobile site and not the desktop? I wouldn't expect this to be an issue for SEO (especially not with a single page - maybe if you were doing this for lots and lots of pages we could see an issue). But I would suggest asking yourself whether it makes sense for this page to be mobile only. If so, how likely is it for a desktop user to even find this page? It likely won't rank for desktop but that's a good thing because it's not really available to desktop searchers (since you've implemented a redirect).

Hi Anirban! I'm not entirely sure what you're asking here. Can you clarify at all?

Interestingly, I was able to access your home page without the redirect several times as well. Maybe they're running some kind of A:B testing? If so, that's not the way I would suggest going about it.

I did found the same issue for my site last months. the issue was my referral traffic and some organic (spam keywords) traffic was drastically increased by spam traffic that make 90% to 100% bounce rate. Check out your referral traffic and organic, this can be the issue too.

Hi Anirban, If you look at https://support.google.com/news/publisher/answer/68323?hl=en that should help you. I applied once and it took a long tome to get it included. Good luck! Tymen

Hi there Google does offer methods on getting your website listed in Google News. I would offer the following resources: Google News Publisher Center Creating a Google News Sitemap Enabling Rich Snippets for Articles I would take a look at your website, make sure the content is there in the way that it is worth being listed, read Google's guidelines, and see what from the above you can get started on. These methods should help get you noticed and possibly listed, but as always, it's up to Google! Hope this helps! Good luck!

Excellent advice. Thanks for jumping in here!

Hello Anirban, The main reason large-scale websites like Indeed feature so prominently on SERP's is that there are more ranking factors at work than just content. While Panda has been created to avoid duplicate content issues and it is widely known that duplicate content can lead to penalties and reduced ranking potential, duplicate content can be over-shadowed by other ranking factors, like a website's link profile and it's Authority relative to websites in its niche. For example, Wikipedia is widely cited by webmasters around the world, but it features a lot of repetition and is an internal linking nightmare where crawling and indexing are concerned. That being said, it is normal to find a Wikipedia page every time a "What Is" query is made. Youtube is in a similar situation. There are duplicated videos and content galore on that domain, but it is linked to so frequently that it simply cannot be beaten when it comes to domain authority and relevance. While Indeed is probably being impacted by duplicate content, this pales in comparison to its link profile and the relevance it has in its industry. Hope this helps! Let me know if I can help with anything else. Best regards, Rob

It seems like the issue is a bug in the way Google handle data from your site ('null' being computer speak for 'empty', and often appearing after buggy handling of data). However, it seems that the indication from Umar is correct, and that this buggy data handling is likely prompted by crawling issue so that is the best place to start.

Hi Devanur, Thanks for your valuable input. Regards, Anirban

I've seen instances where Google has created a canonical relationship between two duplicate URLs, even if one isn't explicitly defined. In these cases, they're basically deciding that the documents are duplicates and choose one for search. The document is linked to another site entirely, which may not be helping, either. If this is a document that lives on multiple sites or is provided by a third party, ranking for it or getting Google to see it as unique may be very difficult. There could be technical issues here, but I'm not seeing any offhand - it's possible Google just doesn't want to index multiple copies of what it sees as exactly the same document. If it's important to rank for it, you might need to create your own, slightly customized copy, or an HTML version.

Google talks about this as part of Dynamic Serving of content. Here is their article, which also includes tips on how to distinguish user agents (including how to signal this to Google): https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/dynamic-serving This is an okay practice and I'd not had any Google penalties when I've utilized it. The big concern with doing this type of dynamic content shift for different devices is to avoid cloaking, which Google mentions in that article as well (be sure to click on the link in that Dynamic Serving article for more about cloaking). So long as you avoid cloaking, you should be in okay territory. My advice is to test out your user agent matches thoroughly - I'd even go so far as to try this on one or two pages with some simple changes for each user agent and then make sure Google indexes those pages correctly before rolling this out to your entire site. Hope that helps.

It's not a secret that Google can use Chrome anyway that it wants for data collecting. Just read the TOS.

Hi Anirban! It looked like you asked a very similar question here: http://moz.com/community/q/fetch-data-for-users-with-ajax-but-show-it-without-ajax-for-google What additional information are you looking for?

I'm with Alan on the server side, 1 second is not really good for just doing a request for some links.

Hello Anirbon, You never want to show Google one thing in the code, and show everyone else something different. That is the very definition of cloaking. Have you looked into using JASON-LD instead of Schema markup? Built Visible has a great article on micro data that includes a section about JSON-LD, which allows you to mark up code in a script instead of wrapping the HTML.