Welcome to the Q&A Forum

I really need to be able to grant login access for other people in my organisation to the pro account and importantly restrict access to individual campaigns. Can this be bumped up the dev schedule (or is it even in the pipeline)?

I guess the answer is to make the site map as "usable" and intuitive for the user. This will largely be down to the number of levels in your site architecture and the number of pages. If you have thousands you won't want to show them all, but then a site search tool would make more sense.

The example you have given is fine in all these respects, but its for a basic site.

Well yes, that's kinda my point. We do have a sensible, crawlable navigation so there will be no problems there, so then the sitemap really becomes an indicator of what needs to be crawled (new and updated pages), but then the same question stands...

With other sites we've managed with thousands of pages we've found it detrimental to give Google hundreds of pages to crawl on a sitemap that we don't feel are important. We're pretty sure (and SEOmoz staff have supported this) that domain authority and the number of pages you can get into the index are closely related.

Hi guys,

Ok this is a bit of a sitemap 101 question but I cant find a definitive answer:

When we're running out XML sitemaps for google to chew on (we're talking ecommerce and directory sites with many pages inside sub-categories here) is there any point in mentioning the homepage or even the second level pages? We know google  is crawling and indexing those and we're thinking we should trim the fat and just send a map of the bottom level pages.

What do you think?

OSE is an amazing tool, but do you guys at SEOmoz have any plans to develop it so we can track numbers of links over time.

I need to demonstrate to clients how the link building is going, and this would be a great quick report to see how many links you found on a given day, month, year, etc. A bit like magesticSEO backlink history graph, but better

All depends on what the client wants the page to do, and how it is designed.

A quick google of "jquery splash page" gets you this

http://meerkat.jarodtaylor.com/how-to/meerkat-splash-page/

That's a basic splash page using jqeury, which times out to the main content. Google will ignore this "page" and head straight for the rest of the site. OK, so its not exactly what your client wants but you could add CSS menus in the meerkat content div and have no (or a very long) timer on it, which would get you what the client sounds like they are after.

Thats with 2 mins of googling. Probably much better solutions out there, but like I say, it all depends on the design and your crazy client

What to do? Assuming you've done all you can to convince them not to do it?

Clever use of jquery and CSS menus can get a homepage that looks like an old school flash landing page, but still allows google to crawl through it and get into the site.

I really need to be able to grant login access for other people in my organisation to the pro account and importantly restrict access to individual campaigns. Can this be bumped up the dev schedule (or is it even in the pipeline)?

All depends on what the client wants the page to do, and how it is designed.

A quick google of "jquery splash page" gets you this

http://meerkat.jarodtaylor.com/how-to/meerkat-splash-page/

That's a basic splash page using jqeury, which times out to the main content. Google will ignore this "page" and head straight for the rest of the site. OK, so its not exactly what your client wants but you could add CSS menus in the meerkat content div and have no (or a very long) timer on it, which would get you what the client sounds like they are after.

Thats with 2 mins of googling. Probably much better solutions out there, but like I say, it all depends on the design and your crazy client

I guess the answer is to make the site map as "usable" and intuitive for the user. This will largely be down to the number of levels in your site architecture and the number of pages. If you have thousands you won't want to show them all, but then a site search tool would make more sense.

The example you have given is fine in all these respects, but its for a basic site.