+1 Sent from my iPad
> On 24 Oct 2014, at 23:22, Ramsey Gurley <[email protected]> wrote: > > You could give the client an estimate for the work upfront and let them > convince themselves this last page is worth it :-) > > Frankly, I don’t think rel next & previous were intended for list pages. > They’re more for something like next chapter, next episode, next volume, next > calendar month; Where you have a well defined ordered set of items. They are > easy to add to something like a blog post page, but would not be appropriate > on something like a product page since there’s no natural order there. It > seems especially inappropriate with something really dynamic like a list > page. You can probably hack out a solution for a simple query results page, > but there’s very little meaning the search engine can glean from it. > > That’s just my opinion though. I’m sure those SEO experts staring at the > google black box have solid hearsay and conjecture to back up their claims > about the inner workings of the page rank algorithms ;-) > > >> On Oct 24, 2014, at 2:55 PM, Gino Pacitti <[email protected]> wrote: >> >> Yes I was thinking this might be the case... Problem being a SEO company has >> convinced the client that this is necessary and the lists already exist as >> component urls.... So I was just trying to load the next and previous to >> link tags so that it satisfied the requirement... >> >> I'll have to keep on searching... I have managed to convert the whole site >> to a great SEO structure though for urls in general... It's just this last >> results page!!! >> >> Sent from my iPad >> >>> On 24 Oct 2014, at 19:39, Ramsey Gurley <[email protected]> wrote: >>> >>> Hi Gino, >>> >>> A naive approach might be to try something like >>> >>> <link rel=‘next’ href=‘<webobject name=“Next”/>’ /> >>> >>> Next: WOActionUrl { >>> action = displayGroup.displayNextBatch; >>> } >>> >>> But you will quickly discover that this doesn’t work. The url’s are dynamic >>> and the spider will simply load list pages till the cows come home or it >>> hits some preset limit. The urls won’t work later because, they are >>> dynamic, and the search engine will notice that too. >>> >>> What you need is a way to represent your next/previous pages as a direct >>> action, which can actually be impossible in some instances. >>> >>> Component actions are stateful and uses stateful urls. SEO wants stateless >>> static urls. You might be able to pull off a direct action url for a simple >>> list, but if you want to make a direct action to handle a list with nested >>> lists which themselves have nested lists, as WO will let you easily do with >>> components, you will very quickly run out of room for sort orderings, >>> indexes, qualifiers, and list IDs in your direct action url. URLs are >>> capped at ~2000 chars in some browsers and search engines, so there just >>> isn’t room to represent all that state. >>> >>> Anyway, you can do it, but only in a limited way, and it’s basically going >>> to be a one-off custom solution for your particular situation. >>> >>> Personally, I wouldn’t bother unless absolutely certain it would have a >>> significant and measurable impact on page rank. >>> >>> Ramsey >>> >>>> On Oct 24, 2014, at 10:45 AM, Gino Pacitti <[email protected]> wrote: >>>> >>>> Hi there… >>>> >>>> Could anyone help me understand how to extract the next batch and previous >>>> batch URLs from a WODisplayGroup instance? >>>> >>>> Any help or pointing in the right direction would be greatly appreciated. >>>> >>>> Gino >>>> _______________________________________________ >>>> Do not post admin requests to the list. They will be ignored. >>>> Webobjects-dev mailing list ([email protected]) >>>> Help/Unsubscribe/Update your Subscription: >>>> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com >>>> >>>> This email sent to [email protected] >>> >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list ([email protected]) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/ginokris%40me.com >>> >>> This email sent to [email protected] >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com >> >> This email sent to [email protected] > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
