Not every site needs a site map, they can certainly be a good idea. Site maps provide a dual purpose: They provide search engine spiders easy access to all of your site pages and they provide site visitors easy access to all of your site pages. The difference is that search engines and visitors access your site map differently and therefore there are different methods that need to be applied to creating site map(s) that are friendly for both engines and search spiders.

Small sites typically don't need a site map so long as all pages are linked in the main navigation. Once you get into main and sub-navigation menu's then site maps are helpful in allowing search engines and visitors to quickly find anything they are looking for within just a couple of clicks. A single site map can be used for both purposes or multiple site maps can be created. Here we'll address creating site maps for spiders and humans separately.

Site Map For Spiders

.xml file

An .xml document should be added to your site's root directory containing links to all site pages. This .xml file should then be referenced should be compiled and placed into a proper .xml document which should be uploaded into the root directory.

Robots.txt file

With your .xml site map file in place you must then make it accessible to search spiders. Reference the site map in your robots.txt file by adding a line for sitemap: URL (example: sitemap: http://www.polepositionmarketing.com/sitemap.xml)

Keep current

Be sure that your .xml file is updated and uploaded frequently, or at least as often as pages are added or removed from your site. Large sites should implement an automated site map update monthly or even weekly or daily.

Site Map For Visitors

Navigation links

A site map designed for human visitors is just like any other website page. Link to the site map page should be included in the primary navigation or the site's global footer. Visitors should be able to find this link without too much searching.

Additional page links

Site map should also be linked from various pages within the site such as Help pages and your custom 404-redirect page. This helps point visitors to the site map as a quick and easy means to find what they need.

Overview

It's helpful to provide a short overview paragraph at the top of your site map page. This can be a nice introduction should someone land on this page directly from a search engine or elsewhere.

Heading and layout

The layout of the site map should present a clear visual hierarchal structure or your website. Both headings and sub-headings should be used above properly grouped links.

Text links & descriptions

Site map should primarily use textual links and page should not be cluttered with images or other distractions. It is also a good idea to provide an additional short description (provided there is room) for each link that allows the visitor to better understand where each link will take them.

Keep current

Be sure that your site map is updated and uploaded frequently, or at least as often as pages are added or removed from your site.

As I said above, not every site needs a site map. But those that do should be sure that the site map(s) they create are actually benefiting them. And the best way to do that is to make sure your site maps provide maximum usability for visitors and search engine spiders.

A part of web development is copywriting. Excellent copy means it has to be appealing to both readers and to search engines. This combination will help websites to rank highly. A problem occurs when there are space constraints to a site, page layout requirements or other issues.

Because appealing to both readers and search engines is so important, you don't want to sacrifice one for the other. Adding a big block of copy to the middle of a page may not be the best answer, however, if a page needs content, adding a couple of sentences to the bottom of each section is a good option. Your copy will still be readable and the additional content will appeal to the search engines.

There are some things to remember when writing content for a website.

• Web users are active. One click and they have left your site. If they don't see a reason to stay, they won't. There is a 10 - 15 second window available to capture a visitor's attention.
• The longer the text is, the less likely they are to read it. With long text, they will skim it, if they bother to read it at all.
• Web users don't believe in hype. If you want a web user to believe you and to believe in you, you must back up your claims.

Four questions must be answered on each page:

• What am I doing here?
• How do I do it?
• What's in it for me?
• Where can I go, next?

If your design and navigation isn't obvious, then you need to explain it in the copy. Most visitors will not take the time to figure this information out. If a first time visitor cannot find their way around your site, they will likely never come back.

Unless your visitors are expecting to read something on your page, don't expect that they will read more than one or two lines of copy.

Understanding your copy is as important as length. Don't make the copy so complicated that it is difficult to comprehend or make it so the customer will have to think about it because they won't.

What this means is you want to convey one key idea in just one or two lines. Don't try to add a third line because if you say too much, then even the first idea won't penetrate. If your site needs more content, break it down into sections that are one or two paragraphs each. Say what you want to say in the first sentence and then expand the thought into the paragraph. Use meaningful headers. Most people will only scan the headers to the paragraphs and not even bother with the copy on the page, unless it is something that appeal to them. It is better to write only one or two lines with links to another page with the longer copy.

Even when users are expecting to find text heavy content, don't expect they will take the time to read all of it. Longer copy doesn't have to be as abrupt as shorter text, but it needs to be as easy to read.

Make your copy clear, but not boring. Lively writing with an unassuming voice is best. Boring writing will turn your reader off and nothing you say at that point will make it through.

How to choose the right IT Company?
How to select the right software partner for my job?
What should I look for when I want to outsource my web development work?
Is it safe to outsource my software / web development work?

If you are concerned about any such issues and are hunting for answers then go on and read the entire stuff.

With rising needs of web development industry, it becomes imperative to choose the right partner for a successful project. The choice of partner will very much impact the overall delivery and implementation for your online presence on World Wide Web. Some people just pick a partner from one of the first few people who contact them while others make their selection based on the prices offered to them from various companies/individuals. What people most often do not consider is the ability and past delivery record of their partner. What's most important is not just to see the project happen on papers, but to visualize it happen in real in the given conditions.

For how long has the partner been into business?

Have they dealt with any customers in your region/area?

Does your partner have the capability to deliver what you are looking for?

Does the partner have technical competence to warn you about any potential flaws or problems that can crop up at a later stage?

Does your partner take care of quality and minor details to bring in professionalism in work?

Has the partner done any similar work in past or something which is comparable and equally complex?

Are the timelines give to you feasible and will be followed?

What happens if deliveries are not made on time for your work?

Are the prices offered to you feasible and to market standards so as to cover the development costs and build a long term relationship?

Is the partner stable and will be in business once your work is done?

Is the partner or their associate traceable in case you need them urgently?

Has the partner had any satisfied customers in the past for any services they have done?

What kind of after sales support will be provided assuming work has been done and delivered?

If you get satisfactory answers for at least 80% of the questions above, then I think you are in good hands. Some people will not be able to provide satisfactory answers to most of these questions. If you land up working with them, the project is bound to fail. We suggest you to continue your search in such cases and think twice before starting any sort of work with non-professional partners.