Or you can use <h:link> with PrettyFaces and use page-actions:
http://ocpsoft.com/docs/prettyfaces/snapshot/en-US/html_single/#config.actions
On Wed, Apr 20, 2011 at 3:14 AM, Jakob Korherr <jakob.korherr_at_gmail.com>wrote:
> IMO you currently have to use h:link components in conjunction with
> f:viewParam components and preRenderView events rather than normal
> h:commandLinks/-Buttons in order to avoid SEO issues.
>
> Regards,
> Jakob
>
> 2011/4/20, Lincoln Baxter, III <lincolnbaxter_at_gmail.com>:
> > URL-rewriting concerns are at a level outside of JSF (they apply to the
> > entire servlet container,) so in that regard, I agree with Ed and do not
> > think it is appropriate to resolve this issue in JSF itself. The
> integration
> > points in JSF provide plenty of power to do this using extensions like
> > PrettyFaces.
> >
> > Regarding the JavaScript "no-page refresh means no SEO link indexes,"
> this
> > would be a problem no matter the technology you choose. If you use
> > JavaScript based links, you'll have SEO issues. However, your idea of
> > placing links in the footer is not a bad one, but search engines do not
> > always read the entire content of a page, so you might also consider
> using
> > something like breadcrumbs in the header (earlier in the content), or an
> > HTML (nonJavaScript) navigation bar or menu.
> >
> > ~Lincoln
> >
> > On Tue, Apr 19, 2011 at 12:39 PM, Ed Burns <edward.burns_at_oracle.com>
> wrote:
> >
> >> Moving to users_at_javaserverfaces-spec-public.
> >>
> >> >>>>> On Tue, 19 Apr 2011 16:09:45 +0000 (GMT),
> >> >>>>> <ken.keller_at_kellerapps.com>
> >> said:
> >>
> >> KK> I didn't notice it while reading 7 pages of issues but sorry if I
> >> KK> missed it. I don't see it listed on the JSR proposal:
> >> KK> http://jcp.org/en/jsr/proposalDetails?id=344
> >>
> >> KK> Is the stance that prettyfaces is sufficient?
> >>
> >> That is my stance, yes. In any case, with the quality of PrettyFaces
> >> being what it is, putting this into the spec is not high priority right
> >> now.
> >>
> >> KK> Related to this is search engine indexing. The component libraries
> use
> >> KK> so much JS that search engines can't index "modern" JSF pages.
> What's
> >> KK> the recommended way to address this? Text links in the footer which
> >> KK> lead to indexable pages?
> >>
> >> I don't know what the best practice is here. Anyone else care to
> >> comment?
> >>
> >> Ed
> >>
> >> --
> >> | edward.burns_at_oracle.com | office: +1 407 458 0017
> >> | homepage: | http://ridingthecrest.com/
> >> | 7 Business Days til JSF 2.2 planning complete
> >> | 44 Business Days til JSF 2.2 Early Draft Review
> >> | 80 Business Days til JSF 2.2 Public Review
> >> | 168 Business Days til JSF 2.2 Proposed Final Draft
> >>
> >
> >
> >
> > --
> > Lincoln Baxter, III
> > http://ocpsoft.com
> > http://scrumshark.com
> > "Keep it Simple"
> >
>
>
> --
> Jakob Korherr
>
> blog: http://www.jakobk.com
> twitter: http://twitter.com/jakobkorherr
> work: http://www.irian.at
>
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"