PageServer vs. PageNavigator

Jeremy Reynolds

Anyone know the difference between using:

support3.convio.com/client/site/SPageServer/?pagename=foo
vs.
support3.convio.com/client/site/SPageNavigator/foo

I've been leaning on the latter, since it's cleaner and looks less freaky to search engines, but couldn't help noticing that many others go with the more dynamic-looking addresses. And then I got to thinking that they've got different [[S4]] output, and now I've freaked myself out.


Anyone have insight?

Chris Cain 2

Jeremy Reynolds:
Anyone know the difference between using:

support3.convio.com/client/site/SPageServer/?pagename=foo
vs.
support3.convio.com/client/site/SPageNavigator/foo

I've been leaning on the latter, since it's cleaner and looks less freaky to search engines, but couldn't help noticing that many others go with the more dynamic-looking addresses. And then I got to thinking that they've got different [[S4]] output, and now I've freaked myself out.


Anyone have insight?

Hey Jeremy - PageNavigator and PageServer ultimately serve the same exact content. You're right in that PageNavigator may offer slightly better SEO, particularly since it supports configuring the pages into a folder hierarchy, but a big reason many orgs use the PageServer structure is the ability to easily add additional URL parameters and use it with S334, which evaluates URL parameters.


In your example above you can use a conditional statement to very easily display certain code/content if and only if the "pagename=foo"


There is still a way to conditionalize on the URL itself (S8) but it's a little more straightforward with S334.


-Chris