Only Crawling 1 page?

[lovealbatross]

Hi Guys,

Any advice much appreciated on this!

Recently set up a new campaign on my dashboard with just 5 keywords. The domain is brammer.co.uk and a quick Google site:brammer.co.uk shows a good amount of indexed pages.

However - first seomoz tool crawl has only crawled 1 url!!

"Last Crawl Completed: Apr. 12th, 2011 Next Crawl Starts: Apr. 17th, 2011"

Any ideas what's stopping the tool crawl anymore of the site??

Cheers in advance..

J

[lovealbatross]

Agreed. I've passed this to the devs.

You've been most helpful today - Thanks for your time, very much appreciated.

J

[Tompt]

Well I don't think we can hold this against SEOmoz particularly, if something as basic as Xenu can't crawl it and W3C can't view it's source code I think it's somewhat fair to blame the site. Even if Google can see it I would imagine if the matter of fixed you might see a boost regardless.

Google needs to be able to see sites no matter what their state because you or I can do the same, they have the resources to implement that as well. Smaller operations (everything else) have to make do with figuring it out the old fashioned way through the source code.

I think it's the encoding simply because that is the first port of call on the page and it's broken. If it was anything further down we would at least be seeing some page data cropping up.

The only other thing it could be (because I can't find a robots.txt) is something server side, and that's something it's very difficult to establish without direct access.

[lovealbatross]

Interesting. Do you think that could be it? Googlebot seems to find it's way around it though. I'd have thought if G could do it then SEOmoz tools would, otherwise I imagined getting an inaccessibility error or similar from moz.

I'll get that changed and see if it makes a difference..

Thanks again for looking at it!

[Tompt]

Xenu doesn't like it either, only indexes the one page.

Ran a w3c validation check and it threw up the fact there is no character encoding specified, which may well be the whole of the problem.

http://validator.w3.org/check?uri=http%3A%2F%2Fwww.brammer.co.uk%2F&charset=%28detect+automatically%29&doctype=Inline&ss=1&group=0&No200=1&verbose=1&user-agent=W3C_Validator%2F1.2

If you look at the source code that w3c displays you can see it's essentially an empty document.

[lovealbatross]

Any ideas? got a report due on the 19th and the next crawl is due on the 17th. Would be great to remove any blockers before then if poss. thanks!

[lovealbatross]

Definately. Cheers.

[Tompt]

Worth a stab.

Probably worthwhile setting that forwarding up in the meantime anyway.

[lovealbatross]

Thanks Tom, but no, it's setup as www.brammer.co.uk so it's not that.

[Tompt]

Well if you've just put in http://brammer.co.uk it may well be falling over because the domain isn't forwarding to http://www.brammer.co.uk

That's my guess. You just need to forward the domain and it should all be sorted.