Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#1 2012-09-22 17:49:39
- dylan-c
- Member
- From: Maine
- Registered: 2012-07-09
- Posts: 13
Optimizing the built in search without hurting SEO
Hi there,
I am building a site for a client, and we’ve found that the built-in search didn’t search image captions. There isn’t much text in the articles themselves, as most of them basically function to contain image galleries. The client would like to pull up at least the relevant gallery. I have found that this is possible by placing relevant keywords in the Excerpt. Here is one (probably one of the longest):
Home furnishing products, including stone bath accessories and products, paperweights, candle and tea light holder, stone candlestick holder, vessels, tacks and pushpins, magnets, soap holder, bookends, coatracks, toothpick holder, decorative items, stone soap dispenser, stone cabinet knobs with hardware.
This is useful in two ways: it makes the search function, and it provides a useful excerpt to the customer so that they can figure out whether they will find what they’re looking for. However I’m concerned that this will be seen as keyword stuffing. Would love opinions on this. I am not trying to stuff for Google— in fact, I don’t care if they crawl these terms or not but can’t find any way to stop it happening. Just want to overcome some limitations with txp’s search.
I would be grateful for any opinions.
Offline
Re: Optimizing the built in search without hurting SEO
Just a two-step untested idea:
- Try an external search tool rather than the native TXP search mechanism.
- Build
tipuesearch_data.js(as see in the tipue page linked to above) on the fly with rah_external_output
At this point you could separate searchable content’s data from the viewable structure of content’s pages, articles, and whatever else.
I’ll explain more if need be.
Last edited by whaleen (2012-10-01 03:38:33)
txtstrap (Textpattern + Twitter Bootstrap + etc…)
Offline
#3 2012-10-01 15:33:41
- dylan-c
- Member
- From: Maine
- Registered: 2012-07-09
- Posts: 13
Re: Optimizing the built in search without hurting SEO
Thank you for responding. I’m not sure I’m skilled enough to implement this. I’m going to keep a note of it regardless in case we do think that our search rank has been impacted; then I may explore implementing it. I was hoping (of course) that there was an easy fix, or something that everyone generally does to prevent this type of issue with the built in search. Alas. Thanks again. I appreciate it.
Offline
Offline
#5 2012-10-04 14:41:24
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,315
Re: Optimizing the built in search without hurting SEO
Oleg, first of all: Thanks for the adoption! :) Looks like you’ve implemented a whole lot of really useful stuff. Bummer that I didn’t yet have an opportunity to implement it, but chances are I’ll try it locally at least, now that I know what it’s capable of.
Is it still the version you posted at the end of the cbs_live_search topic? Even if so, it might be a good idea to bump that thread up a little.
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
Re: Optimizing the built in search without hurting SEO
uli wrote:
Is it still the version you posted at the end of the cbs_live_search topic? Even if so, it might be a good idea to bump that thread up a little.
Hi Uli, both versions are functional, but js are incompatible. I have started to do some cleanup, but need time to understand how it works now :) I would also like to get rid of jQuery dependance and use CSS3 instead. So it might be heavily rewritten in a near future, so I do not officially let it out for the moment, but can send it by email if you want.
Offline