Search engines not crawling custom module content

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
2/4/2013 7:09:29 AM
TRIAD-Next Level
Gravatar
Total Posts 49
View Posts
TRIAD/Next Level Interactive

Search engines not crawling custom module content

Hello!

We created a custom module to display staff bios for one of our clients websites. We're now finding that the search engines are not seeing the content that is displayed on those pages that use the custom module.

An example of one of those pages can be found here -- http://cohencpa.com/bio?BioID=63

Any ideas as to why this content isn't "searchable"? Any help is appreciated.

Thanks!

2/4/2013 7:24:47 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Search engines not crawling custom module content

1. you have not implemented your feature according to recommendations. You should not be passing extra query string params to a cms page, you should have a supporting page and pass pageid, mid, and your extra params. CMS pages have a connonical url that does not include extra params. You can then also optionally implement friendly urls that map to your supporting page with the extra params (likle the blog feature or webstore does).

2. if you implement your feature the correct way then you can also implement a custom site map to submit urls for your feature to google, just as we have for blog, forums, or webstore products.

ie your bio page should have a modulecontrol that lists the staff and the links in the list go to a supporting page that shows the detail

Hope that helps,

Joe

You must sign in to post in the forums. This thread is closed to new posts.