What is cross linking in seo?

Hi, Your site is a Q&A so I presume that every time someone create a new Question it will generate a unique URL for that. Indepentend if you have or not an answer you want Google to crawl and index your site as quick as possible to start to analyzing the new page and bring traffic to it. The best way to expedite this "re-crawling" is to use a ping service that you can trigger after your user answer the question. PS: If you site is updated frequently you shouldn't have a problem with crawling, because Google usually identify this type of website really quick. Drop me a call is free for this week. Best,

I consult with clients who are looking for the right outsourcing situation all the time, and the best way to get started is to figure out what kind of outsourcing partner will be the best 'fit' for your needs. After that, it's easy to find out where that type of outsourcing partner/contractor/freelance hangs out and pick a winner. Try writing up some notes about things like: 1) You mentioned you had a small budget - how small? If your budget is $1500 your options are going to be very different than if it's $25,000. Both of those could be considered 'small budgets' in the right context, so try to put a number out there. 2) You also mentioned that you wanted 'good quality, clean code'. What does this mean and are you willing to pay for that? If you are building an MVP and are really short on funds, you might have to use a less senior developer/team and take the risk of getting sloppier code - but sometimes with an MVP that's ok! If you are building a production app, that's a different story. 3) What is your technical and management expertise? Can you create specifications and manage a developer on your own (not easy to do)? If so, you can save money by using a freelancer, etc. If you are very non-technical and will need PM support, you might consider a small group or agency. 4) What does 'website development' involve, in your vision? Design? Copywriting? QA? Server migration and admin? ui/ux? 5) What is your tolerance for going offshore? You will hear lots of people saying that offshore teams all suck, and lots of people saying that they did it and it went fine. Like most software projects, there is a high failure rate but lots of success with offshore. You can save a ton of money, but you can also take a bath so you need to consider whether you are up to the challenge or not - going offshore takes much more patience, attention, documentation, etc. but it can work. 6) What are the skills/tech that you will need? It's best to get a team that is great at the skills you need. If you want a ruby site, hire a ruby shop. If you want a augmented reality site, find a team that is great at that. Watch out for the generalists :) By thinking through questions like the above, you can change your statement from "Where do you go for outsourcing website development" to something like this: "I am looking for an outsourcing partner who would be interested in a 15k-20k project that will be build in python. This application will be evolved into our production app so the quality must be good. I am a good project manager and will work with the developer on the requirements/spec side, and help test. We will need application/db design and development, server administration, and technical support but all design, content, copy, ui/ux will be provided. We will consider offshore teams but you must have excellent spoken english." When you expand your 'what we're looking for' paragraph, the whole search for outsourcing partner gets much easier! If you like, feel free to give me a call and share your 'vendor profile' with me and I can help point you in the right direction.

Hi there - There are two parts to the answer. First, it's very important to have a site map that is both current and does not have any URLs in it that return a status code other than a 200. Even 301 redirected URLs should not be in there. Also, the site map should not have more than 50,000 URLs. If it has more, then create multiple site maps and list them in an index site map. Second, site maps are a great way to get content *discovered*, but they won't necessarily rank well. You need the URLs to also be easily discoverable on your site through internal linking. I hope this helps. Feel free to book a call with me if you'd like to discuss more. John

The best technology is whatever gets you up and running the quickest. You'll throw away the first iteration (and possibly the second and third...) anyway. What you need most in the beginning is to test your idea and get feedback, and you need it fast.

Google's official stance is that they are "roughly equivalent" and recommends to do what is technically simpler to implement (source: https://www.youtube.com/watch?v=_MswMYk05tk). With that said, I'd recommend a directory over a subdomain. Doing this consolidates signals to a single domain, which should then theoretically build more authority for all pages off of that single domain. This consolidation of authority results in rank increases, which have been documented here: http://moz.com/community/q/moz-s-official-stance-on-subdomain-vs-subfolder-does-it-need-updating. A subdomain would split signals from the blog and the rest of the root domain content. So while Google "says" they're roughly equivalent, SEOs have seen tangible evidence that sticking to a single domain can be beneficial. If you're able to go with www.iconery.com/editorial/, I'd choose that. Hope this helps!